• hello,

    I’ve recently enhanced the default TinyMCE editor in WP 2.5.1 with the plugins ‘table’ and ‘style’. I’ve done this by

    1. downloading the latest version of TinyMCE (3.1.1) from Moxiecode.
    2. copied both plugins ‘table’ and ‘style’ to its proper locations in WP: wp-includes/js/tinymce/plugins
    3. changed the default settings for TinyMCE in wp-includes/js/tinymce/tiny_mce_config.php:
    • added ‘table’ and ‘style’ to array $plugins
    • added ‘tablecontrols’, ‘styleprops’ to $mce_buttons_3

    Basically everything’s works fine, except that the template placeholders in the plugin’s template-files (e.g. wp-includes/js/tinymce/plugins/table/table.htm) don’t get translated:
    {#table_dlg.general_tab} should become “General” – the placeholders are being displayed instead of the translations.

    I found the following remark in TinyMCE’s API-documentation:

    Summary

    Loads a language pack for the specified add-on.

    Syntax

    <void> requireLangPack(<String> n)

    Parameters

    n
    Short name of the add-on.

    Yet changing the first line in wp-includes/js/tinymce/plugins/table/js/table.js from

    tinyMCEPopup.requireLangPack();

    to

    tinyMCEPopup.requireLangPack('table');

    didn’t yield the desired result of getting the placeholders translated to the proper expressions.

    I’ve already posted the same issue to the Moxiecode support-forums, yet nobody there seemed to know how to solve this.

    Anybody here who’s had the same problem or knows more about the underlying secrets of parsing translations? The problem only regards the inline-popups – strings within the TinyMCE-toolbar itself get translated properly.

    Thanks for any hints,

    Stefan

Viewing 2 replies - 1 through 2 (of 2 total)
Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘[tinyMCE] adding ‘table’, ‘style’ functionality in WP 2.5.1’ is closed to new replies.