texinfo/tp TODO

[Patrice Dumas]

CVSROOT:        /sources/texinfo
Module name:    texinfo
Changes by:     Patrice Dumas <pertusus>        12/11/11 20:12:23

Modified files:
        tp             : TODO 

Log message:
        Add narrowed right margin of @quotation in Plaintext.

CVSWeb URLs:
http://cvs.savannah.gnu.org/viewcvs/texinfo/tp/TODO?cvsroot=texinfo&r1=1.306&r2=1.307

Patches:
Index: TODO
===================================================================
RCS file: /sources/texinfo/texinfo/tp/TODO,v
retrieving revision 1.306
retrieving revision 1.307
diff -u -b -r1.306 -r1.307
--- TODO        25 Sep 2012 17:46:35 -0000      1.306
+++ TODO        11 Nov 2012 20:12:23 -0000      1.307
@@ -21,6 +21,8 @@
 Delayed bugs
 ============
 
+In Plaintext, @quotation text should have the right margin narrowed.
+
 Text after @bye should be kept as is when redoing Texinfo.
 
 @-commands in index entries are transliterated when sorting, they should
@@ -59,15 +61,6 @@
 Not sure what should be the right way?
 test in info_test/image_and_punctuation
 
-Instead of _set_global_multiple_commands and _unset_global_multiple_commands
-have a better granularity and do something per command, with the possibility
-to really revert everything, including things that are not set by set_conf.
-(There is a FIXME in the code).  This is not that important, now that the 
-actual case that was problematic (setting encodings as a side effect of 
-setting @documentencoding) is not supported anymore.  (Now the encoding is
-set at the initialization of the converter and should be changed by setting
-the correct customization variable, in general OUTPUT_ENCODING_NAME).
-
 There should be a warning for something like
 @example text
 ...
@@ -198,6 +191,15 @@
 Interrogations and remarks
 ==========================
 
+Instead of _set_global_multiple_commands and _unset_global_multiple_commands
+have a better granularity and do something per command, with the possibility
+to really revert everything, including things that are not set by set_conf.
+(There is a FIXME in the code).  This is not that important, now that the 
+actual case that was problematic (setting encodings as a side effect of 
+setting @documentencoding) is not supported anymore.  (Now the encoding is
+set at the initialization of the converter and should be changed by setting
+the correct customization variable, in general OUTPUT_ENCODING_NAME).
+
 Should more Converter ignore the last new line (with type 
 last_raw_newline) of a raw block format?