[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Texi2html-cvs] texi2html TODO

From: Patrice Dumas
Subject: [Texi2html-cvs] texi2html TODO
Date: Sun, 07 Feb 2010 18:03:18 +0000

CVSROOT:        /cvsroot/texi2html
Module name:    texi2html
Changes by:     Patrice Dumas <pertusus>        10/02/07 18:03:18

Modified files:
        .              : TODO 

Log message:
        Character width stuff is implemented.


Index: TODO
RCS file: /cvsroot/texi2html/texi2html/TODO,v
retrieving revision 1.166
retrieving revision 1.167
diff -u -b -r1.166 -r1.167
--- TODO        11 Jan 2010 00:08:58 -0000      1.166
+++ TODO        7 Feb 2010 18:03:18 -0000       1.167
@@ -3,48 +3,11 @@
 Before next release
-Currently length is used everywhere, so the number of characters is counted.
-This is however not right in some cases. In many cases, indeed, what matters
-is the text width, or the bytes number.
-For the text width one can use
-It also compute end of lines and stuffs!
-There are some places where the number of characters or bytes are counted. 
-At some places it is important to determine how the output looks like, 
-and at some other points it is even more important since it determines 
-the document structure. For the second case, I need to know how info 
-counts since both ways of counting must match.
-Here is a list of places where the width of characters may matter, that 
-impacts only on the output formatting:
-    * Underlying of titles, as described in http://savannah.gnu.org/bugs/?28359
-    * formatting of listoffloats and menus (41 byte-width characters). 
-      My guess here is that info reader doesn't care about the precise 
-      length, what it detects is the format.
-    * formatting of @printindex index entries.
-    * indentation length is more than the current position on 
-      the line (for indented formats, like @itemize, @enumerate).
-    * lines splitting in paragraph
-    * formatting of @center and @flush*
-    * formatting of @multitable
-Here is the place where info readers and formatters must agree:
-    * offset of anchors and nodes
+* line breaking could happen after a full width character.
 * images.texi, paragraph_in_samp.texi should be tested in xml too.
   Maybe they should be moved to coverage, and in coverage all the formats
   should be tested like in sectionning. 
@@ -463,6 +426,9 @@
 Misc info and boring stuff
+* use Unicode::LineBreak if detected for line breaking and character 
+  width computation.
 * texi2html is immune to https://savannah.gnu.org/bugs/?25822
 * the following is erroneous, but maybe it could be better handled anyway

reply via email to

[Prev in Thread] Current Thread [Next in Thread]