From ca7f0881868384c37790d978dd5246fb54baf56c Mon Sep 17 00:00:00 2001 From: "tao%netscape.com" Date: Thu, 25 Jul 2002 17:38:28 +0000 Subject: [PATCH] Update instructions in README and provide link to a new file, leve-xlation.html which has more explanation. --- l10n/tools/moz2embed/README | 28 +++- l10n/tools/moz2embed/lev_xlation.html | 179 ++++++++++++++++++++++++++ 2 files changed, 202 insertions(+), 5 deletions(-) create mode 100644 l10n/tools/moz2embed/lev_xlation.html diff --git a/l10n/tools/moz2embed/README b/l10n/tools/moz2embed/README index aa3721f34cd9..0c3c954f8b13 100644 --- a/l10n/tools/moz2embed/README +++ b/l10n/tools/moz2embed/README @@ -38,9 +38,27 @@ # Author: Tao Cheng # Date : July 22, 2002 # -# Run the main script, "make-l10n-jar.sh", to leverage translations from the -# language packs of existing localized Netscape 7.0 client. +# Instructions: leverage translations from de-FG into English embed.jar +# 1. create a working directory, "workspace". Change directory to it. +# 2. expand the English embed.jar into a subdirectory, "embed_jar". +# 3. expand the localized jars, says de-FG.jar and de-win.jar into +# "de-FG_jar". +# 4. expand the en-US.jar and en-win.jar (from which the de-FG.jar and +# de-win.jar localized from) into "en-US_jar". +# 5. update the jar manifest template, "jar.mn-ab-CD": +# a. compare files between "embed_jar/" and "en-US_jar/". +# b. ignore the files exist in "en-US_jar/" only. +# c. look at the list of differed files to see they do need localization. +# d. update the template, "jar.mn-ab-CD", to reflect what files can be +# copied from "embed_jar/" into the "embed_jar-de-FG/" and what files +# to be leveraged from "de-FG_jar/" +# 6. Run the main script, "make-l10n-jar.sh", to leverage translations from the +# language packs of existing localized Netscape 7.0 client. # -run> make-l10n-jar.sh ${langcode} ver1 ver2 - # this will produce embed.jar-${langcode} & installed-chrome.txt-${langcode} - # and leverage ... see comments in make-l10n-jar.sh +# run> make-l10n-jar.sh de-FG ver1 ver2 +# where ver1 is the localeVersion # of the de-FG.jar +# ver2 is the localeVersion # of the English embed.jar +# This will produce embed.jar-${langcode} & installed-chrome.txt-${langcode} +# and leverage ... see comments in make-l10n-jar.sh +# +# Please refer to lev-xlation.html for details. diff --git a/l10n/tools/moz2embed/lev_xlation.html b/l10n/tools/moz2embed/lev_xlation.html new file mode 100644 index 000000000000..0baa91a13dbe --- /dev/null +++ b/l10n/tools/moz2embed/lev_xlation.html @@ -0,0 +1,179 @@ + + + + + How to create a localized embed.jar from existing translation + + + + + + + +
How to create a localized embed.jar from + existing translation
+
+ +


+

+ +

History

+ + + +

Assumption
+

+ You have a pair of localized browser's jar files in Japanese, ja-JP.jar + and ja-win.jar, based off the N7.0 PR1 (2002-05-12) build. You would like + to create an embed.jar of the same day from it. For T-Bird, you need ja-mac.jar + instead of ja-win.jar.
+ +

What you need

+ All the following jar files from the same day (2002-05-12):
+ + + +

Procedure (I use unix cmd; current working directory is workspace/)

+ Find out what's the difference between the English embed.jar and browser + jar files, en-US.jar and en-win.jar. Expand embed.jar into embed_jar folder + and en-US_jar.
+
+ 1. Find out what files are different first. Jar files are zip archives
+ + + You will find some files exist in embed_jar only + and the others exist in en-US_jar only.
+
+ 2. For the files are different, find out if they need translation at +all
+
+ There should be only a few files are different. Let me name those files, + "en_diff". The rest of exactly the same. Let me call them "en_same". + For PR1, I found only 5 files in "en_diff";  four of them do + not need translation. I only needed to manually edit navigator.properties + to copy/paste localized resources from ja-JP directory. To automate this + process, you can write a small app or perl script to replace resource values + in the English version with those from the localized version.
+
+ 3. Prepare the files/directory for localized embed.jar
+
+ Copy skin and content files first
+ + + Then
+ + + Note that for this last step, you can automate it +with make-jars.pl (one of Mozilla's build tools) & jar.mn
+ + + 4. In embed-ja-JP/locale, open "navigator.properties" + to replace resource values from localized resources in "navigator.properties" + in the  ja-JP_jar directory. To automate + this process, you can write a small app or perl script.
+
+ 5. Repackage them with zip + + 6. Replace all "en-US" strings in installed-chrome.txt with the new language + code, "ja-JP". You are done!
+
+ +

Questions

+ Feel free to contact + me for questions.
+
+
+
+
+ +