FW: New FAQ: Setting encoding in web authoring applications

-----Original Message-----
From: Richard Ishida [mailto:ishida@w3.org] 
Sent: 06 November 2003 10:37
To: 'Chris Lilley'
Cc: Richard Ishida
Subject: RE: New FAQ: Setting encoding in web authoring applications


Thanks Chris,

I'll change "The presence of the BOM can create problems in older
browsers" to "The presence of the BOM for UTF-8 encoded pages can create
problems in older browsers"

> An entry for XML Spy would be good, as would some entries for SVG
creation tools.

If you can provide some info for us, I'll add it.

Cheers,
RI

PS: Can I copy this to the GEO group?

============
Richard Ishida
W3C

contact info: http://www.w3.org/People/Ishida/ 

http://www.w3.org/International/ 
http://www.w3.org/International/geo/ 

W3C Internationalization FAQs
http://www.w3.org/International/questions.html
RSS feed: http://www.w3.org/International/questions.rss



> -----Original Message-----
> From: Chris Lilley [mailto:chris@w3.org]
> Sent: 06 November 2003 10:15
> To: Richard Ishida
> Subject: Re: New FAQ: Setting encoding in web authoring applications
> 
> 
> On Thursday, November 6, 2003, 10:34:42 AM, Richard wrote:
> 
> 
> 
> RI> The latest FAQ addressed by the GEO task force is:
> 
> RI> 	How do I set character encoding in my web authoring
> applications?
> 
> RI> Find our answer at:
> RI> 
> http://www.w3.org/International/questions/qa-setting-encoding-
in-app
RI> lica
RI> tions.html


>From that document

> Some applications automatically insert BOM markup, while others do
> not. The presence of the BOM can create problems in older browsers.

Someone reading that might think 'so, remove it to avoid problems in
older browsers'. Not good if the document is UTF-16.

An entry for XML Spy would be good, as would some entries for SVG
creation tools.

-- 
 Chris                            mailto:chris@w3.org