trans-coord/gnun/prep/gnun TODO

[Yavor Doganov]

CVSROOT:        /sources/trans-coord
Module name:    trans-coord
Changes by:     Yavor Doganov <yavor>   08/01/22 16:10:13

Modified files:
        gnun/prep/gnun : TODO 

Log message:
        Convert to Outline.

CVSWeb URLs:
http://cvs.savannah.gnu.org/viewcvs/trans-coord/gnun/prep/gnun/TODO?cvsroot=trans-coord&r1=1.1.1.1&r2=1.2

Patches:
Index: TODO
===================================================================
RCS file: /sources/trans-coord/trans-coord/gnun/prep/gnun/TODO,v
retrieving revision 1.1.1.1
retrieving revision 1.2
diff -u -b -r1.1.1.1 -r1.2
--- TODO        13 Jan 2008 11:05:39 -0000      1.1.1.1
+++ TODO        22 Jan 2008 16:10:13 -0000      1.2
@@ -1,25 +1,25 @@
-Present bugs
-------------
+GNUnited Nations TODO List                             -*-outline-*-
 
-* home.shtml: Make checks whether the HTML is decently generated.
+* Present bugs
 
-* Po4a wraps the <script> of the FSF widget at /server/banner.html,
+** home.shtml: Make checks whether the HTML is decently generated.
+
+** Po4a wraps the <script> of the FSF widget at /server/banner.html,
   which makes it disfunctional.  It seems that the problem is the
   C++-style comment `// already a member...'.  The solution would be
   either to 1) Include a comment for translators that will appear in
   PO message not to include it; 2) Delete it somehow automatically; 3)
   Persuade Matt not do to such things.
 
-* Put a warning like <!-- Automatically generated... --> at the
+** Put a warning like <!-- Automatically generated... --> at the
   begining of each .xx.html file.
 
-General (when bugs are fixed)
------------------------------
+* General (when bugs are fixed)
 
-* Experiment with msgmerge's `--previous' option and make it the
+** Experiment with msgmerge's `--previous' option and make it the
   default, if feasible.  Requires gettext >= 0.16.
 
-* Add commands to the necessary targets that will cvs add the
+** Add commands to the necessary targets that will cvs add the
   generated POT and the translated HTML, where appropriate.
 
   More specifically, the system should cvs add these files if they are
@@ -29,37 +29,35 @@
     /foo/article.pot (when web-translators managers add a new article)
     /foo/article.xx.html (when a translator commits article.xx.po).
 
-* Write a script that will itself invoke $(MAKE), log all output in a
+** 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.
 
-* Standardize all variables'/rules' names to match GCS.
+** Standardize all variables'/rules' names to match GCS.
 
-* Add a `check' target (probably using Autoconf or DejaGNU) that would
+** Add a `check' target (probably using Autoconf or DejaGNU) that would
   test the environment and all the tools we use.
 
-Expected problems
------------------
+* Expected problems
 
-* make-prototype.scm uses a regexp to split the articles in pieces.
+** make-prototype.scm uses a regexp to split the articles in pieces.
   That regexp might not fit to all articles, that's why it has to be
   tested with as many as possible.
 
-* RTL.
+** RTL.
 
-* Complicated articles like /philosophy/eldred-amicus.
+** Complicated articles like /philosophy/eldred-amicus.
 
-Non-essential
--------------
+* Non-essential
 
-* Implement a `report' target that would be language specific and will
+** Implement a `report' target that would be language specific and will
   output the state of all files for a language team, and extended
   `full-report' that will check the activity of all teams for a
   certain period.  For language teams, a `msgfmt --statistics'-similar
   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
+** 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.
@@ -68,7 +66,7 @@
   This could be useful for some articles under /licenses and for
   several other occasions.
 
-* When commiting automated changes, find a way to generate meaningful
+** When commiting automated changes, find a way to generate meaningful
   CVS log entries, describing the changes.  Something like:
 
   ,----
@@ -89,24 +87,25 @@
   case of failure, it will not be deleted so that the accumulated
   messages will be used in the next run.
 
-* Figure out how to "inject" a language-specific warning, possibly
+** Figure out how to "inject" a language-specific warning, possibly
   from /prep/i18n/outdated.xx.html that will be displayed when the
-  page has 20% (or more) messages untranslated.  We have to think also
-  about a deprecation plan for all gnu.org translated pages, and
-  whether this software can help sorting all issues out.  Idea: We can
-  use the comment <!-- Automatically generated... --> to add a fake
-  #include directive, which will tell Apache that this page is OK, but
-  in its absence will direct to a separate page (like 404) with a
-  a notice that the translation is very outdated and links/options
-  like 1) Visit the English article; 2) Visit the translation anyway;
-  3) Help the Foo translation team; 4) Whatever we decide.
-
-* Check if the diff of a POT-file is only about POT-Creation-Date (by
-  copying the file to a temporary file, running the command, etc.) and
-  consider the target up-to-date if that's the case.  There might be
-  an easier way, though.
+   page has 20% (or more) messages untranslated.  We have to think
+   also about a deprecation plan for all gnu.org translated pages, and
+   whether this software can help sorting all issues out.  Idea: We
+   can use the comment <!-- Automatically generated... --> to add a
+   fake #include directive, which will tell Apache that this page is
+   OK, but in its absence will direct to a separate page (like 404)
+   with a a notice that the translation is very outdated and
+   links/options like 1) Visit the English article; 2) Visit the
+   translation anyway; 3) Help the Foo translation team; 4) Whatever
+   we decide.
+
+** Check if the diff of a POT-file is only about POT-Creation-Date (by
+   copying the file to a temporary file, running the command, etc.)
+   and consider the target up-to-date if that's the case.  There might
+   be an easier way, though.
 
- * Somewhat ugly processing of comments, which leads to integration of
+** Somewhat ugly processing of comments, which leads to integration of
    adjacent comments and large areas of continious whitespace as a
    side effect.