Calendar:Localization: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
No edit summary
Line 1: Line 1:
== Translating releases after Sunbird 0.3a2 ==
Localization, or ''l10n'' for short, is the process of translating and otherwise adapting a piece of software for a specific language and culture. Localization should not be confused with internationalization (i18n), which refers to the infrastructure to support different culture interaction between a user and the software.


After Sunbird 0.3a2 was released, we migrated to the same means of translation being used by Firefox, Thunderbird, and other Mozilla applications in general.
For example: In English, words are written from left to right. In Arabic, the reverse is true. Words are written from right to left. Therefore, not only must someone ''localize'' a piece of software by translating all the menus and dialogs displayed to the user, but someone must ''internationalize'' the software by enabling it to display text in either a left to right, or right to left fashion (often referred to as bi-directional, or ''bi-di'' support), depending on the language.


Calendar localizers should follow the instructions found at
=Status of l10n=
[[Firefox:1.5 Localization]] when building Sunbird. We have added "calendar" directories to the directories already on /l10n/ab-CD.
Thanks to the work of Mozilla contributors and the [http://www.mozilla.org/projects/l10n/ Mozilla Localization Project], there is a centralized location and format for storing locales: the /l10n repository. Firefox and Thunderbird are already using /l10n.


== Translating Sunbird 0.2 through 0.3a2: ==
As of 2006-06-07, so is Sunbird.  


The most practical ways to translate Sunbird 0.2/0.3a2 have proven to be the following which are based on the idea of replacing the en-US files:
Once some other work has been completed, we will to move Lightning to /l10n. This is planned to be complete before 0.3 ships.


* If the language of your choice is NOT being shipped with Sunbird 0.2/0.3a2, you have to provide a calendar-ab-CD.jar file that includes the locale files of your language for calendar. Once you have that file inside the chrome directory along-side other calendar.jar files you can proceed with the next step.
=How to build a non-English Sunbird=
With locales moved to /l10n, building Sunbird in a locale other than English is easy. First, visit the [http://lxr.mozilla.org/mozilla/source/calendar/locales/all-locales list of available locales] to find the locale code you wish to build with. Note that due to the standarization put in place by /l10n, some locales may have been shortened from their "ab-CD" format to simply be "ab". Be sure to check the list to see if this applies to you.


* If the language of your choice is being already shipped with Sunbird 0.2/0.3a2, to start using it in that language all you need to do is to follow the instructions [[Sunbird:language-switch|here]]. If you repackage the Sunbird directory with the modified chrome.rdf file you should have a Sunbird dist in that language. '''Important note''': Doing so will just get you a translation of the calendar UI only. Parts that belong to the toolkit like the password manager will still be English. If you want to go further in translating those parts too you have to translate the en-US.jar file as well as en-win.jar, en-unix.jar and en-mac.jar and modify chrome.rdf in the same manner you did to replace the en-US files for calendar but this hasn't been tested so you have to overcome the problems you may encounter on your own. In that case, please do share your experience for the benefit of others.
Next, add the following lines to your .mozconfig, substituting your preferred locale code for the "ab-CD" in the example:


See also the [[Calendar:Translation]] page here.
ac_add_options --enable-ui-locale=ab-CD
mk_add_options MOZ_CO_LOCALES=ab-CD


== Moving Forward ==
Now build as normal. That's it!
The next versions of Sunbird will come with the same convenient way of translation provided for other Mozilla applications and will start appearing among the list of [http://www.mozilla.org/projects/l10n#projects MLP covered projects].
 
=How to build a language pack=
Language packs, or ''langpacks'' for short, allow users to install additional locales into the application without having to download and keep a second full copy of the app. Support for building langpacks is in place, but has a couple bugs that must be ironed out before it can be used for Sunbird.

Revision as of 13:48, 8 June 2006

Localization, or l10n for short, is the process of translating and otherwise adapting a piece of software for a specific language and culture. Localization should not be confused with internationalization (i18n), which refers to the infrastructure to support different culture interaction between a user and the software.

For example: In English, words are written from left to right. In Arabic, the reverse is true. Words are written from right to left. Therefore, not only must someone localize a piece of software by translating all the menus and dialogs displayed to the user, but someone must internationalize the software by enabling it to display text in either a left to right, or right to left fashion (often referred to as bi-directional, or bi-di support), depending on the language.

Status of l10n

Thanks to the work of Mozilla contributors and the Mozilla Localization Project, there is a centralized location and format for storing locales: the /l10n repository. Firefox and Thunderbird are already using /l10n.

As of 2006-06-07, so is Sunbird.

Once some other work has been completed, we will to move Lightning to /l10n. This is planned to be complete before 0.3 ships.

How to build a non-English Sunbird

With locales moved to /l10n, building Sunbird in a locale other than English is easy. First, visit the list of available locales to find the locale code you wish to build with. Note that due to the standarization put in place by /l10n, some locales may have been shortened from their "ab-CD" format to simply be "ab". Be sure to check the list to see if this applies to you.

Next, add the following lines to your .mozconfig, substituting your preferred locale code for the "ab-CD" in the example:

ac_add_options --enable-ui-locale=ab-CD
mk_add_options MOZ_CO_LOCALES=ab-CD

Now build as normal. That's it!

How to build a language pack

Language packs, or langpacks for short, allow users to install additional locales into the application without having to download and keep a second full copy of the app. Support for building langpacks is in place, but has a couple bugs that must be ironed out before it can be used for Sunbird.