Re: Expat with UTF-32 support (as implemented in 4Suite.org)

Hi Jeremy,

thx again for your fast respond to my new suggestion.

> Just for an update, I've checked in build support code to limit the
> symbols  exported from the cDomlettec.so Python module.  It should now
> be able to be  used within mod_python without conflicts (at least on
> platforms that have a  fairly recent toolchain (2003+).

Ok, I'l check this as soon as a new CVS snapshot file exists.

> Raphael, please try latest CVS without applying the patch to build
> against  libexpat.  Is there someplace that lists a process that would
> reproduce the  conflict/error within mod_python that prompted the
> patch in the first place?   I would really like to be able to test
> this myself as I now run on a  Debian-based distro (Kubuntu).

Please refer to http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=275097
to get a contact address and the history of the mod_python problem.
As soon as I've time I will contact Mirko (original reporter of this problem)
for help in testing. Maybe he has time for us/me ;)

Do you think it make sense to contribute your extension of libexpat upstream?

-- 
Raphael Bossek

_______________________________________________
Expat-discuss mailing list
[email protected]
http://mail.libexpat.org/mailman/listinfo/expat-discuss

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)

iD8DBQFDQujQN2lBq4Nesv8RAoWZAJ9Su98v7J15Hs0rGNOH7DTvPi8FMwCdFqDU
ykfa7xHgQa5BC6/irpnqX/U=
=LrnK
-----END PGP SIGNATURE-----