[Top][All Lists]

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

trans-coord/gnun/server/gnun TODO

From: Yavor Doganov
Subject: trans-coord/gnun/server/gnun TODO
Date: Fri, 26 Sep 2008 10:36:27 +0000

CVSROOT:        /sources/trans-coord
Module name:    trans-coord
Changes by:     Yavor Doganov <yavor>   08/09/26 10:36:27

Modified files:
        gnun/server/gnun: TODO 

Log message:
        (Present bugs): New item about the grep regexp in the
        gnusflashes.%include recipe.
        (Non-essential): New idea about mail notifications for new articles
        and translations.


Index: TODO
RCS file: /sources/trans-coord/trans-coord/gnun/server/gnun/TODO,v
retrieving revision 1.22
retrieving revision 1.23
diff -u -b -r1.22 -r1.23
--- TODO        4 Sep 2008 20:20:55 -0000       1.22
+++ TODO        26 Sep 2008 10:36:27 -0000      1.23
@@ -8,6 +8,13 @@
    order only news which are marked with an asterisk (*) in
    whatsnew.txt propagate in the generated file(s).
+** The regexp in the gnusflashes.%.include rule
+   for grep is not ideal -- it doesn't include the SGI item, because
+   for some reason it appears on three lines:
+   <dd>
+       <a href="http:/
+   </dd>
 ** 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
@@ -113,6 +120,15 @@
    plus probably other useful things that would save purely mechanical
+** Implement notifications for new articles and translations.
+   When the .pot of a new article is 'cvs add'-ed, or a fresh
+   .LANG.html, it would be nice to generate messages for
+   trans-coord-news.  They can include a Keywords: header, so it would
+   be possible to use Mailman's topic feature to subscribe for
+   specific notifications.  This could be widely advertised if it
+   works well.  Currently, it is not feasible for articles until most
+   of the present become listed at
 ** Implement `pedantic' validation.
    This could possibly check if all header fields (comments included)
    are filled in properly, and should probably be developed hand in

reply via email to

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