Re: [Tails-l10n] Please review "Improve Tails in your own la…

Delete this message

Reply to this message
Autor: Matsa
Data:  
A: Tails localization discussion
Assumpte: Re: [Tails-l10n] Please review "Improve Tails in your own language"
Tue, 09 Oct 2012 10:00:33 +0200,
sajolida@??? wrote :

> On 08/10/12 16:57, Matsa wrote:
> >
> > Hi,
> >
> > please review some modifications in
> > https://tails.boum.org/contribute/how/translate
> >
> > As the commitdiff is a bit messy, you may check the new version
> > here:
> > http://repo.or.cz/w/tails/matsa.git/blob/875ab6740ae2ab4c00c1d4520035d0eb750c8f80:/wiki/src/contribute/how/translate.mdwn


> Just two comments on your modifications:
>
> 1. Why did you remove the part on “For English native speakers”?


Hi Sajolida, and thanks for your attention

The actual version says to the native English speakers:

> Most of Tails developers are not native English speakers so you're
> more than welcome to edit, rephrase, correct or improve our English.
> Since you won't be able to use translation tools for that but rather
> edit the original code or wiki pages your best option will be using
> the web interface to the wiki or Git to submit patches"


As it's not possible anymore to use the web interface, the second
sentence is outdated (the possibility to submit Git patches is
still evoked, as one of the options to submit translations)

About the first sentence, I thought that the native English speakers
was 'included enough' in:

> If you are a native speaker of one of the languages available on this
> website, you can help on correcting, improving or completing the
> translations that are already available in Tails.


but we can also write below something like:

> And if you are a native English speaker, you are more than welcome to
> edit, rephrase, correct or improve our English, as it's not the
> mother tongue of most of Tails developers.


What do you think?

> 2. The sentence « The translation system used by both the custom
> programs and the website is called gettext. Every sentence that needs
> to be translated is written in a PO file. » makes sense even for
> Transifex, the same applies to the list of things that need to be
> translated. Why did you removed them from the introductory part
> “Translating Tails”


The list of things that need to be translated has been split up in the
different sections (following the idea that each different option allows
the contributor to translate different things). Do you think something
is missing?

About Transifex, I perceived this tool as an easy way to step-in
translation work, without having to handle PO files at first.

It's in deed possible to use Transifex to lock a resource → download a
PO → edit offline → upload a modified file → then get reviewed and
finally merged.

We plan to test and document it as soon as possible, but, as using
Transifex this way is a quite new workflow, do we want to
evoke/support/promote this from now?

I've been searching around, but I'm still confused about the way it
works: Does Transifex store the translatable files in a separate Git
repository? How interact the translations made with Transifex and the
one made in the main repository?

By the way, I fixed some broken links (commit 826444b4c4cf)

A last thing, is there a relevant place to publish some 'tips&tricks'
for translators, like building the wiki offline for example?

Greetings!