Affects Version/s: 2.0
Fix Version/s: None
When entering foreign, non-western or accented characters into Sakai, it initially accepts and displays them properly. However, if you then edit the text, the character encoding is altered when the content is loaded into the editor resulting in corrupted text. This happens with documents formatted as either UTF-8 or Windows-1252 – starting with different document encodings merely changes how the corruption manifests, but the text will still be corrupted.
This is currently happening in Resources but happens in Melete too, and has been already reported (and apparently fixed in 2.01) in announcements. It seems to be pervasive, and probably happens in other tools as well. Not every tool currently allows the text to be edited afterwards (e.g., discussions) so that might mask the problem.
Possibly related bugs:
SAK-969 - International characters display in WYSIWYG but lose all formatting once you revise/post
SAK-842 - Unicode names not displayed correctly in all deployments
SAK-422 - Cannot save a value in a field that has foreign chars as new field name in schedule
This issue makes teaching language and literature courses difficult if not impossible, and if an edited document is saved results in data loss (corruption of the foreign text within the document/announcment/whatever).
Using accented characters in a Resources document title is even worse, I'm filling that as a separate bug (