- From: Ivan Herman <ivan@w3.org>
- Date: Wed, 4 May 2011 11:16:09 +0200
- To: Richard Cyganiak <richard@cyganiak.de>
- Cc: Andy Seaborne <andy.seaborne@epimorphics.com>, public-rdf-wg@w3.org
On May 4, 2011, at 10:53 , Richard Cyganiak wrote: > > On 3 May 2011, at 07:42, Andy Seaborne wrote: >> On 03/05/11 00:07, Richard Cyganiak wrote: >>> Unicode escapes can be a helpful fallback when some piece of the >>> toolchain messes up the encoding; in such situations, they can be the >>> only way to make things interoperate. >> >> Could you give examples of this? Messing up the encoding that I see happens silently, due to system defaults. \u-escape does not have an impact on that (unfortunately). > > Simple example: editing a Turtle file in a text editor that doesn't understand that Turtle files are UTF-8. Entering non-US-ASCII characters (say, umlauts) in the editor will result in wrongly (say, ISO-8859-1) encoded files. Entering the umlauts as \u escapes is not pretty but solves the immediate problem. > Unfortunately, this indeed happens (in my case, it may become even worse, because if I use Hungarian characters, then it should use ISO-8859-2, and many editors did not even heard about that animal). (That being said, I refuse to use editors that do not understand UTF-8 these days:-) Ivan > Best, > Richard ---- Ivan Herman, W3C Semantic Web Activity Lead Home: http://www.w3.org/People/Ivan/ mobile: +31-641044153 PGP Key: http://www.ivan-herman.net/pgpkey.html FOAF: http://www.ivan-herman.net/foaf.rdf
Received on Wednesday, 4 May 2011 09:15:01 UTC