James Pearson wrote:
> 
> Hi,
> 
> Are there any significant differences between XML4C 3.1.0 and Xerces 1.1.0?

XML4C 3.1.0 = Xerces 1.1.0 + ICU 1.4

ICU is a separate Open Source project (about 10 companies participating) on the
DeveloperWorks site at IBM.  ICU stands for "International Components for 
Unicode", and it
does a large number of conversions between various code pages and Unicode, as 
well as providing
a portable library for manipulating Unicode strings. 

Because it's a separate open source project, we haven't put it into the 
xml.apache.org source 
code repository.  And, Xerces-C has built-in support for a small number of code 
pages (like UTF-8,
iso-latin-1, US-ASCII, and UTF-16), so you don't necessarily need ICU anyway, 
if you stick to those
encodings.

If you need Shift_JIS or Big5 support, for example, you'll need a transcoding 
service.  Xerces
provides
3 ways to do it, using an abstracted transcoding API:  ICU (go get it from 
developerworks), iconv
(many Unixes have this), and Win32 (clearly only available on Win32).

So, for XML4C, the ICU code is publically available, and IBM just does the 
integration.

> I'm planning to port my app (now on Win2000) to Sun and later to OS/390.
> It would be nice if I could use the same source for all platforms - I kinda
> thought I could.

Yes, you should be able to do this.  
 
> Mike Pogue said:
> "The IBM 390 people plan to have a OS/390 version available (using the
> latest Xerces code base) in 60-90 days."
> 
> Does anyone know if this will this be available as a Xerces release?

XML.apache.org won't be building any 390 releases itself, because it doesn't 
have a 390 to
do it on!  So, right now, here's the way it works:  the IBM 390 porting group 
in Poughkeepsie 
ports Xerces to 390, and sends the changes to my group (in California), and we 
put 
the changes into Xerces, so that everybody gets them under the open source 
Apache license.
You can then get Xerces, and compile it yourself.

The Xerces-C 1.1.0 release should build on 390 right now (hey, could you try 
this, and let us
know?).  
I probably should have said that the 390 people will have an _official_ IBM 
release on 390 in 60-90
days, 
but I don't want to turn this into a product announcement or commitment on 
their part.  If you want
to 
know what IBM is doing _officially_, you should talk to them directly...(he 
said with his apache hat
on!)
 
> Thanks,
> Jim Pearson
> Sheepshead Bay, Brooklyn
> 
> -----Original Message-----
> From: Anupam Bagchi [mailto:[EMAIL PROTECTED]
> Sent: Monday, March 13, 2000 6:11 PM
> To: [EMAIL PROTECTED]
> Subject: Re: XML Parser on OS390
> 
> XML4C Version 3.1.0 actually compiles and builds out of the box on OS/390.
> Please download it directly from IBM's AlphaWorks site
> http://www.alphaworks.ibm.com. It is based on Xerces-C 1.1.0.
> 
> - Anupam
> ================================================
> Anupam Bagchi
> Advisory Software Engineer
> XML Development Group, IBM Cupertino
> Email: [EMAIL PROTECTED], [EMAIL PROTECTED]
> Phone: 408-777-5842
> ================================================
> ----- Original Message -----
> From: Yen Trinh <[EMAIL PROTECTED]>
> To: <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>
> Cc: <[EMAIL PROTECTED]>
> Sent: Friday, March 10, 2000 10:13 PM
> Subject: XML Parser on OS390
> 
> > I'm looking for a XML Parser (SAX parser is what we need for now) for
> > OS390.  My main application is running on MVS Batch, with POXIS on and
> > multi threaded environment and it is written mostly in c and some c++.
> > Is there something that has been ported and working on the MVS?
> >
> > In November, Mike Pogue mentioned that Xerces-C with XML4C version 2 was
> > ported to OS390.  Is this still available for download?
> >
> > Thanks for any advice,
> > Yen
> >

Reply via email to