> > 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.
Henri, if it is explicit in the XML instance, it may
make someone consider it in the schema?
I think it is a tiny advantage.
regards DaveP
>
---- LSpots keywords ?> ---- HM ADS ?>
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.
