trans-coord/gnun/server/gnun TODO

[Yavor Doganov]

CVSROOT:        /cvsroot/trans-coord
Module name:    trans-coord
Changes by:     Yavor Doganov <yavor>   08/03/04 21:52:23

Modified files:
        gnun/server/gnun: TODO 

Log message:
        (Non-essential): Delete the item about the propagation of HTML
        comments as PO comments; already present by design.
        New item about a `pedantic' validation mode.
        (General): Mark the item about the script as `maybe' not necessary
        anymore, without actually deleting it.
        Promote GCS compliance sub-items...
        (Present bugs): ...here, since they should be fixed before the code
        review by the webmasters gang.

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

Patches:
Index: TODO
===================================================================
RCS file: /cvsroot/trans-coord/trans-coord/gnun/server/gnun/TODO,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -b -r1.4 -r1.5
--- TODO        2 Mar 2008 23:26:02 -0000       1.4
+++ TODO        4 Mar 2008 21:52:22 -0000       1.5
@@ -17,6 +17,12 @@
    see if formatting it properly in `msgstr' gives good results.
    See gnu/po/initial-announcement.pot.
 
+** GNU Coding Standards compliance.
+
+*** Standardize all variables'/rules' names.
+
+*** Wrap long lines where possible.
+
 * General (when bugs are fixed)
 
 ** The documentation is not complete, and should be improved.
@@ -24,19 +30,14 @@
 ** Experiment with msgmerge's `--previous' option and make it the
    default, if feasible.  Requires gettext >= 0.16.
    This option will be useless, especially with long paragraphs.
-   We could possibly involve wdiff so that the `previoud' msgid is a
+   We could possibly involve wdiff so that the `previous' msgid is a
    wdiff between the previous and the current.  That way, translators
    won't lose much time identifying the changes.
 
 ** Write a script that will itself invoke $(MAKE), log all output in a
    file and cvs commit everything ought to be committed.  Deal with SSH
    woes in order the whole operation to be performed automatically.
-
-** GNU Coding Standards compliance.
-
-*** Standardize all variables'/rules' names.
-
-*** Wrap long lines where possible.
+   NOTE: Isn't this already implemented in a different way?
 
 ** Add a `check' target (probably using Autoconf or DejaGNU) that would
    test the environment and all the tools we use.
@@ -66,15 +67,6 @@
    output would be sufficient, as a start (probably omiting files that
    are 100% complete).  (This could be done with a script too.)
 
-** It would be nice to add some preprocessing logic to include specific
-   HTML comments into the POT, like:
-
-   <!-- TRANSLATORS: Do not translate foo as bar, because mumbo jumbo.
-   Read keleme.html for more info. -->
-
-   This could be useful for some articles under /licenses and for
-   several other occasions.
-
 ** When commiting automated changes, find a way to generate meaningful
    CVS log entries, describing the changes.  Something like:
 
@@ -118,3 +110,11 @@
    standard PO header as generated by Po4a to the recommended format,
    plus probably other useful things that would save purely mechanical
    work.
+
+** Implement `pedantic' validation.
+   This could possibly check if all header fields (comments included)
+   are filled in properly, and should probably be developed hand in
+   hand with the `fsf-report' target.  This kind of validation could
+   check for a valid Last-Translator field and would send mails as
+   reminders both to the team address and the last translator, without
+   failing the build.