+2007-06-30 Bruno Haible <bruno@clisp.org>
+
+ * nls.texi: Update email addresses and URLs after the Translation
+ Project moved.
+
2007-06-03 Bruno Haible <bruno@clisp.org>
* nls.texi (Using This Package): Recommend also to unset LC_ALL etc.
able to synergize with other translators speaking the same language.
Each translation team has its own mailing list. The up-to-date list
of teams can be found at the Free Translation Project's homepage,
-@file{http://www.iro.umontreal.ca/contrib/po/HTML/}, in the
-"National teams" area.
+@file{http://translationproject.org/}, in the "Teams" area.
If you'd like to volunteer to @emph{work} at translating messages, you
should become a member of the translating team for your own language.
difficulties, rather than merely lurking around. If your team does not
exist yet and you want to start one, or if you are unsure about what to
do or how to get started, please write to
-@w{@file{translation@@iro.umontreal.ca}} to reach the
+@w{@file{coordinator@@translationproject.org}} to reach the
coordinator for all translator teams.
The English team is special. It works at improving and uniformizing
If @value{STATUS} seems to be old, you may fetch a more recent copy
of this @file{ABOUT-NLS} file on most GNU archive sites. The most
up-to-date matrix with full percentage details can be found at
-@file{http://www.iro.umontreal.ca/contrib/po/HTML/matrix.html}.
+@file{http://translationproject.org/extra/matrix.html}.
@node Using gettext in own code
Free Translation Project is also available for packages which are not
developed inside the GNU project. Therefore the information given above
applies also for every other Free Software Project. Contact
-@w{@file{translation@@iro.umontreal.ca}} to make the @file{.pot} files
+@w{@file{coordinator@@translationproject.org}} to make the @file{.pot} files
available to the translation teams.
+2007-06-30 Bruno Haible <bruno@clisp.org>
+
+ * gettext.texi (Installing Localizations, Header Entry, Trans Intro 0,
+ Trans Intro 1, Organization, Mailing Lists, Prerequisites): Update
+ email addresses and URLs after the Translation Project moved.
+ * FAQ.html: Likewise.
+
2007-06-17 Bruno Haible <bruno@clisp.org>
* gettext.texi (Locale Names): Explain the variant syntax.
This mailing list is for methodology questions around
internationalization, and for discussions of translator tools,
including but not limited to GNU gettext.</li>
- <li><span style="font-family: monospace;">translation@iro.umontreal.ca</span><br>
+ <li><span style="font-family: monospace;">coordinator@translationproject.org</span><br>
This is the email address of the <a
- href="http://www.iro.umontreal.ca/contrib/po/HTML/">Free Translation
-Project</a>, that is the project which manages the translated message
+ href="http://translationproject.org/">Free Translation Project</a>,
+that is the project which manages the translated message
catalogs for many free software packages. Note that KDE and GNOME
packages are not part of this project; they have their own translation
projects: <a href="http://i18n.kde.org/">i18n.kde.org</a> and <a
@cindex @file{ABOUT-NLS} file
For programs that participate in the Translation Project, you can start
looking for translations here:
-@url{http://www.iro.umontreal.ca/translation/registry.cgi?team=index}.
+@url{http://translationproject.org/team/index.html}.
A snapshot of this information is also found in the @file{ABOUT-NLS} file
that is shipped with GNU gettext.
@cindex list of translation teams, where to find
In the Free Translation Project, each translation team has its own mailing
list. The up-to-date list of teams can be found at the Free Translation
-Project's homepage, @uref{http://www.iro.umontreal.ca/contrib/po/HTML/},
-in the "National teams" area.
+Project's homepage, @uref{http://translationproject.org/}, in the "Teams"
+area.
@item Content-Type
@cindex encoding of PO files
Keep in mind that team members should be interested in @emph{working}
at translations, or at solving translational difficulties, rather than
merely lurking around. If your team does not exist yet and you want to
-start one, please write to @w{@file{translation@@iro.umontreal.ca}};
+start one, please write to @w{@file{coordinator@@translationproject.org}};
you will then reach the coordinator for all translator teams.
A handful of GNU packages have already been adapted and provided
point. But there are many more packages and many languages for
which we have no volunteer translators. If you would like to
volunteer to work at translating messages, please send mail to
-@file{translation@@iro.umontreal.ca} indicating what language(s)
+@file{coordinator@@translationproject.org} indicating what language(s)
you can work on.
@node Trans Intro 1, Discussions, Trans Intro 0, Translators
point. But there are many more packages and many languages
for which we have no volunteer translators. If you'd like to
volunteer to work at translating messages, please send mail to
-@samp{translation@@iro.umontreal.ca} indicating what language(s)
+@samp{coordinator@@translationproject.org} indicating what language(s)
you can work on.
@end quotation
internationalization of free software is dedicated to succeed.
For suggestion clarifications, additions or corrections to this
-document, please e-mail to @file{translation@@iro.umontreal.ca}.
+document, please e-mail to @file{coordinator@@translationproject.org}.
@node Discussions, Organization, Trans Intro 1, Translators
@section Discussions
once well started.
The setup should be minimally completed and tested before GNU
@code{gettext} becomes an official reality. The e-mail address
-@file{translation@@iro.umontreal.ca} has been setup for receiving
+@file{coordinator@@translationproject.org} has been setup for receiving
offers from volunteers and general e-mail on these topics. This address
reaches the Translation Project coordinator.
If we get any inquiries about GNU @code{gettext}, send them on to:
@example
-@file{translation@@iro.umontreal.ca}
+@file{coordinator@@translationproject.org}
@end example
The @file{*-pretest} lists are quite useful to me, maybe the idea could
ideally behave with PO files submissions. As a maintainer, your role is
to authenticate the origin of the submission as being the representative
of the appropriate translating teams of the Translation Project (forward
-the submission to @file{translation@@iro.umontreal.ca} in case of doubt),
+the submission to @file{coordinator@@translationproject.org} in case of doubt),
to ensure that the PO file format is not severely broken and does not
prevent successful installation, and for the rest, to merely put these
PO files in @file{po/} for distribution.
+2007-06-30 Bruno Haible <bruno@clisp.org>
+
+ * po-mode.el (po-translation-project-address): Update email address
+ after the Translation Project moved.
+ (po-translation-project-mail-label): Update comment.
+
2007-06-29 Karl Eichwalder <ke@suse.de>
* po-mode.el (po-subedit-mode-menu-layout, po-mode-menu-layout):
:group 'po)
(defcustom po-translation-project-address
- "translation@iro.umontreal.ca"
+ "robot@translationproject.org"
"*Electronic mail address of the Translation Project.
Typing \\[po-send-mail] (normally bound to `M') the user will send the PO file
to this email address."
:group 'po)
(defcustom po-translation-project-mail-label "TP-Robot"
- "*Subject label when sending the PO file to `po-translation-project-address'.
-Don't change it when you send PO files to \"translation@iro.umontreal.ca\", the
-Translation Project Robot at http://www.iro.umontreal.ca/contrib/po/HTML/. If
-the label is different, your submission will be consiedered as a regular mail
-and not stored at the TP site and also not forwarded to the package maintainer."
+ "*Subject label when sending the PO file to `po-translation-project-address'."
:type 'string
:group 'po)
projects / thirdparty / gettext.git / commitdiff
