mirror of
https://github.com/moparisthebest/pacman
synced 2024-08-13 17:03:46 -04:00
Update translation instructions
Signed-off-by: Dan McGee <dan@archlinux.org>
This commit is contained in:
parent
2d25993d2d
commit
23451e7fa4
@ -4,13 +4,17 @@ Pacman - Translating
|
|||||||
This document is here to guide you in helping translate pacman messages,
|
This document is here to guide you in helping translate pacman messages,
|
||||||
libalpm messages, and the manpages for the entire pacman package.
|
libalpm messages, and the manpages for the entire pacman package.
|
||||||
|
|
||||||
A quick note- the gettext website is a very useful guide to read before
|
We are currently using http://www.transifex.net/[Transifex] as the translation
|
||||||
embarking on translation work, as it describes many of the commands in more
|
platform for pacman and libalpm. You will need to sign up for an account there
|
||||||
detail than I will here:
|
and then register with a translation team on the
|
||||||
http://www.gnu.org/software/gettext/manual/html_node/gettext.html[]
|
http://www.transifex.net/projects/p/archlinux-pacman/[pacman project page].
|
||||||
|
|
||||||
In addition, this site presents a small tutorial that I found useful:
|
NOTE: This may be old information due to our switch to Transifex, but the
|
||||||
http://oriya.sarovar.org/docs/gettext/[]
|
gettext website is a very useful guide to read before embarking on translation
|
||||||
|
work, as it describes many of the commands in more detail than I will here:
|
||||||
|
http://www.gnu.org/software/gettext/manual/html_node/gettext.html[]. In
|
||||||
|
addition, this site presents a small tutorial that I found useful:
|
||||||
|
http://oriya.sarovar.org/docs/gettext/[].
|
||||||
|
|
||||||
|
|
||||||
Translating Messages
|
Translating Messages
|
||||||
@ -28,35 +32,31 @@ original message and the corresponding translation. These po files can then
|
|||||||
either be hand edited, or modified with a tool such as poedit, gtranslator or
|
either be hand edited, or modified with a tool such as poedit, gtranslator or
|
||||||
kbabel. Using a translation tool tends to make the job easier.
|
kbabel. Using a translation tool tends to make the job easier.
|
||||||
|
|
||||||
|
Please read up on Transifex usage using the
|
||||||
|
http://help.transifex.net/[Transifex Help] if you are not familiar.
|
||||||
|
|
||||||
See the <<Notes,Notes>> section for additional hints on translating.
|
See the <<Notes,Notes>> section for additional hints on translating.
|
||||||
|
|
||||||
Pre-release Updates
|
Pre-release Updates
|
||||||
~~~~~~~~~~~~~~~~~~~
|
~~~~~~~~~~~~~~~~~~~
|
||||||
|
|
||||||
A week or two before each release, the codebase will go into a string freeze
|
A week or two before each release, the codebase will go into a string freeze
|
||||||
and an email will be sent by the 'translation lieutenant' to the
|
and an email will be sent to the mailto:pacman-dev@archlinux.org[pacman-dev]
|
||||||
mailto:pacman-dev@archlinux.org[pacman-dev] mailing list asking for
|
mailing list asking for translations. This email will have a prefix of
|
||||||
translations. This email will have a prefix of *[translation]* for anyone
|
*[translation]* for anyone looking to set up an email filter.
|
||||||
looking to set up an email filter.
|
|
||||||
|
|
||||||
At this time, the `.po` language files will be made available at a URL
|
At this time, the latest `.po` language files will be made available at the
|
||||||
specified in the email. Each language will have two files available (backend
|
Transifex project page. Each language will have two files available (backend
|
||||||
and frontend). Translators interested in helping are encouraged to send a
|
and frontend). Translators interested in helping are encouraged to use the
|
||||||
follow-up message to the mailing list stating exactly what they intend to
|
features of Transifex to let others know they are currently translating their
|
||||||
translate so efforts are not duplicated on the same language.
|
language.
|
||||||
|
|
||||||
Once a translator has completed the translation (*OR* realizes they do not have
|
Once a translator has completed the translation (*OR* realizes they do not have
|
||||||
time to finish), please email the `.po` files back to the list with a subject
|
time to finish), please upload your progress back to the Transifex site.
|
||||||
such as '[translation] Updated German translation'. At this point, the
|
|
||||||
'translation lieutenant' will gather the translations together for inclusion in
|
|
||||||
the upcoming release.
|
|
||||||
|
|
||||||
NOTE: Please email your translations back to the list as soon as possible- this
|
NOTE: Please upload your translations as soon as possible- this will give other
|
||||||
will give other speakers of your language time to review your translations and
|
speakers of your language time to review your translations and update them as
|
||||||
update them as necessary.
|
necessary.
|
||||||
|
|
||||||
For those familiar with GIT, you may wish to follow the procedure outlined
|
|
||||||
below as another alternative.
|
|
||||||
|
|
||||||
Incremental Updates
|
Incremental Updates
|
||||||
~~~~~~~~~~~~~~~~~~~
|
~~~~~~~~~~~~~~~~~~~
|
||||||
|
Loading…
Reference in New Issue
Block a user