That is a nasty issue that I don't think has been "solved" in SS even though it seems to be a webkit bug. You would have to do some low-level hacking to replace all chars before sending to the browser. Any idea what the actual issue with webkit is?
I was hoping that someone had already done the same for Silverstripe.
It is very strange that if I copy the source from the Chrome viewer, save it in an HTML file, then open that file in Chrome it works fine.
And I can't believe that other people have done multilingual websites without reporting this.
Any help will be greatly appreciated, as my client is primarily using Chrome.
Good to hear, I've seen several variants on this issue as the newer systems start with the XHTML doc type by default and lots of legacy code doesn't respect the standard. Especially with regards to ampersands and the like. Modern browsers are quick to point out the parsing error but don't offer much else.