Updated Localization (markdown)

chris 2016-08-07 08:21:58 +02:00
parent eab572c397
commit d302d04c72

@ -2,17 +2,10 @@ This document explains how to localize TenFourFox and make a langpack installer.
If you're interested in contributing a localization for your language, please see [issue 42](/classilla/tenfourfox/issues/42).
Summary of changes for 38:
Summary of changes for 45:
- All localization files have been moved from `MacOS` to `Resources` in the application package
- space constraints/truncated strings in the Prefs window are gone because of UI change (prefs moved to tab)
- `Check for Updates` has been moved to the Help menu; localization string remains in `baseMenuOverlay.dtd`
- Addon Manager: Plugin section with warning about Plugin support is obsolete
- `plugins.dtd> <!ENTITY installPlugin` is obsolete
* TenFourFox.dtd and TenFourFox.properties contain strings of features to be added to TFF at a later stage.
* string "TenFourFox does not support plugins for this content." has been moved to chrome/(language)/locale/(language)/pluginproblem/pluginproblem.dtd
# Localization Guide
@ -30,9 +23,9 @@ Summary of changes for 38:
## 2. The installer application
The installer application and script has already been developed to a stable point. File concerns with [issue 61](/classilla/tenfourfox/issues/61).
The installer application and script has already been developed to a stable point. File concerns with [issue 42](/classilla/tenfourfox/issues/42).
Rename your installer application with the correct language and version, e.g., `TFF-24-langpack-(your language).app` or the like so that people can see which exact version of 10.4Fx it is for, and which language the browser is changed to. Strings between minor versions of the browser (24.0.0->24.0.1, 38.0->38.2, etc.) are usually frozen, so the same installer app can be used; however, installers cannot work between major versions (for example, an installer for 17 cannot be used for 24).
Rename your installer application with the correct language and version, e.g., `TFF-24-langpack-(your language).app` or the like so that people can see which exact version of 10.4Fx it is for, and which language the browser is changed to. Strings between minor versions of the browser (24.0.0->24.0.1, 38.0->38.2, etc.) are usually frozen, so the same installer app can be used; however, installers cannot work between major versions (for example, an installer for 38 cannot be used for 45).
The installer app package's `Contents` folder contains:
@ -94,7 +87,7 @@ There are two chrome manifests: in `Resources/browser` and in `Resources`. In ch
There are two manifests that need similar changes in `Resources/browser/chrome` and in `Resources/chrome`. Copy the two respective `en-US.manifest` files from 10.4Fx and rename to (your language)`.manifest.` Inside change all strings accordingly.
Always use the original (!) manifest files from the TenFourFox version you want to translate. _Never copy them from the Intel version or any other version of the installer app_, or otherwise you will run into trouble.
Always use the original manifest files from the TenFourFox version you want to translate. _Never copy them from the Intel version or any other version of the installer app_, or otherwise you will run into trouble.
## 5. The dictionaries
@ -108,7 +101,7 @@ Most languages in recent Firefox versions don't package the traditional dictiona
## 7. Localization strings taken from Intel Firefox
The localization strings are located within two folder trees within the TenFourFox application package: `Contents/Resources/Chrome/`(language) and `Contents/Resources/browser/chrome`/(language). Have a look at the `en-US` folders in 10.4F first. You will need some of the files and strings inside later. The installer script copies your language folder tree from the installer app to 10.4Fx, so that the browser will have the folders for `en-US (inactive)` and `(your language) (active)` in the end.
The localization strings are located within two folder trees within the TenFourFox application package: `Contents/Resources/Chrome/`(language) and `Contents/Resources/browser/chrome`/(language). Have a look at the `en-US` folders in 10.4Fx first. You will need some of the files and strings inside later. The installer script copies your language folder tree from the installer app to 10.4Fx, so that the browser will have the folders for `en-US (inactive)` and `(your language) (active)` in the end.
1. Download the corresponding Intel version of Firefox and get the two `omni.ja` files from its application contents folder (Firefox uses a compressed jar format, while TenFourFox doesn't). Rename to `omni.zip`. Omnijars have a special zip format that Mac OS X itself might be unable to decompress. You can use the application `GUItar` for that.
@ -128,7 +121,7 @@ Some strings differ from the Intel Firefox version because we have our own updat
* `chrome/`(language)`/locale/`(language)`/mozapps/update/updates.dtd` (manual update strings; edit the Intel file and translate and add these strings from the original TenFourFox file) (`manualupdate2/3)`
* `chrome/`(language)`/locale/`(language)`/mozapps/plugins/plugins.dtd`: `<!ENTITY missingPlugin "TenFourFox does not support plugins for this content.">`
* `chrome/`(language)`/locale/`(language)`/pluginproblem/pluginproblem.dtd`: `<!ENTITY missingPlugin "TenFourFox does not support plugins for this content.">`
* `chrome/`(language)`/locale/`(language)`/global/videocontrols.dtd`: instead of `<!ENTITY error.srcNotSupported "Video format or MIME type is not supported.">` use `<!ENTITY error.srcNotSupported "To play, ensure QuickTime Enabler is installed, then right-click and select Open Media in QuickTime.">` in your language.