> On Sun, 2005-07-03 at 15:31 +0300, Henri Sivonen wrote:
>
>>> Shouldn't an encoding header be added to RNC document similar to
>>> @charset in CSS?
>>
>> The current approach of expecting everyone to use UTF-8 or UTF-16 with
>> BOM is much simpler and works already. There is no good excuse for not
>> using UTF-8.
>
> For an rng file, I'd agree, it *should* be specified.
> For an rnc file, that's not so easy.
The RNC spec says that in the absence of external encoding information
the processor assumes UTF-16 if the first two bytes constitute a UTF-16
BOM and assumes UTF-8 otherwise. What's not easy about it? It's the
external information that complicates things.
--
Henri Sivonen
[EMAIL PROTECTED]
http://hsivonen.iki.fi/
YAHOO! GROUPS LINKS
- Visit your group "rng-users" on the web.
- To unsubscribe from this group, send an email to:
[EMAIL PROTECTED]
- Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service.
