MozillaTranslator

Version 3.1 (Feb. 21, 2000)

1. Open a view and select a Entry (equal a row)
2. In the functions dialog choose "Edit Entry" and this will bring up the dialog.

• The program no longer inserts the localization note "no loc note" to every Entry it add's should have a couple of kilobytes in the glossary file.

Version 3 (Feb. 16, 2000)

Features

• Glossary files that support multiple locales, QA support , and localization notes.
• Different views. In V2 there was only the chrome view of the entries and you had to hunt entries down in their specific files. Now there is also a "View untranslated entries" ,  "view redundant entries" and a "view entries with keep original flag set".
• Support for keeping the glossary in sync with the actual chrome, simply select "Update glossary" and everything is done. new entries   added, modified entries corrected and old ones removed.
• Support for import and export of partial glossary files, that only contain the translated text the QA status&comment for a single locale.
• Only need to save the glossary at the end of a session.

Licence

There has been a small change in the licence. While it is still under the MPL, it has dual licenced under the PostCard-licence which goes:
 
"If you use this program, you are encuraged but not requireed to send a snail mail postcard from your part of the world to the auther."


This is merely for fun, but if you wanna play along email me for the mailing address.

System requirements:

• a Mozilla Installation nightly or MileStone
• a java 2 compliant JVM, on windows I recommend the Java 2 SDK 1.3 Release Candiate (java.sun.com)

Installation

• copy the jar file to the harddrive
• delete any files left from V2 (the properties files are not compatible)
• if you are running it on windows, you can download the Run.bat file,so yopu don't have to use the command file

Starting the program

Assuming windows here, other platform should only differ slightly)
• either use the run.bat file (if on windows); or,
• assign the file extention "*.jar" to "java.exe -jar " from the jvm, and you can now just doubleClick on the jar file. (thanx datavanquiser); or,
• assuming that PATH is set to point at java.exe use one of the following commands from a dos prompt
• java -jar MozillaTranslator.jar   (or)
• java -cp MozillaTranslator.jar org.mozilla.translator.kernel.Program

Usage

When the program is started it loads the glossary file if it exists and if it doesn't it will build one from the chrome. The first time the program is launhed (or whenever it can't find mozillatranslator.properties)  it will ask for the placement of the chrome. Then there is the following posibilities for you
• "manage filters" manage your filters and a filter is a rule it uses to test if the Keep original flag should be set when an entry is created
• "Quit" quits the program REMEMBER TO SAVE YOUR GLOSSARY FILE FIRST!!!!!!!!!!!
• "Update glossary" use this if you have downloaded a new version of mozilla. It will syncronize the entries in the glossary with the new chrome.
• "save glossary" saves the glossary to the disk (file = glossary.zip).
• REMEMBER TO SAVE YOUR GLOSSARY FILE BEFORE QUITEING!!!!
• "import locale from chrome" this will read another locale in from the chrome (this to import a translation from before V3)
• "export locale to chrome" writes out the files in the destination locale. it will take all the translated string and build the files that make up the chrome. if a entry has the keep original flag set it will use the original string instead. if there are unstranslated strings then their original text will be used and a warning printed.WARNING: the folder for the files need to be present otherwise it will fail.
• "import locale from glossary" this will import a previously exported partial glossary file, it will use the translated text in the file that is imported and overwrite any you have in you main glossary file. No entries is created or modified, only their translated text is altered if a new text is in the file that is imported
• "export locale to glossary" this will export a locale to a partial glossary file, use these partial glossary files to share the translation with others using mozillaTranslator.
• "report redundant entries" this will output which entries exists where the original text is the same.
• "aktivate a locale" this will make mozilla use the locale, you specify. this is done by creating the appropiate chrome.rdf files
• "view -> The chrome " show the content of the glossary in the same way as in V2
• "view -> unstranslated" show all entries that doen't have a text in the sicified locale and that doesn't have the keep original flag set.
• "view -> redundant " show all entries where two or more entries has the same original text and grouped by the original text. This is nice to see if all 22 instances of "Cancel" has been translated the same.
• "view -> keep original" list all entries that have the keep original flag set.

Issues

• (02/21/2000) The "Edit Entry" function currently only works with a JDK 1.3 JVM, the rest of the program should still run with the 1.2 jvm
• As said the folders for the destination locale must exist.
• The "Pack for submit" action is TEMPORARELY gone.
• ncr style is left "as is" in the strings.
• No resolution on using it on a non native system (I gotta figure out how to make it pick a better font, and perhaps install one if needed)
• The QA status is only show as number right now, this will change for a more appropiate dropdown list
• It doesn't pick up the localization notes from the original files.
• There are no progress indicator, so sometimes the system seems to hang for a while, but it ONLY seams that way, because it isn't redrawing its UI while performing time consumeing action.

Version 2 (Jan. 26, 2000)

Features

• Totally rewritten to root out all hardcoded filtering of things like access keys
• Real filter support
• Run as downloaded!!!! (you download a jar file)
• Gui setup dialog that is automaticaly displayed on first run
• Auto creates missing folders for destination locale
• Gui support for managing of filters (add,remove and edit)
• Scan files, components or the entire chrome for untranslated strings
• Supports both dtd and properties files (no real xml parser yet though)
• Pack all the translatede files into a zip file for easy distribution
• Turn on/off the translation on a component by component basis.
• Every thing is done in the gui now.


System requirements
 

• a Java 2 compatible JVM such as jdk 1.2.2 or 1.3Beta (the linux RC should work although it is untested)
• a mozilla build installed (nightly,milestone or possible home compiled)


Installation/running

I'm asuming windows here, but other OS should be nearly the same.

• download the MozillaTranslator.jar file to where you wanna run the program from (suggestion: put it in a seperate folder as it creates up to 3 files more when run)
• go to a DOS promt window and go to the folder where you downloaded MozillaTranslator.jar to
• type the following  command (Case sensitive and without the quotes): java -cp MozillaTranslator.jar org.mozilla.translator.kernel.Program"
• if that doesn't work try "<full path to java.exe> -cp MozillaTranslator.jar org.mozilla.translator.kernel.Program"
• alternatively you could download the run.bat file i have included in this mail and place it in the same folder as MozillaTranslator.jar


The first time you run the program a setup dialogbox will appear, fill it with the relevant information, it is prefilled with my information as an example (please don't change the Source Locale)

If something isn't filled out correctly or has changed delete the generated MozillaTranslator.properties file and restart the program

Usage
 

The basic usage is that the left part shows a tree structure of the components and files in the chrome, while the right side shows the texts in the loaded file.The filters in the program is used to tell the program which strings are not indtended to be localized (like urls and images). The filters are used when loading and scanning files, but is only used in the condition that the original and translated text as equal, that is so that if you need to translatede a text that has otherwise been filtered you can deselect the keep original check and translate the text. The next time the file is loaded/scanned it wont be filtered out.


The menus
 

• LOAD: loads a file, NOTE: it does NOT check to see if the current file have been saved (yet)
• SAVE: saves the loaded file
• SCAN: scans the file, component or whole chrome depending on the selected item in the tree, for untranslated strings. Only strings where the original and translated text are the same AND that hasn't matched a filter is reported, or if the file hasan't been translated at all.
• PACK: zip up the files from the destination locale (currently saves the file as checkin.zip in the same directory as mozillaTranslator.jar
• TURN ON/OFF: turns on or off the selected component, when turned on mozilla will use the translated version. this is done by creating (or deleting) the appropiate chrome.rdf file
• MANAGE FILTERS: manage (add/edit or remove) filters. the efftect takes place the next time a file is loaded (or scanned)
• QUIT: quit the program, NOTE: it does NOT check to see if the current file have been saved (yet)


Bugs and issues
 

• The splitter sometimes moves by itself after loading a file or editing a text
• When turning off a component it deletes the chrome.rdf file instead of making it use the source locale
• If nothing is selected when a menu is selected then the program will throw a harmless exception in the console. just ignore it

You can't quit by closing the window, you must use the menu