Accented chars in documents' titles & descriptions

I have a general setting of UTF8 for a site, accented characters are correctly managed in the site’s contents, but not in page titles, description and other such fields. These same chars wrongly displayed in the public site, do display ok in the manager left columns and/or when editing the document.

Is there a way to avoid this, what should the collation for the MODx DB in MySql be ?

Switching to ISO-8951 solves the problem with the accented letters but displays other weird characters () before snippet calls in the template and affects the manager...

?!?

Try using html entities instead of the accented characters. Use í instead of í, for example.

As far as I know, TinyMCE automagically converts accented characters to html entities, so that’s why you haven’t got problems in the site’s content area.

Try using html entities instead of the accented characters. Use í instead of í, for example.

This is exactly the kind of things that non-technical editors should not worry about!
I’d really love not having to instruct them about it and not having to check on their newly inserted documents!

Anyhow if I re-edit the chars then they display fine; I guess the errors I was seeing appeared after upgrading MODx or some other module on the server.

Quote from: lukwe at Jan 18, 2007, 04:52 AM

Try using html entities instead of the accented characters. Use í instead of í, for example.

This is exactly the kind of things that non-technical editors should not worry about!
I’d really love not having to instruct them about it and not having to check on their newly inserted documents!

Anyhow if I re-edit the chars then they display fine; I guess the errors I was seeing appeared after upgrading MODx or some other module on the server.

Yes, you need to make sure that your MySQL configurations (charset and collation) match your intended output encoding and that it matches the original database charset and encoding. It’s by no means a simple subject, because there are a lot of variables when dealing with the various MySQL charsets and especially when importing/exporting them to file... I recommend always using mysqldump when dumping and loading data, and not phpmyadmin, which further complicates the process since it must deal with such issues itself (being a web application) and respect whatever connection charset you set in the interface.