Hi,

"NAKAMURA, Hiroshi" <nahi / keynauts.com> wrote:
> See SOAP4R implementation if you are interested.  UTF-8 has
> already been supported.

NQXML doesn't allow non-ASCII character as element's name.

> Hmm. "UTF-8 only" might not be a problem for some system.
> But my intention is "XML as a glue" so XML processor should
> not restrict CES usage of XML application.
> 
> $KCODE = "UTF8" with ruby/1.6 + NQXML works well but I want
> to use EUC/SJIS/iso-8859-1 in my CGI, desktop tool, and so on.

When you use XML, you should live in Unicode's world (as you know :-))

Of cource, text processing in general is different. I also
use non-unicode based character set. But it's not XML.
IMHO, if we parse XML documents, we should convert documents
into Unicode on our own responsibility.

> > According to NQXML's CES support:
> >  * at least, should be able to parse UTF-8 documents.
> 
> Under $KCODE="UTF8" condition.

??
If $KCODE != "UTF8" and document is UTF-8, parser should raise
error?

> > By the way, I think NQXML is slow for large documents. Is it
> > serious problem?
> 
> Can you hack it more deep?

I don't know, but I'll try it.


Regards,

TAKAHASHI Masayoshi