585274 - [zh-TW] Localize the Firefox Home iPhone application strings into Chinese (Traditional)

Status: RESOLVED FIXED

(Mozilla Localizations :: zh-TW / Chinese (Traditional), defect)

Description

[Seth Bindernagel]

The Firefox Home Application for the 1.0.2 release is string frozen and the strings are now loaded in Verbatim.  

http://localize.mozilla.org/projects/fxhome/

You can translate the app using Verbatim, though in this case, you cannot commit directly to the version control system.  Instead, we will take the PO file from Verbatim and convert it back to the original file format.  If you use verbatim, just translate and let us know when you are finished.

If you choose not to use Verbatim, then continue reading.

In Bug 583241, you will find a ZIP containing the files needing localization
for the iPhone Firefox Home application.

Please download that and unzip to see the folders "Strings" and "L10n Strings".
 These folders contain all the files that need l10n.  We will need a copy of
each of the files back with the values of all the entities set to the localized
string.  Please keep the files in UTF-16 encoding.

Specifically, in the "Strings" folder, there is the "English.lproj" folder with
a file called "Localizable.strings".  That file contains the code-based strings
that need translation.  You will see entities like

/* bookmarks menu */
"Bookmarks Menu" = "Bookmarks Menu";

You should translate the string values in the last set of quotations preceding
the semi-colon.  For example, your translation should look like this:

/* bookmarks menu */
"Bookmarks Menu" = "foo bar";

Please translate each entity and save the file in your local folder, not
changing the file name.

In "L10n Strings", you will find several files containing xib-based strings. 
Much like the above, you will see entities in each of these files.  Those
entities look like the following:

/* Class = "IBUIButton"; normalTitle = "Send Me Instructions"; ObjectID = "7";
*/
"7.normalTitle" = "Send Me Instructions";

You should translate the string values in the last set of quotations preceding
the final semi-colon.  For example, your translation should look like this:

/* Class = "IBUIButton"; normalTitle = "Send Me Instructions"; ObjectID = "7";
*/
"7.normalTitle" = "foo bar";

Please translate each entity and save the files in your local folder, not
changing any of the file names.

As you can see, these files look a lot like property files. 

Please reattach a ZIP of all files to this bug when finished.

Further notes of interest:  

All Mac/iPhone localization is done using 'strings' files, which, as just
mentioned, are basically just property files.  All of the localized files get
built into the the binary, and are chosen by matching the ISO 639-1 or 639-2
codes and loading the appropriate file at runtime.

Special request from the dev team:  The size of the strings may be an issue. 
To the extent possible, it would be very helpful if the localized strings were
approximately the same length as the English strings (or shorter).  In many
languages, this will not be realistic, so do the best you can.  

For testing, Dan Walkowsi, copied on this bug, will provide you with a
customized build that you can install on an iPhone.  The dev team is assuming
that someone in your locale has an iPhone to test this app.  If not, please let
us know.

Comment 1

[Peter Pin-Guang Chen [:petercpg] (MozTW.org)]

The strings are uploaded to Verbatim and I have made the review.

Credit goes to Cynthia Ho <transcyn1001 [AT] gmail.com>.

Comment 2

[Seth Bindernagel]

The developer team has discovered a very small set of strings that were missed in the first round of localization because the strings are not actually part of our application.  They are in a small plugin for the OS, which has some advanced settings for Firefox Home.

The file is an XML file where you have to change four strings wrapped in the second set of quotes that serve the value of the English string name.  Example: 

/* this is an example */
"foo" = "foo"

You should translate the second "foo" so that translation might look like this:

/* this is an example */
"foo" = "bar"

Because there are only four strings, we have chosen to send the strings directly via Bugzilla.  The dev team will copy/paste them into the files by hand once we can get them back from the you.

Please translate the following strings in the next comment of this bug.

= Strings =

/* this is a label for the version number of Firefox Home */
"Version" = "Version"

/* this is a warning that this setting should only be used by advanced 
users */
"Caution: use at your own risk" = "Caution: use at your own risk"

/* this is a label for an on/off switch to enable the use of a custom 
Firefox Sync server */
"Use Custom Server" = "Use Custom Server"

/* this is a label for a text field to enter the url of the custom server */
"Server URL" = "Server URL"

Comment 3

[Peter Pin-Guang Chen [:petercpg] (MozTW.org)]

* this is a label for the version number of Firefox Home */
"Version" = "版本"

/* this is a warning that this setting should only be used by advanced 
users */
"Caution: use at your own risk" = "注意：請自行負責"

/* this is a label for an on/off switch to enable the use of a custom 
Firefox Sync server */
"Use Custom Server" = "使用自訂伺服器"

/* this is a label for a text field to enter the url of the custom server */
"Server URL" = "伺服器網址"

Comment 4

[Seth Bindernagel]

Thanks for translating this and working so quickly.  Closing this bug as fixed.

Comment 5

[Seth Bindernagel]

Firefox 1.0.3 will ship with some new string changes.  You can find changes here:  https://localize.mozilla.org/projects/fxhome/

It's likely that you read Gandalf's note in the newsgroup.  

http://groups.google.com/group/mozilla.dev.l10n/msg/f9e45c8bd06113f4

I have reopened this bug to track open tasks.  If you have finished the translation, please close this bug.  If you have not finished the work, please close this bug when you are finished.

Comment 6

[Peter Pin-Guang Chen [:petercpg] (MozTW.org)]

I've update the strings few hours ago. I think it's okay to mark this Bug as FIXED.

Comment 7

[Seth Bindernagel]

Marking fixed.