trans-coord/gnun/server/gnun TODO

[Yavor Doganov]

CVSROOT:        /cvsroot/trans-coord
Module name:    trans-coord
Changes by:     Yavor Doganov <yavor>   08/08/29 20:05:16

Modified files:
        gnun/server/gnun: TODO 

Log message:
        (Present bugs): Add to items -- committed empty HTML translations and
        autoconfiscation.
        (Non-essential): Add item about BOM stripping.

CVSWeb URLs:
http://cvs.savannah.gnu.org/viewcvs/trans-coord/gnun/server/gnun/TODO?cvsroot=trans-coord&r1=1.20&r2=1.21

Patches:
Index: TODO
===================================================================
RCS file: /cvsroot/trans-coord/trans-coord/gnun/server/gnun/TODO,v
retrieving revision 1.20
retrieving revision 1.21
diff -u -b -r1.20 -r1.21
--- TODO        21 Aug 2008 21:00:41 -0000      1.20
+++ TODO        29 Aug 2008 20:05:14 -0000      1.21
@@ -8,6 +8,19 @@
    order only news which are marked with an asterisk (*) in
    whatsnew.txt propagate in the generated file(s).
 
+** Sometimes empty article.LANG.html is committed.
+   When a team commits a .po file, and it is invalid, an empty file is
+   added as .LANG.html.  Furthermore, when a team commits a legitimate
+   valid fully translated article.LANG.po (like why-gnu-linux.sr.po)
+   but it doesn't get built immediately (because of previous errors)
+   or because the original article.html changes after the translator's
+   commit and before the build, again an empty file is `cvs add'-ed
+   and committed, because GRACE is in effect.
+   This may not classify as a bug, but it would be nice to make it
+   more robust.
+
+** Autoconfiscate and prepare for release.
+
 * General (when bugs are fixed)
 
 ** The documentation is not complete, and should be improved.
@@ -112,3 +125,12 @@
    should not print a version number (instead probably a date it was
    last modified, or nothing).  Also, since GNUN is not make-distable,
    we don't have a COPYING file.
+
+** BOM stripping.
+   Apparently some translators use poor editors (or more likely, poor
+   editors in conjunction with Windows) so a BOM is sneakily added.
+   This renders the PO file invalid, and all .LANG.html invalid if
+   header.LANG.html contains a BOM (since po4a 0.34 adds an empty new
+   line at the beginning of the file).
+   Would be nice to handle this unpleasant case automatically rather
+   than fixing the faulty files manually.