Jinx wrote:Beat,
We indeed messed up with the UTF-8 work. We tried a move to UTF-8 in 1.0.3 and then decided to only do it in 1.1. Changes were reverted but the language iso setting was forgotten. We fixed this in 1.0.4 and forgot about the possible consequences. U are right that we should have informed our users about this change. Our apologies !
U can do two things are u change the iso settings in the english langauge file back to UTF-8 or u resave your content items. We are sticking with ISO-8859-1 for the 1.0 series. In your case it might be better to change them back to UTF-8.
Johan,
Thanks for your reply. Yes, you are right, it was 1.0.3, and not 1.0.2 where utf-8 was introduced. Sorry.
It would be reasonable to issue a small and simple easily understandable complement to the upgrade instructions, like this:
The sites which have started their existence with 1.0.3 should edit manually the following line in their english.php file:
DEFINE('_ISO','charset=iso-8859-1');
to
DEFINE('_ISO','charset=utf-8');
in all future 1.0.x versions, including 1.0.4, to avoid database changes. For other languages, please check the language files, which should all be synchronized on the same character set as is defined above.
All sites which have been designed in 1.0.0, 1.0.1 and 1.0.2 should avoid keeping 1.0.3 and move to 1.0.4 asap to avoid further database corruptions (for non-US-ASCII characters). This is because changes made in 1.0.3 (at least in English-language sites) are saved with a different character encoding (utf-8) than before (iso-8859-1). This is only visible for non-US characters, like accented characters and special signs (like tripple point ... etc.).
Constructively, and many tanks for all the other fixes and little new features,
)
below:
