FCKeditor 2.x/Developers Guide/Localization - Revision history

W.olchawa at 10:53, 23 January 2008

2008-01-23T10:53:15Z

W.olchawa at 10:52, 23 January 2008

2008-01-23T10:52:18Z

W.olchawa at 14:32, 18 January 2008

2008-01-18T14:32:31Z

W.olchawa at 14:31, 18 January 2008

2008-01-18T14:31:57Z

W.olchawa: New page: == Interface Localization == The languages files must be placed inside the "editor/lang" directory of the project. You can use the file "'''en.js'''" as the base file for your translation...

2008-01-18T14:28:08Z

New page: == Interface Localization == The languages files must be placed inside the "editor/lang" directory of the project. You can use the file "'''en.js'''" as the base file for your translation...

New page

== Interface Localization ==

The languages files must be placed inside the "editor/lang" directory of the project. You can use the file "'''en.js'''" as the base file for your translations. The file names are based on the [http://www.faqs.org/rfcs/rfc3066.html:RFC 3066] standards (but in lowercase) and the [http://www.loc.gov/standards/iso639-2/php/English_list.php:ISO 639-1]. So, for example, a file for the '''Portuguese language''' should be called "'''pt.js'''".

Translation could also be localized for a specific country. In this case, for example, a Brazilian Portuguese translation file must be called "'''pt-br.js.'''"

The browser’s language auto detection system uses the first available language that best fits the client settings. For example, if a client computer is set to Brazilian Portuguese and there is no pt-br.js file available, the pt.js is used if available. If still not available, the default language is used (from the configuration file, by default English).

When creating new language files, you need to add an entry for it in the "editor/_source/internals/fcklanguagemanager.js" file. Something like this:
<pre>
AvailableLanguages =
{
en : 'English',
pt : 'Portuguese'
}
</pre>
To test your language file, you could run the editor using the [[FCKeditor 2.x/Developers Guide/Customization/Scripts Compression#Using the "_source" files|source scripts]]. Just open the "_samples/html/sample03.html" files.

When you feel the translation is completed and the tests are done, you will need to "re-generate" the compressed JavaScript files of FCKeditor using the [[FCKeditor 2.x/Developers Guide/Customization/Scripts Compression#Using the FCKpackager|FCKpackager]]

@@ Line 26: / Line 26: @@
 == Publishing ==
-A ticket must be opened at our [http://dev.fckeditor.net/:development web site] for each new or updated language file contribution.
+A ticket must be opened at our [http://dev.fckeditor.net/ development web site] for each new or updated language file contribution.
-Before starting a new translation, please take a look at [http://www.fckeditor.net/developers/:our web site] and check if there is no translator assigned to your language. Of course you can also [http://dev.fckeditor.net/search:check] if there are no translations made already.
+Before starting a new translation, please take a look at [http://www.fckeditor.net/developers/ our web site] and check if there is no translator assigned to your language. Of course you can also [http://dev.fckeditor.net/search check] if there are no translations made already.

@@ Line 22: / Line 22: @@
 == File Encoding ==
-'''NOTE''':An important thing is to save the files in the UTF-8 encoded text format. Otherwise, some strange characters could appear instead of any special characters used by different languages, like accented letters, symbols, etc.
+'''NOTE''': An important thing is to save the files in the UTF-8 encoded text format. Otherwise, some strange characters could appear instead of any special characters used by different languages, like accented letters, symbols, etc.
 == Publishing ==

@@ Line 1: / Line 1: @@
 == Interface Localization ==
-The languages files must be placed inside the "editor/lang" directory of the project. You can use the file "'''en.js'''" as the base file for your translations. The file names are based on the [http://www.faqs.org/rfcs/rfc3066.html:RFC 3066] standards (but in lowercase) and the [http://www.loc.gov/standards/iso639-2/php/English_list.php:ISO 639-1]. So, for example, a file for the '''Portuguese language''' should be called "'''pt.js'''".
+The languages files must be placed inside the "editor/lang" directory of the project. You can use the file "'''en.js'''" as the base file for your translations. The file names are based on the [http://www.faqs.org/rfcs/rfc3066.html RFC 3066] standards (but in lowercase) and the [http://www.loc.gov/standards/iso639-2/php/English_list.php ISO 639-1]. So, for example, a file for the '''Portuguese language''' should be called "'''pt.js'''".
 Translation could also be localized for a specific country. In this case, for example, a Brazilian Portuguese translation file must be called "'''pt-br.js.'''"
 The browser’s language auto detection system uses the first available language that best fits the client settings.
 For example, if a client computer is set to Brazilian Portuguese and there is no pt-br.js file available, the pt.js is used if available. If still not available, the default language is used (from the configuration file, by default English).
@@ Line 16: / Line 16: @@
+}
 </pre>
-To test your language file, you could run the editor using the [[FCKeditor 2.x/Developers Guide/Customization/Scripts Compression#Using the |source scripts]]. Just open the "_samples/html/sample03.html" files.
+To test your language file, you could run the editor using the [[FCKeditor 2.x/Developers Guide/Customization/Scripts Compression#Using the|source scripts]]. Just open the "_samples/html/sample03.html" files.
 When you feel the translation is completed and the tests are done, you will need to "re-generate" the compressed JavaScript files of FCKeditor using the [[FCKeditor 2.x/Developers Guide/Customization/Scripts Compression#Using the FCKpackager|FCKpackager]]

@@ Line 5: / Line 5: @@
 Translation could also be localized for a specific country. In this case, for example, a Brazilian Portuguese translation file must be called "'''pt-br.js.'''"
-The browser’s language auto detection system uses the first available language that best fits the client settings. For example, if a client computer is set to Brazilian Portuguese and there is no pt-br.js file available, the pt.js is used if available. If still not available, the default language is used (from the configuration file, by default English).
+The browser’s language auto detection system uses the first available language that best fits the client settings.
 When creating new language files, you need to add an entry for it in the "editor/_source/internals/fcklanguagemanager.js" file. Something like this:
-<pre>
+<pre>AvailableLanguages =
+{
-    en : 'English',
+en&nbsp;: 'English',
-    pt : 'Portuguese'
+pt&nbsp;: 'Portuguese'
+}
 </pre>
-To test your language file, you could run the editor using the [[FCKeditor 2.x/Developers Guide/Customization/Scripts Compression#Using the "_source" files|source scripts]]. Just open the "_samples/html/sample03.html" files.
+To test your language file, you could run the editor using the [[FCKeditor 2.x/Developers Guide/Customization/Scripts Compression#Using the |source scripts]]. Just open the "_samples/html/sample03.html" files.
 When you feel the translation is completed and the tests are done, you will need to "re-generate" the compressed JavaScript files of FCKeditor using the [[FCKeditor 2.x/Developers Guide/Customization/Scripts Compression#Using the FCKpackager|FCKpackager]]