The translations can now be added as properties the same way as all other Confluence translations.
The required properties are listed in the tiny mce plugin itself.

Enjoy
Don and SaM

This is really a bug now.

A user pointed out in the forums (http://forums.atlassian.com/thread.jspa?forumID=96&threadID=17411), that it is now even more difficult to localise the editor because it is now a bundled plugin. To edit the js files, the customer must now pull the editor plugin's jar out of atlassian-bundled-plugins.zip, edit the js files inside the jar, and put it back into atlassian-bundled-plugins.zip.

Hi Neeraj,

First the "en.js" files are not java file nor are they properties files. They are Javascripts file which is the reason why your parser wouldn't work.
Second, moving those texts to a properties files is not in our roadmap at the moment unfortunately.

SaM

Hi,

We tried to work with the seven en.js files mentioned in CONF-6817 but they are proving difficult to localize because (a) the Java file parser we use for localization is giving errors with them (different format expected), and (b) mutiple files are harder to manage unless they are part of a jar package (like in the case of JIRA).

If moving to a better solution (such as adding them to the .properties file) is going to take time, can these .js files be converted to same standard format as the .properties file so atleast there is a away to localize them with our tool?

Thanks,

Neeraj

We would really appreciate if these strings can also be included in the ConfluenceActionSupport.properties fle to keep localization process straight-forward.