diff --git a/l10n/tools/moz2embed/lev_xlation.html b/l10n/tools/moz2embed/lev_xlation.html
index 041e79b896c..e69de29bb2d 100644
--- a/l10n/tools/moz2embed/lev_xlation.html
+++ b/l10n/tools/moz2embed/lev_xlation.html
@@ -1,189 +0,0 @@
-
-
-
-
- How to create a localized embed.jar from existing translation
-
-
-
-
-
-
-
-How to create a localized embed.jar from
- existing translation
-
-
-
-
-
-History
-
-
- - 2002-08-02: refer to README for updated procedure.
-
- - 2002-06-25: added note of partial automation
-
- - 2002-06-24: 1 st version
-
-
-
-
-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):
-
-
- - en-US.jar and en-win.jar from the English US build
- - embed.jar and installed-chrome.txt from the embedding build off
- 2002-05-12's mozilla pull.
-
-
-
-
-Procedure (I use unix cmd; current working directory is workspace/)
-Option 1: read README for more automated process.
-
-Option 2: less automated approach
-
-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
-
-
- - workspace > unzip embed.jar -d
- embed_jar
- - workspace > unzip en-US.jar -d
- en-US_jar
- - workspace > unzip en-win.jar -d en-US_jar
- - workspace > unzip ja-JP.jar -d
- ja-JP_jar
- - workspace > unzip ja-win.jar -d ja-JP_jar
- - workspace > diff --brief embed_jar/locale en-US_jar/locale
- > locDiff.txt
-
-
- 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
-
-
- - workspace > mkdir embed-ja-JP
- - workspace > cp embed_jar/{skin,content} embed-ja-JP
-
-
- Then
-
-
- - copy Japanese version of "en_same" from ja-JP_jar into embed-ja-JP
- - copy "en_diff" from embed_jar/locale
- into embed-ja-JP/locale
-
-
- Note that for this last step, you can automate
-it with make-jars.pl (one of Mozilla's build tools) & jar.mn
-
-
- - workspace > make-jars.pl -s ja-JP_jar < jar.mn
- - workspace > unzip embed.jar -d embed-ja-JP
- - workspace > rm embed.jar
-
-
-
- 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
-
- - workspace > cd embed-ja-JP/
- - workspace > zip embed.jar -r content
- skin locale
-
-
- 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.
-
-
-
-
-
-
-
-