[ANNOUNCE] Localizing Firefox Home Application
Seth Bindernagel
The Firefox Home developer team (Dan and Ragavan copied here) would like
to open its project for localization. This will be a one-offf
experience for us that will require doing most of our work in
text-editors and Bugzilla due to the unique nature of Apple's
localization process.
I have begun to file tracking bugs for the project, with one master
tracking bug (https://bugzilla.mozilla.org/show_bug.cgi?id=583241) and
per-locale trackers blocking that.
We will localize the application, the Mozilla-based website describing
the app, the iTunes App Store description, and some other pieces. Bugs
will be filed for each, blocking your locale's tracker. In each bug, we
will explain what is necessary including things like due dates. In all
likelihood, I will follow up with posts to this newsgroup with other
information.
The Firefox Home team specified a few locales that they would like to
have based on immediate demand they have received. Those locales include:
* de - German
* es-ES - Spanish
* fr French
* it - Italian
* ja - Japanese
* nl- Dutch
* zh-CN Chinese
If your locale is not listed and you would like to participate, please
email me and I will ask the dev team (Dan and Ragavan) if the iPhone
platform allows for localization into your language. Dan and Ragavan
will also be tracking the bugs and will be available alongside the
l10n-drivers to help answer any technical questions about the work,
testing, etc.
We are targeting the Firefox Home 1.1 release, which is scheduled for
approval and release in the next 4-5 weeks, sometime in early September.
I can answer questions as they come up, just ask. If I don't have an
answer, it's probably due to the unique nature of this project.
FYI - you are all awesome.
Best regards,
Seth
文少华
It seems the strings in file
Strings/English.lproj/Localizable.strings are aggregated from files in
/L10N Strings. I guess that Localizable.strings is the only one file
that we need to translate, right?
The Localizable.strings file is encoded as UTF-16. I think we night
need to keep the encoding as it is.
BR.
Holy
> _______________________________________________
> dev-l10n mailing list
> dev-...@lists.mozilla.org
> https://lists.mozilla.org/listinfo/dev-l10n
>
Danishka Navin
Guillermo Movia
There's Iphone in Argentina, but I don't know if it's a different locale
than es-ES. But we could help in testing, if it's needed.
Guillermo
Channy Yun
Thanks,
Channy
---------------------
http://www.linkedin.com/in/channy
* Biomedical Knowledge Engineering Laboratory http://bike.snu.ac.kr
* Daum Developers Network & Affiliates http://dna.daum.net
2010/7/31 Seth Bindernagel <se...@mozilla.com>
Dwayne Bailey
> Hi Everyone,
>
> The Firefox Home developer team (Dan and Ragavan copied here) would like
> to open its project for localization. This will be a one-offf
> experience for us that will require doing most of our work in
> text-editors and Bugzilla due to the unique nature of Apple's
> localization process.
Although the App localisation has stopped for now, a heads up to let you
know that the .strings files can be localised using PO files.
I spoke to Dan at the Summit and said I'd look at ensuring that the
Translate Toolkit (moz2po and friends) can handle these files.
I've updated the Translate Toolkits prop2po converter to handle Mac OS
X .strings files. I've just tested it in the Firefox Home .strings
files and it works perfectly. It hides the UTF-16 text from you, ensures
that you can't break the file and does all the right escaping when
needed. So you can safely edit this in a PO editor and the back
converter will handle the format's specifics.
This is not in any released version of the Toolkit yet I'm afraid. So I
will post the POT files on
https://bugzilla.mozilla.org/show_bug.cgi?id=583241 for you to study.
Its only 118 words of text to translate, so although the app isn't going
to localised just yet I'm sure many of you will do that in less then an
hour. You'll be able to update it easily when the strings are frozen.
--
Dwayne Bailey
Associate Research Director +27 12 460 1095 (w)
Translate.org.za ANLoc +27 83 443 7114 (c)
Recent blog posts:
* What's new in Virtaal 0.6.1
http://www.translate.org.za/blogs/dwayne/en/content/whats-new-virtaal-061
* Localisation: How we guess the target translation language in Virtaal
* Continuous integration, can it work for software localisation?
Firefox web browser in Afrikaans - http://af.www.mozilla.com/af/
African Network for Localisation (ANLoc) - http://africanlocalisation.net/
Seth Bindernagel
Just a reminder that we are not string frozen yet.
But, just to answer your questions below, I emailed Dan W and asked him
to confirm that we need to localize all the files, not just
Localizable.strings. He confirmed that both all the files in L10N
Strings, and the Localizable.strings file need localization.
Also, all strings are encoded in UTF-16 and you should keep that encoding.
Thanks for the questions.
Seth
文少华 wrote:
> Hi,
> It seems the strings in file
> Strings/English.lproj/Localizable.strings are aggregated from files in
> /L10N Strings. I guess that Localizable.strings is the only one file
> that we need to translate, right?
> The Localizable.strings file is encoded as UTF-16. I think we night
> need to keep the encoding as it is.
> BR.
> Holy
>
> On Fri, Jul 30, 2010 at 11:29 PM, Seth Bindernagel<se...@mozilla.com> wrote:
>> Hi Everyone,
>>
>> The Firefox Home developer team (Dan and Ragavan copied here) would like to
>> open its project for localization. This will be a one-offf experience for
>> us that will require doing most of our work in text-editors and Bugzilla due
>> to the unique nature of Apple's localization process.
>>
dynamis
SUMO KB pages are already translated (some are under final review):
https://support.mozilla.com/ja/kb/Firefox+Home+does+not+work
https://support.mozilla.com/ja/kb/Replace+your+Sync+information
https://support.mozilla.com/ja/kb/How+to+set+up+Firefox+Home+on+your+iPhone
https://support.mozilla.com/ja/kb/How+to+use+Firefox+Home
https://support.mozilla.com/ja/kb/Cannot+log+in+to+Firefox+Home+App
https://support.mozilla.com/ja/kb/What+is+Firefox+Sync
https://support.mozilla.com/ja/kb/How+to+sync+Firefox+settings+between+computers
Translation of mozilla.jp site are also ready to open in mozilla.jp.
Only thing we haven't translated yet is, just UI of the App itself. ;)
marcoos
> The Firefox Home team specified a few locales that they would like to
> have based on immediate demand they have received. Those locales include:
>
> * de - German
> * es-ES - Spanish
> * fr French
> * it - Italian
> * ja - Japanese
> * nl- Dutch
> * zh-CN Chinese
pl would like to opt-in.
I think iOS is a big enough platform in Poland to be supported (ca.
20% mobile marketshare @ http://ranking.pl/en/rankings/mobile-devices-producers.html)
:)
Bob Chao
Do we still need to "opt-in" if my locale did not listed here? Or maybe you
can simply open bugs for the locales Apple Store supported, and update the
content when a locale team finish the work?
~Bob
> _______________________________________________
> dev-l10n mailing list
> dev-...@lists.mozilla.org
> https://lists.mozilla.org/listinfo/dev-l10n
>
--
Po-chiang Chao (:BobChao)
Community Liaison,
MozTW (Mozilla Taiwan) Community http://moztw.org
Seth Bindernagel
the string freeze date happens. I have collected interest from the
following additional locales from my starting:
* zh-TW (Traditional Chinese),
* es-AR (Argentina Spanish),
* ko (Korean)
* si (Sinhala), and
* ca (Catalan)
The dev team has told me that "we can localize to any language we want,
but if it is not a locale supported by the OS, it will have no effect"
so I am presently researching whether all these languages are
supported. I need to confirm it with some Apple folk, but I believe
they all are except es-AR. I believe Apple uses Spanish and Mexican
Spanish.
Bob Chao wrote:
> Hi Seth,
>
> Do we still need to "opt-in" if my locale did not listed here? Or
> maybe you can simply open bugs for the locales Apple Store supported,
> and update the content when a locale team finish the work?
>
> ~Bob
>
> On Wed, Aug 4, 2010 at 5:20 AM, marcoos <marek....@gmail.com
> <mailto:marek....@gmail.com>> wrote:
>
> On 30 Lip, 17:29, Seth Bindernagel <se...@mozilla.com
> marcoos.com <http://marcoos.com>
> _______________________________________________
> dev-l10n mailing list
> dev-...@lists.mozilla.org <mailto:dev-...@lists.mozilla.org>
Seth Bindernagel
Seth Bindernagel wrote:
> I will be filing bugs for the additional work and re-announcing when
> the string freeze date happens. I have collected interest from the
> following additional locales from my starting:
>
> * zh-TW (Traditional Chinese),
> * es-AR (Argentina Spanish),
> * ko (Korean)
> * si (Sinhala), and
> * ca (Catalan)
>
> The dev team has told me that "we can localize to any language we
> want, but if it is not a locale supported by the OS, it will have no
> effect" so I am presently researching whether all these languages are
> supported. I need to confirm it with some Apple folk, but I believe
> they all are except es-AR. I believe Apple uses Spanish and Mexican
> Spanish.
>
> Bob Chao wrote:
>> Hi Seth,
>>
>> Do we still need to "opt-in" if my locale did not listed here? Or
>> maybe you can simply open bugs for the locales Apple Store supported,
>> and update the content when a locale team finish the work?
>>
>> ~Bob
>>
>> On Wed, Aug 4, 2010 at 5:20 AM, marcoos <marek....@gmail.com
>> <mailto:marek....@gmail.com>> wrote:
>>
>> On 30 Lip, 17:29, Seth Bindernagel <se...@mozilla.com
>> marcoos.com <http://marcoos.com>
>> _______________________________________________
>> dev-l10n mailing list
>> dev-...@lists.mozilla.org <mailto:dev-...@lists.mozilla.org>
>> https://lists.mozilla.org/listinfo/dev-l10n
>>
>>
>>
>>
>> --
>> Po-chiang Chao (:BobChao)
>> Community Liaison,
>> MozTW (Mozilla Taiwan) Community http://moztw.org
>>
> _______________________________________________
> dev-l10n mailing list
> dev-...@lists.mozilla.org
Selim Şumlu
A bit late, but we are also interested in a Turkish (tr) locale. And I
can confirm that iOS supports it.