trans-coord-devel
[Top][All Lists]
Advanced

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

trans-coord/gnun/prep/gnun ChangeLog gnun.texi


From: Yavor Doganov
Subject: trans-coord/gnun/prep/gnun ChangeLog gnun.texi
Date: Sun, 10 Feb 2008 11:49:56 +0000

CVSROOT:        /cvsroot/trans-coord
Module name:    trans-coord
Changes by:     Yavor Doganov <yavor>   08/02/10 11:49:56

Modified files:
        gnun/prep/gnun : ChangeLog gnun.texi 

Log message:
        (Advantages): Mention that no extra work is required to migrate
        from the old style to new style.

CVSWeb URLs:
http://cvs.savannah.gnu.org/viewcvs/trans-coord/gnun/prep/gnun/ChangeLog?cvsroot=trans-coord&r1=1.41&r2=1.42
http://cvs.savannah.gnu.org/viewcvs/trans-coord/gnun/prep/gnun/gnun.texi?cvsroot=trans-coord&r1=1.5&r2=1.6

Patches:
Index: ChangeLog
===================================================================
RCS file: /cvsroot/trans-coord/trans-coord/gnun/prep/gnun/ChangeLog,v
retrieving revision 1.41
retrieving revision 1.42
diff -u -b -r1.41 -r1.42
--- ChangeLog   10 Feb 2008 11:06:13 -0000      1.41
+++ ChangeLog   10 Feb 2008 11:49:55 -0000      1.42
@@ -2,10 +2,12 @@
 
        * gnun.texi (New Translation, Migrating): Use @group in the PO
        header examples.
+       (Advantages): Mention that no extra work is required to migrate
+       from the old style to new style.
 
 2008-02-09  Yavor Doganov  <address@hidden>
 
-       * gnun.texi: New file; basic skeleton of the documentaiton.
+       * gnun.texi: New file; basic skeleton of the documentation.
        * fdl.texi: Import from the canonical location.
        
 2008-02-08  Yavor Doganov  <address@hidden>

Index: gnun.texi
===================================================================
RCS file: /cvsroot/trans-coord/trans-coord/gnun/prep/gnun/gnun.texi,v
retrieving revision 1.5
retrieving revision 1.6
diff -u -b -r1.5 -r1.6
--- gnun.texi   10 Feb 2008 11:06:14 -0000      1.5
+++ gnun.texi   10 Feb 2008 11:49:55 -0000      1.6
@@ -212,7 +212,10 @@
 @item
 Markup consistency site-wide---it would be substantially easier to
 update the site to a future standard, because translations will
-naturally follow the changes in the original articles.
+naturally follow the changes in the original articles.  This also
+means that translation teams do not have to undergo the boring process
+of converting their articles to the new SSI-based layout; this will be
+done automatically.
 
 @item
 Easy updates by translators.  Modified paragraphs, links, etc. will




reply via email to

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