I think this is a problem specific to TinyMCE, rather than to OCS -- TinyMCE itself should be able to gracefully handle not having a given locale if the site it is installed on is using that locale. Actually, it looks like that is partially the case -- some of the translation keys in your example appear in English
, at least. I looked on the TinyMCE developer's website, and did find a feature request for this kind of functionality: http://tinymce.moxiecode.com/develop/bu ... hp?id=3846
. If the developers there create a way for this to work, and it involves configuration work on our part, we will be happy to implement any changes they suggest.
Concerning the greek TinyMCE translation, keys inside the xml file appear in English because the translation is admittedly incomplete...
The selected buttons that appear in the text areas in OCS where TinyMCE is used (those that I've seen, I haven't checked all), however, are covered by the otherwise incomplete translation (although being wrongly translated...at least meaningful text appears) found in the TinyMCE download page.
Concerning the handling of non translated keys in OCS, I experienced this before translating the plugins...the font size plugin, for example, before I translated it, displayed the message key code instead of falling back to an existing, system default locale e.g. English...
...I guessed it was meant to work that way and that the plugins were rather an essential part of OCS that needed translation.
The same happened with TinyMCE, so I figured it had the same cause...an OCS setting or lack there of, that forces the use of only one locale file version, instead of two (e.g. Greek and English) for text that is meant to appear in different languages.