Re: [4suite-dev] Re: Expat with UTF-32 support (as implemented in
Jeremy Kloth <[email protected]>
| Newsgroups | gmane.text.xml.expat.general |
|---|---|
| Organization | Fourthought, Inc. |
| Message-ID | <[email protected]> |
I will start off with some clarification as to what Raphael is saying is "UTF-32 support". The UTF-32 (or UCS-4, pick your name) support is for *internal* encoding only. That is, for non-Expat hackers, the encoding of XML_Char strings. On Tuesday 04 October 2005 7:22 am, Karl Waclawek wrote: > Raphael Bossek wrote: > >Hi expat team, > > > >first, I'm the 4suite.org Debian GNU/Linux maintainer. 4suite is a > >XML package for Python using expat today with UTF-32 support. And > >here is the problem. Using the official libexpat library will not > >work with 4suite.org due to missing UTF-32 support. The 4suite.org > >team extended the expat implementation for their project themself. > > > >I'm interested in makeing the UTF-32 support part of the upcomming > >2.0 release. Before making the public I would like to discuss the > >problems about this extension. I'l like to know if such extension > >would be accepted before 2.0 release. > > In principle yes, but it depends on how invasive the patch is, and how > it affects the existing > functionality. In any case I would say we would rather release it as > 1.95.9, to give it some public > exposure and find possible bugs. A raw patch against the 4Suite CVS would be somewhat invasive as I also added a few optimization tweaks while implementing internal UTF-32/UCS-4 support. > >Without the UTF-32 support in libexpat it will be mutch harder for > >me to maintain 4suite.org package for Debian GNU/Linux. The usage > >for libexpat instead of staticly linking the 4suite.org extension > >into the Python modules is mandatory for mod_python environments. > >We have to make sure only one version of expat symbols is loaded > >into memory. > > > >Any idears are welcome. In the meantime I'l investigate the patch > >done by the 4suite.org team and make a patch agains latest CVS. > >I've also see MSVC 6.0 support in it. Is there any interest in it? Thankfully, the patch should be only my changes as I sync'ed to CVS before working on the changes. -- Jeremy Kloth Fourthought, Inc. http://fourthought.com/ http://4suite.org/