CKFinder Localization

This website contains links to software which is either no longer maintained or will be supported only until the end of 2019 (CKFinder 2). For the latest documentation about current CKSource projects, including software like CKEditor 4/CKEditor 5, CKFinder 3, Cloud Services, Letters, Accessibility Checker, please visit the new documentation website.

If you look for an information about very old versions of CKEditor, FCKeditor and CKFinder check also the CKEditor forum, which was closed in 2015. If not, please head to StackOverflow for support.

(Localizing the Help Files: Screenshot comments added)
(Localizing the Help Files: Minor updates)
Line 47: Line 47:
 
== Localizing the Help Files ==
 
== Localizing the Help Files ==
 
It is possible to localize the CKFinder Help files. Follow these steps to translate them to, for example, German:
 
It is possible to localize the CKFinder Help files. Follow these steps to translate them to, for example, German:
* Create a copy of the <code>en</code> subfolder in the <code>core/help</code> folder and rename it to <code>de</code>.
+
* Create a copy of the <code>en</code> subfolder in the <code>help</code> folder and rename it to <code>de</code>.
 
* Edit all related HTML files inside the <code>de</code> folder.
 
* Edit all related HTML files inside the <code>de</code> folder.
* In the localization file for German (<code>core/lang/de.js</code>), set the <code>HelpLang</code> entry to <code>de</code>.
+
* In the localization file for German (<code>lang/de.js</code>), set the <code>HelpLang</code> entry to <code>de</code>.
  
 
=== Localizing Help Screenshots ===
 
=== Localizing Help Screenshots ===
 
We recommend to reuse the English language CKFinder screenshots since they are always up-to-date (and you will not need to redo them yourself).
 
We recommend to reuse the English language CKFinder screenshots since they are always up-to-date (and you will not need to redo them yourself).
  
It is also our policy to keep the bilingual names of CKFinder commands and terms in the localized Help files, with the English version given first, and its localized version given in parentheses. Examples: German: '''Cancel''' ('''Abbrechen'''), French: '''Upload''' ('''Envoyer'''), Spanish: '''Select''' ('''Seleccionar''').
+
It is also our policy to keep the bilingual names of CKFinder commands and terms in the localized Help files, with the localized version given first, and its its English equivalent given in parentheses. Examples: German: '''Abbrechen''' ('''Cancel'''), French: '''Envoyer''' ('''Upload'''), Spanish: '''Seleccionar''' ('''Select''').
  
 
Your users will now enjoy a fully localized experience with CKFinder.
 
Your users will now enjoy a fully localized experience with CKFinder.

Revision as of 22:40, 27 September 2011

CKFinder is fully localizable, including language-specific cultural aspects like date formatting.

Automatic Language Detection

By default CKFinder will try to detect the user language. If a localization file is available for that language, the interface will be adapted to it automatically. If no matching language file is available, a default language will be loaded (US English by default).

In order to disable automatic language detection, edit the config.js file and set the language to one of available languages by using the config.language configuration setting.

For example, the following setting forces CKEditor to display the interface in German, disabling the automatic detection feature:

config.language = 'de';

Localizing CKFinder

Localization is the act of adapting software to a culture. In CKFinder this is done by creating the main localization file in the lang folder as well as a small localization file for the server side part of CKFinder inside the core/connector/ext/lang folder.

For example, to create a Japanese localization file, follow the steps described below:

  • Create a copy of the English localization file (en.js) and name it jp.js.
  • Edit the jp.js file and translate all language strings. This file is in JavaScript format, so the string format must respect the JavaScript specification.
  • Save the file. We recommend using the UTF-8 encoding.
  • Open the ckfinder.js file in your favourite editor (make a backup first), and search for:
var l={};a.lang={ko:{cs:1,de:1,en:1,'es-mx':1,hu:1,lv:1,nl:1,no:1,'pt-br':1,sk:1,sv:1,'zh-tw':1,
da:1,el:1,es:1,fr:1,it:1,nb:1,nn:1,pl:1,ru:1,sl:1,'zh-cn':1}

and add 'jp':1 there:

var l={};a.lang={ko:{'jp':1,cs:1,de:1,en:1,'es-mx':1,hu:1,lv:1,nl:1,no:1,'pt-br':1,sk:1,sv:1,'zh-tw':1,da:1,
el:1,es:1,fr:1,it:1,nb:1,nn:1,pl:1,ru:1,sl:1,'zh-cn':1}

Save the file.

  • You may disable automatic language detection and set the new language as the default one in order to force the browser to load your file.
  • Test the user interface to check the correctness of your localization.
  • Note: to avoid having to change ckfinder.js, you can send us your translation (see Contributing Localizations) and we will include it in the next release.

The following are some notes about a few localization entries in the language file:

  • dir – sets the interface reading direction. You can choose between ltr for Left-to-Right languages like English and rtl for Right-to-Left languages like Hebrew or Arabic.
  • HelpLang – sets the language of the Help files. If you have not localized them, leave this entry intact (en) or set it to any of the available translated Help files.
  • HelpTip – if you have not localized the Help files, we recommend you indicate the Help language in the tooltip. For example, for Italian you may translate it to "Aiuto (Inglese)".

Setting the Date and Time Format

CKFinder supports adjusting the date format to the standards of your language. Use the following entries to configure the date and time format:

  • DateTime – sets the date and time format. Use the values provided in the comment to adjust this entry to your needs.
  • DateAmPm – sets the AM/PM display.

Localizing the Help Files

It is possible to localize the CKFinder Help files. Follow these steps to translate them to, for example, German:

  • Create a copy of the en subfolder in the help folder and rename it to de.
  • Edit all related HTML files inside the de folder.
  • In the localization file for German (lang/de.js), set the HelpLang entry to de.

Localizing Help Screenshots

We recommend to reuse the English language CKFinder screenshots since they are always up-to-date (and you will not need to redo them yourself).

It is also our policy to keep the bilingual names of CKFinder commands and terms in the localized Help files, with the localized version given first, and its its English equivalent given in parentheses. Examples: German: Abbrechen (Cancel), French: Envoyer (Upload), Spanish: Seleccionar (Select).

Your users will now enjoy a fully localized experience with CKFinder.

Contributing Localizations

All localization contributions are most welcome by CKSource and much appreciated by the international audience of our product as well as your users. The same goes for all efforts to improve existing translations and complete them. Feel free to contact us if you have any questions or would like to send us your submission.

important note
We prepared a nice gift for each person who will send us a complete (new) translation ;-) Just make sure to provide us with your e-mail address so we can contact you.