Notes for Translations
(Revised: 23rd July 2003)
The languages files must be created inside the lang directory of the project. You can use the file en.js as the base file for your translations. The file names respect the RFC 1766 standards (but in lowercase). 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 should be called pt-br.js.
The client’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 not, the default language is used (from the fck_config.js file).
To test the translations you need to add a line in the fck_lang.js file like:
AvailableLangs["pt"] = true ;
An important think is to save the files in a UTF-8 encoded format. In other case, some strange characters could appear instead of some special chars, like accented letters, symbols, etc.
All translated files must be sent by e-mail to .