Introduction
This reference file should help you to find out what string is used in which context.
Because localizations of multipart strings could be very different from language to language we included some special items with " [***] " prefixes or suffixes. - Please, don't translate these pre- or suffixes.
If you need further help, or if you have suggestions to improve LocaleTracker please contact me.
Important note
Bidirectional language support is not yet supported :-( We plan this for a future release, when Bernard released SpLocale 2.0.
Special characters used in this reference:
[***] suffix or prefix for entries that have the same spelling in English but different meanings in other languages (Don't translate the suffix or prefix.)
In the reference list I used a separator line for such entries. On the upper side you will find the native string, as it is used for the translation of LocaleTracker, below the separator line you see the string which you should use for translation{PATH} synonym for any displayed path, name or a system generated term » this sign is followed by comments to the strings Grey strings are used for displaying in which context a string (bold) appears, I used it to give you examples when an entry will be displayed.
What do you need?
For developing and particularily for checking your new LocaleTracker language files enter "1" into the Tracker entry field
- First of all you need to download and to install SpLocale
- And of course you need the latest version of LocaleTracker
"translator:Name". This will stop a checking mechanism to replace prefix and suffix strings with the English version when
they are not translated.
If you finished your work please enter your name in the "translator:Name" field.
Creating new language(s)
- open LocalePrefs
- enter a name for the new language into the "Name" field (this entry will be used as the name in your applications "Language" menu)
![]()
- select in the "Language" popup menu below, the language you like to create
- click the "Add" button to finish creation
- if necessary, select new fonts for your language
- click "Apply" to set the changes
Important notice:
- When creating a new language for a program, try to build at first one without selecting a specific country. This way, it will be available whatever the country preferences of the users. Then it is OK to build other language files with country specific dialects or specificities.
- open LocaleEdit
- select in the "Application" popup menu the application, you like to translate
(for LocaleTracker you need: "Deskbar", "Tracker" and the "Common dictionary")- to create a template for your language now, add your language with: "Edit > New Language > NameOfYourLanguage"
- doubleclick in the "Translation Editor" field the entry you like to translate and enter your translation into "Translation"
Other very important notes:
- Don't translate language files of running applications when the language you like to translate is the same you currently
use in this application!!!- Avoid to use the "Auto Build" feature while translation (you can deactivte this option in LocalePrefs) !
- In "Common Dictionary" exists two items for displaying a month name for short and long format May_[1] is the short format and May_[2] is the long format for month name May
- when translation is complete, select the language in your applications "Language" menu
- after checking the new translation, please send the LocaleTracker language files from the Deskbar, Tracker and CommonDictionary folders (/boot/home/config/locale) to me: OpenTracker.de@gmx.net and I add them to the LocaleTracker Language site
BeOS, BeIA, Tracker & Deskbar are Trademarks or registered Trademarks of Be, Inc.
BeOS Icons and BeOS Logos used in some screenshot images in this reference: Copyright Be, Inc.
© Copyright of the LocaleTracker Reference: thomas fiedler, 2001.
Go to the Reference » | ||
Copyright © 2001, thomas fiedler. |