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 doc/gnun...


From: Pavel Kharitonov
Subject: trans-coord/gnun/server/gnun ChangeLog doc/gnun...
Date: Mon, 30 Dec 2013 14:16:14 +0000

CVSROOT:        /sources/trans-coord
Module name:    trans-coord
Changes by:     Pavel Kharitonov <ineiev>       13/12/30 14:16:14

Modified files:
        gnun/server/gnun: ChangeLog 
        gnun/server/gnun/doc: gnun.texi web-trans.texi 

Log message:
        * doc/gnun.texi (Introduction, Disadvantages, Overview):
        (GNUmakefile.team Targets, PO Files, Commits): Spellcheck.
        (Runtime Variables, no-grace-items): Eliminate references
        to gnunews.  Minor rewordings.
        (Introduction): Fix link to gettext.
        (Migrating, Webmaster Tips, Files and Directories):
        (gnun-validate-html): Minor cleanups.
        * doc/web-trans.texi (Introduction, Priorities):
        (Submitting as Plain Text): Spellcheck.
        (Joining): Show how orphan teams are marked.
        (Leaders): Update statistics.
        (Leaders, Managing, Savannah, Savannah Support, Co-leaders):
        (Mailing Lists, Savannah Projects, PO Files):
        Minor rewordings.
        (Savannah Homepage): Remove paragraph about historical
        locations, there are no such pages left.
        (Co-leaders): Co-leaders should be admins of `www-lang'.
        (PO Files): Use xref to refer to PO mode.
        (SSI): Add an anchor to `generic.html'.
        (Tracking Tasks): Fix reference to `generic.html'.

CVSWeb URLs:
http://cvs.savannah.gnu.org/viewcvs/trans-coord/gnun/server/gnun/ChangeLog?cvsroot=trans-coord&r1=1.394&r2=1.395
http://cvs.savannah.gnu.org/viewcvs/trans-coord/gnun/server/gnun/doc/gnun.texi?cvsroot=trans-coord&r1=1.92&r2=1.93
http://cvs.savannah.gnu.org/viewcvs/trans-coord/gnun/server/gnun/doc/web-trans.texi?cvsroot=trans-coord&r1=1.59&r2=1.60

Patches:
Index: ChangeLog
===================================================================
RCS file: /sources/trans-coord/trans-coord/gnun/server/gnun/ChangeLog,v
retrieving revision 1.394
retrieving revision 1.395
diff -u -b -r1.394 -r1.395
--- ChangeLog   24 Dec 2013 07:12:56 -0000      1.394
+++ ChangeLog   30 Dec 2013 14:16:14 -0000      1.395
@@ -1,3 +1,26 @@
+2013-12-30  Pavel Kharitonov  <address@hidden>
+
+       * doc/gnun.texi (Introduction, Disadvantages, Overview):
+       (GNUmakefile.team Targets, PO Files, Commits): Spellcheck.
+       (Runtime Variables, no-grace-items): Eliminate references
+       to gnunews.  Minor rewordings.
+       (Introduction): Fix link to gettext.
+       (Migrating, Webmaster Tips, Files and Directories):
+       (gnun-validate-html): Minor cleanups.
+       * doc/web-trans.texi (Introduction, Priorities):
+       (Submitting as Plain Text): Spellcheck.
+       (Joining): Show how orphan teams are marked.
+       (Leaders): Update statistics.
+       (Leaders, Managing, Savannah, Savannah Support, Co-leaders):
+       (Mailing Lists, Savannah Projects, PO Files):
+       Minor rewordings.
+       (Savannah Homepage): Remove paragraph about historical
+       locations, there are no such pages left.
+       (Co-leaders): Co-leaders should be admins of `www-lang'.
+       (PO Files): Use xref to refer to PO mode.
+       (SSI): Add an anchor to `generic.html'.
+       (Tracking Tasks): Fix reference to `generic.html'.
+
 2013-12-24  Pavel Kharitonov  <address@hidden>
 
        * GNUmakefile (grace-is-over): Fix the case

Index: doc/gnun.texi
===================================================================
RCS file: /sources/trans-coord/trans-coord/gnun/server/gnun/doc/gnun.texi,v
retrieving revision 1.92
retrieving revision 1.93
diff -u -b -r1.92 -r1.93
--- doc/gnun.texi       10 Dec 2013 15:20:32 -0000      1.92
+++ doc/gnun.texi       30 Dec 2013 14:16:14 -0000      1.93
@@ -85,7 +85,7 @@
 Public License.
 
 This manual is organized in way that is suitable both for translators
-and GNU Web Translation managers (plus eventually interested GNU
+and GNU Web Translation Managers (plus eventually interested GNU
 Webmasters, if any).  It may also serve as an introductory material and
 reference for new GNUN developers and contributors.  Hopefully, it might
 be useful to people who customize and adopt the software for a third
@@ -146,8 +146,9 @@
 updates to the translation.
 
 The GNU @code{gettext} package already provides the needed
-infrastructure for maintaining translations using PO files.  @xref{Top,
-, Introduction, gettext, GNU gettext tools}, for a basic overview.
+infrastructure for maintaining translations using PO files.
address@hidden, Introduction, , gettext, GNU gettext tools},
+for a basic overview.
 GNUnited Nations fills the gaps to apply this infrastructure to articles
 in @url{http://gnu.org} web address@hidden process of converting
 HTML to PO and the other way around is performed using po4a (``po for
@@ -352,7 +353,7 @@
 @item
 In some rare cases (most notably, for alphabetically sorted lists)
 the structure of the translation should diverge from the structure
-of the original document.  So far, our system has developped no means
+of the original document.  So far, our system has developed no means
 of taking such issues into account.
 @end itemize
 
@@ -555,8 +556,8 @@
 @cindex output, detailed
 @item VERBOSE=yes
 If defined, the value of the variables @code{templates-translated},
address@hidden, @code{articles-translated} and
address@hidden will be printed to the standard output.  This is off by
address@hidden, and @code{articles-translated}
+will be printed to the standard output.  This is off by
 default, but recommended in general since it will show a bug in the
 computation of the basic variables.
 
@@ -571,9 +572,10 @@
 implemented specifically to prevent gratuitous replacement of translated
 strings with the English text when there are only minor formatting
 changes in the original.  The translator has time (the ``grace'' period
-as defined in this variable) to review the changes and unfuzzy the
+as defined in this variable) to review the changes and clear the ``fuzzy''
+mark from the
 strings, while keeping the online translation intact.  Note that this
-variable has no effect on the server templates, gnunews
+variable has no effect on the server templates
 and all articles defined in the variable @code{no-grace-articles}.
 
 @cindex OUTDATED-GRACE
@@ -651,11 +653,11 @@
 
 The @code{no-grace-items} target regenerates a limited set of articles
 that are not affected by the grace period, namely, the
-server templates, gnunews, and all articles defined in the variable
+server templates, and all articles defined in the variable
 @code{no-grace-articles} (@pxref{GRACE,,grace period}).
 
 This target can be rebuilt more often than @code{all}; however,
-currently it is not used.
+currently we just build all with the same period.
 
 @node update-localized-URLs
 @subsection The @code{update-localized-URLs} Target
@@ -1007,7 +1009,7 @@
 
 @end enumerate
 
-Also, sitemaps contain many translatable messages, so it is desirable
+Also, sitemaps contain many translated messages, so it is desirable
 to eliminate manual work where possible.
 
 In order to take this into account, GNUN provides the @code{sitemap}
@@ -1029,7 +1031,7 @@
 @cindex GNUmakefile.team
 
 GNUN operates on the ``official'' Web repository of the Savannah project
-`www', where normally only the coordinators of translation teams have
+`www', where normally only the co-ordinators of translation teams have
 write access.  However, all translation teams have their own projects,
 so it is possible to take advantage of Savannah as a hosting facility to
 make the team work more comfortable.
@@ -1075,7 +1077,7 @@
 the GNU Web Translation Managers to setup them for your team on our
 server.}.  A translator would then normally update the PO file, and
 commit it again in the project's Sources repository, from where the
-coordinator will pick it up and install it in `www'.
+co-ordinator will pick it up and install it in `www'.
 
 To take advantage of this semi-automation, rename this template
 @file{GNUmakefile.team} as @file{GNUmakefile} and install it in the root
@@ -1264,11 +1266,11 @@
 
 @cindex email-aliases
 Email addresses of the translators are kept in a separate file,
address@hidden  Like @file{nottab}, this file contains lines
-separated by `:'; the lines beginning with `#' are ignored.
address@hidden  Like in @file{nottab}, the lines beginning
+with `#' are ignored; other lines contain fields separated by `:'.
 
 The first field is the translator's identifier, the second is
-space-separated list of the translator's email addresses.  These two
+space-separated list of translator's email addresses.  These two
 fields are mandatory.
 
 @cindex reminder period
@@ -1296,7 +1298,7 @@
 
 @item www
 Report cases that suggest actions by the team leader, that is,
-when the translation in the team repository is full whereas
+when the translation in the team repository is complete whereas
 in @dfn{www} it is incomplete or absent.
 @end table
 
@@ -1319,7 +1321,7 @@
 is out of scope of GNUN and this manual.
 
 @item format
-A convenience rule to re-wrap all files upto the standard length.  Many
+A convenience rule to re-wrap all files up to the standard length.  Many
 PO editors leave the @code{msgstr} as a single long line after it has
 been edited, but GNUN will automatically re-wrap the file to the standard
 line length when it is processed.  Wrapping long lines in PO files is a
@@ -1418,7 +1420,7 @@
 @node PO Files
 @chapter Working with PO Files
 
-This section provides technical details about woking with PO files.
+This section provides technical details about working with PO files.
 For general information about PO editors, @pxref{PO Files, ,
 Working with PO Files, web-trans, GNU Web Translators Manual}.
 
@@ -1810,7 +1812,7 @@
 Migrating an existing translation to a PO file format is basically
 editing the header as described in the previous section, and
 populating each of the messages by copying the already translated text
-and/or markup from the existing translation in HTML format in the
+and markup from the existing translation in HTML format in the
 relevant message.
 
 Typically, you will visit @file{po/address@hidden (in PO mode) and
@@ -1831,7 +1833,7 @@
 checkout the revision of the English page, @file{foo.html}, that
 corresponds to the latest revision of the translation,
 @address@hidden  Then you run @command{gnun-preconvert}
-which invokes @command{po4a-gettextize} (@xref{gnun-preconvert}.):
+(@pxref{gnun-preconvert}):
 
 @example
 gnun-preconvert foo.lang.html foo.html
@@ -1841,7 +1843,7 @@
 of @file{foo.html}, error messages will be displayed.  Check them,
 adjust the files and try again.  When you succeed, the result will be
 written to foo.lang.po.  After that, run
address@hidden (@xref{gnun-merge-preconverted}.):
address@hidden (@pxref{gnun-merge-preconverted}):
 
 @example
 gnun-merge-preconverted -C compendium.lang.po foo.lang.po foo.pot
@@ -1857,8 +1859,8 @@
 facilitate checking.
 
 There is no need to delete the existing HTML translation, GNUN will
-automatically overwrite it.  The only thing a translator should do is
-commit the PO file to the repository.
+automatically overwrite it.  The only thing the translator should do
+is commit the PO file to the repository.
 
 When an essay has been translated by several people through the years,
 it is important that this information is recorded and reflected in the
@@ -1899,7 +1901,7 @@
 If you plan to edit a certain page extensively, please do so within a
 reasonable time frame, for example a day or preferably, several hours.
 That way, the translators who are quick to update it immediately won't
-be disappointed if the POT changes again in the next GNUN run(s).
+be disappointed if the POT changes again in the next GNUN run.
 
 @menu
 * Modifying Templates::       How to avoid errors.
@@ -2122,13 +2124,13 @@
 
 @item @dots{}/po/@var{file}.translist
 The list of trasnlations for @address@hidden/@var{file}.html}.  It is
-included in @address@hidden/@var{file}.html} all its translations.
+included in @address@hidden/@var{file}.html} and all its translations.
 
 @item @dots{}/po/@var{file}.pot
 PO templates for articles and included files.
 
 @item @dots{}/po/@var{file}.pot.opt
-POTs of optional templates (currently, @file{planetfeeds.pot.opt}).
+POTs of optional templates.
 @xref{optional-templates}, for more details.
 
 @item @dots{}/po/@address@hidden
@@ -2168,7 +2170,7 @@
 Variables}.
 
 @item server/gnun/languages.txt
-See @ref{languages.txt}.
+Canonical names for languages.  @xref{languages.txt}.
 
 @item server/gnun/compendia
 The directory for compendia.  @xref{Compendia}.
@@ -2386,7 +2388,7 @@
 
 @cindex priorities.mk
 The script depends on the presence of the @file{priorities.mk} file
-in the @file{server/gnun} subdirectory of the working copy of `www'
+in the @file{server/gnun} sub-directory of the working copy of `www'
 repository.
 
 The results are written to standard output.  Example:
@@ -2434,8 +2436,7 @@
 respective W3C standard.  Sometimes webmasters make mistakes, and
 translators too, so this tool is useful to catch errors of that kind.
 
-GNUN enforces HTML validation at build time if invoked with
address@hidden
+GNUN enforces HTML validation at build time by default.
 
 The script expects only one @var{file} as the last argument and will exit
 with an error if it is not specified (which might be the case when an
@@ -2628,9 +2629,9 @@
 @c  LocalWords:  GNUnited afourpaper FIXME titlepage Yavor Doganov vskip filll
 @c  LocalWords:  insertcopying dircategory direntry ifnottex makefiles url emph
 @c  LocalWords:  compendia Compendia GNUN's ineiev cron cindex gnumake config
address@hidden  LocalWords:  pkgdatadadir symlinks ln SVN bzr svn HMTL conf ann 
dfn gnunews
address@hidden  LocalWords:  pkgdatadadir symlinks ln SVN bzr svn HMTL conf ann 
dfn
 @c  LocalWords:  online filesets urls automagically wdiff dir gNewSense Virtaal
 @c  LocalWords:  Gtranslator Lokalize XLIFF API ftplugin txt init URIs
 @c  LocalWords:  preconvert gettextize preconverted RSS de Deutsch
address@hidden  LocalWords:  ul nbsp polski upto committer Boilerplates 
boilerplates png
address@hidden  LocalWords:  ul nbsp polski committer Boilerplates boilerplates 
png
 @c  LocalWords:  FilenameAndURLGuidelines SVG lbAO hardcoded fdl

Index: doc/web-trans.texi
===================================================================
RCS file: /sources/trans-coord/trans-coord/gnun/server/gnun/doc/web-trans.texi,v
retrieving revision 1.59
retrieving revision 1.60
diff -u -b -r1.59 -r1.60
--- doc/web-trans.texi  10 Dec 2013 15:20:32 -0000      1.59
+++ doc/web-trans.texi  30 Dec 2013 14:16:14 -0000      1.60
@@ -89,7 +89,7 @@
 constantly increasing), the ones actively engaged in teaching others to
 appreciate and defend their freedom are only a few.  Consequently and
 rather unfortunately, there are not so many volunteers willing to
-maintain on the long term translations of the various essays that
+maintain in the long term translations of the various essays that
 describe the fundamental values of the free software movement.
 
 Translators of the @uref{http://gnu.org} website are organized in
@@ -143,7 +143,8 @@
 happen, but it's a possibility anyway).
 @end itemize
 
-If the team is marked as @dfn{orphaned}, there is no problem: you can
+If the team is marked as @dfn{orphaned} (``New coordinator needed''),
+there is no problem: you can
 still submit your translation to @email{web-translators@@gnu.org}
 (@pxref{Submitting}).  In case you want to establish a new translation
 team or become a co-ordinator of an existing one, please refer to the
@@ -294,12 +295,12 @@
 @file{.odt}), etc.
 
 Translate the title, the blue heading (if it differs slightly from the
-title) and the body of the article upto the link @samp{back to top}.
+title) and the body of the article up to the link @samp{back to top}.
 For example, for @uref{http://www.gnu.org/@/philosophy/@/free-sw.html}
 that would be:
 
 @example
-What is free software? - GNU Project - Free Software Foundation (FSF)
+What is free software? - GNU Project - Free Software Foundation
 
 What is free software?
 
@@ -365,7 +366,7 @@
 to solve.  Energy and time are always needed, as well as certain
 communication skills.
 
-However, a team leader is not a dictator (for life); every action and/or
+However, a team leader is not a dictator (for life); every action and
 decision taken should have its justification and should stem from the
 goals of the project at large.  Inefficient or inoperative leaders are
 replaced, if necessary.
@@ -421,8 +422,8 @@
 important materials to translate under @file{/philosophy}, @file{/gnu},
 @file{/distros}, @file{/copyleft} and @file{/licenses} directories just
 to get a rough estimate about the amount of work address@hidden of
-December 2012, there are over 250 files to translate in ``important''
-directories; their volume is about 3.5 MB.}.  If you are
+December 2013, there are over 250 files to translate in ``important''
+directories; their volume is about 4 MB.}.  If you are
 still not scared and determined to go on further, excellent.
 
 As you have probably observed, every directory that contains
@@ -611,7 +612,7 @@
 teams, and for general organizational work.  Feel free to discuss
 anything related to the translation process there.
 
-It is strongly recommended translation teams to attempt to recruit
+It is strongly recommended that translation teams attempt to recruit
 native English speakers in order to improve their translation process.
 Translators sometimes misunderstand English idioms and expressions, and
 as a result, they translate them incorrectly or in ways that are
@@ -660,7 +661,7 @@
 @subsection How to Track Tasks and Bugs Using Savannah
 
 The team leader has to make sure that prospective translations are
-reviewed, that they do not contain obvious errors and/or confusing
+reviewed, that they do not contain obvious errors and confusing
 expressions and that they match the spirit and intention of the original
 essay.  However, many teams tend to suffer from a specific problem: team
 members rely on the leader to make these extensive reviews. That is
@@ -696,7 +697,7 @@
 for this purpose.
 
 It is prudent to discuss the most convenient naming scheme and practice
-among team members, and publish the convention and/or rules at the
+among team members, and publish the convention or rules at the
 team's homepage.  Note that you can create @dfn{Custom Fields} in the
 trackers, and resolved bugs can be searched based on these custom
 values.
@@ -732,7 +733,8 @@
 resolved should remain open, naturally.
 @end itemize
 
-Of course, teams can choose to manage these things using external
+If there are compelling reasons, teams can choose to manage these
+things using external
 resources and eventually other bug (or issue) tracking systems.
 Whatever you decide, please make sure that bugs can be reported using
 free software only, and that the software providing that service is
@@ -743,8 +745,7 @@
 If you use a certain facility (i.e. a bug tracking system) to manage
 bugs in translations, it is best to take advantage of
 @address@hidden and advertise it on every page.
address@hidden, , , gnun, The GNUnited Nations Manual}, for
-details.
address@hidden, for details.
 
 @node Unreviewed Translations
 @subsection How to Proceed with Unreviewed Translations
@@ -838,7 +839,7 @@
 subsequently corrupting the file.  @xref{Substitution Modes, , , cvs,
 Version Management with CVS}.  More importantly, using @option{-kb}
 prevents corruption of the binary when people using CVS clients under
-infamous OS checkout, modify the file, and then commit it with
+infamous OS checkout modify the file, and then commit it with
 messed ends of address@hidden years ago there still were
 committers using nonfree operating systems---we don't dictate what
 OS people use, but we can at least prevent this technical kind
@@ -862,7 +863,7 @@
 find information for translation teams and their contacts.
 
 Using external hosting facilities may seem justified sometimes.  Some
-teams may have already established repositories and/or bug tracking
+teams may have already established repositories or bug tracking
 systems where usual contributors already have access.  Some team
 members prefer to work within the established infrastructure of a
 broad translation team (for whatever reason), but this is discouraged.
@@ -948,17 +949,12 @@
 and the FSF HTML Style Sheet
 address@hidden://gnu.org/@/server/@/fsf-html-style-sheet.html}).
 
-For historical reasons, team-specific materials were available in the
address@hidden repository, under ad-hoc locations as @file{/spanish},
address@hidden/wwwsr}, etc.  These locations are deprecated, and the contents
-will be removed without warning.
-
 @node Savannah Support
 @subsection Support Tracker
 
 This tracker is supposed to be related to things about the @emph{project
 management} itself, i.e. project members may report here missing
-functionality and/or features that requires the project admin's
+functionality and features that requires the project admin's
 action.  Do not use it for anything else as it quickly becomes
 confusing.  It is OK to disable it if the team is small.
 
@@ -1055,7 +1051,7 @@
 @section Promoting Members as Co-leaders
 
 When the team grows large and it becomes hard for a single person to
-manage, there is no problem to add another (or even another two) people
+manage, there is no problem to add another (or even two other) people
 to help.  Note that a subsequently appointed team co-ordinator is not
 simply a @dfn{committer} with write access to the @samp{www} repository;
 she has full responsibilities just like a single leader, although the
@@ -1063,8 +1059,8 @@
 
 If you'd like another person to act as a co-leader and help you with the
 management tasks, send a message to @email{web-translators@@gnu.org}
-with her name and Savannah account.  She has to be already a member of
address@hidden@var{lang}}.
+with her name and Savannah account.  She has to be already
+an administrator of @address@hidden
 
 The procedure for co-leaders is a simplified version of the one for a
 new team or taking over an existing team.  @xref{New Team}.
@@ -1191,7 +1187,7 @@
 parlance this means doing something in between which is typically easier
 to handle.
 
-You can find links automatic reports about current status of
+You can find links to automatic reports about current status of
 translations of all active teams sorted by their priority in
 @uref{http://www.gnu.org/software/gnun/reports/}.  If the page for
 your team is missing there, please ask
@@ -1256,7 +1252,7 @@
 Nations Manual}.
 
 @item
-GNUmakefile.team also has a means to send more detaled reports
+GNUmakefile.team also has a means to send more detailed reports
 to specific translators; @pxref{notify in GNUmakefile.team, , , gnun,
 The GNUnited Nations Manual}.  The notification facility takes the
 output of the @code{report} target, adds the URLs of relevant files,
@@ -1270,7 +1266,7 @@
 @email{web-translators@@gnu.org}.
 
 @item
-If your editors don't hightlight differences against previous
+If your editors don't highlight differences against previous
 messages, you may find it useful to track the changes in the messages
 with @command{gnun-add-fuzzy-diff}.  For more details,
 @pxref{gnun-add-fuzzy-diff, , , gnun, The GNUnited Nations Manual}.
@@ -1386,7 +1382,7 @@
 @node Mailing Lists
 @section Related Mailing Lists
 
-Here is a short summary of the mailing lists relevant to the translation
+Here is a summary of the mailing lists relevant to the translation
 process, and a brief description about how they relate to the various
 participants in the process.
 
@@ -1408,8 +1404,8 @@
 
 @item trans-coord-discuss@@gnu.org
 The main discussion list for the GNU Web Translators.  Team leaders must
-subscribe, as errors from GNUN are mailed here.  Active team members are
-highly recommended to join as well, because the changes in general
+subscribe, as errors from GNUN are mailed here.  It's highly recommended
+that active team members join as well, because the changes in general
 policies for translations are also announced and discussed here.
 
 This is a private mailing list.
@@ -1443,7 +1439,7 @@
 @node Savannah Projects
 @section Savannah Projects Membership
 
-Participants in the www.gnu.org translations process normally have to be
+Participants in the www.gnu.org translation process normally have to be
 members of the following Savannah projects, depending on the case:
 
 @table @samp
@@ -1453,7 +1449,7 @@
 Translation Manager (in order to approve leaders' applications).  All
 team leaders (and co-leaders) should be members of this project.
 
-Note that this project has no direct relationship with translators,
+Note that this project has no direct relation to translators,
 although almost anything happening in @samp{www} directly affects
 them.  The @samp{www} project is managed separately and has
 a different (entirely unrelated) process for approving contributors.
@@ -1494,8 +1490,8 @@
 
 Note that recent versions of some PO editors (both offline
 and web-based) offer access to various translation services that
-do machine translation for their users.  Using a translation service
-is a clear example of SaaSS (see
+do machine translation for their users.  Using a machine translation
+service is a clear example of SaaSS (see
 @uref{https://www.gnu.org/philosophy/who-does-that-server-really-serve.html}),
 so please don't use such editors unless they only submit requests
 to your (or GNU project's) own servers.
@@ -1512,7 +1508,7 @@
 switch to PO mode.  You can enable/disable it with @code{M-x po-mode
 @key{RET}}.  On some GNU/Linux distros such as gNewSense, PO mode is
 available in a separate package, @code{gettext-el}. See
address@hidden://www.gnu.org/software/gettext}.
address@hidden Mode, Emacs's PO File Editor, , gettext, Gettext Manual}.
 
 @item
 Gtranslator---the GNOME PO editor.  See
@@ -1623,6 +1619,7 @@
 This is a very short file currently containing the ``back to top'' link.
 Also translatable via GNUN.
 
address@hidden
 @item server/generic.html
 This file is empty; its ``localized'' versions may contain optional
 short messages providing more information about the translation
@@ -1883,17 +1880,17 @@
 @c  LocalWords:  dircategory direntry ifnottex ordinators GNUN gnun uref samp
 @c  LocalWords:  coord pxref ordinatorship TranslationsUnderway dfn ordinator
 @c  LocalWords:  indicateurl lang html CVS www cvs gettextized LINGUAS online
address@hidden  LocalWords:  emph UTF gEdit OpenOffice txt odt upto FSF cvsweb 
historial hy
address@hidden  LocalWords:  emph UTF gEdit OpenOffice txt odt FSF cvsweb 
historial hy
 @c  LocalWords:  quisiera revisar los cambios que hemos hecho por vea abajo el
 @c  LocalWords:  href inline distros mai Maithili br zh cn uuml VCS ne
 @c  LocalWords:  WebSite Unreviewed subsubsection SourceForge webmaster's Yay
 @c  LocalWords:  Panjabi png kb RCS Windoze EOLs committers unmarking checkbox
address@hidden  LocalWords:  pollinking hoc spanish wwwsr assignee RSS 
subsubheading Pootle
address@hidden  LocalWords:  pollinking assignee RSS subsubheading Pootle
 @c  LocalWords:  Vertaal Narro msgmerge th webmastering SSI CSS filenames xml
 @c  LocalWords:  GNUN's RTL dir xmlns ar rtl encodings filename css
 @c  LocalWords:  itemx underfull hbox Runtime stylesheet fssbox screenshot svg
 @c  LocalWords:  topbanner Inkscape toplevel pre cronjob GNU's Dlaczego Powinno
 @c  LocalWords:  Oprogramowanie Wolne Fondation Logiciel Libre Deutsch NoDerivs
 @c  LocalWords:  textarea Dit werk gelicenseerd onder een Naamsvermelding ann
address@hidden  LocalWords:  GeenAfgeleideWerken Verenigde licentie Texinfo 
gnunews fdl cp
address@hidden  LocalWords:  GeenAfgeleideWerken Verenigde licentie Texinfo fdl 
cp
 @c  LocalWords:  texi FIXME printindex eval pdf ispell american



reply via email to

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