Voting starts in March for the Drupal Association Board election.
As of, Drupal ships with its own "image" and "link" plugins for CKEditor. What we haven't figured out yet, is how to deal with translations.
CKEditor has its own translation system, as does Drupal:
Drupal.t() only works if any JS it is used in is loaded via PHP: Drupal dynamically adds the translation JS file for a given JS file (see
But … Drupal-specific CKEditor plugins are still CKEditor plugins, hence CKEditor is what loads them, not Drupal. Which means the translation files won't be loaded automatically.
So, the question is: how do we deal with this? Pinging Drupal domain experts Gábor Hojtsy & nod_, as well as the CKEditor developers.
Note: non-Drupal-specific CKEditor plugins should of course use CKEditor's translation system.
|#22||interdiff.txt||1.15 KB||Gábor Hojtsy|
|#22||ck_plugin_language-2035721-22.patch||5.25 KB||Gábor Hojtsy|
PASSED: [[SimpleTest]]: [MySQL] 58,578 pass(es). View
|#21||ck_plugin_language-2035721-17.patch||4.29 KB||Wim Leers|
PASSED: [[SimpleTest]]: [MySQL] 58,780 pass(es). View
|#17||ck_plugin_language-2035721-17-do-not-test.patch||4.29 KB||Wim Leers|
|#17||interdiff.txt||1.52 KB||Wim Leers|