Re: Diacritic Signs

Doh!

Well look at that.  Set browser encoding to UTF-8 ... paste content ...
success.


----- Original Message -----
From: "Bill Kearney" <bill@wkearney.com>
To: "Stephen K. Rhoads" <rhoads@thrupoint.net>
Cc: <www-rdf-interest@w3.org>
Sent: Wednesday, January 22, 2003 2:22 PM
Subject: Re: Diacritic Signs


> If your browser isn't configured to use a given encoding how can the
server
> guess to use a different one?
>
> Connection negotiation is often the hidden problem in many encoding
debugging
> situations.
>
> Using UTF-8 works for almost everything.  UTF-16 does cover everything
(very,
> very nearly).  If your application can figure out what the source encoding
is
> and then transcode it into UTF-8 you'd be in good shape.  At least for a
> majority of situations.
>
> -Bill Kearney
>
> (which rdf list is or isn't supposed to be chat-like?)
>
>
> ----- Original Message -----
> From: "Stephen K. Rhoads" <rhoads@thrupoint.net>
> To: <cco@dydax.com>
> Cc: <www-rdf-interest@w3.org>
> Sent: Wednesday, January 22, 2003 1:25 PM
> Subject: Re: Diacritic Signs
>
>
> >
> > So, I added the "iso-8859-1" encoding declaration, and it worked, but
ONLY
> > when I retrieved the RDF document from a web server using the "Parse
URI"
> > feature in the RDF Validator.  When I cut and paste via a browser
window, I
> > get the same error.  Any thoughts as to why?
> >
> > Also, I anticipate adding additional languages in the future which go
beyond
> > the characters in 8859.  Thus I would prefer to generate files encoded
in
> > UTF-8.  Any tips on how to do this?  I'm using PERL and various text
editors
> > to generate my XML.

Received on Wednesday, 22 January 2003 14:45:21 UTC