The Kaltura KMC – Kaltura Management Console is the part of the Kaltura system that allows for content management.
In this blog post I will describe how to add support for your (or your customers) language to the Kaltura KMC.
The Kaltura supports localization natively.
The following languages are currently supported in the upstream version:
Korean translation is being worked on for one of our customers, right now we do not have a full translation available, if you require it contact us.
Localization of the Kaltura KMC starts with translation of the strings used by the KMC.
Translation of the Kaltura KMC
The locale files are part of the KMC source code, there are a few different sub-projects that require translation:
https://github.com/panda-os/kmc/tree/master/KMC/locale – The Kaltura KMC itself
https://github.com/panda-os/kmc/tree/master/KalturaLib/locale/ – KalturaLib – a library written by Kaltura and used by the KMC
https://github.com/panda-os/kmc/tree/master/KedLib/locale/ KedLib – a library written by Kaltura and used by the KMC
https://github.com/panda-os/kmc/tree/master/AutoComplete/locale/ – AutoComplete – a library written by Kaltura and used by the KMC
https://github.com/panda-os/kmc/tree/master/vendors/Cairngorm/locale/ Cairngorm – an open source library written by Adobe used for rich internet applications.
It is recommended to use the en_US translation as a source, keep in mind that length of strings should be preserved, since otherwise display issues may occur.
Compilation and testing
First, Follow the steps in this post but before step 12, do the following:
Run the copylocale command from each Flash SDK you are using (probably 3.5 and 3.6A, if you are using Flash Builder 4.7) with the source and destination locales as arguments.
In most cases, you may need to do this for the already existing locales, as the SDK does not have them built in.
Add a language=<locale> to the flashvars in the index.template.html file.
Compile the locales as described in step 12 of the building and running post.
Clean and build the project, to generate an updated KMC.html file with the language and the variables you updated when following the build instructions.
Test that your locale is displaying as you expected by running the project, keep in mind that in most .
The built locale files will be created in the /KMC/html-template/locale/ directory under the workspace root.
Adding the new locale to the system
If you are happy with the result, copy the built locale files to all of your frontend servers in the path:
To set the Kaltura KMC language for a partner run the following on any of the frontend servers:
php /opt/kaltura/app/alpha/scripts/utils/setPartnerKMCLanguage.php <Partner ID> <locale>