Narro for Scottish Gaelic
Kevin Scannell
and I'm helping the lead translator get set up for maintaining this in
the long term.
I originally gave him the PO files we use for Irish to translate and
then I used the translate-toolkit to generate the tree with .dtd and
.properties files - that's about to be committed to Mercurial. For
various reasons I think Narro would be a better choice than PO files
in this particular case.
Is it possible to import translations from an existing tree (.dtd and
.properties) into Narro? If so, could a project be set up for this
language, please? Language code is "gd", our contact info is here:
https://wiki.mozilla.org/L10n:Teams:gd
Kevin
Alexandru Szasz
Hi Kevin,
I added the language.
Please send me the files or give me a link to them, and also a username
so I can give you extra rights.
--
Alexandru Szasz
Kevin Scannell
> Pe 20.04.2010 20:10, Kevin Scannell a scris:
>>
>> A localization of Firefox into Scottish Gaelic is nearing completion
>> and I'm helping the lead translator get set up for maintaining this in
>> the long term.
>>
>
> Hi Kevin,
>
> I added the language.
> Please send me the files or give me a link to them, and also a username so I
> can give you extra rights.
>
Thanks!
Here are the translated files:
http://borel.slu.edu/obair/gd.tar.gz
I'll write off list about usernames, permissions after I talk with the
other team member.
Kevin
Axel Hecht
Could we bootstrap the narro instance from what I land on hg? I'm not
sure yet, but there's some likelyhood that there are edits and/or tweaks
to be made on initial landing, and narro doesn't really roundtrip nicely
when you do edits in hg, and not in narro. At least that's as much as I
know.
Axel
Alexandru Szasz
what's exported from Narro on a fresh clone from hg there won't ever be
problems, that's the future plan to do it automatically from Narro.
I had the hg import going for the target language as well in the
begining, getting edits from two different sources doesn't bring
conflicts in Narro but you might have a ping pong effect, somebody
translates File to Disk in hg and somebody else translates File to Unit
in Narro.
Both translations will be kept, but the import is ran by default with
--approve so the most recent import or approval in Narro will win.
So it might be better to just provide an option to import the
translations from Mercurial in the import page.
--
Alexandru Szasz
Axel Hecht
Sounds like a good idea, yeah.
Axel
Tim Chien (MozTW)
I think Narro should provide two import options, "Pull latest changes
from en-US", "Pull latest changes from en-US and attempt to merge
existing translations from locale dir".
The current import function could do both of things, if clean up the
locale dir before clicking import, but that's quite confusing. (By
clean up I mean clicking "export" to overwrite old translations in the
dir or simply remove the files)
Also, the current dir structure design makes it hard to bootstrap a
localization; you have to figure out which /???/locales/en-US to put
into the Narro en-US directory yourself and the respective locale
directory structure. I did this by clone en-US hg repo then soft link
the directories, and all of these are currently manual.
Tim
On Wed, Apr 21, 2010 at 12:55 PM, Alexandru Szasz <ale...@gmail.com> wrote:
> Pe 21.04.2010 02:18, Axel Hecht a scris:
>>
> The idea in Narro is to keep it simple, so if you always overwrite what's
> exported from Narro on a fresh clone from hg there won't ever be problems,
> that's the future plan to do it automatically from Narro.
>
> I had the hg import going for the target language as well in the begining,
> getting edits from two different sources doesn't bring conflicts in Narro
> but you might have a ping pong effect, somebody translates File to Disk in
> hg and somebody else translates File to Unit in Narro.
> Both translations will be kept, but the import is ran by default with
> --approve so the most recent import or approval in Narro will win.
>
> So it might be better to just provide an option to import the translations
> from Mercurial in the import page.
>
> --
> Alexandru Szasz
> _______________________________________________
> dev-l10n mailing list
> dev-...@lists.mozilla.org
> https://lists.mozilla.org/listinfo/dev-l10n
>
Alexandru Szasz
> Alexandru,
>
> I think Narro should provide two import options, "Pull latest changes
> from en-US", "Pull latest changes from en-US and attempt to merge
> existing translations from locale dir".
>
> The current import function could do both of things, if clean up the
> locale dir before clicking import, but that's quite confusing. (By
> clean up I mean clicking "export" to overwrite old translations in the
> dir or simply remove the files)
>
> Also, the current dir structure design makes it hard to bootstrap a
> localization; you have to figure out which /???/locales/en-US to put
> into the Narro en-US directory yourself and the respective locale
> directory structure. I did this by clone en-US hg repo then soft link
> the directories, and all of these are currently manual.
>
Hi Tim,
The cleanup button just removes all files from the export dir.
Some options are coming in the long awaited version 1.0.
I'm adding several sources, including Mercurial for importing. Hopefully
exporting also.
From what you're saying I see also an option to scan a mozilla tree for
l10n.ini files to see where the sources are.
Also Narro will be more flexible about the locale dir. So if you upload
a extension, in .xpi format, Narro will scan it until it finds a en-US
folder and switch to that before importing.
>
> Tim
>
>
> On Wed, Apr 21, 2010 at 12:55 PM, Alexandru Szasz<ale...@gmail.com> wrote:
>
>> Pe 21.04.2010 02:18, Axel Hecht a scris:
>>
>> The idea in Narro is to keep it simple, so if you always overwrite what's
>> exported from Narro on a fresh clone from hg there won't ever be problems,
>> that's the future plan to do it automatically from Narro.
>>
>> I had the hg import going for the target language as well in the begining,
>> getting edits from two different sources doesn't bring conflicts in Narro
>> but you might have a ping pong effect, somebody translates File to Disk in
>> hg and somebody else translates File to Unit in Narro.
>> Both translations will be kept, but the import is ran by default with
>> --approve so the most recent import or approval in Narro will win.
>>
>> So it might be better to just provide an option to import the translations
>> from Mercurial in the import page.
>>
>> --
>> Alexandru Szasz
>> _______________________________________________
>> dev-l10n mailing list
>> dev-...@lists.mozilla.org
>> https://lists.mozilla.org/listinfo/dev-l10n
>>
>>
--
Alexandru Szasz