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

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

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


From: Yavor Doganov
Subject: trans-coord/gnun/server/gnun ChangeLog gnun.texi
Date: Tue, 04 Mar 2008 18:49:14 +0000

CVSROOT:        /cvsroot/trans-coord
Module name:    trans-coord
Changes by:     Yavor Doganov <yavor>   08/03/04 18:49:14

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

Log message:
        (New Translation): Explain all PO header fields.
        (Concepts): Delete whitespace before @footnote.

CVSWeb URLs:
http://cvs.savannah.gnu.org/viewcvs/trans-coord/gnun/server/gnun/ChangeLog?cvsroot=trans-coord&r1=1.15&r2=1.16
http://cvs.savannah.gnu.org/viewcvs/trans-coord/gnun/server/gnun/gnun.texi?cvsroot=trans-coord&r1=1.7&r2=1.8

Patches:
Index: ChangeLog
===================================================================
RCS file: /cvsroot/trans-coord/trans-coord/gnun/server/gnun/ChangeLog,v
retrieving revision 1.15
retrieving revision 1.16
diff -u -b -r1.15 -r1.16
--- ChangeLog   4 Mar 2008 18:15:35 -0000       1.15
+++ ChangeLog   4 Mar 2008 18:49:13 -0000       1.16
@@ -1,3 +1,8 @@
+2008-03-04  Yavor Doganov  <address@hidden>
+
+       * gnun.texi (New Translation): Explain all PO header fields.
+       (Concepts): Delete whitespace before @footnote.
+
 2008-03-04  Ali Servet Dönmez  <address@hidden>
 
        * gnun.mk (TEMPLATE_LINGUAS): Add `tr'.

Index: gnun.texi
===================================================================
RCS file: /cvsroot/trans-coord/trans-coord/gnun/server/gnun/gnun.texi,v
retrieving revision 1.7
retrieving revision 1.8
diff -u -b -r1.7 -r1.8
--- gnun.texi   29 Feb 2008 20:37:34 -0000      1.7
+++ gnun.texi   4 Mar 2008 18:49:13 -0000       1.8
@@ -4,7 +4,7 @@
 @settitle GNUnited Nations Manual
 @c FIXME: Would be nice to have it in the format `%:b %:d, %:y', but
 @c in English.
address@hidden lastupdate 29.02.2008
address@hidden lastupdate 04.03.2008
 @afourpaper
 @c %**end of header
 
@@ -136,19 +136,19 @@
 @section What @acronym{GNU}nited Nations is and Should be
 
 The basic concept behind @acronym{GNUN} is that localization of HTML
-articles is similar to localization of computer programs
address@hidden, it is much more closer to localization of software
-documentation, where typically strings (also known as ``messages'' in
-gettext's context) are longer than strings in programs.  Nevertheless,
-all points raised still apply.}.  In articles, like in programs, not
-every string is considered translatable, so translatable strings must
-be identified first, and then collected in a file (called ``PO
-template'') for translation.  Articles, like programs, tend to change
-in time, but not every change in the sources calls for a translation
-update.  Sometimes the change does not affect the translatable
-strings, but sometimes it does.  So, translators must have means to
-identify those changes and apply the appropriate updates to the
-translation.
+articles is similar to localization of computer
address@hidden, it is much more closer to localization of
+software documentation, where typically strings (also known as
+``messages'' in gettext's context) are longer than strings in
+programs.  Nevertheless, all points raised still apply.}.  In
+articles, like in programs, not every string is considered
+translatable, so translatable strings must be identified first, and
+then collected in a file (called ``PO template'') for translation.
+Articles, like programs, tend to change in time, but not every change
+in the sources calls for a translation update.  Sometimes the change
+does not affect the translatable strings, but sometimes it does.  So,
+translators must have means to identify those changes and apply the
+appropriate updates to the translation.
 
 The @acronym{GNU} @code{gettext} package already provides the needed
 infrastructure for maintaining translations using PO files.
@@ -731,8 +731,54 @@
 @end example
 
 You have to edit the header to match the already established
-conventions, and the rules for gnu.org translations.  Here is an
-example of a properly edited header:
+conventions, and the rules for gnu.org translations.  For reference,
+here is a list with all fields explained:
+
address@hidden @samp
address@hidden Project-Id-Version
+Add here the filename of the original article, without the
+sub-directory, like ``banner.html'' or ``free-sw.html''.
+
address@hidden POT-Creation-Datenn
+Do not edit this field, it is already set when the POT is created.
+
address@hidden PO-Revision-Date
+Likewise, do not edit.  This field is automatically filled in when you
+save the file with any decent PO editor.
+
address@hidden Last-Translator
+The name and email address of the last translator who have edited the
+translation.  Pay attention that normally this is the name of a member
+of your team, it can be the translation team leader if he/she was the
+person who updated the translation.  For example:
+
address@hidden
+Elvis Parsley <king@@grassland.com>
address@hidden example
+
address@hidden Language-Team
+This field should contain the mailing list on which the translation
+team can be reached---sometimes this is the alias
address@hidden@@gnu.org}, but in some cases it is a
+separate, address@hidden list.  It could be a URL of the team's
+homepage, provided that it contains contact details.  Example:
+
address@hidden
+French <trad-gnu@@april.org>
address@hidden example
+
address@hidden MIME-Version
+Leave it like it is.
+
address@hidden Content-Type
+Usually this is @code{text/plain; charset=UTF-8}; change the charset
+accordingly.
+
address@hidden Content-Transfer-Encoding
+Set this to @code{8bit}.
address@hidden table
+
+Here is an example of a properly edited header:
 
 @example
 @group
@@ -756,14 +802,7 @@
 
 Notice the absence of the ``fuzzy'' marker; you should ``unfuzzy'' the
 header after entering the necessary information (this is done by
-simply pressing @key{TAB} in PO mode).  The @code{PO-Revision-Date}
-is automatically filled in when you save the file in PO mode and in
-most of the other PO editors.
-
-The @code{Lanuage-Team} field should contain the mailing list on which
-the translation team can be reached---sometimes this is the alias
address@hidden@@gnu.org}, but in some cases it is a
-separate, address@hidden list.
+simply pressing @key{TAB} in PO mode).
 
 There are some special messages that appear in the POT and PO:
 
@@ -778,6 +817,7 @@
 This is again optional, and should contain the name (and address) of
 the person who made the translation.  ``Translate'' this string as a
 space (@key{SPC}) if you do not want your name to appear there.
address@hidden Slot}.
 @end table
 
 Most of the PO editors do not wrap long lines that inevitably appear




reply via email to

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