585270 - [ko] Localize the Firefox Home iPhone application strings into Korean

Status: RESOLVED FIXED

(Mozilla Localizations :: ko / Korean, 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

[Channy Yun [:channy]]

Attachment: Korean(ko) translation for Firefox Home

Comment 2

[Channy Yun [:channy]]

Fixed by adding translations in attached file.

Comment 3

[Seth Bindernagel]

Hi Channy,

We have spotted a bug in your Firefox Home localization, where it appears that you copied and pasted "Firefox Home을" into a string that contains Firefox Sync in English.

Line 38 of Welcomepage.xib.strings

Can you make the fix and reattach the new file.  You can probably send us just the Welcomepage.xib.strings file.

Comment 4

[Channy Yun [:channy]]

Oh I see. You can just replace "Firefox Home을" => "Firefox Sync를".

Comment 5

[Channy Yun [:channy]]

Attachment: Fixed line 38 in Localizable.strings

Comment 6

[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 7

[Channy Yun [:channy]]

= Strings =

/* 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" = "서버 URL"

Comment 8

[Seth Bindernagel]

Closing again.  Thanks for working so quickly.

Comment 9

[Channy Yun [:channy]]

I checked Firefox Home via VNC viewer. But, there is small change in Main Window.strings.

I guess 
/* Class = "IBUINavigationItem"; title = "Bookmarks"; ObjectID = "91"; */
"91.title" = "책갈피";

But, it must be
/* Class = "IBUINavigationItem"; title = "Bookmarks"; ObjectID = "91"; */
"91.title" = "북마크";

"책갈피" is pure Korean world for bookmark. But we used "북마크" instead of. Please check it.

Comment 10

[Dan Walkowski]

I'm sorry, but the bookmark icon at the bottom of the screen is a System Icon provided by Apple, and is automatically localized by operating system.  I cannot change it.

Comment 11

[Channy Yun [:channy]]

I see. iPhone uses old term different from Firefox. It breaks consistency with Firefox. It's hard to change all terms for bookmarks in Firefox Home. Is there any solution?

Comment 12

[Seth Bindernagel]

(In reply to comment #11)
> I see. iPhone uses old term different from Firefox. It breaks consistency with
> Firefox. It's hard to change all terms for bookmarks in Firefox Home. Is there
> any solution?

I believe I saw a comment in the French bug where Dan explained that the term bookmarks is a system wide iPhone term that they do not allow for customization.

Here is the comment:

https://bugzilla.mozilla.org/show_bug.cgi?id=583250#c15

Comment 13

[Seth Bindernagel]

Sorry...I didn't realize Dan had already responded in Comment 10.  Apologies for the spam.

Comment 14

[Channy Yun [:channy]]

Hmm. Let's discuss later in this issue and release first.

Comment 15

[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 16

[Seth Bindernagel]

Ping.  We will need to gather all of these translations by Wednesday, Sept 29, 17:00 PDT (UTC -7).  Please let me know if you can make it.

Comment 17

[Channy Yun [:channy]]

Seth, I cannot check string changes because my locale was not updated in https://localize.mozilla.org/ko/fxhome/. Would you update Korean translated strings to Verbatim?

Comment 18

[Seth Bindernagel]

Gandalf, can you help Channy by merging his prior translation into Verbatim?  He cannot complete the work until we do that for him.  His earlier translations should be attached to this bug.

Comment 19

[Seth Bindernagel]

Or, Channy, you can download from Verbatim the LoginController.xib.strings.po and the Localizable.strings.po files and those should contain all the new words needing attention.  If you're using a PO editor, it should be able to identify the new words needing attention...I think.  :)

https://localize.mozilla.org/ko/fxhome/LC_MESSAGES/

Comment 20

[Channy Yun [:channy]]

Attachment: Two files for fxhome-1.0.3

Seth, I added above two translated files as you assigned.

Comment 21

[Seth Bindernagel]

Thanks, Channy.  Marking this bug fixed for now.

Comment 22

[Seth Bindernagel]

Channy, do you have fxhome-1.0.2 files in .po format or did you do everything directly in the .strings format?

Comment 23

[Channy Yun [:channy]]

I don't have po format except above two files. The rest are .strings format in attached files. Do you need to get all localized .po files?

Comment 24

[Seth Bindernagel]

No need, I was able to convert everything with the translate toolkit and update verbatim with your most recent work.  Thanks, Channy!