Thank you to all!!!!!
Since you're not sure you're going to be the one who finishes it, you
might consider Narro (
https://l10n.mozilla.org/narro/narro_project_list.php?l=la ). You can
translate online, others can help you and you can get a working
language pack with no fuss.
I've translate (I think) a few strings from Narro (
https://l10n.mozilla.org/narro/narro_project_text_list.php?l=la&p=5&tf=3&st=1&s=
), but you can work on Firefox 3.
If you decide to use it let me know so I can give you rights to
approve. Firefox in Latin sure sounds interesting.
--
Alexandru Szasz
I think it is a good tool, however the first objective must to be
Firefox 3.x; surely not Firefox 3.0.x.
Thanks for your tool.
I renew the call for participation in this project!!!!
You can translate which version you like, but it's harder to test 3.1
since it's not out yet and it will take a while before people will
actually use it (after extensions get updated).
--
Alexandru Szasz
The 3.1b2 is out with binaries, then we can start directly with it.
Ok, we can start with FF 3.0.x, and then modify it to FF 3.x. On
Narro, the FF 3.0.x branch look like complete, is correct?
If yes, I can start to translate something.
You can start with 3 and export what's done in 3.1. Since there are
more users of Firefox 3 now, I expect you will have more feedback if
the language pack is installable on their version. Moving to 3.1 won't
take long, just a few new strings and approving some strings that
moved around.
I gave you some extra permissions on Latin language, you need to login again.
Everytime you export the project there's a xpi language pack on the
project list that you can install in Firefox.
Then type about:config in the address bar, filter for
"useragent.locale" and change "en-US" or what's there with "la". Or
use an extension to do this.
--
Alexandru Szasz
Ok, thanks.
FWIW, 3.0 doesn't matter anymore in terms of what we're looking at for
taking in as official releases.
3.1 is not just a few strings away, but a few hundred strings away, and
depending on your speed, you might have wasted time a few deprecated
strings.
If you're interested in getting an official localization for Firefox,
https://wiki.mozilla.org/L10n:Localization_Process is the guiding document.
Axel
Hey everyone:
Please allow me to re-emphasize Axel's point. We are on the Firefox 3.1
release cycle right now. For those starting a localization from the
beginning, I recommend starting with Firefox 3.1. As Axel mentions,
there are more than a couple hundred strings difference between Firefox
3 and 3.1. Plus, it is likely that you will finish your translation
either by Firefox 3.1 Beta 4 or after that. If you'd like to
participate as an official localization, you should plan on shipping
Firefox 3.1.
Following the existing documentation about the process will help provide
the most clarity about what steps to take. In addition to Axel's link
above, you will find this main site helpful:
As you move through the process, you'll need to also discuss localized
web parts and services with Pascal and Stas. These are two helpful site
for that:
https://wiki.mozilla.org/L10n:Web_parts
https://wiki.mozilla.org/Firefox_web_services_guidelines
If you have any questions as you move through the process, please don't
hesitate to ask on this newsgroup.
Alexandru, thanks for your continued support to localizers with Narro.
I know many of our community members are using it to translate. Can you
enable alessiogiov...@gmail.com (sorry, did not have a name) to
localize FF 3.1 on Narro? (if he chooses to use the tool to localize)
Thanks everyone,
Sure, he can translate any project that's listed there.
For 3.1 language packs, he can use the files here to match the
language packs generated in Narro:
http://ftp.mozilla.org/pub/mozilla.org/firefox/nightly/latest-mozilla-1.9.1/
This is until beta 3 is officially out.
I don't know about other people, but I can't translate without seeing
once in a while how the translated product looks like.
--
Alexandru Szasz
Well, you don't have to link to latest, you can link to a dated nightly
dir. How often do you update the in-development en-US trees in narro?
Axel
Every two days. You have a point there, I could show a link to the
dated nightly.
--
Alexandru Szasz
A question: when you update the tree, if there are conflicts? For
example, if a file is modified, we lost the translation?
Thanks.
If the context is modified (text was moved in another file, key
changed) you just have to approve it again, translations are deleted
only manually and are associated with texts, not with contexts.
--
Alexandru Szasz