We just had a couple of people from our community just report this, after we upgraded from v3. It happens on 4.3.2 and 4.3.3, if the parent HTML document is not utf-8 and the server is not explicitly configured to make .js files utf-8.
It seems something in the CKEditor source, or the minification process, has an implicit assumption of the files being parsed as utf-8.
A fix (which I recommend being incorporated) is to add this to the .htaccess file:
You do have BOMs (byte order marks). However I'd accidentally stripped them because I ran the files through dos2unix, as a matter of course, when normalising our development repository. I just confirmed, dos2unix strips BOMs out, unless you explicitly tell it to add them back in.
Then, when I re-tested the code, I got the latest ckeditor.js code in there via copy&paste, so still was missing the BOMs.
So this is not a bug in CKEditor, but it's a really easy pitfall.
You might have a charset
You might have a charset issue. Some have fixed it by changing the site's charset to UTF-8. Also never hurts to have the latest CKEditor.
Customer and Community Manager, CKSource
Follow us on: Facebook, Twitter, LinkedIn
If you think you found a bug in CKEditor, read this!
Thanks, that solved the
Thanks, that solved the problem.
We just had a couple of
We just had a couple of people from our community just report this, after we upgraded from v3. It happens on 4.3.2 and 4.3.3, if the parent HTML document is not utf-8 and the server is not explicitly configured to make .js files utf-8.
It seems something in the CKEditor source, or the minification process, has an implicit assumption of the files being parsed as utf-8.
A fix (which I recommend being incorporated) is to add this to the .htaccess file:
AddCharset UTF-8 .js
Ah, update on my last post...
Ah, update on my last post...
You do have BOMs (byte order marks). However I'd accidentally stripped them because I ran the files through dos2unix, as a matter of course, when normalising our development repository. I just confirmed, dos2unix strips BOMs out, unless you explicitly tell it to add them back in.
Then, when I re-tested the code, I got the latest ckeditor.js code in there via copy&paste, so still was missing the BOMs.
So this is not a bug in CKEditor, but it's a really easy pitfall.