Skip to Content.
Sympa Menu

xom-interest - Antwort: RE: Antwort: [XOM-interest] Character conversion problem

xom-interest AT lists.ibiblio.org

Subject: XOM API for Processing XML with Java

List archive

Chronological Thread  
  • From: dvholten AT computer.org
  • To: "Michael Kay" <mike AT saxonica.com>
  • Cc: xom-interest AT lists.ibiblio.org
  • Subject: Antwort: RE: Antwort: [XOM-interest] Character conversion problem
  • Date: Thu, 04 Nov 2004 10:52:03 GMT

ok, i see - good point .

sure, xml supports characters wider than 2 bytes - but does java ??
having a valid xml-document doesnt mean, that anybody can actually process
it.

after parsing the document, the attribute 'character="&#x50000;" ' is just
a java-string, limited to 2byte characters - i think.

would be interesting to see, if *any* xsl-processor can make sense of
that.
and it's sure, that there *really is* a character at x50000 ? - unicode
has gaps.

AFAIK, the latest java version 5 has better support for 'higher' character
sets...

maybe wrapping the thing in CDATA can help..

dvholten
>From mike AT saxonica.com Thu Nov 4 06:03:59 2004
Return-Path: <mike AT saxonica.com>
X-Original-To: xom-interest AT lists.ibiblio.org
Delivered-To: xom-interest AT lists.ibiblio.org
Received: from ukmail1.eechost.net (ukmail1.eechost.net [217.69.32.40])
by happyhouse.metalab.unc.edu (Postfix) with ESMTP id 25ED14C005
for <xom-interest AT lists.ibiblio.org>;
Thu, 4 Nov 2004 06:03:59 -0500 (EST)
Received: from [81.98.109.162] (helo=Turtle)
by ukmail1.eechost.net with asmtp (Exim 4.10)
id 1CPfPL-0005GI-00; Thu, 04 Nov 2004 11:03:59 +0000
From: "Michael Kay" <mike AT saxonica.com>
To: <dvholten AT computer.org>
Subject: RE: Antwort: RE: Antwort: [XOM-interest] Character conversion problem
Date: Thu, 4 Nov 2004 11:03:56 -0000
MIME-Version: 1.0
X-Mailer: Microsoft Office Outlook, Build 11.0.5510
Thread-Index: AcTCXIqFQjBgTFQmSbWCiwdcElWWHwAAS5AQ
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
In-Reply-To: <OFA6C73A6F.C4D4B353-ONC1256F42.003A0486 AT dvholten.de>
Message-Id: <E1CPfPL-0005GI-00 AT ukmail1.eechost.net>
X-Auth-Info: mike AT saxonica.com (login)
Content-Type: text/plain;
charset="US-ASCII"
Content-Transfer-Encoding: 7bit
X-Content-Filtered-By: Mailman/MimeDel 2.1.5
Cc: xom-interest AT lists.ibiblio.org
X-BeenThere: xom-interest AT lists.ibiblio.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: xom-interest.lists.ibiblio.org
List-Unsubscribe: <http://lists.ibiblio.org/mailman/listinfo/xom-interest>,
<mailto:xom-interest-request AT lists.ibiblio.org?subject=unsubscribe>
List-Archive: <https://lists.ibiblio.org/sympa/arc/xom-interest>
List-Post: <mailto:xom-interest AT lists.ibiblio.org>
List-Help: <mailto:sympa AT lists.ibiblio.org?subject=HELP>
List-Subscribe: <http://lists.ibiblio.org/mailman/listinfo/xom-interest>,
<mailto:xom-interest-request AT lists.ibiblio.org?subject=subscribe>
X-List-Received-Date: Thu, 04 Nov 2004 11:03:59 -0000

sure, xml supports characters wider than 2 bytes - but does java ??
having a valid xml-document doesnt mean, that anybody can actually process
it.

Characters above 65535 are represented in Java as a so-called surrogate
pair.

after parsing the document, the attribute 'character="&#x50000;" ' is just
a java-string, limited to 2byte characters - i think.

would be interesting to see, if *any* xsl-processor can make sense of that.

Of course they can. Certainly Saxon can.

Michael Kay




Archive powered by MHonArc 2.6.24.

Top of Page