ProTip: You can test your add-on locales by changing the value of via about:config and restarting the browser. The Add-on SDK uses a similar but different localization system. I demonstrated all of the above in a full-blown example add-on. add a flag.png to all locales, and have the en-GB locale be the Star-Spangled Banner, the en-GB locale be the Union Jack, while having the fr-FR be Le Tricolore. You can then access some.dtd by chrome://my-addon/locale/some.dtd and the application will automatically select whatever locale best corresponds to the browser and user preferences, e.g. You'd then add some.dtd to all locales (locale directories): So for example you might have the following chrome.manifest declarations: locale my-addon en-US locale/en-US/ Using stringbundles (aka.properties) for everything else (or even instead of DTDs even for XUL).

Using DTD in XUL (overlays, windows, dialogs).The browser will then make available the most appropriate locale automatically by the same URI prefix. Declaring one or more locales in your chrome.manifest.The old-but-still-accurate XUL Tutorial and the XUL School tutorial (add-ons) have some examples and descriptions. XUL overlays add-ons usually localize with DTD or.

Firefox bonjour add on