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: Sun, 16 Mar 2008 08:36:11 +0000

CVSROOT:        /cvsroot/trans-coord
Module name:    trans-coord
Changes by:     Yavor Doganov <yavor>   08/03/16 08:36:11

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

Log message:
        (PO Tips, Bugs): New nodes.
        (Webmaster Tips): Add a warning about potential breakage.
        (Concepts): Add a xref and ignore two paragraphs, for now.
        (mailfail, validate-html-notify): Typo fix.

CVSWeb URLs:
http://cvs.savannah.gnu.org/viewcvs/trans-coord/gnun/server/gnun/ChangeLog?cvsroot=trans-coord&r1=1.48&r2=1.49
http://cvs.savannah.gnu.org/viewcvs/trans-coord/gnun/server/gnun/gnun.texi?cvsroot=trans-coord&r1=1.21&r2=1.22

Patches:
Index: ChangeLog
===================================================================
RCS file: /cvsroot/trans-coord/trans-coord/gnun/server/gnun/ChangeLog,v
retrieving revision 1.48
retrieving revision 1.49
diff -u -b -r1.48 -r1.49
--- ChangeLog   15 Mar 2008 23:12:17 -0000      1.48
+++ ChangeLog   16 Mar 2008 08:36:11 -0000      1.49
@@ -1,5 +1,10 @@
 2008-03-16  Yavor Doganov  <address@hidden>
 
+       * gnun.texi (PO Tips, Bugs): New nodes.
+       (Webmaster Tips): Add a warning about potential breakage.
+       (Concepts): Add a xref and ignore two paragraphs, for now.
+       (mailfail, validate-html-notify): Typo fix.
+
        * GNUmakefile (MSGMERGE, MSGFMT, PO4A-GETTEXTIZE)
        (PO4A-TRANSLATE, SED, M4, PO4A-GETTEXTIZEFLAGS)
        (PO4A-TRANSLATEFLAGS, PO4A_XHTMLFLAGS): Define as simply expanded

Index: gnun.texi
===================================================================
RCS file: /cvsroot/trans-coord/trans-coord/gnun/server/gnun/gnun.texi,v
retrieving revision 1.21
retrieving revision 1.22
diff -u -b -r1.21 -r1.22
--- gnun.texi   15 Mar 2008 14:56:32 -0000      1.21
+++ gnun.texi   16 Mar 2008 08:36:11 -0000      1.22
@@ -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 15.03.2008
address@hidden lastupdate 16.03.2008
 @afourpaper
 @c %**end of header
 
@@ -59,6 +59,7 @@
 * Introduction::        Overview of GNUnited Nations.
 * Usage::               Basic usage, invocation and tips.
 * Internals::           Dive into @acronym{GNUN}.
+* Bugs::                How to report bugs.
 * Index::
 * Copying This Manual:: The GNU Free Documentation License.
 @end menu
@@ -204,18 +205,21 @@
 The first time though, there is no @address@hidden@var{lang}.po}
 yet, so a translator must manually copy @address@hidden to
 @address@hidden@var{lang}.po}, where @var{lang} represents the
-target language.  See FIXME:``Introducing new translation language for
-an article'' for details.
+target language.  See @xref{New Translation}, for details.
 
 Then comes the initial translation of messages in
 @address@hidden@var{lang}.po}.  Translation in itself is a whole
 matter, whose complexity far overwhelms the level of this manual.
 Nevertheless, a few hints are given in some other chapter of this
-manual (FIXME:Translators (but only if we would like to include some
+manual.
+
address@hidden
+(FIXME:Translators (but only if we would like to include some
 practical advices to candidate translators on how to join a gnu.org
 translating team)).  You will also find there indications about how to
 contact translating teams, or becoming part of them, for sharing your
 translating concerns with others who target the same native language.
address@hidden ignore
 
 You may use any compatible PO editor to add translated messages into
 the PO file.  @xref{Editing, , Editing, gettext, GNU gettext tools},
@@ -247,9 +251,9 @@
 will be needed.  @address@hidden@var{lang}.html} will be
 automatically regenerated to reflect the changes.
 
-FIXME: The following paragraphs should go to a separate section that
-explains those details like exact paths in www, diagram with the basic
-directory layout, additional files like .translinks, etc.
address@hidden FIXME: The following paragraphs should go to a separate section
address@hidden that explains those details like exact paths in www, diagram with
address@hidden the basic directory layout, additional files like .translinks, 
etc.
 
 The POT for every article under @acronym{GNUN}'s control is kept in
 the `www' repository under a special directory @file{po/}, which is a
@@ -712,6 +716,7 @@
 * New Translation::     How to start a new translation.
 * Migrating::           How to migrate an existing translation to a PO
                           format under @acronym{GNUN}'s control.
+* PO Tips::             Tips and hints for translators.
 * generic.LANG.html::   Specifying information that will propagate in
                           every translation in a certain language.
 * PO Files and Team::   How to maintain translations in the team's
@@ -1032,6 +1037,62 @@
 translation, address@hidden made some changes in 2007, and the original
 translator returned in 2008 and continued maintaining it.
 
address@hidden PO Tips
address@hidden Useful Hints For Editing PO Files
+
+This section contains additional explanations, some in the form of
+advices and recommendations; not all of them are strictly related to
+PO files editing.
+
address@hidden
address@hidden
+Dealing with obsolete strings.  Elements which are removed from the
+original articles appear in the PO files as ``obsolete'' strings---the
+translation is not lost, but they are marked in a special way at the
+end of the PO file.  You don't have to update a PO file if it contains
+obsolete strings---do this only if it has ``fuzzy'' or
+``untranslated'', and of course when you want to improve the existing
+translated ones.  Sometimes these obsolete strings are useful, and
+they can save time.  For example, if you anticipate that the deleted
+text may reappear some time in the future, you can preserve the string
+and hopefully it would be marked as ``fuzzy'' when this happens.
+Failing that, you can still copy it and yank it at the appropriate
+place.
+
address@hidden
+You can add comments to every message in a PO file---for example if
+you want to remember that you have to do something, or to remind you
+why this particular message is translated in a special way.  These
+comments to not appear in the generated HTML source.
+
address@hidden
+Sometimes, especially when the original message contains many links,
+it is easier to copy it to @code{msgstr} and edit the latter by
+translating the English text.  In PO mode, this is done by @kbd{C-j}.
+This is useful also for large chunks of text in @code{<pre>} elements,
+which normally you would want to preserve verbatim.
+
address@hidden
+To reduce the load on the webmasters RT queue, please replace
address@hidden@@gnu.org} in the standard footer with
address@hidden@@gnu.org}.
+
address@hidden
+If you translate ``Free Software Foundation, Inc.'' in your native
+language in the copyright notice, then please prepend the English name
+to the @code{<address>}; otherwise it looks awkward in most
+languages.  Example:
+
address@hidden
+# type: Content of: <div><address>
+#: ../../gnu/po/gnu.proto:85
+msgid "51 Franklin St, Fifth Floor, Boston, MA 02110-1301, USA"
+msgstr ""
+"Free Software Foundation, Inc., 51 Franklin St, Fifth Floor, "
+"Boston, MA 02110-1301, USA"
address@hidden example
address@hidden itemize
+
 @node generic.LANG.html
 @subsection The @address@hidden file
 
@@ -1277,7 +1338,7 @@
 The script @command{validate-html} is useful for webmasters who want to
 verify if their (potentially intrusive) changes result in a valid
 markup.  It is recommended to make a symlink somewhere in your
address@hidden (like @file{~/bin})---that way you will automaically use the
address@hidden (like @file{~/bin})---that way you will automatically use the
 latest version, provided that you regularly update your working copy.
 Before committing your changes, you can check if it is valid by running
 
@@ -1312,7 +1373,16 @@
 As per the established convention, start the comment with
 @code{TRANSLATORS:} to catch their attention, and do not add a space
 after the beginning of the HTML comment (@code{<!--}), since this will
-unecessarily indent the comment in the POT.
+unnecessarily indent the comment in the POT.
+
address@hidden:} Any structural diversion from
address@hidden in a specific article is likely to result in
+errors from @acronym{GNUN}.  Any unexpected updates to the server
+templates (such as changing the entire look & feel of the site) will
+most probably break @emph{all} translations under @acronym{GNUN}'s
+control.  Of course, this does not mean that such changes should not
+happen---only that they must be applied in our sandbox first, to
+ensure a smooth transition.
 
 @node Internals
 @chapter Unexciting Information for @acronym{GNUN}'s Operation
@@ -1437,7 +1507,7 @@
 Does not send the email message.
 
 @item RCPT
-The recepient of the message in a valid format, like
+The recipient of the message in a valid format, like
 @code{someone@@somehost.org}.
 
 @item SUBJECT
@@ -1486,7 +1556,7 @@
 Does not actually send the message, just like @command{mailfail}.
 
 @item RCPT
-The recepient of the message.
+The recipient of the message.
 
 @item FILE
 The HTML file that has to be validated for compliance with the
@@ -1502,6 +1572,20 @@
 
 Read the source code, then please tell us :-)
 
address@hidden Bugs
address@hidden Reporting Bugs
+
address@hidden Nations, like any other software, is not bug free.
+There are some known bugs and annoyances, which are listed in the
address@hidden file, but it is absolutely certain that there are more
+which we know nothing about.
+
+If you encounter a bug, or if you have suggestions of any kind, please
+do not hesitate to report them at @email{trans-coord-devel@@gnu.org}
+or
address@hidden://savannah.gnu.org/@/bugs/@/?func=additem&group=trans-coord},
+category @code{-- GNUnited Nations --}.
+
 @node Copying This Manual
 @appendix GNU Free Documentation License
 
@@ -1522,3 +1606,17 @@
 compile-command: "texi2pdf -c gnun.texi"
 ispell-local-dictionary: "american"
 End:
+
address@hidden  LocalWords:  uref gettext gettext's po html samp lang www 
translinks sw SSI
address@hidden  LocalWords:  indicateurl TODO Pootle wiki CVS POs flushright 
O'Rielly's cd
address@hidden  LocalWords:  webmaster's makefile gmake Runtime VCS itemx cvs 
POTs XHMTL mk
address@hidden  LocalWords:  NOTFIY devel addr LINGUAS ing XHTML distclean 
subsubsection el
address@hidden  LocalWords:  GNUmakefile keepingup basename DIRS basenames RET 
distros KDE
address@hidden  LocalWords:  gTranslator KBabel Poedit wxWidgets cp templated 
msginit msgid
address@hidden  LocalWords:  msgstr charset CHARSET filename UTF unfuzzy SPC 
msgcat emacs
address@hidden  LocalWords:  kbd defun eq tmp buf progn zerop goto msgfmt cv 
href TransNote
address@hidden  LocalWords:  ol li CSS buggestions Traduction Drieu lt FSF 
Corazza pre bg
address@hidden  LocalWords:  prepend Fooish timestamp other's coord workflow br 
wwwdir zh
address@hidden  LocalWords:  cn tw msgmerge unnumberedsubsubsec crontab dom mon 
dow accute
address@hidden  LocalWords:  symlink env fooish bazzling mailfail proto RCS 
stdout BSD's
address@hidden  LocalWords:  Mailutils mailx CMD ARG




reply via email to

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