From: "NAKAMURA, Hiroshi" <nahi@...>
Date: 2001-07-17T19:22:57+09:00
Subject: [ruby-talk:17978] Re: Movement in scripting language communities to  integrate XML-RPC

Hi,

> From: TAKAHASHI Masayoshi [mailto:maki@inac.co.jp]
> Sent: Tuesday, July 17, 2001 7:06 PM

> "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.

Then, don't you think we should wait?  I don't know anything
about 1.7's m17n, $KCODE won't be used in it...

BTW: Fortunately, SOAP and Ruby binding won't hit this
problem.  IIRC, matz does not hope you to use non-ascii char
as variable 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 :-))

XML spec does not require "utf-8 ONLY" (as you know :-)

> > > 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?

No.  I misunderstood you.  You listed requirements here...
Sorry.

I agree that XML processor should be able to parse utf-8
encoded XML instance(as spec requires).

// NaHi