Strings for specialchar plugin added directly to editor.lang instead of editor.lang.specialChar

[Teresa Monahan]

The strings for the special characters dialog are available directly on the editor.lang object when the editor is loaded in a new language. They should be inside the editor.lang.specialChar object.

To Reproduce:

1. Add the attached fr.js (pseudo translation file) to the specialchar/lang directory and change the value of availableLangs in specialchar\plugin.js to:

availableLangs : { en:1, fr:1 },

2. Open ui_languages.html in a browser.
3. Click into the editor and open the special characters dialog. Close the dialog.
4. Inspect the editor.lang object in the DOM. editor.lang.specialChar will contain all the strings for the specialchar plugin.
5. Now change the language to French and inspect the editor.lang object in the DOM again.

Problem: All the strings for the specialchars plugin are now available directly on the editor.lang object. Note that these are the strings in English. When the special characters dialog is opened again, the editor.lang.specialChar object is correctly updated with the pseudo French strings.

specialchar\plugin.js does extend the editor.lang.specialChar object with the string values.

CKEDITOR.tools.extend( editor.lang.specialChar, plugin.langEntries[ langCode ] );

However the CKEDITOR.plugins.load function in core\editor.js always extends the editor.lang object.

CKEDITOR.tools.extend( editor.lang, plugin.langEntries[ lang ] );

This works correctly for the a11yhelp plugin because the strings in a11yhelp\lang\xx.js are specified within the accessibilityHelp group. Perhaps the special characters lang files also need to group the strings like this?

[Jakub Ś]

Issue has been reproducible form CKEditor 3.5.3.

Before 3.5.5 version, this TC caused error:
Message: array.indexOf is not a function
Line: 522
URI: /3.5/ckeditor/_source/core/tools.js