Extension:Firefox toolbar

'''Note: For those who do not know, I (Shane or meta:User:Bugs5382) have taken over this project. With the new version v0.8.0 there will be no more template translating, but the DTD files will still need to be translated. Also this page will be updated once I get the new version out. I enabled 0.7.1 as the stable tree for Firefox 1.5. Any questions, please post on the mailing list. Please post all bug reports to this page. Thanks! --Bugs5382 03:35, 12 April 2006 (UTC)'''

This page is meant to coordinate the translation efforts for the Firefox/Mozilla Wikipedia toolbar extension developed by meta:User:Bananeweizen. If you want to help in translation, you can do so in two different ways. If you are familiar with CVS, I would really appreciate it if you become a member of the wikipedia.mozdev.org project and edit the files directly using CVS. That saves me hours of copying translations between CVS and the wiki.

Otherwise please add your language to the following list. Create a new sub page for your language and grab the contents of the English translation. Give it a status (including your signature) which indicates that you are working on the translation so others don't do the same work. When you have finished your translation, please set the status to "finished".

To find out the language code, use the Help->About menu in Firefox and have a look at the version information at the bottom of the dialog. It should look like "de-DE", "en-US" or something like that.

Whenever new strings are needed in more recent versions, they will be added as English strings to every language and the status field will be reset to indicate that some work is needed for that language. When a new major version of the extension is to be released, all current language strings from the pages below will be copied into that release, so you can expect the first inclusion of other languages than English and German in version 0.7.

General remarks about translation
All languages remains in English Thank you
 * Any string must be UTF-8 encoded.
 * You can not add new special characters through translation. Customizable special characters are planned for the next major version and may require an additional translation file then.
 * Leave the order of the strings as it is and don't remove comments (you may translate comments, if wanted). That makes comparison of different language files easier. All translations with a changed order of strings will not be included in the extension.

What needs to be translated
The to be translated strings currently consist of three parts:

User interface
All static user interface strings are represented as XML file where every string is encoded as XML entity. A single entry in those files is of the form
 * You can modify anything between the quotation marks.
 * You may translate the comments in between the  patterns (but leaving them as is makes comparison of language files easier). Don't remove the comments completely!

Strings in code
Strings used directly in the code are given like in a Java properties file. This list includes user interface strings which are build dynamically (like the special characters menu items). A single entry is of the form  with an example like
 * You can modify anything after the equals sign.
 * If you need line breaks in the string, they can be represented as.
 * Numbered percent signs like  are placeholders which are filled during runtime. They must also occur in your translated string, but you can change their order if necessary (e.g. having   appear before   is allowed). The actual values are always bound to the same number.
 * Please leave comments (starting with a  character) as they are.

Wikipedia templates
Language specific Wikipedia templates are given as XML file. They allow to insert language specific templates for stubs, copyright violations, deletion requests (or whatever may be common in your Wikipedia) via menu item. They are defined in an XML file and have the form A (non real word) example for English would be
 * You may add as many templates as you want by adding more ... tags in between the tags.
 * The templates will be shown in this order as menu items in the templates menu (in 0.5 there is a bug, so they are only shown after the menu for the right mouse key has been shown the first time).
 * The tooltip tag is optional. So you can either leave the text between the tooltip tags empty or you complete remove the tooltip tags.
 * If the label is set to "-" (a minus sign, without the quotation marks) then a menu separator (a gray horizontal line) will be inserted in the menu. So you can group your items. The other tags are ignored in that case.

Available translations
'''Current status: Version 0.7 is feature complete. You may translate the newly added strings for that version.''' Version 0.7.0.1 on the project homepage includes all of the translations for version 0.5, so you can check how your former translations are doing.