|
[XML-DEV Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message] Re: Well-formed Blueberry
Elliotte,
I am having a real problem understanding why you want to put a wall between
docs requiring blueberry and docs not requiring blueberry. I must be taking
a point of view on version progression that is too naive. The following does
give me a hint:
> further propose that the encoding declaration must be explicit.
> That is, this is malformed even though the default character
> set is UTF-8:
> <?xml version="1.1"?>
However, I am having a hard time figuring out why the standard should treat
authors of nonstandard XML documents better than people who simply want to
use their own language in markup.
In a corollary point of confusion for me, you seem to assume in your posts
that, even without your wall, a blueberry capable parser must have both the
pre-blueberry character classification tables and the blueberry character
classification tables. In my naive point of view, a document that is valid
XML 1.0 ought to be valid blueberry, thus, the complete table should be the
only necessary table, unless you want to build a wall.
So I must have missed some posts on this subject. Can you direct me to them?
One more thing, to which (single) Japanese character set do you refer below?
Joel Rees
programmer -- rees@m...
----------------------------------------------------
To be a tree supporting all information,
giving root to the chaos
and branches to the trivia,
information breathing anew --
This is the aim of Yggdrasill.
============================XML as Best Solution===
Media Fusion Co. ,Ltd. $B3t<02q |
PURCHASE STYLUS STUDIO ONLINE TODAY!Purchasing Stylus Studio from our online shop is Easy, Secure and Value Priced! Download The World's Best XML IDE!Accelerate XML development with our award-winning XML IDE - Download a free trial today! Subscribe in XML format
|
|||||||||

Cart








