* Only ''*.properties'' files should be used for localization (Firebug doesn't want to use DTD files due a lack of script-ability)

* Only ''*.properties'' files should be used for localization (Firebug doesn't want to use DTD files due a lack of script-ability)

+

+

* Do not put an empty string into ''*.properties'' files.

== Naming Conventions ==

== Naming Conventions ==

Line 27:

Line 31:

Every string in ''*.properties'' file is identified by ID (a key). For example, following string is identified by ''net.Response_Header'' and it's value is set to ''net.Response Header''.

Every string in ''*.properties'' file is identified by ID (a key). For example, following string is identified by ''net.Response_Header'' and it's value is set to ''net.Response Header''.

-

<code>net.Response_Header=Response Header</code>

+

<source lang="properties">

+

net.Response_Header=Response Header

+

</source>

String IDs in Firebug use following naming rules:

String IDs in Firebug use following naming rules:

Line 37:

Line 43:

See examples:

See examples:

-

<code>$STR("net.Response Header");</code>

+

<source lang="javascript">

+

$STR("net.Response Header");

+

</source>

* key is: ''net.Response_Header''

* key is: ''net.Response_Header''

* default is: ''Response Header''

* default is: ''Response Header''

-

<code>$STR("net.timing.Request Time");</code>

+

<source lang="javascript">

+

$STR("net.timing.Request Time");

+

</source>

* key is: ''net.timing.Request_Time''

* key is: ''net.timing.Request_Time''

* default is: ''Request Time''

* default is: ''Request Time''

-

''Firebug 1.6 (beta) uses a new way how to deal with missing translations. In case when a string is not translated for the current Firefox locale, the en-US locale is used as fall-back (en-US translation is used instead). Note that en-US locale must always define all strings.''

''Firebug 1.6 (beta) uses a new way how to deal with missing translations. In case when a string is not translated for the current Firefox locale, the en-US locale is used as fall-back (en-US translation is used instead). Note that en-US locale must always define all strings.''

Line 51:

Line 60:

There are several APIs that are be used to make Firebug code localizable.

There are several APIs that are be used to make Firebug code localizable.

* <code>$STRP</code> - localization of a plural form (see an [https://developer.mozilla.org/En/Localization_and_Plurals#Polish example]).

Some examples:

Some examples:

-

<pre class="code">

+

<source lang="javascript">

// Search for key "Label" within firebug *.properties files and returns its value.

// Search for key "Label" within firebug *.properties files and returns its value.

// If the key doesn't exist returns "Label".

// If the key doesn't exist returns "Label".

$STR("Label");

$STR("Label");

-

</pre>

+

</source>

-

<pre class="code">

+

<source lang="javascript">

// Search for key "Button_Label" within the firebug *.properties files.

// Search for key "Button_Label" within the firebug *.properties files.

// If the key doesn't exist returns "Button Label".

// If the key doesn't exist returns "Button Label".

$STR("Button Label");

$STR("Button Label");

-

</pre>

+

</source>

-

<pre class="code">

+

<source lang="javascript">

// Search for key "net.Response_Header".

// Search for key "net.Response_Header".

// If the key doesn't exist returns "Response Header".

// If the key doesn't exist returns "Response Header".

$STR("net.Response Header");

$STR("net.Response Header");

-

</pre>

+

</source>

-

<pre class="code">

+

<source lang="javascript">

var param1 = 10;

var param1 = 10;

var param2 = "ms";

var param2 = "ms";

// Returns "Request Time: 10 [ms]" for key that looks as follows:

// Returns "Request Time: 10 [ms]" for key that looks as follows:

-

// net.timing.Request_Time=Request Time: %S [%S]

+

// net.timing.Request_Time=Request Time: %1$S [%2$S]

$STRF("net.timing.Request Time", param1, param2);

$STRF("net.timing.Request Time", param1, param2);

-

</pre>

+

</source>

+

+

<source lang="javascript">

+

// the key can look like as follows for en-US (two plural forms):

+

// plural.Request_Count=%1$S request;%1$S requests

+

$STRP("plural.Request Count", 1); // Returns: 1 request

+

$STRP("plural.Request Count", 10); // Returns: 10 requests

+

</source>

In order to register a new string bundle (*.properties file) use <code>Firebug.registerStringBundle</code> method. This method should be also used from within a Firebug extension so, Firebug localization API properly work.

In order to register a new string bundle (*.properties file) use <code>Firebug.registerStringBundle</code> method. This method should be also used from within a Firebug extension so, Firebug localization API properly work.

Revision as of 09:21, 18 May 2011

Contents

Localization

Firebug is using BabelZilla (BZ) to utilize an existing community of localizers and get translation to various languages. This effort requires a process and Firebug developers should follow some rules that help to synchronize files coming from BZ to the development source tree.

In case of any problems related to wrong usage of translated string within the Firebug's UI, please report a new issue.

Links

Development Rules

FB developers should change only the en-US locale files, which stand like a

template for all other translated locales.

If some string (its value) is changed, change also its key so, translators can see

there is something new to translate.

When updating from BZ, always get all translations (even for not released

locales) from BZ before uploading new version. So, no translation made since the last
upload is lost. The only dir, which is *not* synced with BZ is locale/en-US.

Only *.properties files should be used for localization (Firebug doesn't want to use DTD files due a lack of script-ability)

Do not put an empty string into *.properties files.

Naming Conventions

Every string in *.properties file is identified by ID (a key). For example, following string is identified by net.Response_Header and it's value is set to net.Response Header.

net.Response_Header=Response Header

String IDs in Firebug use following naming rules:

The key is prefixed with lower case module name using the string (e.g. net or console, ...)

In case of many strings in one module you can use additional prefix to further group related strings. Again such prefix should be followed by a period.

The part after last period is used as the default value (with underscores replaced by spaces) in case the string is not available in the current locale.

See examples:

$STR("net.Response Header");

key is: net.Response_Header

default is: Response Header

$STR("net.timing.Request Time");

key is: net.timing.Request_Time

default is: Request Time

Firebug 1.6 (beta) uses a new way how to deal with missing translations. In case when a string is not translated for the current Firefox locale, the en-US locale is used as fall-back (en-US translation is used instead). Note that en-US locale must always define all strings.

Localization APIs

There are several APIs that are be used to make Firebug code localizable.

In order to register a new string bundle (*.properties file) use Firebug.registerStringBundle method. This method should be also used from within a Firebug extension so, Firebug localization API properly work.

Localization Events

Every Firebug module (Firebug.Module), no matter if it's built-in core module or coming from an extension, should perform initial localization within internationalizeUI method. This module method is executed upon an internationalizeUI event that is dispatched to all registered modules during Firebug initialization process.