Release Notes translations
asgeirf at gmail.com
Tue Mar 24 01:31:14 UTC 2009
On Tue, Mar 24, 2009 at 9:52 AM, Dimitris Glezos <dimitris at glezos.com> wrote:
> On Tue, Mar 24, 2009 at 12:36 AM, Ruediger Landmann
> <r.landmann at redhat.com> wrote:
>> Diego Búrigo Zacarão wrote:
>>> Can someone, please, tell me why all the Release Notes translations (PO
>>> files) were deleted?
>> They haven't been deleted; the po files for the Fedora 10 Release Notes were
>> moved to a separate git branch as we prepare for Fedora 11. See here:
> May I suggest a heads-up to fedora-trans-list before landing big
> changes. It's always a good idea. =)
> Also, note that I'm still waiting for a patch that adds support for
> Publican documents for Transifex. Is there a plan behind this change
> in vital Fedora documents that takes translators into consideration?
As far as I understand publican, one of the major benefits of this
toolchain *is* translations. Hence, supporting Transifex on the
infrastructure side should be very easy. A simple recipe:
1) In the toplevel 'Makefile' read the OTHER_LANGS variable to get a
list of target-languages (e.g. ja-JP gu-IN)
2) For each of these languages, there is a sub-directory (e.g.
./ja-JP,/ ./gu-IN/) that reflects the exact directory-layout of the
./pot/ directory (containing the POT templates).
3) Present this nicely with statistics in the Transifex UI and allow
So, getting info out of publican is easy. The tricky part is that
Transifex 0.5 took a 'minor shortcut' by designing the application (at
least the UI) around the concept of 'one PO file pr component'. There
seems to be some support for additional files pr language, but this is
not a 'simple patch' and requires cooperation from the core
development team. I'm happy to assist with publican support if we find
a solution for multiple files in general within Transifex.
We have a Fedora L10N Infrastructure team meeting later today where I
will put this on the agenda.
More information about the docs