[Message Prev][Message
Next][Thread Prev][Thread Next][Message
Index][Thread Index]
Re: Character encoding in xAP messages
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01
Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1"
http-equiv="Content-Type">
<title></title>
</head>
<body bgcolor="#ffffff" text="#000000">
Edward Pearson wrote:
<blockquote
cite="midECOWS04MzYviEYWHuoV00087791@xxxxxxx"
type="cite">
<meta http-equiv="Content-Type" content="text/html;
">
<meta content="MSHTML 6.00.2900.2523"
name="GENERATOR">
<div align="left" dir="ltr"><span
class="307273822-19012005"><font
color="#0000ff" face="Arial" size="2">Oh
cool - you fixed an old bug
in my Extreamer client that'd I'd never had the time to track
down!</font></span></div>
<div align="left" dir="ltr"><span
class="307273822-19012005"></span> </div>
<div align="left" dir="ltr"><span
class="307273822-19012005"><font
color="#0000ff" face="Arial" size="2">To
formalise this - the xAP
specification says ASCII everywhere. Was this done for a specific
reason or were the specification definers just being a bit loose here?
Maybe the spec should be revised to say
UTF8.</font></span></div>
<div align="left" dir="ltr"><span
class="307273822-19012005"></span> </div>
<div align="left" dir="ltr"><span
class="307273822-19012005"><font
color="#0000ff" face="Arial"
size="2">Right, I'm off to listen to some
German techno with umlauts in the title and other diacritically
challenged corners of my music
collection...</font></span></div>
</blockquote>
I had understood that non-ASCII stuff should all be represented in a
binary format, and therefore use the "keyword!" rather than the
"keyword=" form... and that the UTF-8 encoding should be
specified as
the encoding method in notes section of the Schema definition<br>
<br>
xAP_Development Main Index |
xAP_Development Thread Index |
xAP_Development Home |
Archives Home
|