Re: xmlproc maintainer?
Alban Hertroys wrote: We recently (about a week ago) sent a patch to the maintainer of xmlproc, but we didn't receive a reply yet. A look at the site reveals that the last update was somewhere in 2000. Does anybody know who the current maintainer is (if that changed), or what the status of xmlproc is? We kind of depend on it... xmlproc is maintained as part of PyXML now; please sent the patch to the patches tracker at sf.net/projects/pyxml. That said, PyXML did not have a release on its own for quite some time, either; mainly due to lack of user interest. Regards, Martin -- http://mail.python.org/mailman/listinfo/python-list
Re: xmlproc maintainer?
Alban Hertroys wrote: We recently (about a week ago) sent a patch to the maintainer of xmlproc, but we didn't receive a reply yet. A look at the site reveals that the last update was somewhere in 2000. Does anybody know who the current maintainer is (if that changed), or what the status of xmlproc is? We kind of depend on it... The patch fixes a buffering problem if the XML contains utf-8 codes, which gets especially problematic if one such character pair starts as the last byte in the buffer... Patch attached, in case someone can use it. This should no longer be an issue with Python 2.4, because the stateful UTF-8 and UTF-16 decoder have been fixed to support incomplete input. Unfortunately xmlproc doesn't seem to use the stateful decoder but the stateless decoder (and even handcrafted decoders when the codecs module doesn exist). Adding support for this might be a little tricky, because the parser must determine which encoding to use before instantiating the decoder. Bye, Walter Dörwald -- http://mail.python.org/mailman/listinfo/python-list
xmlproc maintainer?
Hello all,
We recently (about a week ago) sent a patch to the maintainer of
xmlproc, but we didn't receive a reply yet. A look at the site reveals
that the last update was somewhere in 2000.
Does anybody know who the current maintainer is (if that changed), or
what the status of xmlproc is? We kind of depend on it...
The patch fixes a buffering problem if the XML contains utf-8 codes,
which gets especially problematic if one such character pair starts as
the last byte in the buffer... Patch attached, in case someone can use it.
Regards,
Alban Hertroys,
MAG Productions.
--- ../xmlproc-backup/xmlutils.py 2005-03-11 11:04:44.0 +0100
+++ xmlutils.py 2005-03-11 13:45:43.0 +0100
@@ -264,8 +264,8 @@
decoder could have run out of data. The latter case is very
hard to determine in Python 2.0"""
-if str(exc) in ["UTF-8 decoding error: unexpected end of data",
-"UTF-16 decoding error: truncated data"]:
+s = str(exc)
+if s.find('unexpected end of data')!=-1 or s.find('truncated
data')!=-1:
while 1:
self.encoded_data = new_data[-1]+self.encoded_data
new_data = new_data[:-1]
@@ -296,7 +296,7 @@
first_feed = 1
self.parseStart()
-new_data = new_data + self.encoded_data
+new_data = self.encoded_data + new_data
self.encoded_data = ""
if not decoded and not self.charset_converter:
@@ -720,6 +720,7 @@
# to the recoding.
try:
self.data = self.charset_converter(self.data)
+ self.datasize = len(self.data)
except UnicodeError, e:
self._handle_decoding_error(self.data, e)
self.input_encoding = enc1
--
http://mail.python.org/mailman/listinfo/python-list
