You don't need to worry too much about WinCE users of the parser, because there should not be very many. To my knowledge, there are no WinCE compilers that support exception handling which is used through-out the Xerces code. We found this out, because we are using both Xerces C and Xerces J for development and hoped to use Xerces C in the WinCE version of our product, but once we began the port, we discovered the lack of exception handling capabilities.
Now, VC++ for WinCE does support what M$ calls 'structured exceptions', basically using a different and incompatible syntax... -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Tuesday, March 07, 2000 4:53 PM To: [EMAIL PROTECTED] Subject: Win32 transcoder I just checked in an early first cut of a Win32 transcoder, basd very loosely on Eric Ulivek's donated code. I've simplified it quite a bit, and I haven't added the support for the IE based code pages. We want to explore the ramifications of this a little more before commiting to that. The current cut will use any valid installed windows code pages. Unless I'm missing something, this is *not* the list in the charsets page. That page shows you all of the possibilities, but not all of them are valid installed code pages. This is not how Eric's works, as best I can tell, which seems to assume that they are all available for use. But, from some emperical experiment's some of them listed which are not IE based ones either, are not available unless they explicitly loaded onto the host system. Anyway, check it out and comment if you have any thoughts. And comment on the pros/cons of using the IE based ones, and what that might mean for instance for a WinCE user of this parser and other related issues. ---------------------------------------- Dean Roddey Software Weenie IBM Center for Java Technology - Silicon Valley [EMAIL PROTECTED]
