I also would like to ask is there any way to translate editors on multi-language site? Is it a good idea to use Drupal.t() function for string translation in the editors?
Button titles can be translated by prefixing them with t:. So if you set the title as t:Bold it will be have the result of t('Bold').
For button content, you can either use Drupal.t() for js buttons or t() for php buttons.
Comments
Comment #1
ufku commentedUse import/export interface after customizing your editor.
Comment #2
chi commentedUnfortunately, it isn't possible to use this interface in Drupal distributions like Starter.
Comment #3
chi commentedI also would like to ask is there any way to translate editors on multi-language site? Is it a good idea to use Drupal.t() function for string translation in the editors?
Comment #4
ufku commentedButton titles can be translated by prefixing them with
t:. So if you set the title as t:Bold it will be have the result of t('Bold').For button content, you can either use Drupal.t() for js buttons or t() for php buttons.
Comment #5
chi commentedGabor says that t() is the wrong answer.
Comment #6
ufku commentedThen, don't do it.
Comment #7
chi commentedHere is my solution:
In bueditor.in I have bueditor profile with special tags .
It should work fine if you have .po file with translation for this. But I do not know how it will work on l.d.o. So I am closing this.