From brian@sweetapp.com  Fri May  2 19:54:03 2003
From: brian@sweetapp.com (Brian Quinlan)
Date: Fri, 02 May 2003 11:54:03 -0700
Subject: [XML-SIG] ANN: Pyana 0.8.0 Released
In-Reply-To: <5het8b.tqs.ln@jbmail.com>
Message-ID: <004401c310dc$33926eb0$21795418@dell1700>

ANN: Pyana 0.8.0 Released

Download it from:
http://sourceforge.net/project/showfiles.php?group_id=28142

Changes:

- Node-sets can now be passed as XPath extension arguments
- A few more DOM methods are exposed
- Experimental support for transformation to DOM
- Support for Python wide Unicode builds
- Support for external schema validation
- Bug fixes
- Mac OS X build support
- Updated for Xalan 1.5/Xerces 2.2
- Python2.3b1 support (including support for the new bool type
  in XPath expressions)
- The getEncoding(), getPublicID() and getSystemID() methods of 
  InputSource objects are now honored
- More detailed (and Python customizable) information presented 
  when DOM nodes are printed

What is Pyana?

Pyana is a Python interface to the Xalan C XSLT processor.

Some usage examples are provided here:
http://pyana.sourceforge.net/examples/



From noreply@sourceforge.net  Mon May  5 04:01:43 2003
From: noreply@sourceforge.net (SourceForge.net)
Date: Sun, 04 May 2003 20:01:43 -0700
Subject: [XML-SIG] [ pyxml-Bugs-732458 ] Source RPM
Message-ID: <E19CWEZ-0005Hk-00@sc8-sf-web4.sourceforge.net>

Bugs item #732458, was opened at 2003-05-04 22:01
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=106473&aid=732458&group_id=6473

Category: None
Group: None
Status: Open
Resolution: None
Priority: 5
Submitted By: Christopher Blunck (blunck2)
Assigned to: Nobody/Anonymous (nobody)
Summary: Source RPM

Initial Comment:
The i386 RPMs are linked against a Python interpreter
that supports UCS2 encoding.  The latest RedHat uses
Python 2.2.2, which supports UCS4.  It would be helpful
to provide a source RPM that we RedHat folks could use
so that we can build our own PyXML that works with our
Python.



----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=106473&aid=732458&group_id=6473


From Ian.Sparks@etrials.com  Mon May  5 21:45:48 2003
From: Ian.Sparks@etrials.com (Ian Sparks)
Date: Mon, 5 May 2003 16:45:48 -0400
Subject: [XML-SIG] Newbie : Identifying characters that will choke XML parser
Message-ID: <41A1CBC76FDECC42B67946519C6677A9A20B28@pippin.int.etrials.com>

I build an XML document from data pulled from a database. Sometimes the =
database contains "bad" characters, how can I filter out the bad and =
properly encode the good?

Here's my example program...I'm sure I'm missing something fundamental.=20

from xml.dom.minidom import parseString

bad_string =3D chr(133) + chr(6) + chr(180)

doc1 =3D parseString('<test/>')
docNode =3D doc1.childNodes[0]
docNode.setAttributeNS(None,'a',unicode(bad_string,'iso-8859-1'))
source =3D doc1.toxml('iso-8859-1')   #result is badly formed xml


From martin@v.loewis.de  Mon May  5 23:09:40 2003
From: martin@v.loewis.de (Martin v. =?iso-8859-15?q?L=F6wis?=)
Date: 06 May 2003 00:09:40 +0200
Subject: [XML-SIG] Newbie : Identifying characters that will choke XML parser
In-Reply-To: <41A1CBC76FDECC42B67946519C6677A9A20B28@pippin.int.etrials.com>
References: <41A1CBC76FDECC42B67946519C6677A9A20B28@pippin.int.etrials.com>
Message-ID: <m3of2h82qj.fsf@mira.informatik.hu-berlin.de>

"Ian Sparks" <Ian.Sparks@etrials.com> writes:

> I build an XML document from data pulled from a database. Sometimes
> the database contains "bad" characters, how can I filter out the bad
> and properly encode the good?

If you want to completely discard the bad characters, I recommend use
use string.replace.

Regards,
Martin



From Ian.Sparks@etrials.com  Tue May  6 13:17:15 2003
From: Ian.Sparks@etrials.com (Ian Sparks)
Date: Tue, 6 May 2003 08:17:15 -0400
Subject: [XML-SIG] Newbie : Identifying characters that will choke XML parser
Message-ID: <41A1CBC76FDECC42B67946519C6677A95AE4F8@pippin.int.etrials.com>

Hmm...as I feared. As I discover new XML-chokers I'm building up a =
library like :

#Remove ACK's (I've seen it!)
w =3D w.replace(chr(6),'')
#Remove ... characters (again, I've seen it)
w =3D w.replace(chr(133),'')

I was hoping to find some way of identifying everything that will choke =
my XML, some rule to auto-filter out the nastiness..


-----Original Message-----
From: Martin v. L=F6wis [mailto:martin@v.loewis.de]
Sent: Monday, May 05, 2003 6:10 PM
To: Ian Sparks
Cc: Xml-Sig (E-mail)
Subject: Re: [XML-SIG] Newbie : Identifying characters that will choke
XML parser


"Ian Sparks" <Ian.Sparks@etrials.com> writes:

> I build an XML document from data pulled from a database. Sometimes
> the database contains "bad" characters, how can I filter out the bad
> and properly encode the good?

If you want to completely discard the bad characters, I recommend use
use string.replace.

Regards,
Martin



From tug@wilson.co.uk  Tue May  6 13:32:47 2003
From: tug@wilson.co.uk (John Wilson)
Date: Tue, 6 May 2003 13:32:47 +0100
Subject: [XML-SIG] Newbie : Identifying characters that will choke XML parser
References: <41A1CBC76FDECC42B67946519C6677A95AE4F8@pippin.int.etrials.com>
Message-ID: <000b01c313cb$99f3dad0$640a0b0a@handel>

Ian,

If the character is in the following ranges it's illegal:

c < 0X0009
c > 0X000A and c < 0X000D
c > 0X000D and c < 0X0020
c > 0XD7FF and c < 0XE000
c > 0XFFFD

John Wilson
The Wilson Partnership
http://www.wilson.co.uk

----- Original Message ----- 
From: "Ian Sparks" <Ian.Sparks@etrials.com>
To: "Martin v. Löwis" <martin@v.loewis.de>
Cc: "Xml-Sig (E-mail)" <xml-sig@python.org>
Sent: Tuesday, May 06, 2003 1:17 PM
Subject: RE: [XML-SIG] Newbie : Identifying characters that will choke XML
parser


Hmm...as I feared. As I discover new XML-chokers I'm building up a library
like :

#Remove ACK's (I've seen it!)
w = w.replace(chr(6),'')
#Remove ... characters (again, I've seen it)
w = w.replace(chr(133),'')

I was hoping to find some way of identifying everything that will choke my
XML, some rule to auto-filter out the nastiness..



From joakley@solutioninc.com  Tue May  6 14:40:32 2003
From: joakley@solutioninc.com (James Oakley)
Date: Tue, 6 May 2003 10:40:32 -0300
Subject: [XML-SIG] Newbie : Identifying characters that will choke XML parser
In-Reply-To: <41A1CBC76FDECC42B67946519C6677A95AE4F8@pippin.int.etrials.com>
References: <41A1CBC76FDECC42B67946519C6677A95AE4F8@pippin.int.etrials.com>
Message-ID: <200305061040.36857.joakley@solutioninc.com>

=2D----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Tuesday 06 May 2003 09:17 am, Ian Sparks wrote:
> Hmm...as I feared. As I discover new XML-chokers I'm building up a library
> like :
>
> #Remove ACK's (I've seen it!)
> w =3D w.replace(chr(6),'')
> #Remove ... characters (again, I've seen it)
> w =3D w.replace(chr(133),'')
>
> I was hoping to find some way of identifying everything that will choke my
> XML, some rule to auto-filter out the nastiness..

I had the same trouble with a xmlrpclib.loads(). Here's what I did:


# These characters are forbidden in XML. We'll just drop them
badchars =3D (0, 1, 2, 3, 4, 5, 6, 7, 8, 11, 12, 14, 15, 16, 17, 18, 19, 20=
, \
            21, 22, 23, 24, 25, 26, 27, 28, 29, 30, 31)

# Remove invalid characters
data =3D filter(lambda x: ord(x) not in badchars, data)

# Convert 8-bit characters to numeric entities
data =3D re.sub(r'[\x7F-\xFF]',
               lambda m: '&#%d;' % ord(m.group(0)),
              data
             )



Hope that helps,

=2D --=20
James Oakley
Engineering - SolutionInc Ltd.
joakley@solutioninc.com
http://www.solutioninc.com
=2D----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.7 (GNU/Linux)

iD8DBQE+t7tR+FOexA3koIgRAoXmAKCSPJhyTIX/s3jWewvJf1n1l4dn8gCghr1X
kZ6QtVmIR33bJAtXaceH/L0=3D
=3DE+Xs
=2D----END PGP SIGNATURE-----



From Ian.Sparks@etrials.com  Tue May  6 17:45:33 2003
From: Ian.Sparks@etrials.com (Ian Sparks)
Date: Tue, 6 May 2003 12:45:33 -0400
Subject: [XML-SIG] Newbie : Identifying characters that will choke XML parser
Message-ID: <41A1CBC76FDECC42B67946519C6677A9A20B29@pippin.int.etrials.com>

Thank you James & John your solutions allow me to filter out what should =
be marked as "bad" characters.

However, I'm having real problems with character conversions. I'm =
building an xml document using minidom and setAttributeNS()

I want to be able to do something like :

from xml.dom.minidom import parseString

doc1 =3D parseString('<test/>')
docNode =3D doc1.childNodes[0]
docNode.setAttributeNS(None,'a',chr(180))
source =3D doc1.toxml('iso-8859-1')

and have source contain :

<?xml version=3D"1.0" encoding=3D"iso-8859-1" ?>=20
<test a=3D"&#180;"/>

without getting UnicodeErrors from codecs.py on toxml() and without =
ending up with :

<?xml version=3D"1.0" encoding=3D"iso-8859-1" ?>=20
<test a=3D"&amp;#180;"/>

Either this is really hard or, more likely, I'm really ignorant.






From tug@wilson.co.uk  Tue May  6 21:55:40 2003
From: tug@wilson.co.uk (John Wilson)
Date: Tue, 6 May 2003 21:55:40 +0100
Subject: [XML-SIG] Newbie : Identifying characters that will choke XML parser
References: <41A1CBC76FDECC42B67946519C6677A9A20B29@pippin.int.etrials.com>
Message-ID: <098f01c31411$daa26060$640a0b0a@handel>

I've done some poking around with minidom (I have never used it before). It
would appear that it does (correctly) replace & with &amp; but it does not
like characters with values > 127 and does not replace them with numeric
character entities.

I would suggest that you try using the full DOM implementation.

John Wilson
The Wilson Partnership
http://www.wilson.co.uk

----- Original Message ----- 
From: "Ian Sparks" <Ian.Sparks@etrials.com>
To: "James Oakley" <joakley@solutioninc.com>; <xml-sig@python.org>; "John
Wilson" <tug@wilson.co.uk>
Sent: Tuesday, May 06, 2003 5:45 PM
Subject: RE: [XML-SIG] Newbie : Identifying characters that will choke XML
parser


Thank you James & John your solutions allow me to filter out what should be
marked as "bad" characters.

However, I'm having real problems with character conversions. I'm building
an xml document using minidom and setAttributeNS()

I want to be able to do something like :

from xml.dom.minidom import parseString

doc1 = parseString('<test/>')
docNode = doc1.childNodes[0]
docNode.setAttributeNS(None,'a',chr(180))
source = doc1.toxml('iso-8859-1')

and have source contain :

<?xml version="1.0" encoding="iso-8859-1" ?>
<test a="&#180;"/>

without getting UnicodeErrors from codecs.py on toxml() and without ending
up with :

<?xml version="1.0" encoding="iso-8859-1" ?>
<test a="&amp;#180;"/>

Either this is really hard or, more likely, I'm really ignorant.







From dholub@intersight.com  Wed May  7 00:06:18 2003
From: dholub@intersight.com (Deirdre Holub)
Date: Tue, 6 May 2003 16:06:18 -0700
Subject: [XML-SIG] broken setup.py for pyxml-0.8.2 on OSX
Message-ID: <5804E20A-8017-11D7-BCC4-000A957665F6@intersight.com>

I had to modify the setup.py by adding:

import distutils

to get setup.py to run on my OSX box.




From mark@easymailings.com  Wed May  7 01:13:09 2003
From: mark@easymailings.com (Mark Bucciarelli)
Date: Tue, 6 May 2003 20:13:09 -0400
Subject: [XML-SIG] Is this a memory leak?
Message-ID: <200305062013.10358.mark@easymailings.com>

#!/usr/bin/python

import xml.sax
import StringIO
import gc

gc.set_debug(gc.DEBUG_SAVEALL)

class TestHandler(xml.sax.handler.ContentHandler):
    all_things = {}

    def __init__(self):
        TestHandler.all_things[id(self)] = 1
    def __del__(self):
        del TestHandler.all_things[id(self)]

for i in range(400):
    parser = xml.sax.make_parser()
    t = TestHandler()
    parser.setContentHandler(t)
    input = xml.sax.xmlreader.InputSource()
    input .setByteStream(StringIO.StringIO('bad soap request'))
    try: parser.parse(input)
    except: pass

gc.collect()
print 'garbage', len(gc.garbage)   # 11970
print len(TestHandler.all_things)  # 400

Moving the parser = xml.sax.make_parser() out of the loop changes the 
print statement output 0 and 1.

Mark

P.S.  Occurs on both:
python 2.2.1, Linux, has .../site-packages/_xmlplus
python 2.2.2, XP, doesn't have .../site-packages/_xmlplus

P.P.S While working on this problem, I found a great blog entry by 
Jeremy Hylton on debugging memory leaks at:

http://www.python.org/~jeremy/weblog/030410.html

Looks like the next release of ZODB (and Zope) will have some leaks 
plugged.


From tpassin@comcast.net  Wed May  7 07:10:51 2003
From: tpassin@comcast.net (Thomas B. Passin)
Date: Wed, 07 May 2003 02:10:51 -0400
Subject: [XML-SIG] Newbie : Identifying characters that will choke XML
 parser
References: <41A1CBC76FDECC42B67946519C6677A9A20B29@pippin.int.etrials.com>
Message-ID: <003001c3145f$695b36e0$6401a8c0@tbp1>

Ian,

You need to put a unicode character in there to begin with -

docNode.setAttributeNS(None,'a',unicode('\xb4','iso-8859-1'))

chr(xxx) does not do this for you.

Cheers,

Tom P

[Ian Sparks]

Thank you James & John your solutions allow me to filter out what should be
marked as "bad" characters.

However, I'm having real problems with character conversions. I'm building
an xml document using minidom and setAttributeNS()

I want to be able to do something like :

from xml.dom.minidom import parseString

doc1 = parseString('<test/>')
docNode = doc1.childNodes[0]
docNode.setAttributeNS(None,'a',chr(180))
source = doc1.toxml('iso-8859-1')

and have source contain :

<?xml version="1.0" encoding="iso-8859-1" ?>
<test a="&#180;"/>

without getting UnicodeErrors from codecs.py on toxml() and without ending
up with :

<?xml version="1.0" encoding="iso-8859-1" ?>
<test a="&amp;#180;"/>





From mark@easymailings.com  Wed May  7 14:26:02 2003
From: mark@easymailings.com (Mark Bucciarelli)
Date: Wed, 7 May 2003 09:26:02 -0400
Subject: [XML-SIG] Is this a memory leak?
In-Reply-To: <200305062013.10358.mark@easymailings.com>
References: <200305062013.10358.mark@easymailings.com>
Message-ID: <200305070926.02347.mark@easymailings.com>

More info ...

According to a comment on SOAPpy bug #585837, the reset() method in 
expatreader.py creates a bound function loop.

I'm going to try and figure out a patch and then submit something to 
the pyxml sourceforge site.

Since the same behavior occurs whether or not I have _xmlplus 
installed, should I submit one to the python sourceforge site as 
well?

Mark


From noreply@sourceforge.net  Wed May  7 15:06:32 2003
From: noreply@sourceforge.net (SourceForge.net)
Date: Wed, 07 May 2003 07:06:32 -0700
Subject: [XML-SIG] [ pyxml-Bugs-733890 ] Memory Leak in expatparser.py
Message-ID: <E19DPZ2-0000hZ-00@sc8-sf-web3.sourceforge.net>

Bugs item #733890, was opened at 2003-05-07 10:06
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=106473&aid=733890&group_id=6473

Category: SAX
Group: None
Status: Open
Resolution: None
Priority: 5
Submitted By: Mark Bucciarelli (mbucc)
Assigned to: Nobody/Anonymous (nobody)
Summary: Memory Leak in expatparser.py

Initial Comment:
Looks like there is a bound-function loop created in 
ExpatReader.reset() method. 
 
I've attached a script that demonstrates the leak as well as a work 
around. 
 
Here are some comments from pywebsvcs bug #585837 on 
sourceforge: 
 
... printing out the contents of gc.garbage shows  
 
 <bound method ExpatParser.start_element_ns of 
<xml.sax.expatreader.ExpatParser instance at 
0x816b17c>>, 
 <bound method ExpatParser.end_element_ns of 
<xml.sax.expatreader.ExpatParser instance at 
0x816b17c>>, 
 

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=106473&aid=733890&group_id=6473


From phthenry@earthlink.net  Wed May  7 17:04:18 2003
From: phthenry@earthlink.net (Paul Tremblay)
Date: Wed, 7 May 2003 12:04:18 -0400
Subject: [XML-SIG] checking a string for well-formedness
Message-ID: <20030507120418.Q13810@localhost.localdomain>

I need to check a string for well-formedness. I stumbed across the
fact that you can use expat directly, so I devised this code, which
works, so long as unicode and entities aren't used:

import xml.parsers.expat
parser = xml.parsers.expat.ParserCreate()
import sys

def validate(data):
    parser.Parse(data)
    try:
        parser.Parse(data)
        return 0
    except xml.parsers.expat.ExpatError:
        sys.stderr.write('tagging text will result in invalid XML\n')
        return 1

data = '<doc><tag>text</tag><tag>text,</tag></doc>'
validate(data)

The function validate returns 0 in this case. However, if I try this:

data = u'<doc><tag>text</tag><tag>text\u201c</tag></doc>'

I get the following error:


Traceback (most recent call last):
  File "/home/paul/lib/python/paul/xml/expat.py", line 50, in ?
    parser.Parse(data)                                         
UnicodeError: ASCII encoding error: ordinal not in range(128)

Any idea what is going on here? 

I have re-written the function so that it it writes the string to a
file, and then I use SAX to parse the file. If SAX fails, I know I
have ill-formed XML. However, this second solution is a kludge. I
would like to be able to test the string directly.

Thanks

Paul
-- 

************************
*Paul Tremblay         *
*phthenry@earthlink.net*
************************


From mal@lemburg.com  Wed May  7 17:57:07 2003
From: mal@lemburg.com (M.-A. Lemburg)
Date: Wed, 07 May 2003 18:57:07 +0200
Subject: [XML-SIG] Is this a memory leak?
In-Reply-To: <200305070926.02347.mark@easymailings.com>
References: <200305062013.10358.mark@easymailings.com> <200305070926.02347.mark@easymailings.com>
Message-ID: <3EB93AE3.8010400@lemburg.com>

Mark Bucciarelli wrote:
> More info ...
> 
> According to a comment on SOAPpy bug #585837, the reset() method in 
> expatreader.py creates a bound function loop.
> 
> I'm going to try and figure out a patch and then submit something to 
> the pyxml sourceforge site.
> 
> Since the same behavior occurs whether or not I have _xmlplus 
> installed, should I submit one to the python sourceforge site as 
> well?

I remember having seen reports of memory leaks in pyexpat. No
idea whether they've been fixed, though. You may want to try
this against Python CVS.

-- 
Marc-Andre Lemburg
eGenix.com

Professional Python Software directly from the Source  (#1, May 07 2003)
 >>> Python/Zope Products & Consulting ...         http://www.egenix.com/
 >>> mxODBC, mxDateTime, mxTextTools ...        http://python.egenix.com/
________________________________________________________________________
EuroPython 2003, Charleroi, Belgium:                        48 days left



From mark@easymailings.com  Wed May  7 21:46:31 2003
From: mark@easymailings.com (Mark Bucciarelli)
Date: Wed, 7 May 2003 16:46:31 -0400
Subject: [XML-SIG] Two SimpleXMLRPCServer questions
In-Reply-To: <003001c2e732$091a3a10$21795418@dell1700>
References: <003001c2e732$091a3a10$21795418@dell1700>
Message-ID: <200305071646.31073.mark@easymailings.com>

On Monday 10 March 2003 1:22 pm, Brian Quinlan wrote:

> > The other question I have is how to make this server stop (and
> > perhaps finish it's work) when someone presses a control-C in the
> > console.
>
> Hmmmm....the fact that this doesn't work better already is probably
> a bug.

Just noticed that this behavior is different on Linux than on Windows.  
On Linux (2.2.1), ctrl-c stops the server.  On Windows (2.2.2), it 
does not.

Mark


From jedp@ilm.com  Wed May  7 23:34:31 2003
From: jedp@ilm.com (Jed Parsons)
Date: Wed, 7 May 2003 15:34:31 -0700 (PDT)
Subject: [XML-SIG] endElement handler for XMLValParser?
Message-ID: <200305072234.PAA15537@gleason.lucasdigital.com>

Hola -

I'm writing my first handler using the validating parser from
xml.sax.sax2exts.XMLValParserFactory.make_parser().  I can't figure
out how to handle end tags for elements.

I've set up a content handler that extends
xml.sax.handler.ContentHandler.

I use the parser's setContentHandler method and parse.

My startElement, characters, and ignorableWhitespace methods all get
called, but my endElement is sadly neglected.

A peek at _xmlplus/sax/drivers/drv_xmlproc_val.py finds no end element 
handlers for this parser.

(CVS info: drv_xmlproc_val.py,v 1.9 2001/12/30 12:13:45 loewis)

What to do?

Thanks for any help,

Jed

-- 
Jed Parsons       Industrial Light + Magic  (415) 448-2974 
	     
grep(do{for(ord){(!$_&&print"$s\n")||(($O+=(($_-1)%6+1)and
grep(vec($s,$O++,1)=1,1..int(($_-6*6-1)/6))))}},(split(//,
"++,++2-27,280,481=1-7.1++2,800+++2,8310/1+4131+1++2,80\0.  What!?"))); 


From fredrik@pythonware.com  Thu May  8 10:54:57 2003
From: fredrik@pythonware.com (Fredrik Lundh)
Date: Thu, 8 May 2003 11:54:57 +0200
Subject: [XML-SIG] Re: checking a string for well-formedness
References: <20030507120418.Q13810@localhost.localdomain>
Message-ID: <b9d9eu$28i$1@main.gmane.org>

Paul Tremblay wrote:

> import xml.parsers.expat
> parser = xml.parsers.expat.ParserCreate()
> import sys
>
> def validate(data):
>     parser.Parse(data)
>     try:
>         parser.Parse(data)
>         return 0
>     except xml.parsers.expat.ExpatError:
>         sys.stderr.write('tagging text will result in invalid XML\n')
>         return 1
>
> data = '<doc><tag>text</tag><tag>text,</tag></doc>'
> validate(data)
>
> The function validate returns 0 in this case.

or raise an exception, if you don't remove the first call to
parser.Parse(data).

unfortunately, even if you remove that line, the function may
still return 0 for invalid XML snippets, e.g:

> data = '<doc><tag>text</tag><tag>text,</tag>'

to fix this, you have to tell the parser that you won't call
it again with more data:

    parser.Parse(data, 1)

> However, if I try this:
>
> data = u'<doc><tag>text</tag><tag>text\u201c</tag></doc>'
>
> I get the following error:
>
> Traceback (most recent call last):
>   File "/home/paul/lib/python/paul/xml/expat.py", line 50, in ?
>     parser.Parse(data)
> UnicodeError: ASCII encoding error: ordinal not in range(128)
>
> Any idea what is going on here?

the parse function requires an 8-bit string, and Python defaults
to ASCII when converting Unicode to 8-bit data.

the simplest way to work around this is to convert the string to
the XML default encoding (utf-8) on the way in:

def validate(data):
    try:
        if isinstance(data, type(u"")):
            data = data.encode("utf-8")
        parser.Parse(data, 1)
        return 0
    except xml.parsers.expat.ExpatError:
        sys.stderr.write('tagging text will result in invalid XML\n')
        return 1

</F>





From nick@isilon.com  Thu May  8 17:10:27 2003
From: nick@isilon.com (Nicholas M. Kirsch)
Date: Thu, 8 May 2003 09:10:27 -0700 (PDT)
Subject: [XML-SIG] Subclassing xml.dom.minidom
In-Reply-To: <16040.15265.307632.75018@grendel.zope.com>
References: <20030424121313.R7584@fireblade.isilon.com>
 <16040.15265.307632.75018@grendel.zope.com>
Message-ID: <20030508090222.N582@fireblade.isilon.com>

> Depending on just which node types you want to affect, this may be
> fairly easy, or it may be more painful.  Changing Text nodes will be
> most difficult if you intend to use xml.dom.xmlbuilder without further
> subclassing.
>
> At the very least, you can expect to subclass the DOMImplementation
> and Document classes (to control the factory functions) and the
> specific node types you want to affect.
>
> I'll be glad to try and answer further questions, but you'll need to
> be more specific.

My desire is to modify the behavior of getAttribute and add inheritance
functionality such that an element inherits its parents attributes (if not
defined) and other wackiness.

I have subclassed DOMImplementation and Document, but using
xml.dom.minidom things still don't work properly. I modified
xml.dom.expatbuilder.theDOMImplementation to be an instance of my
DOMImplementation. When I use xml.dom.minidom.parse, I successfully
retrieve an instance of my Document. However, the Elements are not
subclasses, despite having overriden the Document.createElement method.

Looking at expatbuilder.py, I have found quite a few cases in which it
instantiates an Element by using minidom.Element() instead of
theDOMImplementation.createElement. The same behavior is repeated for
Attributes and Text. This seems like a bug to me?!

Am I going about this incorrectly?

Thanks.

Nick


From jedp@ilm.com  Thu May  8 19:02:31 2003
From: jedp@ilm.com (Jed Parsons)
Date: Thu, 8 May 2003 11:02:31 -0700 (PDT)
Subject: [XML-SIG] end element handling with XMLValidator?
In-Reply-To: <4528886@toto.iv>
Message-ID: <200305081802.LAA19259@gleason.lucasdigital.com>

I'm unable to get a hold of 'end element' events from the validating
parser.  Can anyone explain to me what I'm doing wrong?

Here is a test to show you what's happening:

 1. I extend the xmlproc.Application class, which is what
    xmlval.ValidatingApp does:

<code>
from xml.parsers.xmlproc import xmlproc
class PleaseOhPleaseWork(xmlproc.Application):
    def handle_data(self, data, start, end):
        print "%d chars of good data: [%s]" % (end-start, data[start:end])

    def handle_ignorable_data(self, data, start, end):
        print "%d chars of trash: [%s]" % (end-start, data[start:end])

    def handle_start_tag(self, name, attrs):
        print "start", name

    def handle_end_tag(self, name):
        print "end", name

</code>

 2. I use this test xml file:

<?xml version='1.0'?>
<!DOCTYPE foo SYSTEM "foo.dtd">
<foo>
 <para>
  Glug is the son of Zeus
 </para>
</foo>

 3. I can run two tests at the python console.  Using
    xmlproc.XMLProcessor, I get my start and end handlers.  Using
    xmlval.XMLValidator, I only get the start handler:

> python
Python 2.1.3 (#1, Apr 22 2002, 18:24:35) 
[GCC 2.96 20000731 (Red Hat Linux 7.1 2.96-98)] on linux2
Type "copyright", "credits" or "license" for more information.
>>> from Test import PleaseOhPleaseWork
>>> from xml.parsers.xmlproc import xmlproc
>>> from xml.parsers.xmlproc import xmlval
>>> p_noval = xmlproc.XMLProcessor()
>>> p_noval.set_application(PleaseOhPleaseWork())
>>> p_noval.parse_resource('test.xml')
start foo
2 chars of good data: [
 ]
start para
28 chars of good data: [
  Glug is the son of Zeus
 ]
end para
1 chars of good data: [
]
end foo
>>> p_val = xmlval.XMLValidator()
>>> p_val.set_application(PleaseOhPleaseWork())
>>> p_val.parse_resource('test.xml')
start foo
2 chars of trash: [
 ]
start para
28 chars of good data: [
  Glug is the son of Zeus
 ]
1 chars of trash: [
]
>>> 

This is starting to drive me a little bit insane.  Can somebody
explain to me what is going on here?

Thanks,

Jed

I wrote yesterday (taking a different approach):
> 
> Hola -
> 
> I'm writing my first handler using the validating parser from
> xml.sax.sax2exts.XMLValParserFactory.make_parser().  I can't figure
> out how to handle end tags for elements.
> 
> I've set up a content handler that extends
> xml.sax.handler.ContentHandler.
> 
> I use the parser's setContentHandler method and parse.
> 
> My startElement, characters, and ignorableWhitespace methods all get
> called, but my endElement is sadly neglected.
> 
> A peek at _xmlplus/sax/drivers/drv_xmlproc_val.py finds no end element 
> handlers for this parser.
> 
> (CVS info: drv_xmlproc_val.py,v 1.9 2001/12/30 12:13:45 loewis)
> 
> What to do?
> 
> Thanks for any help,
> 
> Jed

-- 
Jed Parsons       Industrial Light + Magic  (415) 448-2974 
	     
grep(do{for(ord){(!$_&&print"$s\n")||(($O+=(($_-1)%6+1)and
grep(vec($s,$O++,1)=1,1..int(($_-6*6-1)/6))))}},(split(//,
"++,++2-27,280,481=1-7.1++2,800+++2,8310/1+4131+1++2,80\0.  What!?"))); 


From phthenry@earthlink.net  Thu May  8 23:08:38 2003
From: phthenry@earthlink.net (Paul Tremblay)
Date: Thu, 8 May 2003 18:08:38 -0400
Subject: [XML-SIG] Re: checking a string for well-formedness
In-Reply-To: <b9d9eu$28i$1@main.gmane.org>
References: <20030507120418.Q13810@localhost.localdomain> <b9d9eu$28i$1@main.gmane.org>
Message-ID: <20030508180838.D29954@localhost.localdomain>

> the parse function requires an 8-bit string, and Python defaults
> to ASCII when converting Unicode to 8-bit data.

I must be dense when it comes to unicode. So Python converts unicode
to a 7-bit (ASCII) string?

You solution worked, but then I immediately ame up  ith a new problem
when I tried to test the speed of this funciton:

# assume the same exact funtion from below, which I cut and pasted
for j in range(10):
    data = u'<doc><tag>text\u201c</tag><tag>thext,</tag></doc>'
    validate(data)

The first time the string is tested, it comes out as valid. But every
single instance afterwards comes out all ill-formed XML.

Thanks

Paul


On Thu, May 08, 2003 at 11:54:57AM +0200, Fredrik Lundh wrote:
> To: xml-sig@python.org
> From: "Fredrik Lundh" <fredrik@pythonware.com>
> Subject: [XML-SIG] Re: checking a string for well-formedness
> Date: Thu, 8 May 2003 11:54:57 +0200
> 
> Paul Tremblay wrote:
> 
> > import xml.parsers.expat
> > parser = xml.parsers.expat.ParserCreate()
> > import sys
> >
> > def validate(data):
> >     parser.Parse(data)
> >     try:
> >         parser.Parse(data)
> >         return 0
> >     except xml.parsers.expat.ExpatError:
> >         sys.stderr.write('tagging text will result in invalid XML\n')
> >         return 1
> >
> > data = '<doc><tag>text</tag><tag>text,</tag></doc>'
> > validate(data)
> >
> > The function validate returns 0 in this case.
> 
> or raise an exception, if you don't remove the first call to
> parser.Parse(data).
> 
> unfortunately, even if you remove that line, the function may
> still return 0 for invalid XML snippets, e.g:
> 
> > data = '<doc><tag>text</tag><tag>text,</tag>'
> 
> to fix this, you have to tell the parser that you won't call
> it again with more data:
> 
>     parser.Parse(data, 1)
> 
> > However, if I try this:
> >
> > data = u'<doc><tag>text</tag><tag>text\u201c</tag></doc>'
> >
> > I get the following error:
> >
> > Traceback (most recent call last):
> >   File "/home/paul/lib/python/paul/xml/expat.py", line 50, in ?
> >     parser.Parse(data)
> > UnicodeError: ASCII encoding error: ordinal not in range(128)
> >
> > Any idea what is going on here?
> 
> the parse function requires an 8-bit string, and Python defaults
> to ASCII when converting Unicode to 8-bit data.
> 
> the simplest way to work around this is to convert the string to
> the XML default encoding (utf-8) on the way in:
> 
> def validate(data):
>     try:
>         if isinstance(data, type(u"")):
>             data = data.encode("utf-8")
>         parser.Parse(data, 1)
>         return 0
>     except xml.parsers.expat.ExpatError:
>         sys.stderr.write('tagging text will result in invalid XML\n')
>         return 1
> 
> </F>
> 
> 
> 
> 
> _______________________________________________
> XML-SIG maillist  -  XML-SIG@python.org
> http://mail.python.org/mailman/listinfo/xml-sig

-- 

************************
*Paul Tremblay         *
*phthenry@earthlink.net*
************************


From fredrik@pythonware.com  Thu May  8 23:16:26 2003
From: fredrik@pythonware.com (Fredrik Lundh)
Date: Fri, 9 May 2003 00:16:26 +0200
Subject: [XML-SIG] Re: Re: checking a string for well-formedness
References: <20030507120418.Q13810@localhost.localdomain> <b9d9eu$28i$1@main.gmane.org> <20030508180838.D29954@localhost.localdomain>
Message-ID: <b9ekt6$pmq$1@main.gmane.org>

(please don't top-post)

Paul Tremblay wrote:

> > the parse function requires an 8-bit string, and Python defaults
> > to ASCII when converting Unicode to 8-bit data.
>
> I must be dense when it comes to unicode. So Python converts unicode
> to a 7-bit (ASCII) string?

if you're using a Unicode string where Python expects an 8-bit
string, Python refuses to guess, and raises an exception if the
Unicode string contains anything that's not plain ASCII.

> You solution worked, but then I immediately ame up  ith a new problem
> when I tried to test the speed of this funciton:
>
> # assume the same exact funtion from below, which I cut and pasted
> for j in range(10):
>     data = u'<doc><tag>text\u201c</tag><tag>thext,</tag></doc>'
>     validate(data)
>
> The first time the string is tested, it comes out as valid. But every
> single instance afterwards comes out all ill-formed XML.

You have to create a new parser for each run (my mistake; I'd already
fixed two bugs in your code, and missed the third one ;-)

> > def validate(data):
> >     try:
> >         if isinstance(data, type(u"")):
> >             data = data.encode("utf-8")

+ +         parser = xml.parsers.expat.ParserCreate()

> >         parser.Parse(data, 1)
> >         return 0
> >     except xml.parsers.expat.ExpatError:
> >         sys.stderr.write('tagging text will result in invalid XML\n')
> >         return 1

</F>





From phthenry@earthlink.net  Fri May  9 02:51:52 2003
From: phthenry@earthlink.net (Paul Tremblay)
Date: Thu, 8 May 2003 21:51:52 -0400
Subject: [XML-SIG] Re: Re: checking a string for well-formedness
In-Reply-To: <b9ekt6$pmq$1@main.gmane.org>
References: <20030507120418.Q13810@localhost.localdomain> <b9d9eu$28i$1@main.gmane.org> <20030508180838.D29954@localhost.localdomain> <b9ekt6$pmq$1@main.gmane.org>
Message-ID: <20030508215151.F29954@localhost.localdomain>

On Fri, May 09, 2003 at 12:16:26AM +0200, Fredrik Lundh wrote:
> 
> (please don't top-post)
> 
> Paul Tremblay wrote:
> 
> > > the parse function requires an 8-bit string, and Python defaults
> > > to ASCII when converting Unicode to 8-bit data.
> >
> > I must be dense when it comes to unicode. So Python converts unicode
> > to a 7-bit (ASCII) string?
> 
> if you're using a Unicode string where Python expects an 8-bit
> string, Python refuses to guess, and raises an exception if the
> Unicode string contains anything that's not plain ASCII.
> 

This makes a bit more sense. I'll have to read up on encoding.

> > You solution worked, but then I immediately ame up  ith a new problem
> > when I tried to test the speed of this funciton:
> >
> > # assume the same exact funtion from below, which I cut and pasted
> > for j in range(10):
> >     data = u'<doc><tag>text\u201c</tag><tag>thext,</tag></doc>'
> >     validate(data)
> >
> > The first time the string is tested, it comes out as valid. But every
> > single instance afterwards comes out all ill-formed XML.
> 
> You have to create a new parser for each run (my mistake; I'd already
> fixed two bugs in your code, and missed the third one ;-)
> 

Thanks! I thought that it would take a lot of time to create a new
instance each time (don't know why). It takes only one second on my
100 mhz machine to test my string 1,000 times. This method is much
faster than my regular expression hack.

Paul

> > > def validate(data):
> > >     try:
> > >         if isinstance(data, type(u"")):
> > >             data = data.encode("utf-8")
> 
> + +         parser = xml.parsers.expat.ParserCreate()
> 
> > >         parser.Parse(data, 1)
> > >         return 0
> > >     except xml.parsers.expat.ExpatError:
> > >         sys.stderr.write('tagging text will result in invalid XML\n')
> > >         return 1
> 
> </F>
> 
> 
> 
> 
> _______________________________________________
> XML-SIG maillist  -  XML-SIG@python.org
> http://mail.python.org/mailman/listinfo/xml-sig

-- 

************************
*Paul Tremblay         *
*phthenry@earthlink.net*
************************


From Alexandre.Fayolle@logilab.fr  Fri May  9 07:34:50 2003
From: Alexandre.Fayolle@logilab.fr (Alexandre Fayolle)
Date: Fri, 9 May 2003 08:34:50 +0200
Subject: [XML-SIG] end element handling with XMLValidator?
In-Reply-To: <200305081802.LAA19259@gleason.lucasdigital.com>
References: <200305081802.LAA19259@gleason.lucasdigital.com>
Message-ID: <20030509063450.GH20935@calvin>

On Thu, May 08, 2003 at 11:02:31AM -0700, Jed Parsons wrote:
> 
> I'm unable to get a hold of 'end element' events from the validating
> parser.  Can anyone explain to me what I'm doing wrong?

I'm not able to reproduce your problem using either python2.1 or
python2.2 and pyxml 0.8.2, on a Linux machine. 

There's been similar reports in the past, see bug report #658932 on
sourceforge, available at the following URL: 

http://sourceforge.net/tracker/index.php?func=detail&aid=658932&group_id=6473&atid=106473


-- 
Alexandre Fayolle
LOGILAB, Paris (France).
http://www.logilab.com   http://www.logilab.fr  http://www.logilab.org
Développement logiciel avancé - Intelligence Artificielle - Formations


From martin@v.loewis.de  Fri May  9 13:57:40 2003
From: martin@v.loewis.de (=?ISO-8859-1?Q?=22Martin_v=2E_L=F6wis=22?=)
Date: Fri, 09 May 2003 14:57:40 +0200
Subject: [XML-SIG] Re: checking a string for well-formedness
In-Reply-To: <20030508180838.D29954@localhost.localdomain>
References: <20030507120418.Q13810@localhost.localdomain> <b9d9eu$28i$1@main.gmane.org> <20030508180838.D29954@localhost.localdomain>
Message-ID: <3EBBA5C4.6070406@v.loewis.de>

Paul Tremblay wrote:

 > I must be dense when it comes to unicode. So Python converts unicode
 > to a 7-bit (ASCII) string?

In some cases, yes. If you use an API function that requires a byte 
string, such as file.write, it converts to byte strings using the system 
default encoding, which is ASCII.

The resulting strings are still 8-bit strings (i.e. byte strings), since 
your computer cannot represent 7-bit quantities. However, for each byte, 
the MSB will be 0.

> The first time the string is tested, it comes out as valid. But every
> single instance afterwards comes out all ill-formed XML.

The parser maintains internal state, to remember where inside the 
document it is. When parse completes, the state says "at the end of the 
document". It is an error to provide more markup at this point.

You either need to throw away the parser object and create a new one, or 
reset the parser object that you already have.

Regards,
Martin




From steve@bizcardscd.com  Fri May  9 15:24:20 2003
From: steve@bizcardscd.com (Steve Scott (BizCardsCD.com))
Date: Fri, 09 May 2003 10:24:20 -0400
Subject: [XML-SIG] Books on CD or DVD
Message-ID: <023401c31636$af1e00d0$651cd642@StevenLeonScott>

Hello,

I just visited your website and wanted to take a minute to introduce =
myself
and Disc Media Manufacturing. We offer a variety of products and =
services
your currently using.

Disc Media Manufacturing is a full service CD-rom and DVD replication =
facility that offers
in house mastering, CD-ROM, DVD-5, DVD-9 and DVD-10 replication, custom
package design and printing, fully automated and hand packaging, as well =
as
fulfillment and direct mail services. Disc Media Manufacturing currently =
has capacity
to manufacture over 13,000,000 CD=92s a month. We have also added =
additional
DVD-5, DVD-9 and DVD-10 capacity to meet your needs.

We have the experience and ability to replicate your CD/DVD title with =
the
highest commitment to quality, security, and on time delivery! The =
bottom
line, Disc Media offers the most completive rates, on time delivery and =
the
best customer service in the business!

I hope to learn more about your CD/DVD replication needs. I would like =
the
opportunity to earn your business! Call or reply to this e-mail for a
complete price list and or additional information!

Thank you for your time and interest in Disc Media.

Sincerely,

Steve Scott
Disc Media Manufacturing
3820 E. 5th Street
Long Beach, CA 90814

PH # 562-787-0527


From phthenry@earthlink.net  Fri May  9 20:53:36 2003
From: phthenry@earthlink.net (Paul Tremblay)
Date: Fri, 9 May 2003 15:53:36 -0400
Subject: [XML-SIG] state of py-xml?
Message-ID: <20030509155336.G29954@localhost.localdomain>

What is the state of the py.xml package? I downloaded the most recent
version about a  year ago, and upgraded my python to 2.2. 

However, I got frustrated with bugs and was told I needed to use
python 2.1 in order to get SAX to work.

Is it recommended to update both my version of python and the XML
tools at this point?

Paul

-- 

************************
*Paul Tremblay         *
*phthenry@earthlink.net*
************************


From carpet@firework.org  Sun May 11 06:49:30 2003
From: carpet@firework.org (Danny Clark)
Date: Sun, 11 May 2003 01:49:30 -0400
Subject: [XML-SIG] Link Sharing
Message-ID: <005c01c31781$e2572d90$6601a8c0@danny>

I did a web search on interior design and your site was one of those =
listed.  I think the content of our website is similar enough to yours =
that our visitors would benefit from us sharing links.

Therefore, I would like to make the proposal that we each put a link on =
our website to the other=92s site.  Hopefully, this will increase the =
traffic of both sites and provide interest to our readers.

If you are interested, send me the exact URL that you would like me to =
use and a 1-5 word description.

I intend to add it to the links page at http://www.rugs-direct.com/links =
which has a link from our homepage at http://www.rugs-direct.com

Below is the information for my website:

Link Info:
http://www.rugs-direct.com
Description: Area Rugs

For your convenience, here is the HTML Code:

<a href=3D"http://www.rugs-direct.com">Area Rugs</a>

Thank you for your time.

Karen Clark
Rugs Direct



From jensj@fysik.dtu.dk  Mon May 12 15:23:12 2003
From: jensj@fysik.dtu.dk (Jens Jorgen Mortensen)
Date: Mon, 12 May 2003 16:23:12 +0200
Subject: [XML-SIG] Floating exception on alpha machine
Message-ID: <200305121623.12111.jensj@bose.fysik.dtu.dk>

Hi,

I am trying to install PyXML-0.8.2 on an alpha.  After doing a build and an 
install, I try to import xml.xpath.  The result is:

Python 2.2.1 (#1, Jun  4 2002, 15:33:18) [C] on osf1V4
Type "help", "copyright", "credits" or "license" for more information.
>>> import xml.xpath
Floating exception (core dumped)

When I installed PyXML on my linux machine, there were no problems.  I don't 
know if it is important, but during build on the alpha, I got these two 
warnings:

building '_xmlplus.parsers.pyexpat' extension
creating build
creating build/temp.osf1-V4.0-alpha-2.2
cc -DNDEBUG -O -Olimit 1500 -DXML_NS=1 -DXML_DTD=1 -DBYTEORDER=1234 
-DXML_CONTEXT_BYTES=1024 -Iextensions/expat/lib 
-I/usr/local/include/python2.2 -c extensions/pyexpat.c -o 
build/temp.osf1-V4.0-alpha-2.2/pyexpat.o
cc: Warning: extensions/expat/lib/expat.h, line 656: In this declaration, the 
enum "XML_Status" is not defined. (undefenum)
XMLPARSEAPI(enum XML_Status)
^
cc -DNDEBUG -O -Olimit 1500 -DXML_NS=1 -DXML_DTD=1 -DBYTEORDER=1234 
-DXML_CONTEXT_BYTES=1024 -Iextensions/expat/lib 
-I/usr/local/include/python2.2 -c extensions/expat/lib/xmlparse.c -o 
build/temp.osf1-V4.0-alpha-2.2/xmlparse.o
cc: Warning: extensions/expat/lib/expat.h, line 656: In this declaration, the 
enum "XML_Status" is not defined. (undefenum)
XMLPARSEAPI(enum XML_Status)
^

Does anybody know what could be wrong?

Jens J. Mortensen


From martin@v.loewis.de  Mon May 12 22:05:05 2003
From: martin@v.loewis.de (Martin v. =?iso-8859-15?q?L=F6wis?=)
Date: 12 May 2003 23:05:05 +0200
Subject: [XML-SIG] Floating exception on alpha machine
In-Reply-To: <200305121623.12111.jensj@bose.fysik.dtu.dk>
References: <200305121623.12111.jensj@bose.fysik.dtu.dk>
Message-ID: <m3el33g9ku.fsf@mira.informatik.hu-berlin.de>

Jens Jorgen Mortensen <jensj@fysik.dtu.dk> writes:

> Does anybody know what could be wrong?

No. Can you report a debugger backtrace?

Regards,
Martin


From jberry@sandia.gov  Mon May 12 23:04:03 2003
From: jberry@sandia.gov (Jon Berry)
Date: Mon, 12 May 2003 16:04:03 -0600
Subject: [XML-SIG] best current way to access OO XML Schema features
Message-ID: <3EC01A53.7050006@sandia.gov>

I am interested in accessing the object-oriented
features of XML Schema (from SOX, melded
into XSDL as I understand it) from Python.  

I read that the Xerces parser has the required
support, so I tried hooking up to that.  The
process had me compile Xerces-c, then try
to hook up to it with Pirxx.  For reasons involving
versioning, I haven't been able to do it yet.

On another tack, I looked at XSV, but all I
could find was a status page.  It claims to
conform to XML Schema Part 1: Structures,
but makes no claim about Part 2, so that gave
me pause.  Some of my limited reading suggests
that I might still be all right (still having
access to OO features), but I'm not sure since
Part 1 seems to reference Part 2.

Hopefully I am overlooking an easy solution.
I've got the most recent PyXML and 4Suite
installed.  What's the easiest way to get
access from Python to the most complete
XML Schema parser?

-Jon Berry




From jedp@ilm.com  Mon May 12 23:31:18 2003
From: jedp@ilm.com (Jed Parsons)
Date: Mon, 12 May 2003 15:31:18 -0700 (PDT)
Subject: [XML-SIG] end element handling with XMLValidator?
In-Reply-To: <20030509063450.GH20935@calvin>
References: <200305081802.LAA19259@gleason.lucasdigital.com>
 <20030509063450.GH20935@calvin>
Message-ID: <200305122231.PAA41347@gleason.lucasdigital.com>

Thanks - updating my PyXML to 0.8.2 did the trick.

j

Alexandre Fayolle writes:
> On Thu, May 08, 2003 at 11:02:31AM -0700, Jed Parsons wrote:
> >=20
> > I'm unable to get a hold of 'end element' events from the validatin=
g
> > parser.  Can anyone explain to me what I'm doing wrong?
>=20
> I'm not able to reproduce your problem using either python2.1 or
> python2.2 and pyxml 0.8.2, on a Linux machine.=20
>=20
> There's been similar reports in the past, see bug report #658932 on
> sourceforge, available at the following URL:=20
>=20
> http://sourceforge.net/tracker/index.php?func=3Ddetail&aid=3D658932&g=
roup_id=3D6473&atid=3D106473
>=20
>=20
> --=20
> Alexandre Fayolle
> LOGILAB, Paris (France).
> http://www.logilab.com   http://www.logilab.fr  http://www.logilab.or=
g
> D=E9veloppement logiciel avanc=E9 - Intelligence Artificielle - Forma=
tions

--=20
Jed Parsons       Industrial Light + Magic  (415) 448-2974=20
=09    =20
grep(do{for(ord){(!$_&&print"$s\n")||(($O+=3D(($_-1)%6+1)and
grep(vec($s,$O++,1)=3D1,1..int(($_-6*6-1)/6))))}},(split(//,
"++,++2-27,280,481=3D1-7.1++2,800+++2,8310/1+4131+1++2,80\0.  What!?"))=
);=20


From jberry@sandia.gov  Mon May 12 23:33:58 2003
From: jberry@sandia.gov (Jon Berry)
Date: Mon, 12 May 2003 16:33:58 -0600
Subject: [XML-SIG] XSLT sorting by "authors" element, with multiple authors
Message-ID: <3EC02156.7040304@sandia.gov>

The XSLT sorting articles I've seen on the web
don't address the issue of sorting citations by
"authors," where the latter is a group of authors
(not the single authors typical of web examples).

For example:

<article>
        <title>    "An Article"
        </title>
        <authors>
              <person lastname = "Smith"/>
              <person lastname = "Doe"/>
         </authors>
</article>

...

I'd like to sort by the last name, alphabetically by
first differing author.  So the algorithm would be:
    * within each article, sort authors by lastname
    * to compare Article A with Article B:
              * Look at last names of first author (if different, 
comparison done)
              * else if first authors are the same, look at second authors,
              * etc.
              * if not distinguished, go on to next sorting key (say 
'title')

Noting of course that we might be comparing articles with
different numbers of authors.  

In initial searches, it looked like the   xsl:for-each-group
and/or xsl:function constructs might help, but they don't seem
to be supported by the current PyXML/4Suite implementations.

So, with the constraint that I'm trying to avoid buying a book for now,
is this doable using templates, easy, and currently implementable
with free software?

thanks,
Jon Berry




From tpassin@comcast.net  Tue May 13 02:42:19 2003
From: tpassin@comcast.net (Thomas B. Passin)
Date: Mon, 12 May 2003 21:42:19 -0400
Subject: [XML-SIG] XSLT sorting by "authors" element, with multiple authors
References: <3EC02156.7040304@sandia.gov>
Message-ID: <001e01c318f0$e6ed60c0$6401a8c0@tbp1>

[Jon Berry]
>...
> In initial searches, it looked like the   xsl:for-each-group
> and/or xsl:function constructs might help, but they don't seem
> to be supported by the current PyXML/4Suite implementations.
>
> So, with the constraint that I'm trying to avoid buying a book for now,
> is this doable using templates, easy, and currently implementable
> with free software?
>

Best to go to the Mulberry xslt list with xslt questions!  The two
instructions you mention are not in xslt1.0 but rather in the draft xslt2.0.
It seems unlikely that the 4Thought people will ever have much interest in
getting 4xslt conformant with xslt2.0, so you need another approach.

Your problem is a grouping problem, and most grouping problems can be solved
with xslt1.0 - you have to learn a few patterns that people have discovered,
and sometimes be a little creative, but you can generally solve them.  Check
the FAQs, including Jeni Tennison's web site.

If all else fails, you can accomplish your task by using a 2-pass process.
Use one stylesheet to do an intermediate transform, then a final one to do
the rest (which may at that point just be the sorting).

The latest version of Mike Kay's Saxon supports good parts of the draft 2.0
Rec.  You could use it from Python by means of a system call.  Bear in mind,
though, that xslt2.0 is not completely stable yet, and also there are some
subtle (and some not-so-subtle, but those are less likely to cause problems)
differences between similar constructions in 1.0 and 2.0.

Cheers,

Tom P




From phthenry@earthlink.net  Tue May 13 06:37:51 2003
From: phthenry@earthlink.net (Paul Tremblay)
Date: Tue, 13 May 2003 01:37:51 -0400
Subject: [XML-SIG] XSLT sorting by "authors" element, with multiple authors
In-Reply-To: <001e01c318f0$e6ed60c0$6401a8c0@tbp1>
References: <3EC02156.7040304@sandia.gov> <001e01c318f0$e6ed60c0$6401a8c0@tbp1>
Message-ID: <20030513013751.I29954@localhost.localdomain>

On Mon, May 12, 2003 at 09:42:19PM -0400, Thomas B. Passin wrote:
> 
> [Jon Berry]
> >...
> > In initial searches, it looked like the   xsl:for-each-group
> > and/or xsl:function constructs might help, but they don't seem
> > to be supported by the current PyXML/4Suite implementations.
> >
> > So, with the constraint that I'm trying to avoid buying a book for now,
> > is this doable using templates, easy, and currently implementable
> > with free software?
> >
> 
> Best to go to the Mulberry xslt list with xslt questions!  The two
> instructions you mention are not in xslt1.0 but rather in the draft xslt2.0.
> It seems unlikely that the 4Thought people will ever have much interest in
> getting 4xslt conformant with xslt2.0, so you need another approach.

Why is this? 

Paul

> 
> Your problem is a grouping problem, and most grouping problems can be solved
> with xslt1.0 - you have to learn a few patterns that people have discovered,
> and sometimes be a little creative, but you can generally solve them.  Check
> the FAQs, including Jeni Tennison's web site.
> 
> If all else fails, you can accomplish your task by using a 2-pass process.
> Use one stylesheet to do an intermediate transform, then a final one to do
> the rest (which may at that point just be the sorting).
> 
> The latest version of Mike Kay's Saxon supports good parts of the draft 2.0
> Rec.  You could use it from Python by means of a system call.  Bear in mind,
> though, that xslt2.0 is not completely stable yet, and also there are some
> subtle (and some not-so-subtle, but those are less likely to cause problems)
> differences between similar constructions in 1.0 and 2.0.
> 
> Cheers,
> 
> Tom P
> 
> 
> 
> _______________________________________________
> XML-SIG maillist  -  XML-SIG@python.org
> http://mail.python.org/mailman/listinfo/xml-sig

-- 

************************
*Paul Tremblay         *
*phthenry@earthlink.net*
************************


From jensj@fysik.dtu.dk  Tue May 13 13:04:11 2003
From: jensj@fysik.dtu.dk (Jens Jorgen Mortensen)
Date: Tue, 13 May 2003 14:04:11 +0200
Subject: [XML-SIG] Floating exception on alpha machine
In-Reply-To: <m3el33g9ku.fsf@mira.informatik.hu-berlin.de>
References: <200305121623.12111.jensj@bose.fysik.dtu.dk> <m3el33g9ku.fsf@mira.informatik.hu-berlin.de>
Message-ID: <200305131404.11795.jensj@bose.fysik.dtu.dk>

Martin v. L=F6wis:
> Jens Jorgen Mortensen <jensj@fysik.dtu.dk> writes:
> > Does anybody know what could be wrong?
>
> No. Can you report a debugger backtrace?

I have included my best shot at a backtrace to the end of this mail.  I a=
m=20
afraid it is not very useful - the debugger reads the symbols before I im=
port=20
xml.xpath! - how should this be done? =20

On an alpha, it is my experience that the "floating point overflow" error=
=20
often indicates that a floating point operation was performed on some=20
uninitialized data. =20

Jens J=F8rgen

Backtrace:

Welcome to the Ladebug Debugger Version 4.0-49
------------------
object file name: /usr/local/bin/python2
Reading symbolic information ...done
(ladebug) run
Python 2.2.1 (#1, Jun  4 2002, 15:33:18) [C] on osf1V4
Type "help", "copyright", "credits" or "license" for more information.
>>> import xml.xpath
Thread received signal FPE
stopped at [<opaque> UnknownProcedure16FromFile31(...) 0x1200710c8]

Information:  An <opaque> type was presented during execution of the prev=
ious=20
command.  For complete type information on this symbol, recompilation of =
the=20
program will be necessary.  Consult the compiler man pages for details on=
=20
producing full symbol table information using the -g (and -gall for cxx)=20
flags.

(ladebug) where
>0  0x1200710c8 in UnknownProcedure16FromFile31(0x1400172e0, 0x1400172e0,=
=20
0x10, 0x140038090, 0x1, 0x30) in /usr/local/bin/python2
#1  0x1200a4170 in UnknownProcedure14FromFile45(0x1400172e0, 0x1400172e0,=
=20
0x10, 0x140038090, 0x1, 0x30) in /usr/local/bin/python2
#2  0x1200a43c8 in UnknownProcedure15FromFile45(0x1400172e0, 0x1400172e0,=
=20
0x10, 0x140038090, 0x1, 0x30) in /usr/local/bin/python2
#3  0x1200a4bd4 in PyNumber_Multiply(0x1400172e0, 0x1400172e0, 0x10,=20
0x140038090, 0x1, 0x30) in /usr/local/bin/python2
#4  0x120074fa8 in UnknownProcedure12FromFile33(0x1400172e0, 0x1400172e0,=
=20
0x10, 0x140038090, 0x1, 0x30) in /usr/local/bin/python2
#5  0x12007c234 in PyEval_EvalCodeEx(0x1400172e0, 0x1400172e0, 0x10,=20
0x140038090, 0x1, 0x30) in /usr/local/bin/python2
#6  0x120074408 in PyEval_EvalCode(0x1400172e0, 0x1400172e0, 0x10,=20
0x140038090, 0x1, 0x30) in /usr/local/bin/python2
#7  0x12002f420 in PyImport_ExecCodeModuleEx(0x1400172e0, 0x1400172e0, 0x=
10,=20
0x140038090, 0x1, 0x30) in /usr/local/bin/python2
#8  0x12002fca4 in UnknownProcedure14FromFile11(0x1400172e0, 0x1400172e0,=
=20
0x10, 0x140038090, 0x1, 0x30) in /usr/local/bin/python2
#9  0x1200307b8 in UnknownProcedure18FromFile11(0x1400172e0, 0x1400172e0,=
=20
0x10, 0x140038090, 0x1, 0x30) in /usr/local/bin/python2
#10 0x12002ff20 in UnknownProcedure15FromFile11(0x1400172e0, 0x1400172e0,=
=20
0x10, 0x140038090, 0x1, 0x30) in /usr/local/bin/python2
#11 0x120030854 in UnknownProcedure18FromFile11(0x1400172e0, 0x1400172e0,=
=20
0x10, 0x140038090, 0x1, 0x30) in /usr/local/bin/python2
#12 0x120031da4 in UnknownProcedure27FromFile11(0x1400172e0, 0x1400172e0,=
=20
0x10, 0x140038090, 0x1, 0x30) in /usr/local/bin/python2
#13 0x120031660 in UnknownProcedure25FromFile11(0x1400172e0, 0x1400172e0,=
=20
0x10, 0x140038090, 0x1, 0x30) in /usr/local/bin/python2
#14 0x120031064 in PyImport_ImportModuleEx(0x1400172e0, 0x1400172e0, 0x10=
,=20
0x140038090, 0x1, 0x30) in /usr/local/bin/python2
#15 0x120068e24 in UnknownProcedure0FromFile28(0x1400172e0, 0x1400172e0, =
0x10,=20
0x140038090, 0x1, 0x30) in /usr/local/bin/python2
#16 0x12006f790 in PyCFunction_Call(0x1400172e0, 0x1400172e0, 0x10,=20
0x140038090, 0x1, 0x30) in /usr/local/bin/python2
#17 0x1200a7da4 in PyObject_Call(0x1400172e0, 0x1400172e0, 0x10, 0x140038=
090,=20
0x1, 0x30) in /usr/local/bin/python2
#18 0x12007ce10 in PyEval_CallObjectWithKeywords(0x1400172e0, 0x1400172e0=
,=20
0x10, 0x140038090, 0x1, 0x30) in /usr/local/bin/python2
#19 0x120078da0 in UnknownProcedure12FromFile33(0x1400172e0, 0x1400172e0,=
=20
0x10, 0x140038090, 0x1, 0x30) in /usr/local/bin/python2
#20 0x12007c234 in PyEval_EvalCodeEx(0x1400172e0, 0x1400172e0, 0x10,=20
0x140038090, 0x1, 0x30) in /usr/local/bin/python2
#21 0x120074408 in PyEval_EvalCode(0x1400172e0, 0x1400172e0, 0x10,=20
0x140038090, 0x1, 0x30) in /usr/local/bin/python2
#22 0x120017320 in UnknownProcedure36FromFile3(0x1400172e0, 0x1400172e0, =
0x10,=20
0x140038090, 0x1, 0x30) in /usr/local/bin/python2
#23 0x120015694 in PyRun_InteractiveOneFlags(0x1400172e0, 0x1400172e0, 0x=
10,=20
0x140038090, 0x1, 0x30) in /usr/local/bin/python2
#24 0x120015330 in PyRun_InteractiveLoopFlags(0x1400172e0, 0x1400172e0, 0=
x10,=20
0x140038090, 0x1, 0x30) in /usr/local/bin/python2
#25 0x120015108 in PyRun_AnyFileExFlags(0x1400172e0, 0x1400172e0, 0x10,=20
0x140038090, 0x1, 0x30) in /usr/local/bin/python2
#26 0x120014080 in Py_Main(0x1400172e0, 0x1400172e0, 0x10, 0x140038090, 0=
x1,=20
0x30) in /usr/local/bin/python2
#27 0x120013570 in main(0x1400172e0, 0x1400172e0, 0x10, 0x140038090, 0x1,=
=20
0x30) in /usr/local/bin/python2
#28 0x1200134f8 in __start(0x1400172e0, 0x1400172e0, 0x10, 0x140038090, 0=
x1,=20
0x30) in /usr/local/bin/python2


From tpassin@comcast.net  Tue May 13 14:33:37 2003
From: tpassin@comcast.net (Thomas B. Passin)
Date: Tue, 13 May 2003 09:33:37 -0400
Subject: [XML-SIG] XSLT sorting by "authors" element, with multiple authors
References: <3EC02156.7040304@sandia.gov> <001e01c318f0$e6ed60c0$6401a8c0@tbp1>
 <20030513013751.I29954@localhost.localdomain>
Message-ID: <001201c31954$42501e40$6401a8c0@tbp1>

[Paul Tremblay]
> >
> > Best to go to the Mulberry xslt list with xslt questions!  The two
> > instructions you mention are not in xslt1.0 but rather in the draft
xslt2.0.
> > It seems unlikely that the 4Thought people will ever have much interest
in
> > getting 4xslt conformant with xslt2.0, so you need another approach.
>
> Why is this?
>

Read the archives of xml-dev for the last few months, or of the xslt list
for the last 6 months, and you will see a lot of anguish over the complexity
of combining XSL Schema types with xslt and xpath (sometimes the discussion
is more focused on XQuery, but there is a close relationship because
XQuery's needs have strongly influenced xpath2).

Uche has said many times that he thinks that xpath2/xslt2 are complex
abominations (my words, trying to capture what I think he expressed) and
that he has no interest in implementing them.

He is interested in an alternative approach to a new xpath/xslt and there is
a small list where it is being discussed.

Cheers,

Tom P




From martin@v.loewis.de  Tue May 13 16:13:39 2003
From: martin@v.loewis.de (Martin v. =?iso-8859-15?q?L=F6wis?=)
Date: 13 May 2003 17:13:39 +0200
Subject: [XML-SIG] Floating exception on alpha machine
In-Reply-To: <200305131404.11795.jensj@bose.fysik.dtu.dk>
References: <200305121623.12111.jensj@bose.fysik.dtu.dk>
 <m3el33g9ku.fsf@mira.informatik.hu-berlin.de>
 <200305131404.11795.jensj@bose.fysik.dtu.dk>
Message-ID: <m3smriev6k.fsf@mira.informatik.hu-berlin.de>

Jens Jorgen Mortensen <jensj@fysik.dtu.dk> writes:

> I have included my best shot at a backtrace to the end of this mail.
> I am afraid it is not very useful - the debugger reads the symbols
> before I import xml.xpath! - how should this be done?

If you can't get your debugger to load symbols for shared libraries
afterwards, you could either try a different debugger (gdb comes to
mind), or you could try to link all code with the executable. For
this, you would have to relink the python binary, after putting
initpyexpat into config.c (pyexpat is likely the extension module for
which it can't find the symbols).

HTH,
Martin



From fredrik@pythonware.com  Tue May 13 17:22:28 2003
From: fredrik@pythonware.com (Fredrik Lundh)
Date: Tue, 13 May 2003 18:22:28 +0200
Subject: [XML-SIG] ANN: ElementTree 1.1
Message-ID: <b9r619$h7k$1@main.gmane.org>

The Element type is a simple but flexible container object, designed
to store hierarchical data structures, such as simplified XML infosets,
in memory.

The ElementTree toolkit contains an Element implementation in Python,
and code to read XML and HTML files into trees of Element objects, and
write them out as XML.

You can get the ElementTree toolkit from:

    http://effbot.org/downloads#elementtree

Changes include XML literal factory, a self-contained ElementTree
module, use ASCII as default encoding, and various minor speed and
memory optimizations, etc.  See the README file for details:

    http://effbot.org/downloads/index.cgi/elementtree-1.1-20030511.zip/README


Brief documentation and some code samples (including an XML-RPC
unmarshaller in 16 lines) are available from:

    http://effbot.org/zone/element-index.htm

For more background, see Uche Ogbuji's xml.com article:

    "Simple XML Processing With elementtree"
    http://www.xml.com/pub/a/2003/02/12/py-xml.html


Report bugs to this list, and/or (preferred) directly to me.

enjoy /F





From jh@web.de  Tue May 13 18:10:06 2003
From: jh@web.de (Juergen Hermann)
Date: Tue, 13 May 2003 19:10:06 +0200
Subject: [XML-SIG] best current way to access OO XML Schema features
In-Reply-To: <3EC01A53.7050006@sandia.gov>
Message-ID: <E19FdH9-0007ZQ-00@smtp.web.de>

On=20Mon,=2012=20May=202003=2016:04:03=20-0600,=20Jon=20Berry=20wrote:

>I=20read=20that=20the=20Xerces=20parser=20has=20the=20required
>support,=20so=20I=20tried=20hooking=20up=20to=20that.=20=20The
>process=20had=20me=20compile=20Xerces-c,=20then=20try
>to=20hook=20up=20to=20it=20with=20Pirxx.=20=20For=20reasons=20involving
>versioning,=20I=20haven't=20been=20able=20to=20do=20it=20yet.

What=20was=20the=20exact=20version=20combination,=20including=20platform=20=
(gcc?).


Ciao,=20J=FCrgen




From kajiyama@grad.sccs.chukyo-u.ac.jp  Tue May 13 18:14:03 2003
From: kajiyama@grad.sccs.chukyo-u.ac.jp (Tamito KAJIYAMA)
Date: Wed, 14 May 2003 02:14:03 +0900
Subject: [XML-SIG] XSLT sorting by "authors" element, with multiple authors
In-Reply-To: <3EC02156.7040304@sandia.gov> (jberry@sandia.gov)
Message-ID: <200305131714.h4DHE3215527@grad.sccs.chukyo-u.ac.jp>

"Jon Berry" <jberry@sandia.gov> writes:
| 
| I'd like to sort by the last name, alphabetically by
| first differing author.  So the algorithm would be:
|     * within each article, sort authors by lastname
|     * to compare Article A with Article B:
|               * Look at last names of first author (if different, 
| comparison done)
|               * else if first authors are the same, look at second authors,
|               * etc.
|               * if not distinguished, go on to next sorting key (say 
| 'title')
| 
| Noting of course that we might be comparing articles with
| different numbers of authors.  
| 
| In initial searches, it looked like the   xsl:for-each-group
| and/or xsl:function constructs might help, but they don't seem
| to be supported by the current PyXML/4Suite implementations.
| 
| So, with the constraint that I'm trying to avoid buying a book for now,
| is this doable using templates, easy, and currently implementable
| with free software?

I believe that using extension functions is a good approach to
cope with your problem.

The primary cause of your problem is that the xsl:sort looks at
only the value of the first node, instead of all the selected
nodes.  For example, the following xsl:sort element selects all
the last names of an article's authors, but only the first last
name is used as a sort key.

<xsl:sort select="authors/person/@lastname" order="ascending" />

So, a simple solution is to change this behavior of xsl:sort by
defining an extension function like this:

<xsl:sort select="ext:strings(authors/person/@lastname)" order="ascending" />

where the extension function ext:strings() can be defined, for
example, as follows:

def strings(context, nodeset):
    return "".join(map(lambda x: x.nodeValue, nodeset))

It seems very Pythonic, doesn't it? :-)  See documentation for
more information on extension functions in Python.

Another comment:

| * if not distinguished, go on to next sorting key (say 'title')

XSLT allows multiple xsl:sort elements, so this should not be
a problem.

Hope this helps,

-- 
KAJIYAMA, Tamito <kajiyama@grad.sccs.chukyo-u.ac.jp>


From rsalz@datapower.com  Tue May 13 16:55:38 2003
From: rsalz@datapower.com (Rich Salz)
Date: Tue, 13 May 2003 11:55:38 -0400
Subject: [XML-SIG] XSLT sorting by "authors" element, with multiple authors
In-Reply-To: <20030513013751.I29954@localhost.localdomain>
References: <3EC02156.7040304@sandia.gov> <001e01c318f0$e6ed60c0$6401a8c0@tbp1> <20030513013751.I29954@localhost.localdomain>
Message-ID: <3EC1157A.9080107@datapower.com>

>>It seems unlikely that the 4Thought people will ever have much interest in
>>getting 4xslt conformant with xslt2.0, so you need another approach.
> 
> Why is this? 


If you look at the xml-dev list (hosted at lists.oasis.org, to skim 
archives), you can see that Uche has been very emphatic about his 
disdain for XSLT2.0, and his interest in seeing alternatives develop.
	/r$



From grobinson@transpose.com  Wed May 14 02:21:26 2003
From: grobinson@transpose.com (Gary Robinson)
Date: Tue, 13 May 2003 21:21:26 -0400
Subject: [XML-SIG] Installation trouble on OS X
Message-ID: <BAE71256.245DB%grobinson@transpose.com>

Hello,

I'm trying to install PyXML-0.8.2 on OS X. I think I've located a bug in the
installer.

I'm running 

    python setup.py install

I get the error:

% python setup.py install
Traceback (most recent call last):
  File "setup.py", line 58, in ?
    if sys.platform[:6] == "darwin" and \
NameError: name 'distutils' is not defined


When I examine setup.py, at the top I see:

    from distutils.sysconfig import get_config_vars

but lines 58 and 59, where it is choking, say:

    if sys.platform[:6] == "darwin" and \
    distutils.sysconfig.get_config_var("LDSHARED").find("-flat_namespace") \
        == -1:

The problem seems to be that distutils hasn't been imported; just
get_config_vars has been. So the above should say:

    if sys.platform[:6] == "darwin" and \
       get_config_vars("LDSHARED").find("-flat_namespace") == -1:

Is that right?

Also -- I'm a newbie to the process of doing this kind of install. Does it
matter where in my directory structure I place the PyXML-0.8.2 directory
which contains setup.py when I run it? Or can it be anywhere (in which case
it must be smart enough to know where everything should go).
        
Many thanks in advance for any help you can give.

--Gary

-- 
<http://ThisURLEnablesEmailToGetThroughOverzealousSpamFilters.org>

Gary Robinson
CEO
Transpose, LLC
grobinson@transpose.com
207-942-3463
http://www.transpose.com
http://radio.weblogs.com/0101454




From phthenry@earthlink.net  Wed May 14 02:35:29 2003
From: phthenry@earthlink.net (Paul Tremblay)
Date: Tue, 13 May 2003 21:35:29 -0400
Subject: [XML-SIG] XSLT sorting by "authors" element, with multiple authors
In-Reply-To: <001201c31954$42501e40$6401a8c0@tbp1>
References: <3EC02156.7040304@sandia.gov> <001e01c318f0$e6ed60c0$6401a8c0@tbp1> <20030513013751.I29954@localhost.localdomain> <001201c31954$42501e40$6401a8c0@tbp1>
Message-ID: <20030513213528.K29954@localhost.localdomain>

On Tue, May 13, 2003 at 09:33:37AM -0400, Thomas B. Passin wrote:
> 
> Read the archives of xml-dev for the last few months, or of the xslt list
> for the last 6 months, 

>and you will see a lot of anguish over the complexity
> of combining XSL Schema types with xslt and xpath (sometimes the discussion
> is more focused on XQuery, but there is a close relationship because
> XQuery's needs have strongly influenced xpath2).

I had kind of picked this up on the xslt mailing list the last few
weeks, and just wanted to confirm my guess.

Thanks

Paul 

> 
> Uche has said many times that he thinks that xpath2/xslt2 are complex
> abominations (my words, trying to capture what I think he expressed) and
> that he has no interest in implementing them.
> 
> He is interested in an alternative approach to a new xpath/xslt and there is
> a small list where it is being discussed.
> 
> Cheers,
> 
> Tom P
> 
> 
> 
> _______________________________________________
> XML-SIG maillist  -  XML-SIG@python.org
> http://mail.python.org/mailman/listinfo/xml-sig

-- 

************************
*Paul Tremblay         *
*phthenry@earthlink.net*
************************


From ryanwilcox@mac.com  Wed May 14 04:26:06 2003
From: ryanwilcox@mac.com (Ryan Wilcox)
Date: Tue, 13 May 2003 23:26:06 -0400
Subject: [XML-SIG] Installation trouble on OS X
In-Reply-To: <BAE71256.245DB%grobinson@transpose.com>
Message-ID: <r01050400-1025-CCC89FD485BB11D792F600039310A782@[10.0.1.2]>

On 5/13/03, at 9:21 PM, Gary Robinson said:

>Hello,
>
>I'm trying to install PyXML-0.8.2 on OS X. I think I've located a bug in the
>installer.
>
>I'm running 
>
>    python setup.py install
>
>I get the error:
>
>% python setup.py install
>Traceback (most recent call last):
>  File "setup.py", line 58, in ?
>    if sys.platform[:6] == "darwin" and \
>NameError: name 'distutils' is not defined

Yup, I get this error too.

I believe you're correct in how to fix it.

BTW: I did this work for Darwin Ports maybe a month back. Darwin Ports makes it
pretty much braindead to install PyXML ('cause you also should install xpat,
etc). (It's a package manager, like Fink)

http://www.opendarwin.org/projects/darwinports/.

This has also been discussed in the archives a few times...

Good luck,
-Ryan

Who recommends downloading Darwin Ports, even if to just get my patch file for
setup.py ;)


>-- 
><http://ThisURLEnablesEmailToGetThroughOverzealousSpamFilters.org>
>
>Gary Robinson
>CEO
>Transpose, LLC
>grobinson@transpose.com
>207-942-3463
>http://www.transpose.com
>http://radio.weblogs.com/0101454
>
>
>
>_______________________________________________
>XML-SIG maillist  -  XML-SIG@python.org
>http://mail.python.org/mailman/listinfo/xml-sig

---------------------------------------------------------------------
Wilcox Design: Understanding Data              http://www.wilcoxd.com


From jensj@fysik.dtu.dk  Wed May 14 09:32:39 2003
From: jensj@fysik.dtu.dk (Jens Jorgen Mortensen)
Date: Wed, 14 May 2003 10:32:39 +0200
Subject: [XML-SIG] Floating exception on alpha machine
In-Reply-To: <m3smriev6k.fsf@mira.informatik.hu-berlin.de>
References: <200305121623.12111.jensj@bose.fysik.dtu.dk> <200305131404.11795.jensj@bose.fysik.dtu.dk> <m3smriev6k.fsf@mira.informatik.hu-berlin.de>
Message-ID: <200305141032.39323.jensj@bose.fysik.dtu.dk>

Martin v. L=F6wis:
> Jens Jorgen Mortensen <jensj@fysik.dtu.dk> writes:
> > I have included my best shot at a backtrace to the end of this mail.
> > I am afraid it is not very useful - the debugger reads the symbols
> > before I import xml.xpath! - how should this be done?
>
> If you can't get your debugger to load symbols for shared libraries
> afterwards, you could either try a different debugger (gdb comes to
> mind)

Here is what I get with gdb:

GNU gdb 4.17
Copyright 1998 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you =
are
welcome to change it and/or distribute copies of it under certain conditi=
ons.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB.  Type "show warranty" for detail=
s.
This GDB was configured as "alphaev56-dec-osf4.0d"...
(no debugging symbols found)...
(gdb) set heuristic-fence-post 1000000
(gdb) run
Starting program: /usr/local/bin/python2
(no debugging symbols found)...(no debugging symbols found)...Python 2.2.=
1=20
(#1, Jun  4 2002, 15:33:18) [C] on osf1V4
Type "help", "copyright", "credits" or "license" for more information.
>>> import xml.xpath

Program received signal SIGFPE, Arithmetic exception.
0x1200710c8 in PyFloat_AsReprString ()
(gdb) backtrace
#0  0x1200710c8 in PyFloat_AsReprString ()
#1  0x1200a4174 in PyNumber_Check ()
#2  0x1200a4174 in PyNumber_Check ()
#3  0x1200a43cc in PyNumber_Check ()
#4  0x1200a4bd8 in PyNumber_Multiply ()
#5  0x120074fac in PyEval_EvalCode ()
#6  0x12007c238 in PyEval_EvalCodeEx ()
#7  0x12007440c in PyEval_EvalCode ()
#8  0x12002f424 in PyImport_ExecCodeModuleEx ()
#9  0x12002fca8 in PyImport_ExecCodeModuleEx ()
#10 0x1200307bc in PyImport_ExecCodeModuleEx ()
#11 0x12002ff24 in PyImport_ExecCodeModuleEx ()

>, or you could try to link all code with the executable. For
> this, you would have to relink the python binary, after putting
> initpyexpat into config.c (pyexpat is likely the extension module for
> which it can't find the symbols).

OK, hmmm...  I will try to experiment with this some day when I have some=
=20
time.

Regards,
Jens J=F8rgen


From jensj@fysik.dtu.dk  Wed May 14 10:10:26 2003
From: jensj@fysik.dtu.dk (Jens Jorgen Mortensen)
Date: Wed, 14 May 2003 11:10:26 +0200
Subject: [XML-SIG] Re: Floating exception on alpha machine
In-Reply-To: <200305121623.12111.jensj@bose.fysik.dtu.dk>
References: <200305121623.12111.jensj@bose.fysik.dtu.dk>
Message-ID: <200305141110.27285.jensj@bose.fysik.dtu.dk>

Jens Jorgen Mortensen:
> Hi,
>
> I am trying to install PyXML-0.8.2 on an alpha.  After doing a build an=
d an
> install, I try to import xml.xpath.  The result is:
>
> Python 2.2.1 (#1, Jun  4 2002, 15:33:18) [C] on osf1V4
> Type "help", "copyright", "credits" or "license" for more information.
> >>> import xml.xpath
> Floating exception (core dumped)

I have found that the core dump comes from line 20 in=20
PyXML-0.8.2/xml/xpath/__init__.py.  It goes like this:

Python 2.2.1 (#1, Jun  4 2002, 15:33:18) [C] on osf1V4
Type "help", "copyright", "credits" or "license" for more information.
>>> Inf =3D Inf =3D 1e300 * 1e300
Floating exception (core dumped)

A very simple way to crash the python interpreter!!  Does anybody know wh=
at to=20
do about it?  How should Inf be defined?

Regards,
Jens J=F8rgen


From grobinson@transpose.com  Wed May 14 13:02:13 2003
From: grobinson@transpose.com (Gary Robinson)
Date: Wed, 14 May 2003 08:02:13 -0400
Subject: [XML-SIG] Installation trouble on OS X
In-Reply-To: <r01050400-1025-CCC89FD485BB11D792F600039310A782@[10.0.1.2]>
Message-ID: <BAE7A885.2467F%grobinson@transpose.com>

Thanks Ryan!

will darwinports work to install pyxml for the apple-supplied version of
Python, or does it expect a darwinports-supplied python? (I notice that fink
tends to put things in its own locations, which are sometimes incompatible
with the locations non-fink packages expect...)

Which brings me also to my other question, when I run setup.py for a
package, does it move it automatically find the right directory to put the
files into, no matter where I ran it from?

--Gary

-- 
<http://ThisURLEnablesEmailToGetThroughOverzealousSpamFilters.org>

Gary Robinson
CEO
Transpose, LLC
grobinson@transpose.com
207-942-3463
http://www.transpose.com
http://radio.weblogs.com/0101454


> From: Ryan Wilcox <ryanwilcox@mac.com>
> Date: Tue, 13 May 2003 23:26:06 -0400
> To: Gary Robinson <grobinson@transpose.com>, xml-sig@python.org
> Subject: Re: [XML-SIG] Installation trouble on OS X
> 
> On 5/13/03, at 9:21 PM, Gary Robinson said:
> 
>> Hello,
>> 
>> I'm trying to install PyXML-0.8.2 on OS X. I think I've located a bug in the
>> installer.
>> 
>> I'm running 
>> 
>>    python setup.py install
>> 
>> I get the error:
>> 
>> % python setup.py install
>> Traceback (most recent call last):
>>  File "setup.py", line 58, in ?
>>    if sys.platform[:6] == "darwin" and \
>> NameError: name 'distutils' is not defined
> 
> Yup, I get this error too.
> 
> I believe you're correct in how to fix it.
> 
> BTW: I did this work for Darwin Ports maybe a month back. Darwin Ports makes
> it
> pretty much braindead to install PyXML ('cause you also should install xpat,
> etc). (It's a package manager, like Fink)
> 
> http://www.opendarwin.org/projects/darwinports/.
> 
> This has also been discussed in the archives a few times...
> 
> Good luck,
> -Ryan
> 
> Who recommends downloading Darwin Ports, even if to just get my patch file for
> setup.py ;)
> 
> 
>> -- 
>> <http://ThisURLEnablesEmailToGetThroughOverzealousSpamFilters.org>
>> 
>> Gary Robinson
>> CEO
>> Transpose, LLC
>> grobinson@transpose.com
>> 207-942-3463
>> http://www.transpose.com
>> http://radio.weblogs.com/0101454
>> 
>> 
>> 
>> _______________________________________________
>> XML-SIG maillist  -  XML-SIG@python.org
>> http://mail.python.org/mailman/listinfo/xml-sig
> 
> ---------------------------------------------------------------------
> Wilcox Design: Understanding Data              http://www.wilcoxd.com
> 



From ryanwilcox@mac.com  Wed May 14 14:34:42 2003
From: ryanwilcox@mac.com (Ryan Wilcox)
Date: Wed, 14 May 2003 09:34:42 -0400
Subject: [XML-SIG] Installation trouble on OS X
In-Reply-To: <BAE7A885.2467F%grobinson@transpose.com>
Message-ID: <r01050400-1025-D198D2C2861011D792F600039310A782@[10.0.1.2]>

On 5/14/03, at 8:02 AM, Gary Robinson said:

>Thanks Ryan!
>
>will darwinports work to install pyxml for the apple-supplied version of
>Python, or does it expect a darwinports-supplied python? (I notice that fink
>tends to put things in its own locations, which are sometimes incompatible
>with the locations non-fink packages expect...)

Darwin Ports puts stuff in it's own location as well.

You _should_ be able to set the PYTHONPATH enviromental variable to include
where DP puts stuff (in this case: /opt/local/lib/python2.2/site-packages/).

>
>Which brings me also to my other question, when I run setup.py for a
>package, does it move it automatically find the right directory to put the
>files into, no matter where I ran it from?

It should, yes.

If you want to explicitly tell it, call setup.py like so:

python setup.py --prefix /usr/something/somewhere


Hope this helps,
-Ryan Wilcox

>>> <http://ThisURLEnablesEmailToGetThroughOverzealousSpamFilters.org>
>>> 
>>> Gary Robinson
>>> CEO
>>> Transpose, LLC
>>> grobinson@transpose.com
>>> 207-942-3463
>>> http://www.transpose.com
>>> http://radio.weblogs.com/0101454

---------------------------------------------------------------------
Wilcox Design: Understanding Data              http://www.wilcoxd.com


From txagcs98@hotmail.com  Wed May 14 18:58:24 2003
From: txagcs98@hotmail.com (William McLendon)
Date: Wed, 14 May 2003 11:58:24 -0600
Subject: [XML-SIG] How do I process CDATA when the characters looks like XML
Message-ID: <BAY7-F93ZwKxqCxX6HG0001ef4c@hotmail.com>

Hi,

I'm working with the basic python SAX parser (xml.sax.handler, etc) and am 
needing to process some XML that has "<" and ">" characters going in CDATA 
fields.

For example, the model I want to have is this:

<A>X</A>  where "X" is some kind of character data.

but if X = <B> giving me this situation:

<A><B></A>

A parser is going to think that "<B>" is a new XML tag and it'll die saying 
that I have mismatched tags.  This field also may or may not have <*> type 
entries in it, or it might have many blocks like that.

Is there a way to set a processing flag to specify that I want to grab 
everything between <A> and </A> as a character buffer?  If there's not a 
built in way to grab that, is there a trick I can use to get the same 
effect?

I can't just flip a state in the parser and 'build' the string from 
startElement and endElement names because  the character data won't be well 
formed XML (no </> style elements)

Any help is greatly appreciated!
  -William

_________________________________________________________________
Tired of spam? Get advanced junk mail protection with MSN 8. 
http://join.msn.com/?page=features/junkmail



From mike@skew.org  Wed May 14 19:19:33 2003
From: mike@skew.org (Mike Brown)
Date: Wed, 14 May 2003 12:19:33 -0600 (MDT)
Subject: [XML-SIG] How do I process CDATA when the characters looks like
 XML
In-Reply-To: <BAY7-F93ZwKxqCxX6HG0001ef4c@hotmail.com> "from William McLendon
 at May 14, 2003 11:58:24 am"
Message-ID: <200305141819.h4EIJXrm049202@chilled.skew.org>

William McLendon wrote:
> I'm working with the basic python SAX parser (xml.sax.handler, etc) and am 
> needing to process some XML that has "<" and ">" characters going in CDATA 
> fields.
> 
> For example, the model I want to have is this:
> 
> <A>X</A>  where "X" is some kind of character data.
> 
> but if X = <B> giving me this situation:
> 
> <A><B></A>

If you're wanting to put markup characters "<" or "&" in character data, you
must escape them, either using character or entity references, or the special
markup for a CDATA section:

<A>&lt;B></A>  (escaping the > is optional)
or
<A><![CDATA[<B>]]></A>


From txagcs98@hotmail.com  Wed May 14 20:58:26 2003
From: txagcs98@hotmail.com (William McLendon)
Date: Wed, 14 May 2003 13:58:26 -0600
Subject: [XML-SIG] How do I process CDATA when the characters looks like XML
Message-ID: <BAY7-F44oDnP8vFoU910001f741@hotmail.com>

Thanks!  That did the trick.


>From: Mike Brown <mike@skew.org>
>To: William McLendon <txagcs98@hotmail.com>
>CC: xml-sig@python.org
>Subject: Re: [XML-SIG] How do I process CDATA when the characters looks 
>like XML
>Date: Wed, 14 May 2003 12:19:33 -0600 (MDT)
>William McLendon wrote:
> > I'm working with the basic python SAX parser (xml.sax.handler, etc) and 
>am
> > needing to process some XML that has "<" and ">" characters going in 
>CDATA
> > fields.
> >
> > For example, the model I want to have is this:
> >
> > <A>X</A>  where "X" is some kind of character data.
> >
> > but if X = <B> giving me this situation:
> >
> > <A><B></A>
>
>If you're wanting to put markup characters "<" or "&" in character data, 
>you
>must escape them, either using character or entity references, or the 
>special
>markup for a CDATA section:
>
><A>&lt;B></A>  (escaping the > is optional)
>or
><A><![CDATA[<B>]]></A>

_________________________________________________________________
Tired of spam? Get advanced junk mail protection with MSN 8. 
http://join.msn.com/?page=features/junkmail



From martin@v.loewis.de  Wed May 14 21:38:40 2003
From: martin@v.loewis.de (Martin v. =?iso-8859-15?q?L=F6wis?=)
Date: 14 May 2003 22:38:40 +0200
Subject: [XML-SIG] Floating exception on alpha machine
In-Reply-To: <200305141032.39323.jensj@bose.fysik.dtu.dk>
References: <200305121623.12111.jensj@bose.fysik.dtu.dk>
 <200305131404.11795.jensj@bose.fysik.dtu.dk>
 <m3smriev6k.fsf@mira.informatik.hu-berlin.de>
 <200305141032.39323.jensj@bose.fysik.dtu.dk>
Message-ID: <m3r871w9f3.fsf@mira.informatik.hu-berlin.de>

Jens Jorgen Mortensen <jensj@fysik.dtu.dk> writes:

> Here is what I get with gdb:

Thanks. Doesn't sound too convincing: those functions don't call each
other. Did you strip the executables?

> >, or you could try to link all code with the executable. For
> > this, you would have to relink the python binary, after putting
> > initpyexpat into config.c (pyexpat is likely the extension module for
> > which it can't find the symbols).
> 
> OK, hmmm...  I will try to experiment with this some day when I have some 
> time.

I think this might give additional insights still.

Regards,
Martin


From martin@v.loewis.de  Wed May 14 21:41:20 2003
From: martin@v.loewis.de (Martin v. =?iso-8859-15?q?L=F6wis?=)
Date: 14 May 2003 22:41:20 +0200
Subject: [XML-SIG] Re: Floating exception on alpha machine
In-Reply-To: <200305141110.27285.jensj@bose.fysik.dtu.dk>
References: <200305121623.12111.jensj@bose.fysik.dtu.dk>
 <200305141110.27285.jensj@bose.fysik.dtu.dk>
Message-ID: <m3n0hpw9an.fsf@mira.informatik.hu-berlin.de>

Jens Jorgen Mortensen <jensj@fysik.dtu.dk> writes:

> >>> Inf = Inf = 1e300 * 1e300
> Floating exception (core dumped)
> 
> A very simple way to crash the python interpreter!!  

The code is fine; the interpreter should not crash. Please report a
bug as sf.net/projects/python. The interpreter should not crash. At
worst, it should raise a Python exception.

> Does anybody know what to a do about it?  How should Inf be defined?
 
Only a platform expert could know.

Regards,
Martin



From rodsenra@gpr.com.br  Wed May 14 22:48:43 2003
From: rodsenra@gpr.com.br (Rodrigo Senra)
Date: Wed, 14 May 2003 18:48:43 -0300
Subject: [XML-SIG] Problems passing paths to xmlproc_catalog
Message-ID: <20030514214833.066D4128082@gunga.terra.com.br>

 Hi,

 First of all thanks for PyXML. It is great!

 Just recently I found out something that might me a bug.
 (But it could be a feature, in that case I apologize in advance ;o)

 This works fine:

 cat=catalog.xmlproc_catalog("catalog.soc",\
                             catalog.CatParserFactory())

 However, that does not:

 cat=catalog.xmlproc_catalog("<some_other_path>\catalog.soc",\
                             catalog.CatParserFactory())
 
 If I pass a path in the first parameter instead of the file name,
 it does not work anymore.

 This can be reproduced with xvcmd.py:

 OK  ->  python xvcmd.py  -c  catalog.soc      urls.xml
 BUG ->  python xvcmd.py  -c  /tmp/catalog.soc urls.xml

 I'm using xmlproc that is shipped in PyXML 0.8.2.

 I have already forwarded this message to the xmlproc maintainer,
 but I though this would interest xml-sig users also.

 Thanks in advance,
 Rod Senra

-- 
Rodrigo Senra                 (ICQ 114477550)
MSc Computer Engineer     rodsenra@gpr.com.br  
GPr Sistemas Ltda       http://www.gpr.com.br 



From tpassin@comcast.net  Thu May 15 04:59:39 2003
From: tpassin@comcast.net (Thomas B. Passin)
Date: Wed, 14 May 2003 23:59:39 -0400
Subject: [XML-SIG] Re: Floating exception on alpha machine
References: <200305121623.12111.jensj@bose.fysik.dtu.dk>
 <200305141110.27285.jensj@bose.fysik.dtu.dk>
 <m3n0hpw9an.fsf@mira.informatik.hu-berlin.de>
Message-ID: <002601c31a96$68b6c190$6401a8c0@tbp1>

[Martin v. L=F6wis]

> Jens Jorgen Mortensen <jensj@fysik.dtu.dk> writes:
>
> > >>> Inf =3D Inf =3D 1e300 * 1e300
> > Floating exception (core dumped)
> >
> > A very simple way to crash the python interpreter!!
>
> The code is fine; the interpreter should not crash. Please report a
> bug as sf.net/projects/python. The interpreter should not crash. At
> worst, it should raise a Python exception.
>
> > Does anybody know what to a do about it?  How should Inf be defin=
ed?
>

I only know that it does not crash on Python 2.2.1 on Windows 2000.

Cheers,

Tom P





From tpassin@comcast.net  Thu May 15 05:02:17 2003
From: tpassin@comcast.net (Thomas B. Passin)
Date: Thu, 15 May 2003 00:02:17 -0400
Subject: [XML-SIG] Problems passing paths to xmlproc_catalog
References: <20030514214833.066D4128082@gunga.terra.com.br>
Message-ID: <002b01c31a96$c690c9a0$6401a8c0@tbp1>

[Rodrigo Senra]
>
>  This can be reproduced with xvcmd.py:
>
>  OK  ->  python xvcmd.py  -c  catalog.soc      urls.xml
>  BUG ->  python xvcmd.py  -c  /tmp/catalog.soc urls.xml
>

Try using a file: url, either

file:/tmp/catalog.soc urls.xml

or

file:///tmp/catalog.soc urls.xml

(the latter is correct but some code might still be wanting the first form).

This is just a guess but it is worth trying.

Cheers,

Tom P




From fredrik@pythonware.com  Thu May 15 08:24:23 2003
From: fredrik@pythonware.com (Fredrik Lundh)
Date: Thu, 15 May 2003 09:24:23 +0200
Subject: [XML-SIG] Re: Re: Floating exception on alpha machine
References: <200305121623.12111.jensj@bose.fysik.dtu.dk><200305141110.27285.jensj@bose.fysik.dtu.dk> <m3n0hpw9an.fsf@mira.informatik.hu-berlin.de>
Message-ID: <b9vf88$n36$1@main.gmane.org>

Martin v. Löwis wrote:

> > >>> Inf = Inf = 1e300 * 1e300
> > Floating exception (core dumped)
> >
> > A very simple way to crash the python interpreter!!
>
> The code is fine; the interpreter should not crash. Please report a
> bug as sf.net/projects/python. The interpreter should not crash. At
> worst, it should raise a Python exception.
>
> > Does anybody know what to a do about it?  How should Inf be defined?
>
> Only a platform expert could know.

brief summary:

ax005> cat q.c
main()
{
  double value = 1e300;
  printf("%f\n", value * value);
}
ax005> cc q.c
ax005> ./a.out
Floating exception (core dumped)
ax005> cc -ieee q.c
ax005> ./a.out
INF
ax005> man ieee
... more information ...

</F>





From noreply@sourceforge.net  Thu May 15 17:12:43 2003
From: noreply@sourceforge.net (SourceForge.net)
Date: Thu, 15 May 2003 09:12:43 -0700
Subject: [XML-SIG] [ pyxml-Bugs-738362 ] XHtmlPrettyPrint: Bad URL in DOCTYPE
Message-ID: <E19GLLX-000085-00@sc8-sf-web1.sourceforge.net>

Bugs item #738362, was opened at 2003-05-15 18:12
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=106473&aid=738362&group_id=6473

Category: DOM
Group: None
Status: Open
Resolution: None
Priority: 5
Submitted By: Jacek Konieczny (jajcus)
Assigned to: Nobody/Anonymous (nobody)
Summary: XHtmlPrettyPrint: Bad URL in DOCTYPE

Initial Comment:
Following code results in invalid XHTML - the URL in
DOCTYPE is wrong.

--- cut ---
#!/usr/bin/python
                           
from xml.dom import implementation
from xml.dom import DOMException                      
                 
from xml.dom.ext import XHtmlPrettyPrint              
                         

doc=implementation.createDocument(None,None,None)     
                        
doc.appendChild(doc.createElement("html"))            
                        
XHtmlPrettyPrint(doc)
--- cut ---

Here is the output:
--- cut ---
<?xml version='1.0' encoding='UTF-8'?>                
                         

<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0
Strict//EN" DTD/xhtml1-strict.dtd">                   
                                                           
<html xmlns='http://www.w3.org/1999/xhtml'/>
--- cut ---


----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=106473&aid=738362&group_id=6473


From noreply@sourceforge.net  Thu May 15 17:23:54 2003
From: noreply@sourceforge.net (SourceForge.net)
Date: Thu, 15 May 2003 09:23:54 -0700
Subject: [XML-SIG] [ pyxml-Bugs-738366 ] Unneccessary comments from external DTD
Message-ID: <E19GLWM-00012R-00@sc8-sf-web4.sourceforge.net>

Bugs item #738366, was opened at 2003-05-15 18:23
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=106473&aid=738366&group_id=6473

Category: DOM
Group: None
Status: Open
Resolution: None
Priority: 5
Submitted By: Jacek Konieczny (jajcus)
Assigned to: Nobody/Anonymous (nobody)
Summary: Unneccessary comments from external DTD

Initial Comment:
When reading document that uses external DTD with
xml.dom.ext.reader.Sax2.Reader and then writting it
with xml.dom.ext.Print or PrettyPrint the output
includes unneccessary comments from the DTD.

Here is a sample of code:
-- cut ---
from xml.dom import implementation
from xml.dom import DOMException
from xml.dom.ext.reader.Sax2 import Reader
from xml.dom.ext import PrettyPrint

import cStringIO

doc_str="""
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0
Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"
xml:lang="en" lang="en"/>
"""

reader=Reader()
doc=reader.fromStream(cStringIO.StringIO(doc_str))
PrettyPrint(doc)
-- cut ---

And here is a fragment of its output:
-- cut ---
<?xml version='1.0' encoding='UTF-8'?>                
                         
<!DOCTYPE html PUBLIC
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd" "-//W3
C//DTD XHTML 1.0 Strict//EN">
<html xmlns='http://www.w3.org/1999/xhtml'
xml:lang='en' lang='en'/>
<!--
   Extensible HTML version 1.0 Strict DTD             
                        
              
   This is the same as HTML 4 Strict except for       
                        
   changes due to the differences between XML and SGML.
-- cut ---


----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=106473&aid=738366&group_id=6473


From nmkolev@uni-bonn.de  Fri May 16 22:57:53 2003
From: nmkolev@uni-bonn.de (Nickolay Kolev)
Date: Fri, 16 May 2003 23:57:53 +0200
Subject: [XML-SIG] Serializing DOM tree to file
Message-ID: <20030516235753.73ff1088.nmkolev@uni-bonn.de>

Hi all,

I am having trouble finding a way to simply serialize a DOM tree to a
file. I have been googling for half an hour and still can find no info
on the subject.

Basically, what I want to do is to have what PrettyPrint from
xml.dom.ext writes to the console. But I want it in a file.

I am sure this has been discussed many times, I just cannot find any
info.

Many thanks in advance,
nmk


From Ian.Sparks@etrials.com  Fri May 16 23:23:25 2003
From: Ian.Sparks@etrials.com (Ian Sparks)
Date: Fri, 16 May 2003 18:23:25 -0400
Subject: [XML-SIG] Serializing DOM tree to file
Message-ID: <41A1CBC76FDECC42B67946519C6677A95AE59F@pippin.int.etrials.com>

Something more than?

            file =3D open('file.xml','w')
            file.write(dom.toprettyxml(indent=3D'  '))
            file.close()

-----Original Message-----
From: Nickolay Kolev [mailto:nmkolev@uni-bonn.de]
Sent: Friday, May 16, 2003 5:58 PM
To: xml-sig@python.org
Subject: [XML-SIG] Serializing DOM tree to file


Hi all,

I am having trouble finding a way to simply serialize a DOM tree to a
file. I have been googling for half an hour and still can find no info
on the subject.

Basically, what I want to do is to have what PrettyPrint from
xml.dom.ext writes to the console. But I want it in a file.

I am sure this has been discussed many times, I just cannot find any
info.

Many thanks in advance,
nmk

_______________________________________________
XML-SIG maillist  -  XML-SIG@python.org
http://mail.python.org/mailman/listinfo/xml-sig


From nmkolev@uni-bonn.de  Sat May 17 00:22:41 2003
From: nmkolev@uni-bonn.de (Nickolay Kolev)
Date: Sat, 17 May 2003 01:22:41 +0200
Subject: [XML-SIG] Serializing DOM tree to file
In-Reply-To: <C276323E-87EC-11D7-A2F2-000A27979162@Oefelein.de>
References: <20030516235753.73ff1088.nmkolev@uni-bonn.de>
 <C276323E-87EC-11D7-A2F2-000A27979162@Oefelein.de>
Message-ID: <20030517012241.299dfb64.nmkolev@uni-bonn.de>

> Easy. You still can use PrettyPrint:
> 
> f = file(...)
> PrettyPrint(root, f)
> f.close()

Thank you, thank you!!

Just what I was looking for. Might any of you have tips on looking up
information like that? Too bad the archives aren't searchable.

nmk


From rsalz@datapower.com  Sat May 17 00:44:54 2003
From: rsalz@datapower.com (Rich Salz)
Date: Fri, 16 May 2003 19:44:54 -0400 (EDT)
Subject: [XML-SIG] Serializing DOM tree to file
In-Reply-To: <20030516235753.73ff1088.nmkolev@uni-bonn.de>
Message-ID: <Pine.LNX.4.44L0.0305161937190.11173-100000@smtp.datapower.com>

On Fri, 16 May 2003, Nickolay Kolev wrote:
> Basically, what I want to do is to have what PrettyPrint from
> xml.dom.ext writes to the console. But I want it in a file.

I was going to say that PrettyPrint is pretty ugly, because it moves
all the namespace declarations up to the outermost element.

Well it's worse than ugly, it's seriously broken.  It moves the default
namespace declaration to the top.  Here's my prettyprint script:
    ; cat $h/bin/xml/pp
    #! /usr/bin/env python2
    import sys
    from xml.dom.ext.reader import PyExpat
    from xml.dom.ext import PrettyPrint
    r = PyExpat.Reader()
    dom = r.fromStream(sys.stdin)
    PrettyPrint(dom)

Here's the input:
    ; cat x.xml
    <S:foo xmlns:S="http://example.com/1">
        <bar>test</bar>
        <bar xmlns='http://example.com/2'>test2</bar>
        <S:bar xmlns:S='http://example.com/2'>test2</S:bar>
    </S:foo>

And the output:
    <?xml version='1.0' encoding='UTF-8'?>
    <S:foo xmlns:S='http://example.com/1' xmlns='http://example.com/2'>
      <bar>test</bar>
      <bar>test2</bar>
      <S:bar xmlns:S='http://example.com/2'>test2</S:bar>
    </S:foo>

Seriously broken!

    from xml.com.ext.c14n import Canonicalize
    s = Canonicalize(node)         # returns output as a string
    Canonicalize(node, sys.stdout) # anything with a write() method


--
Rich Salz                     Chief Security Architect
DataPower Technology          http://www.datapower.com
XS40 XML Security Gateway     http://www.datapower.com/products/xs40.html



From nmkolev@uni-bonn.de  Sat May 17 08:17:48 2003
From: nmkolev@uni-bonn.de (Nickolay Kolev)
Date: Sat, 17 May 2003 09:17:48 +0200
Subject: [XML-SIG] Serializing DOM tree to file
In-Reply-To: <Pine.LNX.4.44L0.0305161937190.11173-100000@smtp.datapower.com>
References: <20030516235753.73ff1088.nmkolev@uni-bonn.de>
 <Pine.LNX.4.44L0.0305161937190.11173-100000@smtp.datapower.com>
Message-ID: <20030517091748.7bfc7e8a.nmkolev@uni-bonn.de>

>     from xml.com.ext.c14n import Canonicalize
>     s = Canonicalize(node)         # returns output as a string
>     Canonicalize(node, sys.stdout) # anything with a write() method


This does return something quite different that PrettyPrint. I was going
to ask a new question I had in a different question but both issues seem
to be quite involved so I will ask it here.

My situation: I have just started playing with Python and am trying to
write a simple messaging (blogging) system as an excercise. It uses XML
files as a data source. They have the following layout:

<?xml version="1.0" encoding="UTF-8"?>
<post>
	<date>16 May 2003</date>
	<category>Internal</category>
	<author>The Boss</author>
	<title>Raise</title>
	<message>You all get a salyry raise.</message>
</post>

It could hardly be any simpler. Every time a message is posted a post
object is constructed. It has a method for exposrting itself as xml:

def formatXML(self):

		self.formattedXML += '<?xml version="1.0" encoding="UTF-8"?>' \
		+ '\n<post>' \
		+ '\n\t<date>'     + self.date      +  '</date>' \
		+ '\n\t<category>' + self.category  +  '</category>' \
		+ '\n\t<author>'   + self.author    +  '</author>' \
		+ '\n\t<title>'    + self.title     +  '</title>' \
		+ '\n\t<message>'  + self.message   +  '</message>' \
		+ '\n</post>'

This formatted xml string then gets written to an xml file and the index
file containing the latest posts needs to be updated. The index.xml
looks like this:

<?xml version="1.0" encoding="UTF-8"?>
<index>
	<post>
		...
	</post>

	<post>
		...
	</post>

	...

</index>

The way I do it is with the updateIndex method:

def updateIndex(self):

		self.rebuildXML() #does nothing relevant in this case
				
		postElement =
xml.dom.minidom.parseString(self.formattedXML).firstChild

		o = open(os.path.join(self.root, 'index.xml'), 'rw')
		f = o.read()

		doc = xml.dom.minidom.parseString(f)
		docRoot = doc.firstChild

		docRoot.insertBefore(postElement, docRoot.firstChild)

		#PrettyPrint(doc)
		#Cannonicalize(doc, sys.stdout)

This doc variable needs to be serialized to the index.xml file now. Lets
assume we have only one post element in the index file. Using
prettyprint i get what I expect (see above). Using canonicalize the
newest post gets inserted before the opening index element?? Why is
that?

The other question I have is, is the code above optimal? What can be
done to make it more elegant? How about using importNode? Would you
recommend this over what I do now? Is there somewhere I can read more on
importNode (tutorial like preferred).

Thank you very much for taking the time!

Best regards,
nmk


From tom.kalmijn@warpgear.com  Sat May 17 17:22:50 2003
From: tom.kalmijn@warpgear.com (Tom Kalmijn)
Date: Sat, 17 May 2003 18:22:50 +0200
Subject: [XML-SIG] Favorez & XBEL
Message-ID: <ILECKJPFNONBHLKJABHCKEBNCMAA.tom.kalmijn@warpgear.com>

hi there,

I am the author of a program called Favorez. Favorez
is an AxtiveX IE 5+ plug-in program that creates web 
pages from the users' favorites.

XBEL
Favorez 1.2 has just been released and now supports 
the XBEL standard. I have been careful to make the
program adhere to the XBEL DTD.

XSLT
Favorez 1.2 ships with several XSL transformation 
files that should be interesting to your audience.
The XSLT's can be used for any valid XBEL data file.

(example at the bottom of this email)

Favorez website:
http://www.favorez.com/xml

I was hoping to maybe get into your list of XBEL 
compatible programs? :-)

Hope to hear from you and thanks for your efforts!

kind regards,
Tom

Tom Kalmijn
WarpGear Software
tom.kalmijn@warpgear.com  


>>> example >>>

Here's an example of how the HTML page may look when
Favorez transforms the XBEL data:
http://www.favorez.com/samples/xml/favorez.xml

The link will automatically transform in IE 5+.

Otherwise please follow this link (html):
http://www.favorez.com/samples/my_favorites/index.html

The xml above points to this stylesheet:
http://www.favorez.com/samples/xml/op_my_favorites.xsl

When you download and install Favorez you will find
a total of three new XSLT's and I have also included
two XSLT's that I found on the web (from Juergen Hermann).

>>> note on XBEL compatibility >>>

The special favicons where added to the DTD like this:

<!DOCTYPE xbel PUBLIC 
  "+//IDN python.org//DTD XML Bookmark Exchange Language 1.0//EN//XML"
  "http://www.python.org/topics/xml/dtds/xbel-1.0.dtd" 
[
<!ENTITY % local.url.att "favicon CDATA '01.png' target CDATA '_blank'"> 
]>

The XSL transformation templates actively check for these 
attributes and substitute values if needed.

ps
I had considered using XML namespaces but didn't want to
end up with a well formed but "invalid" XBEL file. I have
read quite a few articles on DTD validation and namespaces
and I must admit: it did became a tiny bit hairy for me...

If you have read all the way down to here... I say cheers!
Thanks again for your time.








From uche.ogbuji@fourthought.com  Mon May 19 17:24:58 2003
From: uche.ogbuji@fourthought.com (Uche Ogbuji)
Date: 19 May 2003 10:24:58 -0600
Subject: [XML-SIG] Re: XSLT in PyXML
In-Reply-To: <1053359286.3ec8fcb615477@webmail.ago.fr>
References: <1053359286.3ec8fcb615477@webmail.ago.fr>
Message-ID: <1053361497.2627.223.camel@localhost.localdomain>

On Mon, 2003-05-19 at 09:48, David Soulayrol wrote:
> Hi.
> 
> I saw you're the one who is assigned to XSLT bugs in PyXML. I know about 4Suite,
> but i'd like to know if PyXML XSLT is still broken, or if it should work soon.

Still broken.  A fixed version will likely not be incorporated until
after the 4Suite 1.0 release because of the amount of work the
re-integration will take.


-- 
Uche Ogbuji                                    Fourthought, Inc.
http://uche.ogbuji.net    http://4Suite.org    http://fourthought.com
Using libxml in Python - http://www.xml.com/pub/a/2003/05/14/py-xml.html
Charming Jython - http://www-106.ibm.com/developerworks/java/library/j-jython.html
The commons of creativity - http://www-106.ibm.com/developerworks/xml/library/x-think18.html
Is XQuery an omni-tool? - http://www.adtmag.com/article.asp?id=7620



From amf@northwestern.edu  Mon May 19 23:01:56 2003
From: amf@northwestern.edu (Adam Finlayson)
Date: Mon, 19 May 2003 17:01:56 -0500
Subject: [XML-SIG] Compiling XML package v0.8.2
Message-ID: <818E0567-8A45-11D7-8345-0003933D1DB8@northwestern.edu>

Running setup.py as-is didn't work on my OS X box (10.2.5)

[angilas:local/src/PyXML-0.8.2] miklo# python setup.py build
Traceback (most recent call last):
   File "setup.py", line 58, in ?
     if sys.platform[:6] == "darwin" and \
NameError: name 'distutils' is not defined

Adding distutils to the import statement compiled like a charm.

Take care,

--Adam

/*
  * Adam Finlayson
  * Web Developer, Web Communications
  * University Relations, Northwestern University
  * 620 Lincoln #204
  * Evanston, IL 60208-4230
  * amf@northwestern.edu
  * 847-491-4580
  */



From Alexandre.Fayolle@logilab.fr  Tue May 20 08:17:24 2003
From: Alexandre.Fayolle@logilab.fr (Alexandre Fayolle)
Date: Tue, 20 May 2003 09:17:24 +0200
Subject: [XML-SIG] Re: XSLT in PyXML
In-Reply-To: <1053361497.2627.223.camel@localhost.localdomain>
References: <1053359286.3ec8fcb615477@webmail.ago.fr> <1053361497.2627.223.camel@localhost.localdomain>
Message-ID: <20030520071724.GC4699@calvin>

On Mon, May 19, 2003 at 10:24:58AM -0600, Uche Ogbuji wrote:
> On Mon, 2003-05-19 at 09:48, David Soulayrol wrote:
> > Hi.
> > 
> > I saw you're the one who is assigned to XSLT bugs in PyXML. I know about 4Suite,
> > but i'd like to know if PyXML XSLT is still broken, or if it should work soon.
> 
> Still broken.  A fixed version will likely not be incorporated until
> after the 4Suite 1.0 release because of the amount of work the
> re-integration will take.

Any idea of a release date for 4Suite-1.0?

-- 
Alexandre Fayolle
LOGILAB, Paris (France).
http://www.logilab.com   http://www.logilab.fr  http://www.logilab.org
Développement logiciel avancé - Intelligence Artificielle - Formations


From 13w2e5vi8@aol.com  Tue May 20 11:44:39 2003
From: 13w2e5vi8@aol.com (Cheryl Johnston)
Date: Tue, 20 May 03 10:44:39 GMT
Subject: [XML-SIG] houdhni dwibble
Message-ID: <42yyb$jn5sz-6oyr3@pe35.c163an>

This is a multi-part message in MIME format.

--0B7C._4__8
Content-Type: text/plain;
Content-Transfer-Encoding: quoted-printable

<HTML><BODY></  ></  ><FONT color=3D#4b4b4b><TABLE width=3D"75%"></  ><TBO=
DY></  ><TR><TD><FONT color=3D#e8451b face=3D"Arial, Helvetica, sans-serif=
"  size=3D+1><STRONG>WARNING: </STRONG></FONT><FONT color=3D#356f88
face=3D=
"Arial, Helvetica, sans-serif" size=3D+1></  ><STRONG>D</  >o</  >n'</  >t=
 be f</  >o</  >ole</  >d b</  >y</  > 
 </  >pr</  >od</  >uct</  >s </  >cl</  >ai</  >ming to b</  >e</  > "</ =
 >HG</  >H".</  ></STRONG></  ><BR></  ></FONT></  ><FONT color=3D#2c2c2c =
face=3D"Arial, Helvetica, sans-serif"></  ><BR></  ><a href=3D"http://rd.y=
ahoo.com/*http://www.freemember.us/pm/index.htm?"></  >Pu</  >re</  > G</ =
 >H-</  >R</  >el</  >eas</  >er</a> c</  >o</  >nta</  >ins 
 </FONT></  ><FONT color=3D#888888 face=3D"Arial, Helvetica, sans-serif">1=
00% </  >natu</  >ra</  >l</FONT></  ><FONT color=3Dblack face=3D"Arial, H=
elvetica, sans-serif"></  ></FONT></  ><FONT color=3D#2c2c2c face=3D"Arial=
, Helvetica, sans-serif">h</  >om</  >eopa</  >thic H</  >GH in </  >an </=
  >easy t</  >o s</  >wal</  >low </  >c</  >ap</  >su</  >le fo</  >rm.</=
  > Cli</  >ni</  >ca</  >ll</  >y-</  >pro</  >ve</  >n </  >to<B> inc</ =
 >rea</  >se 
 IGF</  >-1 </  >by a whop</  >ping 40</  >2%!</B>  </  ><a href=3D"http:/=
/rd.yahoo.com/*http://www.freemember.us/pm/clinical.htm">C</  >lick H</  >=
ere</a> for th</  >e ent</  >ire study</  >!<BR><BR><a href=3D"http://rd.y=
ahoo.com/*http://www.freemember.us/pm/index.htm?">Pure G</  >H-</  >R</  >=
el</  >easer</a> is n</  >ot a Sti</  >mulat</  >or, Replacer, Steroid or =
Hormone. I</  >t is a 1</  >00</  >% Na</  >tural G</  >rowt</  >h Horm</ =
 >one Sec</  >retagog</  >ue, wi</  >th a new a</  >ctive </  >Hom</  >eop=
ath</  >ic 
 HG</  >H Enhance</  >r in an easy to swallow capsule form. It can be abso=
rbed effectively by the body to reactivate your Dormant Pituitary Gland an=
d  give an Extra Boost of HGH into the blood stream to be picked by the li=
ver 
 for conversion into IGF -1. Which begins to reverse your Aging Process at=
 a much faster rate.</FONT></TD></TR><TR><TD bgColor=3D#cecb99><TABLE bgCo=
lor=3D#fffdd5 cellPadding=3D10 width=3D"100%"><TBODY><TR><TD><FONT
color=3D=
#ff6000 face=3D"Arial, Helvetica, sans-serif"><B><I>What it is not:<BR></I=
></B></FONT><FONT color=3D#514f3c face=3D"Arial, Helvetica, sans-serif" si=
ze=3D-1>Pure GH-Releaser<B> does not contain</B> Synthetic HGH, 5HTP, DHEA=
, L -DOPA, Estrogen, Progesterone, Melatonin, Testosterone or any other Sy=
nthetic Growth Factors.</FONT></TD></TR></TBODY></TABLE></TD></TR><TR><TD>=
<FONT color=3D#2c2c2c face=3D"Arial, Helvetica, sans-serif">Quite simply,<=
a href=3D"http://rd.yahoo.com/*http://www.freemember.us/pm/index.htm?"> Pu=
re GH-Releaser </a> is the most effective anti-aging supplement ever devel=
oped. While most other capsules lose their efficacy as they pass through t=
he stomach, Pure GH-Releaser contains true homeopathic hgh infused into an=
 advanced capsule that instantly releases igf-1 into the bloodstream for f=
aster uptake. <BR><BR><HR noShade SIZE=3D1></FONT><FONT color=3D#471508 fa=
ce=3D"Arial, Helvetica, sans-serif" size=3D-1><BR><a href=3D"http://rd.yah=
oo.com/*http://www.freemember.us/pm/index.htm?">Click here </a> to learn m=
ore about this revolutionary new product and take advantage of our 90 day =
no questions asked strong-arm guarantee!</FONT><p>&nbsp;</p></FONT><p alig=
n=3D"center"><font color=3D"#471508" face=3D"Arial, Helvetica, sans-serif"=
 size=3D"-1">I stop recieving these ads please <a href=3D"http://rd.yahoo.=
com/*http://www.freemember.us/rem/remove.html?">click here</a></font></p><=
/TD></TR></TBODY></TABLE></BODY></HTML>

--0B7C._4__8--



From walter@livinglogic.de  Wed May 21 21:45:38 2003
From: walter@livinglogic.de (=?ISO-8859-15?Q?Walter_D=F6rwald?=)
Date: Wed, 21 May 2003 22:45:38 +0200
Subject: [XML-SIG] PyXML 0.8.2+Python 2.3 CVS gives encoding error
Message-ID: <3ECBE572.4040603@livinglogic.de>

This is a multi-part message in MIME format.
--------------010101020703000004010606
Content-Type: text/plain; charset=ISO-8859-15; format=flowed
Content-Transfer-Encoding: 8bit

PyXML 0.8.2 seems to be broken when used with the current CVS version
of Python.

Doing "import xml.dom" results in:

LookupError: unknown encoding: CHARSET

(see attachment for the complete stack trace)

The relevant file seems to be:
/usr/local/lib/python2.3/site-packages/_xmlplus/dom/en_US/LC_MESSAGES/4Suite.mo

I would have reported this on the SF bug tracker, but it's
not clear to me whether this should go to the Python, PyXML
or 4Suite trackers.

Bye,
    Walter Dörwald


--------------010101020703000004010606
Content-Type: text/plain;
 name="gettext-stacktrace.txt"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline;
 filename="gettext-stacktrace.txt"

Python 2.3b1+ (#1, May 21 2003, 22:00:21) 
[GCC 2.96 20000731 (Red Hat Linux 7.3 2.96-113)] on linux2
Type "help", "copyright", "credits" or "license" for more information.
>>> import xml.dom    
Traceback (most recent call last):
  File "<stdin>", line 1, in ?
  File "/usr/local/lib/python2.3/site-packages/_xmlplus/dom/__init__.py", line 237, in ?
    import MessageSource
  File "/usr/local/lib/python2.3/site-packages/_xmlplus/dom/MessageSource.py", line 22, in ?
    gettext.install('4Suite', locale_dir)
  File "/usr/local/lib/python2.3/gettext.py", line 428, in install
    translation(domain, localedir, fallback=True).install(unicode)
  File "/usr/local/lib/python2.3/gettext.py", line 416, in translation
    t = _translations.setdefault(key, class_(open(mofile, 'rb')))
  File "/usr/local/lib/python2.3/gettext.py", line 176, in __init__
    self._parse(fp)
  File "/usr/local/lib/python2.3/gettext.py", line 304, in _parse
    tmsg = unicode(tmsg, self._charset)
LookupError: unknown encoding: CHARSET
--------------010101020703000004010606--



From mike@skew.org  Wed May 21 22:56:55 2003
From: mike@skew.org (Mike Brown)
Date: Wed, 21 May 2003 15:56:55 -0600 (MDT)
Subject: [XML-SIG] Re: XSLT in PyXML
In-Reply-To: <20030520071724.GC4699@calvin> "from Alexandre Fayolle at May 20,
 2003 09:17:24 am"
Message-ID: <200305212156.h4LLutak082079@chilled.skew.org>

Alexandre Fayolle wrote:
> On Mon, May 19, 2003 at 10:24:58AM -0600, Uche Ogbuji wrote:
> > On Mon, 2003-05-19 at 09:48, David Soulayrol wrote:
> > > Hi.
> > > 
> > > I saw you're the one who is assigned to XSLT bugs in PyXML. I know about 4Suite,
> > > but i'd like to know if PyXML XSLT is still broken, or if it should work soon.
> > 
> > Still broken.  A fixed version will likely not be incorporated until
> > after the 4Suite 1.0 release because of the amount of work the
> > re-integration will take.
> 
> Any idea of a release date for 4Suite-1.0?

I am guessing there will be 1.0a2 by end of June, with
 - minor fixes already in CVS
 - RDF related server optimizations Mike Olson is working on
 - maybe a working, revamped Dashboard (also MikeO's)

and then the first beta, 1.0b1, by end of September...
 - most reported bugs fixed
 - maybe some better documentation in the distribution
 - some XPath optimizations Uche and I were working on

and then 1.0 final shortly after...  October/November?
 - centralized documentation on 4suite.org
 - new bugs fixed
 - pending feature requests considered

Is this realistic? I don't know.


From phthenry@earthlink.net  Thu May 22 05:45:15 2003
From: phthenry@earthlink.net (Paul Tremblay)
Date: Thu, 22 May 2003 00:45:15 -0400
Subject: [XML-SIG] install problem: can't find libraries (modules)
Message-ID: <20030522004515.A8476@supermac600.earthlink.net>

I just downloaded the most recent version (0.5.5.1) of PyXml. I
performed the normal build with no problems. I installed the packages
as the README told me to, putting them is site-packags/xml.

However, Python does not seem to be able to find these libraries. 
I ran the dem script sax/saxdemo.py, and got this error message:


Traceback (most recent call last):
  File "/usr/local/src/PyXML-0.5.5.1/demo/sax/saxdemo.py", line 5, in ?
    from xml.sax import saxexts, saxlib, saxutils
ImportError: cannot import name saxexts

I get similar messages when I try to run any of the XML software. For
example, when I try to run expat directly, I get a messae that pyexpat
cannot be found.

Thanks

Paul

-- 
************************
*Paul Tremblay         *
*phthenry@earthlink.net*
************************


From malcolm@commsecure.com.au  Thu May 22 06:10:39 2003
From: malcolm@commsecure.com.au (Malcolm Tredinnick)
Date: Thu, 22 May 2003 15:10:39 +1000
Subject: [XML-SIG] install problem: can't find libraries (modules)
In-Reply-To: <20030522004515.A8476@supermac600.earthlink.net>
References: <20030522004515.A8476@supermac600.earthlink.net>
Message-ID: <20030522051039.GB26899@ws14.commsecure.com.au>

On Thu, May 22, 2003 at 12:45:15AM -0400, Paul Tremblay wrote:
> I just downloaded the most recent version (0.5.5.1) of PyXml. I
> performed the normal build with no problems. I installed the packages
> as the README told me to, putting them is site-packags/xml.

I cannot help with your particular problem, but it could have something
to do with the fact that what you think is the latest version is quite
old.  The latest version of PyXML is 0.8.2.

Go to http://sourceforge.net/project/showfiles.php?group_id=6473 for
authoritative sources.

Malcolm

-- 
Many are called, few volunteer.


From martin@v.loewis.de  Thu May 22 08:15:25 2003
From: martin@v.loewis.de (Martin v. =?iso-8859-15?q?L=F6wis?=)
Date: 22 May 2003 09:15:25 +0200
Subject: [XML-SIG] PyXML 0.8.2+Python 2.3 CVS gives encoding error
In-Reply-To: <3ECBE572.4040603@livinglogic.de>
References: <3ECBE572.4040603@livinglogic.de>
Message-ID: <m3vfw378qa.fsf@mira.informatik.hu-berlin.de>

Walter D=F6rwald <walter@livinglogic.de> writes:

> LookupError: unknown encoding: CHARSET

I've observed the same thing. It would be good if you could find out
why that happens.

Regards,
Martin



From walter@livinglogic.de  Thu May 22 12:34:58 2003
From: walter@livinglogic.de (=?ISO-8859-15?Q?Walter_D=F6rwald?=)
Date: Thu, 22 May 2003 13:34:58 +0200
Subject: [XML-SIG] PyXML 0.8.2+Python 2.3 CVS gives encoding error
In-Reply-To: <m3vfw378qa.fsf@mira.informatik.hu-berlin.de>
References: <3ECBE572.4040603@livinglogic.de> <m3vfw378qa.fsf@mira.informatik.hu-berlin.de>
Message-ID: <3ECCB5E2.1040007@livinglogic.de>

This is a multi-part message in MIME format.
--------------010800060208030301090805
Content-Type: text/plain; charset=ISO-8859-15; format=flowed
Content-Transfer-Encoding: 8bit

Martin v. Löwis wrote:
> Walter Dörwald <walter@livinglogic.de> writes:
> 
>>LookupError: unknown encoding: CHARSET
> 
> I've observed the same thing. It would be good if you could find out
> why that happens.

I'm attaching a detailed stack trace that shows local variables.

I guess this problem stems from xml/dom/en_US/LC_MESSAGES/4Suite.mo

The readable part looks like this:

Project-Id-Version: PACKAGE VERSION
PO-Revision-Date: Sun Feb 18 17:52:04 2001
Last-Translator: FULL NAME <EMAIL@ADDRESS>
Language-Team: LANGUAGE <LL@li.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=CHARSET
Content-Transfer-Encoding: ENCODING
Generated-By: pygettext.py 1.1

This looks to me like some default configuration that hasn't
been changed. I guess Python version before 2.3 simple ignored
this information (especially the Content-Type).

Maybe Python should fail back to the ASCII if the charset is
unknown?

Bye,
    Walter Dörwald

--------------010800060208030301090805
Content-Type: text/plain;
 name="gettext-stacktrace-long.txt"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline;
 filename="gettext-stacktrace-long.txt"

Python 2.3b1+ (#1, May 21 2003, 22:00:21) 
[GCC 2.96 20000731 (Red Hat Linux 7.3 2.96-113)] on linux2
Type "help", "copyright", "credits" or "license" for more information.
>>> import xml.dom
Traceback and locals (innermost call last; 7 frames, 0 dropped):

   File <stdin>, line 1, in ?
         __builtins__  = <module '__builtin__' (built-in)>
         __doc__       = None
         __file__      = '/home/walter/.pythonrc.py'
         __name__      = '__main__'
         help          = <pydoc.Helper instance>
         nested_scopes = _Feature((2, 1, 0, 'beta', 1), (2, 2, 0, 'alpha', 0), 16)

   File /usr/local/lib/python2.3/site-packages/_xmlplus/dom/__init__.py, line 237, in ?
      235     EMPTY_PREFIX = None
      236     
      237 >>> import MessageSource
      238     DOMExceptionStrings = MessageSource.__dict__['DOMExceptionStrings']
      239     EventExceptionStrings = MessageSource.__dict__['EventExceptionStrings']
         BAD_BOUNDARYPOINTS_ERR      = 1
         BadBoundaryPointsErr        = <class xml.dom.BadBoundaryPointsErr at 0x4057126c>
         DOMError                    = <class xml.dom.DOMError at 0x40560e0c>
         DOMException                = <class xml.dom.DOMException at 0x4056d02c>
         DOMImplementation           = <module 'xml.dom.DOMImplementation' from '/usr/local/lib/python2.3/site-packages/_xmlplus/dom/DOMImplementation.pyc'>
         DOMSTRING_SIZE_ERR          = 2
         DOMStringSizeErr            = <class xml.dom.DomstringSizeErr at 0x4056dbcc>
         DomstringSizeErr            = <class xml.dom.DomstringSizeErr at 0x4056dbcc>
         EMPTY_NAMESPACE             = None
         EMPTY_PREFIX                = None
         EventException              = <class xml.dom.EventException at 0x4056d26c>
         FT_EXCEPTION_BASE           = 1000
         FtException                 = <class xml.dom.FtException at 0x4056d7dc>
         HIERARCHY_REQUEST_ERR       = 3
         HTMLDOMImplementation       = <module 'xml.dom.html.HTMLDOMImplementation' from '/usr/local/lib/python2.3/site-packages/_xmlplus/dom/html/HTMLDOMImplementation.pyc'>
         HierarchyRequestErr         = <class xml.dom.HierarchyRequestErr at 0x4056dbfc>
         INDEX_SIZE_ERR              = 1
         INUSE_ATTRIBUTE_ERR         = 10
         INVALID_ACCESS_ERR          = 15
         INVALID_CHARACTER_ERR       = 5
         INVALID_MODIFICATION_ERR    = 13
         INVALID_NODE_TYPE_ERR       = 2
         INVALID_STATE_ERR           = 11
         IndexSizeErr                = <class xml.dom.IndexSizeErr at 0x4056d95c>
         InuseAttributeErr           = <class xml.dom.InuseAttributeErr at 0x4056dd7c>
         InvalidAccessErr            = <class xml.dom.InvalidAccessErr at 0x4056de6c>
         InvalidCharacterErr         = <class xml.dom.InvalidCharacterErr at 0x4056dc5c>
         InvalidModificationErr      = <class xml.dom.InvalidModificationErr at 0x4056de0c>
         InvalidNodeTypeErr          = <class xml.dom.InvalidNodeTypeErr at 0x4057129c>
         InvalidStateErr             = <class xml.dom.InvalidStateErr at 0x4056ddac>
         MessageSource               = <module 'xml.dom.MessageSource' from '/usr/local/lib/python2.3/site-packages/_xmlplus/dom/MessageSource.pyc'>
         NAMESPACE_ERR               = 14
         NOT_FOUND_ERR               = 8
         NOT_SUPPORTED_ERR           = 9
         NO_DATA_ALLOWED_ERR         = 6
         NO_MODIFICATION_ALLOWED_ERR = 7
         NamespaceErr                = <class xml.dom.NamespaceErr at 0x4056de3c>
         NoDataAllowedErr            = <class xml.dom.NoDataAllowedErr at 0x4056dcbc>
         NoModificationAllowedErr    = <class xml.dom.NoModificationAllowedErr at 0x4056dcec>
         Node                        = <class xml.dom.Node at 0x40560b6c>
         NotFoundErr                 = <class xml.dom.NotFoundErr at 0x4056dd1c>
         NotSupportedErr             = <class xml.dom.NotSupportedErr at 0x4056dd4c>
         Range                       = <module 'xml.dom.Range' from '/usr/local/lib/python2.3/site-packages/_xmlplus/dom/Range.pyc'>
         RangeException              = <class xml.dom.RangeException at 0x4056d4dc>
         SYNTAX_ERR                  = 12
         SyntaxErr                   = <class xml.dom.SyntaxErr at 0x4056dddc>
         UNSPECIFIED_EVENT_TYPE_ERR  = 0
         UnspecifiedEventTypeErr     = <class xml.dom.UnspecifiedEventTypeErr at 0x4056defc>
         UserDataHandler             = <class xml.dom.UserDataHandler at 0x40560c8c>
         VALIDATION_ERR              = 16
         ValidationErr               = <class xml.dom.ValidationErr at 0x4056decc>
         WRONG_DOCUMENT_ERR          = 4
         WrongDocumentErr            = <class xml.dom.WrongDocumentErr at 0x4056dc2c>
         XHTML_NAMESPACE             = 'http://www.w3.org/1999/xhtml'
         XMLNS_NAMESPACE             = 'http://www.w3.org/2000/xmlns/'
         XML_NAMESPACE               = 'http://www.w3.org/XML/1998/namespace'
         XML_PARSE_ERR               = 1001
         XmlParseErr                 = <class xml.dom.XmlParseErr at 0x4057123c>
         __builtins__                = {'help': Type help() for interactive help, or help(object) for help about object., 'vars': <built-in...ions.AttributeError at 0x4015474c>, 'OverflowError': <class exceptions.OverflowError at 0x401549bc>}
         __doc__                     = '\nWWW: http://4suite.org/4DOM         e-mail: support@4suite.org\n\nCopyright (c) 2000 Fourthought ....   All Rights Reserved.\nSee  http://4suite.org/COPYRIGHT  for license and copyright information\n'
         __file__                    = '/usr/local/lib/python2.3/site-packages/_xmlplus/dom/__init__.pyc'
         __name__                    = 'xml.dom'
         __path__                    = ['/usr/local/lib/python2.3/site-packages/_xmlplus/dom']
         html                        = <module 'xml.dom.html' from '/usr/local/lib/python2.3/site-packages/_xmlplus/dom/html/__init__.pyc'>
         implementation              = <xml.dom.html.HTMLDOMImplementation.HTMLDOMImplementation instance at 0x405dd1cc>

   File /usr/local/lib/python2.3/site-packages/_xmlplus/dom/MessageSource.py, line 24, in ?
      22         gettext.install('4Suite', locale_dir)
      23     except (ImportError, AttributeError, IOError):
      24 >>>     def _(msg):
      25             return msg
      26     
         BAD_BOUNDARYPOINTS_ERR      = 1
         DOMSTRING_SIZE_ERR          = 2
         HIERARCHY_REQUEST_ERR       = 3
         INDEX_SIZE_ERR              = 1
         INUSE_ATTRIBUTE_ERR         = 10
         INVALID_ACCESS_ERR          = 15
         INVALID_CHARACTER_ERR       = 5
         INVALID_MODIFICATION_ERR    = 13
         INVALID_NODE_TYPE_ERR       = 2
         INVALID_STATE_ERR           = 11
         NAMESPACE_ERR               = 14
         NOT_FOUND_ERR               = 8
         NOT_SUPPORTED_ERR           = 9
         NO_DATA_ALLOWED_ERR         = 6
         NO_MODIFICATION_ALLOWED_ERR = 7
         SYNTAX_ERR                  = 12
         UNSPECIFIED_EVENT_TYPE_ERR  = 0
         VALIDATION_ERR              = 16
         WRONG_DOCUMENT_ERR          = 4
         XML_PARSE_ERR               = 1001
         __builtins__                = {'help': Type help() for interactive help, or help(object) for help about object., 'vars': <built-in...ions.AttributeError at 0x4015474c>, 'OverflowError': <class exceptions.OverflowError at 0x401549bc>}
         __doc__                     = None
         __file__                    = '/usr/local/lib/python2.3/site-packages/_xmlplus/dom/MessageSource.pyc'
         __name__                    = 'xml.dom.MessageSource'
         gettext                     = <module 'gettext' from '/usr/local/lib/python2.3/gettext.pyc'>
         locale_dir                  = '/usr/local/lib/python2.3/site-packages/_xmlplus/dom'
         os                          = <module 'os' from '/usr/local/lib/python2.3/os.pyc'>

   File /usr/local/lib/python2.3/gettext.py, line 428, in install
      426     
      427     def install(domain, localedir=None, unicode=False):
      428 >>>     translation(domain, localedir, fallback=True).install(unicode)
      429     
      430     
         domain    = '4Suite'
         localedir = '/usr/local/lib/python2.3/site-packages/_xmlplus/dom'
         unicode   = False

   File /usr/local/lib/python2.3/gettext.py, line 416, in translation
      414             t = _translations.get(key)
      415             if t is None:
      416 >>>             t = _translations.setdefault(key, class_(open(mofile, 'rb')))
      417             # Copy the translation object to allow setting fallbacks.
      418             # All other instance data is shared with the cached object.
         class_    = <class gettext.GNUTranslations at 0x405e12fc>
         domain    = '4Suite'
         fallback  = True
         key       = '/usr/local/lib/python2.3/site-packages/_xmlplus/dom/en_US/LC_MESSAGES/4Suite.mo'
         languages = None
         localedir = '/usr/local/lib/python2.3/site-packages/_xmlplus/dom'
         mofile    = '/usr/local/lib/python2.3/site-packages/_xmlplus/dom/en_US/LC_MESSAGES/4Suite.mo'
         mofiles   = ['/usr/local/lib/python2.3/site-packages/_xmlplus/dom/en_US/LC_MESSAGES/4Suite.mo']
         result    = None
         t         = None

   File /usr/local/lib/python2.3/gettext.py, line 176, in __init__
      174             self._fallback = None
      175             if fp is not None:
      176 >>>             self._parse(fp)
      177     
      178         def _parse(self, fp):
         fp   = <open file '/usr/local/lib/python2.3/site-packages/_xmlplus/dom/en_US/LC_MESSAGES/4Suite.mo', mode 'rb' at 0x405e2f60>
         self = <gettext.GNUTranslations instance at 0x405e356c>

   File /usr/local/lib/python2.3/gettext.py, line 304, in _parse
      302                     if self._charset:
      303                         msg = unicode(msg, self._charset)
      304 >>>                     tmsg = unicode(tmsg, self._charset)
      305                     catalog[msg] = tmsg
      306                 # advance to next entry in the seek tables
         buf       = '\xde\x12\x04\x95\x00\x00\x00\x00\x01\x00\x00\x00\x1c\x00\x00\x00$\x00\x00\x00\x00\x00\x00\x00\x00\x...t/plain; charset=CHARSET\nContent-Transfer-Encoding: ENCODING\nGenerated-By: pygettext.py 1.1\n\x00'
         buflen    = 331
         catalog   = {}
         filename  = '/usr/local/lib/python2.3/site-packages/_xmlplus/dom/en_US/LC_MESSAGES/4Suite.mo'
         fp        = <open file '/usr/local/lib/python2.3/site-packages/_xmlplus/dom/en_US/LC_MESSAGES/4Suite.mo', mode 'rb' at 0x405e2f60>
         i         = 0
         ii        = '<II'
         item      = 'Generated-By: pygettext.py 1.1'
         k         = 'generated-by'
         lastk     = 'generated-by'
         magic     = 2500072158L
         masteridx = 28L
         mend      = 44L
         mlen      = 0L
         moff      = 44L
         msg       = u''
         msgcount  = 1L
         self      = <gettext.GNUTranslations instance at 0x405e356c>
         tend      = 330L
         tlen      = 285L
         tmsg      = 'Project-Id-Version: PACKAGE VERSION\nPO-Revision-Date: Sun Feb 18 17:52:04 2001\nLast-Translator: F... text/plain; charset=CHARSET\nContent-Transfer-Encoding: ENCODING\nGenerated-By: pygettext.py 1.1\n'
         toff      = 45L
         transidx  = 36L
         unpack    = <built-in function unpack>
         v         = 'pygettext.py 1.1'
         version   = 0L

LookupError: unknown encoding: CHARSET
>>> 
--------------010800060208030301090805--



From Jean-Michel.Bruel@univ-pau.fr  Thu May 22 15:10:43 2003
From: Jean-Michel.Bruel@univ-pau.fr (Jean-Michel BRUEL)
Date: Thu, 22 May 2003 16:10:43 +0200
Subject: [XML-SIG] QoS CBSE 2003 - Call For Participation
Message-ID: <200305221410.h4MEAh623854@univ-pau.fr>

(Apologies if you receive multiple copies of this announcement)

     !!! Early Registration deadline is May 24th !!!
--------------------------------------------------------------
                   Call for Participation

                  Quality of Service in
           Component-Based Software Engineering

                      QoSCBSE'2003

        Workshop at "Reliable Software Technologies 2003"
       http://www.ada-europe.org/conference2003.html

           June 20th, 2003, Toulouse, France

   Workshop webpage : http://liuppa.univ-pau.fr/QoSCBSE2003

--------------------------------------------------------------

Registration is available on-line on the main conference web site:
           http://www.irit.fr/AdaEurope2003/




From phthenry@earthlink.net  Fri May 23 04:48:44 2003
From: phthenry@earthlink.net (Paul Tremblay)
Date: Thu, 22 May 2003 23:48:44 -0400
Subject: [XML-SIG] install problem: can't find libraries (modules)
In-Reply-To: <20030522051039.GB26899@ws14.commsecure.com.au>; from malcolm@commsecure.com.au on Thu, May 22, 2003 at 03:10:39PM +1000
References: <20030522004515.A8476@supermac600.earthlink.net> <20030522051039.GB26899@ws14.commsecure.com.au>
Message-ID: <20030522234844.A1316@supermac600.earthlink.net>

On Thu, May 22, 2003 at 03:10:39PM +1000, Malcolm Tredinnick wrote:
> 
> On Thu, May 22, 2003 at 12:45:15AM -0400, Paul Tremblay wrote:
> > I just downloaded the most recent version (0.5.5.1) of PyXml. I
> > performed the normal build with no problems. I installed the packages
> > as the README told me to, putting them is site-packags/xml.
> 
> I cannot help with your particular problem, but it could have something
> to do with the fact that what you think is the latest version is quite
> old.  The latest version of PyXML is 0.8.2.
> 
> Go to http://sourceforge.net/project/showfiles.php?group_id=6473 for
> authoritative sources.
> 

Thanks. That worked.

I thought .5.5.1 was the latest version because I was directed to this
from the python home page. Is this not a problem? Might not others
make the same mistake as I did?

Thanks

Paul

-- 
************************
*Paul Tremblay         *
*phthenry@earthlink.net*
************************


From phthenry@earthlink.net  Fri May 23 04:53:56 2003
From: phthenry@earthlink.net (Paul Tremblay)
Date: Thu, 22 May 2003 23:53:56 -0400
Subject: [XML-SIG] using PyXML on a string
Message-ID: <20030522235356.B1316@supermac600.earthlink.net>

I would like to use SAX to parse a string rather than a file. Is there
a way? I know how to use expat directly to parse a string, and I know
how to use SAX to parse a file. However, one cannot use expat in the
way I like:

# code will break!
class ExpatDir:

    
    def __init__(self):
        self.__initiate_parser()


    def __start_element(name, attrs):
        print repr(name)

    def __end_element(name):
        print repr(name)
 
    def __char_data(data):
        print repr(name)

    def __initiate_parser(self):
        parser = xml.parsers.expat.ParserCreate()
        parser.StartElementHandler = self.__start_element
        parser.EndElementHandler = self.__end_element
        parser.CharacterDataHandler = self.__char_data
        self.__parser = parser

    def parse_string(self, a_string):
        self.__parser.parse(a_string)

This code will break becaue I am passing to expat a method rather than
a definition.

When I use SAX with python, I subclass my documenthandler in the
standard way, and then use parse(file).

Can I not use parse(string)?

Thanks

Paul


-- 
************************
*Paul Tremblay         *
*phthenry@earthlink.net*
************************


From tpassin@comcast.net  Fri May 23 06:01:56 2003
From: tpassin@comcast.net (Thomas B. Passin)
Date: Fri, 23 May 2003 01:01:56 -0400
Subject: [XML-SIG] install problem: can't find libraries (modules)
References: <20030522004515.A8476@supermac600.earthlink.net>
 <20030522051039.GB26899@ws14.commsecure.com.au>
 <20030522234844.A1316@supermac600.earthlink.net>
Message-ID: <00c001c320e8$6f557980$6401a8c0@tbp1>

[Paul Tremblay]
> I thought .5.5.1 was the latest version because I was directed to this
> from the python home page. Is this not a problem? Might not others
> make the same mistake as I did?
>

How did you get there?  I took two different routes and got to the correct
current version both ways:

1) Python Home/Python Topic Guides/Python and XML Processing/Download Page

2) Python Home/SIGs/xml-sig/PYXML

Cheers,

Tom P




From tpassin@comcast.net  Fri May 23 06:19:29 2003
From: tpassin@comcast.net (Thomas B. Passin)
Date: Fri, 23 May 2003 01:19:29 -0400
Subject: [XML-SIG] using PyXML on a string
References: <20030522235356.B1316@supermac600.earthlink.net>
Message-ID: <00c701c320ea$e2eced40$6401a8c0@tbp1>

[Paul Tremblay]

> I would like to use SAX to parse a string rather than a file. Is there
> a way? I know how to use expat directly to parse a string, and I know
> how to use SAX to parse a file. However, one cannot use expat in the
> way I like:
>

One easy way is to use StringIO (or cStringIO) to turn the string into a
file-like object.  Then feed it to the parser as if it were a file.

Cheers,

Tom P




From martin@v.loewis.de  Fri May 23 06:18:59 2003
From: martin@v.loewis.de (Martin v. =?iso-8859-15?q?L=F6wis?=)
Date: 23 May 2003 07:18:59 +0200
Subject: [XML-SIG] using PyXML on a string
In-Reply-To: <20030522235356.B1316@supermac600.earthlink.net>
References: <20030522235356.B1316@supermac600.earthlink.net>
Message-ID: <m3of1ugrzw.fsf@mira.informatik.hu-berlin.de>

Paul Tremblay <phthenry@earthlink.net> writes:

> Can I not use parse(string)?

There are several ways to do that. One is to create a [c]StringIO
object and parse that; the other is to use the IncrementalReader API,
and invoke .feed instead of .parse.

HTH,
Martin



From phthenry@earthlink.net  Fri May 23 23:32:49 2003
From: phthenry@earthlink.net (Paul Tremblay)
Date: Fri, 23 May 2003 18:32:49 -0400
Subject: [XML-SIG] install problem: can't find libraries (modules)
In-Reply-To: <00c001c320e8$6f557980$6401a8c0@tbp1>; from tpassin@comcast.net on Fri, May 23, 2003 at 01:01:56AM -0400
References: <20030522004515.A8476@supermac600.earthlink.net> <20030522051039.GB26899@ws14.commsecure.com.au> <20030522234844.A1316@supermac600.earthlink.net> <00c001c320e8$6f557980$6401a8c0@tbp1>
Message-ID: <20030523183249.C1575@supermac600.earthlink.net>

On Fri, May 23, 2003 at 01:01:56AM -0400, Thomas B. Passin wrote:
> How did you get there?  I took two different routes and got to the correct
> current version both ways:
> 
> 1) Python Home/Python Topic Guides/Python and XML Processing/Download Page
> 
> 2) Python Home/SIGs/xml-sig/PYXML
> 
> Cheers,
> 
> Tom P
> 
> 
> 

I'm not sure myself now! Maybe I did a google search? I just did a
google search again, and came up with this link:

http://www.auth.gr/mirrors/python/topics/xml/download.html

This mirror also lists the current version as 0.5x

Thanks

Paul


-- 
************************
*Paul Tremblay         *
*phthenry@earthlink.net*
************************


From martin@v.loewis.de  Sat May 24 12:17:31 2003
From: martin@v.loewis.de (Martin v. =?iso-8859-15?q?L=F6wis?=)
Date: 24 May 2003 13:17:31 +0200
Subject: [XML-SIG] install problem: can't find libraries (modules)
In-Reply-To: <20030523183249.C1575@supermac600.earthlink.net>
References: <20030522004515.A8476@supermac600.earthlink.net>
 <20030522051039.GB26899@ws14.commsecure.com.au>
 <20030522234844.A1316@supermac600.earthlink.net>
 <00c001c320e8$6f557980$6401a8c0@tbp1>
 <20030523183249.C1575@supermac600.earthlink.net>
Message-ID: <m38ysw8ugk.fsf@mira.informatik.hu-berlin.de>

Paul Tremblay <phthenry@earthlink.net> writes:

> This mirror also lists the current version as 0.5x

I sent a message to the administrator requesting that he changes the
mirror.

Regards,
Martin



From pyxml@wonderclown.com  Sun May 25 15:47:24 2003
From: pyxml@wonderclown.com (pyxml@wonderclown.com)
Date: Sun, 25 May 2003 09:47:24 -0500
Subject: [XML-SIG] Handling of character entity references
Message-ID: <20030525144723.GD14154@aerosol>

I am trying to produce XHTML files from input XML files which contain
a mixture of XHTML and custom markup. (I am essentially building a
template system, where the content is written devoid of any page
layout, and I then use python/PyXML to parse the content, add in
banners and navigation menus and such, and write out XHTML.) I'm
having a problem, though, getting character entity references in the
source document to pass through to the output. Things like &amp;,
&lt;, and &gt; work fine, but &eacute; does not.

I do not have a complete DTD for my custom markup, as I don't
particularly care to validate it. However, the parser seems unwilling
to leave entities alone, so I have tried adding the following to my
source document:

<!DOCTYPE gallery [
    <!ENTITY % HTMLlat1 PUBLIC
       "-//W3C//ENTITIES Latin 1 for XHTML//EN"
       "http://www.w3.org/TR/xhtml1/DTD/xhtml-lat1.ent">
    %HTMLlat1;
]>

This brings in the XHTML Latin-1 entities, which seems to work well
enough to get the parser to accept the source, but then &eacute; gets
translated to the following two-byte sequence on output: 0xC3
0xA9. Curiously enough, I have also tried to output what the parser is
giving me by printing the nodeValue of the text node containing this
entity, and I get an exception:

  File "./Gallery.py", line 39, in generateContent
    print child.nodeValue
UnicodeError: ASCII encoding error: ordinal not in range(128)

I'm not sure what to make of that; my knowledge of how Python handles
Unicode is limited.

So essentially what I'm asking is how do I get PyXML to preserve
"&eacute;" as-is and output it in the same manner when I PrettyPrint()
it? (Or, equivalently, convert it to its Unicode representation on
input and back to an entity reference on output.)

Thanks for any help,

Randall Nortman


From tpassin@comcast.net  Sun May 25 18:17:32 2003
From: tpassin@comcast.net (Thomas B. Passin)
Date: Sun, 25 May 2003 13:17:32 -0400
Subject: [XML-SIG] Handling of character entity references
References: <20030525144723.GD14154@aerosol>
Message-ID: <001001c322e1$87653a10$6401a8c0@tbp1>

[<pyxml@wonderclown.com>]

> I am trying to produce XHTML files from input XML files which contain
> a mixture of XHTML and custom markup.
>...
> I'm
> having a problem, though, getting character entity references in the
> source document to pass through to the output. Things like &amp;,
> &lt;, and &gt; work fine, but &eacute; does not.
>

This sounds like a fine job for XSLT, rather than custom code...

You need to realize that by the time the parser has done its job, there is
no such thing as "&eacute;" any more.  All entities and character references
will have been replaced by their actual characters.  This is how XML is
supposed to work - it is spelled out in the XML Rec.

When it comes time to output the results, the serializer has no way to check
back to see that some particular character originally was serialized as some
particular entity.  What comes out is up to the serializer.  It is also up
to the original encoding as well, since the serializer cannot output a
character that does not exist in the chosen encoding.

The question is, why do you care whether or not an "&eacute;" entity is
used?  A browser will not care.  There is no reason to go to any trouble to
get those entities inserted.  The real reason you might think you need them
is that your output is in a different encoding from what the browser
expects.  If you are getting a two-byte output for that character, then you
are probably putting out utf-8, whereas most browsers are set for either
latin-1 (iso-8859-1) or to some Windows encoding.

Also, even if the right character is there in the right encoding, if you
read it with some editors and other applications, it may __look__ wrong
because they think the encoding is different from utf-8. A browser would
display it correctly as long as it knew what the encoding was.

If you are going to produce html for a browser to display, then you have
several choices:

1) Use xslt, specify the html output method, and let the serializer handle
the issue.  It will put out entities and character references where needed.

2) Change the encoding of your output to something your browser expects.
This is not a good solution,though, because you cannot know what encoding a
random browser is set up for.

3) If you know the actual output encoding, put a meta element in the head of
the document that specifies the correct encoding.  You can find out the
syntax through Google.  This is not really an independent alternative as it
is good practice anyway.

4) Write your own serializer that converts specific characters into entities
or chracter references.  This is the least desirable because it is more work
and more prone to errors.  It is also not really necessary, as you can see
from the above.

Really, the only time it is necessary (or useful) to preserve entities like
eacute is for editing applications, and that is a very specialized area.

This question comes up a lot.  Look at the various xslt FAQs and try Google
for more discussion.  Look in the archive of this list, too.

> ... I have tried adding the following to my
> source document:
>
> <!DOCTYPE gallery [
>     <!ENTITY % HTMLlat1 PUBLIC
>        "-//W3C//ENTITIES Latin 1 for XHTML//EN"
>        "http://www.w3.org/TR/xhtml1/DTD/xhtml-lat1.ent">
>     %HTMLlat1;
> ]>
>
> This brings in the XHTML Latin-1 entities, which seems to work well
> enough to get the parser to accept the source, but then &eacute; gets
> translated to the following two-byte sequence on output: 0xC3
> 0xA9.

Well, that is interesting because it is the utf-8 encoding of the value E9,
which is the latin-1 encoding of eacute.  However, the unicode character for
&eacute; (you can see this in your DTD) is U+00C9, which would be encoded in
utf-8 as C3 89.  Therefore your code is not decoding and encoding the input
correctly.  You seem to be taking the sequence of bytes of a latin-1 source
and encoding it into utf-8 as if the source were really in unicode instead
of latin-1.

This reinforces my suggestion that you use xslt for this job.  Then your
encoding issues will get handled correctly.  If you still want to do it with
your own code, then you have to make sure that

1) you are correctly informing the parser which encoding is in use, and
2) Any character strings that you generate yourself are generated with the
right encoding.  Or, to be more precise, make sure that all the code agrees
that it is using the Python internal unicode representation.  It appears
that right now that is not happening.  If you are using SAX, it might be
your SAX handler, which might be using strings with the default encoding
instead of the right encoding.

Here is a useful resource about utf-8 and unicode -

http://www.cl.cam.ac.uk/~mgk25/unicode.html

> Curiously enough, I have also tried to output what the parser is
> giving me by printing the nodeValue of the text node containing this
> entity, and I get an exception:
>
>   File "./Gallery.py", line 39, in generateContent
>     print child.nodeValue
> UnicodeError: ASCII encoding error: ordinal not in range(128)
>

The standard print function is expecting the string it prints to be encoded
using the platform default,which is not the case here.  You can avoid this
by encoding the string using a writer from the codec module (part of the
standard library).  Read the module docs to see how.

Cheers,

Tom P




From martin@v.loewis.de  Sun May 25 18:28:10 2003
From: martin@v.loewis.de (Martin v. =?iso-8859-15?q?L=F6wis?=)
Date: 25 May 2003 19:28:10 +0200
Subject: [XML-SIG] Handling of character entity references
In-Reply-To: <20030525144723.GD14154@aerosol>
References: <20030525144723.GD14154@aerosol>
Message-ID: <m3y90vlyvp.fsf@mira.informatik.hu-berlin.de>

pyxml@wonderclown.com writes:

> So essentially what I'm asking is how do I get PyXML to preserve
> "&eacute;" as-is and output it in the same manner when I PrettyPrint()
> it?

That depends very much on the precise parsing technology you use.

Regards,
Martin


From martin@v.loewis.de  Sun May 25 18:55:26 2003
From: martin@v.loewis.de (Martin v. =?iso-8859-15?q?L=F6wis?=)
Date: 25 May 2003 19:55:26 +0200
Subject: [XML-SIG] Handling of character entity references
In-Reply-To: <20030525144723.GD14154@aerosol>
References: <20030525144723.GD14154@aerosol>
Message-ID: <m3ptm6nc6p.fsf@mira.informatik.hu-berlin.de>

pyxml@wonderclown.com writes:

> This brings in the XHTML Latin-1 entities, which seems to work well
> enough to get the parser to accept the source, but then &eacute; gets
> translated to the following two-byte sequence on output: 0xC3
> 0xA9. 

[I had to think of what the problem might be]

You mean, you get this byte sequence in the pretty-printed XML?

This is just fine, and expected. 0xc3,0xa9 *is* the byte sequence that
represents &eacute;, atleast in UTF-8, and UTF-8 is the default
encoding of XML. Unless there is a problem with that, I suggest you
accept the output as-is - it *is* the document you meant to produce.

Regards,
Martin


From dieter@handshake.de  Sun May 25 19:30:39 2003
From: dieter@handshake.de (Dieter Maurer)
Date: Sun, 25 May 2003 20:30:39 +0200
Subject: [XML-SIG] Handling of character entity references
In-Reply-To: <20030525144723.GD14154@aerosol>
References: <20030525144723.GD14154@aerosol>
Message-ID: <16081.3023.983485.306128@gargle.gargle.HOWL>

pyxml@wonderclown.com wrote at 2003-5-25 09:47 -0500:
 > ....
 > I do not have a complete DTD for my custom markup, as I don't
 > particularly care to validate it. However, the parser seems unwilling
 > to leave entities alone, so I have tried adding the following to my
 > source document:
 > 
 > <!DOCTYPE gallery [
 >     <!ENTITY % HTMLlat1 PUBLIC
 >        "-//W3C//ENTITIES Latin 1 for XHTML//EN"
 >        "http://www.w3.org/TR/xhtml1/DTD/xhtml-lat1.ent">
 >     %HTMLlat1;
 > ]>
 > 
 > This brings in the XHTML Latin-1 entities, which seems to work well
 > enough to get the parser to accept the source, but then &eacute; gets
 > translated to the following two-byte sequence on output: 0xC3
 > 0xA9.

Character entities are a thing of the past, in general no longer
needed with Unicode.

XML using Unicode tried get rid of the no longer necessary complexities of 
character entities.

Your parser converted the entities into Unicode characters.
On output, they have apparently been converted to UTF-8 (the
XML default encoding).


Dieter


From kajiyama@grad.sccs.chukyo-u.ac.jp  Sun May 25 20:56:34 2003
From: kajiyama@grad.sccs.chukyo-u.ac.jp (Tamito KAJIYAMA)
Date: Mon, 26 May 2003 04:56:34 +0900
Subject: [XML-SIG] Handling of character entity references
In-Reply-To: <001001c322e1$87653a10$6401a8c0@tbp1> (tpassin@comcast.net)
References: <001001c322e1$87653a10$6401a8c0@tbp1>
Message-ID: <200305251956.h4PJuYS04744@grad.sccs.chukyo-u.ac.jp>

"Thomas B. Passin" <tpassin@comcast.net> writes:
|
| [<pyxml@wonderclown.com>]
| 
| > I am trying to produce XHTML files from input XML files which contain
| > a mixture of XHTML and custom markup.
| >...
| > I'm
| > having a problem, though, getting character entity references in the
| > source document to pass through to the output. Things like &amp;,
| > &lt;, and &gt; work fine, but &eacute; does not.
| >
| 
| This sounds like a fine job for XSLT, rather than custom code...

I had a similar problem with Randall's one a few years ago, so
I'd like to describe my problem and a solution to it (just FYI:
I totally agree with the suggestion about XSLT).

I've used a SAX-based Python script for years to convert a set
of XML files into an HTML file.  The file encodings of the input
and output files are EUC-JP and ISO-2022-JP, respectively.
I also had a need to use Latin-1 characters in the input and
output files.  However, because of the Japanese file encodings,
raw character codes (say, 0xe9 in ISO-8859-1 for &eacute;) were
not acceptable.  Therefore, I needed a way to represent Latin-1
characters in the input XML files and to produce character
references in the output HTML file.

So, I decided to use a special markup to represent Latin-1
characters in the input XML files, as illustrated below:

<char name="eacute" />

I also changed the Python script so that appropriate character
references were generated in the output HTML file according to
the special markup.  (Numeric character references can also be
produced by the form <char code="..." />.)

I'm not sure this is a good solution and in fact the special
markup looks somewhat clumsy, but anyway it works fine.  When I
wrote the Python script, XSLT was at the stage of working draft
and there was no usable Python implementation of XSLT.  I'd use
XSLT if I rewrote the Python script now.

HTH,

-- 
KAJIYAMA, Tamito <kajiyama@grad.sccs.chukyo-u.ac.jp>


From tpassin@comcast.net  Sun May 25 21:16:24 2003
From: tpassin@comcast.net (Thomas B. Passin)
Date: Sun, 25 May 2003 16:16:24 -0400
Subject: [XML-SIG] Handling of character entity references
References: <001001c322e1$87653a10$6401a8c0@tbp1>
 <200305251956.h4PJuYS04744@grad.sccs.chukyo-u.ac.jp>
Message-ID: <005101c322fa$83dccd40$6401a8c0@tbp1>

[Tamito KAJIYAMA]

> So, I decided to use a special markup to represent Latin-1
> characters in the input XML files, as illustrated below:
>
> <char name="eacute" />

Some people have done the same kind of thing using processing instructions.
Topologi's editor replaces illegal characters with PIs is this way.  The
idea is that you are not actually changing the information content of the
original (because you are not inserting new elements), yet you can inform
the processor about the situation since PIs can be reported.

Encoding issues are always hard!  Just try to capture the titles of web
pages, using a range of browsers, and combine them into one document (I am
referring to trying to combine the bookmarks from different browsers using
XBEL).  You can end up with all kinds of strange results.

Cheers,

Tom P




From casa@sweetohm.net  Sun May 25 22:04:40 2003
From: casa@sweetohm.net (Michel Casabianca)
Date: Sun, 25 May 2003 23:04:40 +0200
Subject: [XML-SIG] Problem installing PyXML 0.8.2 on MacOSX
Message-ID: <8051DC78-8EF4-11D7-A5D6-000393BDD5BA@sweetohm.net>

This version doesn't install on MacOSX with the following error message:

$ sudo python setup.py
Traceback (most recent call last):
   File "setup.py", line 58, in ?
     if sys.platform[:6] == "darwin" and \
NameError: name 'distutils' is not defined

The previous version 0.8.1 installs correctly.
--
Michel CASABIANCA
casa@sweetohm.net
http://www.sweetohm.net



From noreply@sourceforge.net  Mon May 26 00:35:40 2003
From: noreply@sourceforge.net (SourceForge.net)
Date: Sun, 25 May 2003 16:35:40 -0700
Subject: [XML-SIG] [ pyxml-Bugs-743374 ] Error processing empty namespace attribute
Message-ID: <E19K51g-00087t-00@sc8-sf-web2.sourceforge.net>

Bugs item #743374, was opened at 2003-05-25 23:35
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=106473&aid=743374&group_id=6473

Category: DOM
Group: None
Status: Open
Resolution: None
Priority: 5
Submitted By: Chui Tey (teyc)
Assigned to: Nobody/Anonymous (nobody)
Summary: Error processing empty namespace attribute

Initial Comment:
The following XML file was parsed, but could not be 
printed by minidom.

<?xml version="1.0" ?>
<test1 xmlns="uri:test.com">
  <test2 xmlns="">
     <test3>Hello</test3>
  </test2>
</test1>

>>> import xml.dom.minidom
>>> doc=xml.dom.minidom.parse('test.xml')
>>> print doc.toxml()
Traceback (most recent call last):
  File "<stdin>", line 1, in ?
  File "C:\Python22\Lib\site-
packages\_xmlplus\dom\minidom.py", line 47, in toxml
    return self.toprettyxml("", "", encoding)
  File "C:\Python22\Lib\site-
packages\_xmlplus\dom\minidom.py", line 59, in 
toprettyxml
    self.writexml(writer, "", indent, newl, encoding)
  File "C:\Python22\Lib\site-
packages\_xmlplus\dom\minidom.py", line 1746, in 
writexml
    node.writexml(writer, indent, addindent, newl)
  File "C:\Python22\Lib\site-
packages\_xmlplus\dom\minidom.py", line 816, in 
writexml
    node.writexml(writer,indent+addindent,addindent,newl)
  File "C:\Python22\Lib\site-
packages\_xmlplus\dom\minidom.py", line 811, in 
writexml
    _write_data(writer, attrs[a_name].value)
  File "C:\Python22\Lib\site-
packages\_xmlplus\dom\minidom.py", line 301, in 
_write_data
    data = data.replace("&", "&amp;").replace("<", "&lt;")
AttributeError: 'NoneType' object has no attribute 'replace'

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=106473&aid=743374&group_id=6473


From mike@skew.org  Mon May 26 00:42:11 2003
From: mike@skew.org (Mike Brown)
Date: Sun, 25 May 2003 17:42:11 -0600 (MDT)
Subject: [XML-SIG] Handling of character entity references
In-Reply-To: <200305251956.h4PJuYS04744@grad.sccs.chukyo-u.ac.jp>
 "from Tamito KAJIYAMA at May 26, 2003 04:56:34 am"
Message-ID: <200305252342.h4PNgBaJ010381@chilled.skew.org>

Tamito KAJIYAMA wrote:
> "Thomas B. Passin" <tpassin@comcast.net> writes:
> |
> | [<pyxml@wonderclown.com>]
> | 
> | > I am trying to produce XHTML files from input XML files which contain
> | > a mixture of XHTML and custom markup.
> | >...
> | > I'm
> | > having a problem, though, getting character entity references in the
> | > source document to pass through to the output. Things like &amp;,
> | > &lt;, and &gt; work fine, but &eacute; does not.
> | >
> | 
> | This sounds like a fine job for XSLT, rather than custom code...
> 
> I had a similar problem with Randall's one a few years ago, so
> I'd like to describe my problem and a solution to it (just FYI:
> I totally agree with the suggestion about XSLT).
> 
> I've used a SAX-based Python script for years to convert a set
> of XML files into an HTML file.  The file encodings of the input
> and output files are EUC-JP and ISO-2022-JP, respectively.
> I also had a need to use Latin-1 characters in the input and
> output files.  However, because of the Japanese file encodings,
> raw character codes (say, 0xe9 in ISO-8859-1 for &eacute;) were
> not acceptable.  Therefore, I needed a way to represent Latin-1
> characters in the input XML files and to produce character
> references in the output HTML file.

This wouldn't be needed today, since python is now Unicode friendly. You have
Unicode strings being passed to your SAX methods, and on the output side, the
EUC-JP or ISO-2022-JP codec used by the XML serializer will convert to bytes
all the characters supported by those encodings. The non-ASCII range of
ISO-8859-1 (\u00A0-\u00FF) would not be handled by the codecs, but the XML
serializer will simply deal with that by emitting numeric character references
automatically.

> So, I decided to use a special markup to represent Latin-1
> characters in the input XML files, as illustrated below:
> 
> <char name="eacute" />

Similar project:
http://xmlchar.sourceforge.net/

Seems like it's past the point of diminishing returns, to me..


From mike@skew.org  Mon May 26 00:49:54 2003
From: mike@skew.org (Mike Brown)
Date: Sun, 25 May 2003 17:49:54 -0600 (MDT)
Subject: [XML-SIG] Problem installing PyXML 0.8.2 on MacOSX
In-Reply-To: <8051DC78-8EF4-11D7-A5D6-000393BDD5BA@sweetohm.net>
 "from Michel Casabianca at May 25, 2003 11:04:40 pm"
Message-ID: <200305252349.h4PNnsPV010428@chilled.skew.org>

Michel Casabianca wrote:
> This version doesn't install on MacOSX with the following error message:
> 
> $ sudo python setup.py
> Traceback (most recent call last):
>    File "setup.py", line 58, in ?
>      if sys.platform[:6] == "darwin" and \
> NameError: name 'distutils' is not defined

Indeed, the imports are a little sloppy.

e.g. get_config_vars is imported, while there's a reference to
a fully qualified get_config_var (no 's')...

from distutils.sysconfig import get_config_vars
[...]
if sys.platform[:6] == "darwin" and \
   distutils.sysconfig.get_config_var("LDSHARED").find("-flat_namespace") == -1:

Hopefully someone will check in a fix.

> The previous version 0.8.1 installs correctly.

...but comes with a version of expat that may cause crashes for you.
0.8 is actually safer :)


From dalke@dalkescientific.com  Mon May 26 04:42:34 2003
From: dalke@dalkescientific.com (Andrew Dalke)
Date: Sun, 25 May 2003 21:42:34 -0600
Subject: [XML-SIG] CHARSET and Python 2.3
Message-ID: <165C2BC4-8F2C-11D7-A8E6-000393C92466@dalkescientific.com>

The _xmlplus package doesn't work under Python 2.3 where it works under =20=

2.2.
It appears to be because of the gettext entry, which contains a =20
"charset:"
of "CHARSET", which 2.3 doesn't like.

Details below.

# First, it works under Python 2.2

[Andrew-Dalkes-Computer:~/ftps/SOAPpy-0.10.1] dalke% env =20
PYTHONPATH=3D/usr/local/lib/python2.3/site-packages python2.2
Python 2.2 (#1, 07/14/02, 23:25:09)
[GCC Apple cpp-precomp 6.14] on darwin
Type "help", "copyright", "credits" or "license" for more information.
 >>> import xml.dom.minidom
 >>> import xml
 >>> xml.__file__
'/usr/local/lib/python2.3/site-packages/_xmlplus/__init__.py'
 >>> ^D

# but not under 2.3

[Andrew-Dalkes-Computer:~/ftps/SOAPpy-0.10.1] dalke% python2.3
Python 2.3b1+ (#9, May  7 2003, 23:33:14)
[GCC 3.1 20020420 (prerelease)] on darwin
Type "help", "copyright", "credits" or "license" for more information.
 >>> import xml.dom.minidom
Traceback (most recent call last):
   File "<stdin>", line 1, in ?
   File =20
"/usr/local/lib/python2.3/site-packages/_xmlplus/dom/__init__.py", line =20=

237, in ?
     import MessageSource
   File =20
"/usr/local/lib/python2.3/site-packages/_xmlplus/dom/MessageSource.py", =20=

line 22, in ?
     gettext.install('4Suite', locale_dir)
   File "/usr/local/lib/python2.3/gettext.py", line 423, in install
     translation(domain, localedir, fallback=3DTrue).install(unicode)
   File "/usr/local/lib/python2.3/gettext.py", line 411, in translation
     t =3D _translations.setdefault(key, class_(open(mofile, 'rb')))
   File "/usr/local/lib/python2.3/gettext.py", line 176, in __init__
     self._parse(fp)
   File "/usr/local/lib/python2.3/gettext.py", line 299, in _parse
     tmsg =3D unicode(tmsg, self._charset)
LookupError: unknown encoding: CHARSET
 >>> import xml
 >>> xml.__file__
'/usr/local/lib/python2.3/site-packages/_xmlplus/__init__.pyc'
 >>> xml.__version__
'0.8.2'

# The gettext for my 'en-US' locale is

[Andrew-Dalkes-Computer:~/ftps/SOAPpy-0.10.1] dalke% cat =20
/usr/local/lib/python2.3//site-packages/_xmlplus/dom/en_US/LC_MESSAGES/=20=

4Suite.mo
=A1Z=A1Z$,-Project-Id-Version: PACKAGE VERSION
PO-Revision-Date: Sun Feb 18 17:52:04 2001
Last-Translator: FULL NAME <EMAIL@ADDRESS>
Language-Team: LANGUAGE <LL@li.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=3DCHARSET
Content-Transfer-Encoding: ENCODING
Generated-By: pygettext.py 1.1
[Andrew-Dalkes-Computer:~/ftps/SOAPpy-0.10.1] dalke%

# If I change the 'CHARSET' to 'Latin-1' I have no problem.

This 4Suite.mo file in CVS also has 'CHARSET', so I assume there
is still a problem.

Neither Google nor alltheweb found references to this exception
message.

					Andrew
					dalke@dalkescientific.com



From phthenry@earthlink.net  Mon May 26 06:58:23 2003
From: phthenry@earthlink.net (Paul Tremblay)
Date: Mon, 26 May 2003 01:58:23 -0400
Subject: [XML-SIG] using PyXML on a string
In-Reply-To: <00c701c320ea$e2eced40$6401a8c0@tbp1>; from tpassin@comcast.net on Fri, May 23, 2003 at 01:19:29AM -0400
References: <20030522235356.B1316@supermac600.earthlink.net> <00c701c320ea$e2eced40$6401a8c0@tbp1>
Message-ID: <20030526015823.B1006@supermac600.earthlink.net>

On Fri, May 23, 2003 at 01:19:29AM -0400, Thomas B. Passin wrote:
> 
> One easy way is to use StringIO (or cStringIO) to turn the string into a
> file-like object.  Then feed it to the parser as if it were a file.
> 

Thanks. The documentation for cStringIO implies that you can't pass to
it a string containing unicode with values above 128. However, I found
the exact opposite to be true. If I pass a string containing uincode
above 128 to StringI0, I get a unicode error. If I use cStringIO, I
get no error.

I would rather use cStringIO anyway, since it is faster, but wanted to
know if I had missed something in the documentation.

thanks

Paul

-- 
************************
*Paul Tremblay         *
*phthenry@earthlink.net*
************************


From phthenry@earthlink.net  Mon May 26 07:12:24 2003
From: phthenry@earthlink.net (Paul Tremblay)
Date: Mon, 26 May 2003 02:12:24 -0400
Subject: [XML-SIG] Handling of character entity references
In-Reply-To: <200305252342.h4PNgBaJ010381@chilled.skew.org>; from mike@skew.org on Sun, May 25, 2003 at 05:42:11PM -0600
References: <200305251956.h4PJuYS04744@grad.sccs.chukyo-u.ac.jp> <200305252342.h4PNgBaJ010381@chilled.skew.org>
Message-ID: <20030526021224.C1006@supermac600.earthlink.net>

On Sun, May 25, 2003 at 05:42:11PM -0600, Mike Brown wrote:
> From: Mike Brown <mike@skew.org>
> Subject: Re: [XML-SIG] Handling of character entity references
> To: Tamito KAJIYAMA <kajiyama@grad.sccs.chukyo-u.ac.jp>
> Cc: xml-sig@python.org
> Date: Sun, 25 May 2003 17:42:11 -0600 (MDT)
> 
> Tamito KAJIYAMA wrote:
> > "Thomas B. Passin" <tpassin@comcast.net> writes:
> > |
> > | [<pyxml@wonderclown.com>]
> > | 
> > | > I am trying to produce XHTML files from input XML files which contain
> > | > a mixture of XHTML and custom markup.
> > | >...
> > | > I'm
> > | > having a problem, though, getting character entity references in the
> > | > source document to pass through to the output. Things like &amp;,
> > | > &lt;, and &gt; work fine, but &eacute; does not.
> > | >
> > | 
> > | This sounds like a fine job for XSLT, rather than custom code...
> > 
> > I had a similar problem with Randall's one a few years ago, so
> > I'd like to describe my problem and a solution to it (just FYI:
> > I totally agree with the suggestion about XSLT).
> > 
> > I've used a SAX-based Python script for years to convert a set
> > of XML files into an HTML file.  The file encodings of the input
> > and output files are EUC-JP and ISO-2022-JP, respectively.
> > I also had a need to use Latin-1 characters in the input and
> > output files.  However, because of the Japanese file encodings,
> > raw character codes (say, 0xe9 in ISO-8859-1 for &eacute;) were
> > not acceptable.  Therefore, I needed a way to represent Latin-1
> > characters in the input XML files and to produce character
> > references in the output HTML file.
> 
> This wouldn't be needed today, since python is now Unicode friendly. You have
> Unicode strings being passed to your SAX methods, and on the output side, the
> EUC-JP or ISO-2022-JP codec used by the XML serializer will convert to bytes
> all the characters supported by those encodings. The non-ASCII range of
> ISO-8859-1 (\u00A0-\u00FF) would not be handled by the codecs, but the XML
> serializer will simply deal with that by emitting numeric character references
> automatically.
> 
> > So, I decided to use a special markup to represent Latin-1
> > characters in the input XML files, as illustrated below:
> > 
> > <char name="eacute" />
> 
> Similar project:
> http://xmlchar.sourceforge.net/
> 
> Seems like it's past the point of diminishing returns, to me..
> 
> _______________________________________________
> XML-SIG maillist  -  XML-SIG@python.org
> http://mail.python.org/mailman/listinfo/xml-sig



Interestingly enough, I saw the following emails on an xsl mailing
list covering this very topic:

Paul

*****

> how can you make special characters(like &eacute;) appairs in a text
> output file in xsl encoding?

I thought I'd take this opportunity to describe one of the new
features in XSLT 2.0 -- the ability to map characters in text nodes
and attribute values during output onto arbitrary strings. This is
done through a "character map".

To say that é should be output as &eacute;, for example, you can
create a character map as follows:

<xsl:character-map name="latin-1">
  <xsl:output-character character="&#xE9;" string="&amp;eacute;" />
</xsl:character-map>

and reference this character map from your output definition:

<xsl:output use-character-maps="latin-1" />

When the result tree is output, every occurrence of é, in text or in
attribute values, will be replaced by the string &eacute;.

Note that this will work for é characters that get into the output
from being part of the source document as well as the é characters
that you use in your stylesheet. It also does the replacement in
attribute values as well as text nodes. In both ways it's more
powerful than d-o-e.

Of course that might mean that your output is not well-formed, because
there's no guarantee that the output has an entity declaration for the
&eacute; entity, so you should usually specify a doctype-system so
that the output includes a DOCTYPE declaration that contains the
relevant entity declaration.

Cheers,

Jeni

---
Jeni Tennison
http://www.jenitennison.com/


 XSL-List info and archive:  http://www.mulberrytech.com/xsl/xsl-list


>I thought I'd take this opportunity to describe one of the new
>features in XSLT 2.0 -- the ability to map characters in text nodes
>and attribute values during output onto arbitrary strings. This is
>done through a "character map".

Wow! That's something we in the document world have been hacking in one
way or another for ages. People who aren't in our world often tell us
we don't need it ("just do everything in UNICODE" they say, but that
is often impractical).

This is wonderful. (I haven't been following XSLT 2.0 in detail, being
under the impression that is was totally focused on data and we
document types were going to be able to  ignore it.  Perhaps I'd
better start reading.)

-- Tommie

-- 
************************
*Paul Tremblay         *
*phthenry@earthlink.net*
************************


From martin@v.loewis.de  Mon May 26 07:54:06 2003
From: martin@v.loewis.de (=?ISO-8859-1?Q?=22Martin_v=2E_L=F6wis=22?=)
Date: Mon, 26 May 2003 08:54:06 +0200
Subject: [XML-SIG] using PyXML on a string
In-Reply-To: <20030526015823.B1006@supermac600.earthlink.net>
References: <20030522235356.B1316@supermac600.earthlink.net> <00c701c320ea$e2eced40$6401a8c0@tbp1> <20030526015823.B1006@supermac600.earthlink.net>
Message-ID: <3ED1BA0E.8040207@v.loewis.de>

Paul Tremblay wrote:
> Thanks. The documentation for cStringIO implies that you can't pass to
> it a string containing unicode with values above 128. However, I found
> the exact opposite to be true. If I pass a string containing uincode
> above 128 to StringI0, I get a unicode error. If I use cStringIO, I
> get no error.

Hmm. There is no such thing as a "string containing unicode", atleast 
not if, by "string", you really mean <type 'string'>. You only can pass
<type 'string'> to cStringIO, not <type 'unicode'>. I usually call 
objects of <type 'string'> 'byte strings', and objects of <type 
'unicode'> 'Unicode strings'. IOW, cStringIO supports only byte strings,
whereas StringIO supports both byte strings and Unicode strings. In one
Python release, there was a bug and StringIO rejected Unicode strings. 
cStringIO has never supported Unicode strings, and never will.

Regards,
Martin



From kajiyama@grad.sccs.chukyo-u.ac.jp  Mon May 26 08:50:24 2003
From: kajiyama@grad.sccs.chukyo-u.ac.jp (Tamito KAJIYAMA)
Date: Mon, 26 May 2003 16:50:24 +0900
Subject: [XML-SIG] Handling of character entity references
In-Reply-To: <200305252342.h4PNgBaJ010381@chilled.skew.org> (message from Mike
 Brown on Sun, 25 May 2003 17:42:11 -0600 (MDT))
References: <200305252342.h4PNgBaJ010381@chilled.skew.org>
Message-ID: <200305260750.h4Q7oOX05758@grad.sccs.chukyo-u.ac.jp>

Mike Brown <mike@skew.org> writes:
|
| > I've used a SAX-based Python script for years to convert a set
| > of XML files into an HTML file.  The file encodings of the input
| > and output files are EUC-JP and ISO-2022-JP, respectively.
| > I also had a need to use Latin-1 characters in the input and
| > output files.  However, because of the Japanese file encodings,
| > raw character codes (say, 0xe9 in ISO-8859-1 for &eacute;) were
| > not acceptable.  Therefore, I needed a way to represent Latin-1
| > characters in the input XML files and to produce character
| > references in the output HTML file.
| 
| This wouldn't be needed today, since python is now Unicode friendly. You have
| Unicode strings being passed to your SAX methods, and on the output side, the
| EUC-JP or ISO-2022-JP codec used by the XML serializer will convert to bytes
| all the characters supported by those encodings. The non-ASCII range of
| ISO-8859-1 (\u00A0-\u00FF) would not be handled by the codecs, but the XML
| serializer will simply deal with that by emitting numeric character references
| automatically.
| 
| > So, I decided to use a special markup to represent Latin-1
| > characters in the input XML files, as illustrated below:
| > 
| > <char name="eacute" />

Thank you for the tip, but I was not able to figure out how to
realize what you suggested.  To the best of my knowledge, the
method ContentHandler.characters() determines how characters are
to be handled on the output side.  So, encoding-related things
won't be _automatically_ done.  I've missed something important?

Thanks,

-- 
KAJIYAMA, Tamito <kajiyama@grad.sccs.chukyo-u.ac.jp>


From andrew.straw@adelaide.edu.au  Mon May 26 08:54:09 2003
From: andrew.straw@adelaide.edu.au (Andrew Straw)
Date: Mon, 26 May 2003 17:24:09 +0930
Subject: [XML-SIG] fixes for PyXML and Python2.3
Message-ID: <3B47C56D-8F4F-11D7-8B82-00039311EA24@adelaide.edu.au>

Hi all,

Here's a diff of what I had to do against a CVS checkout of PyXML to 
get it to build with Python 2.3b1.  Hopefully someone can check these 
trivial changes into CVS to save other poor souls from tracking down 
little bugs like this.

Index: setup.py
===================================================================
RCS file: /cvsroot/pyxml/xml/setup.py,v
retrieving revision 1.79
diff -c -r1.79 setup.py
*** setup.py	26 Jan 2003 10:28:25 -0000	1.79
--- setup.py	26 May 2003 07:43:28 -0000
***************
*** 6,11 ****
--- 6,12 ----

   import sys, os, string

+ import distutils
   from distutils.core import setup, Extension
   from setupext import Data_Files, install_Data_Files, 
wininst_request_delete
   from distutils.sysconfig import get_config_vars
Index: xml/FtCore.py
===================================================================
RCS file: /cvsroot/pyxml/xml/xml/FtCore.py,v
retrieving revision 1.4
diff -c -r1.4 FtCore.py
*** xml/FtCore.py	27 Mar 2003 22:27:42 -0000	1.4
--- xml/FtCore.py	26 May 2003 07:43:29 -0000
***************
*** 52,58 ****
               locale_dir = os.path.join(_top, pkg.replace(".", os.sep))
               try:
                   f = gettext.translation('4Suite', locale_dir).gettext
!             except IOError:
                   f = _
               _cache[pkg] = f
           return _cache[pkg]
--- 52,58 ----
               locale_dir = os.path.join(_top, pkg.replace(".", os.sep))
               try:
                   f = gettext.translation('4Suite', locale_dir).gettext
!             except (IOError,LookupError):
                   f = _
               _cache[pkg] = f
           return _cache[pkg]



From mjais@gmx-gmbh.de  Mon May 26 11:10:52 2003
From: mjais@gmx-gmbh.de (Markus Jais)
Date: Mon, 26 May 2003 12:10:52 +0200
Subject: [XML-SIG] DOM -> String ?
Message-ID: <200305261210.52455.mjais@gmx-gmbh.de>

hello

is there a way to transform a DOM Tree into a Python string ???
identation is  not necessary. I just want to send the DOM Tree over
a socket.

Markus

-- 
Markus Jais
Software Developer
GMX Aktiengesellschaft
Riesstraße 17, 80992 München
Phone: +49 89 14 339-514
mailto:mjais@gmx-gmbh.de
http://www.gmx.de





From trooper@ttnet.net.tr  Mon May 26 11:20:08 2003
From: trooper@ttnet.net.tr (=?iso-8859-9?Q?Tongu=E7?= Yumruk)
Date: Mon, 26 May 2003 13:20:08 +0300
Subject: [XML-SIG] DOM -> String ?
In-Reply-To: <200305261210.52455.mjais@gmx-gmbh.de>
References: <200305261210.52455.mjais@gmx-gmbh.de>
Message-ID: <20030526102007.GA1281@Serafettin.fazlamesai.net>

--k1lZvvs/B4yU6o8G
Content-Type: text/plain; charset=iso-8859-9
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

from xml.dom.ext import Print

Print(document, file_descriptor)

This writes the dom document to that file descriptor. I never tried
socket programming under python but as sockets are simple file
descriptors (at least under Unix) this may work

Mon, May 26, 2003 at 12:10:52PM +0200 Tarihinde Markus Jais Demi=FEki :
> hello
>=20
> is there a way to transform a DOM Tree into a Python string ???
> identation is  not necessary. I just want to send the DOM Tree over
> a socket.
>=20
> Markus
>=20
> --=20
> Markus Jais
> Software Developer
> GMX Aktiengesellschaft
> Riesstra=DFe 17, 80992 M=FCnchen
> Phone: +49 89 14 339-514
> mailto:mjais@gmx-gmbh.de
> http://www.gmx.de
>=20
>=20
>=20
>=20
> _______________________________________________
> XML-SIG maillist  -  XML-SIG@python.org
> http://mail.python.org/mailman/listinfo/xml-sig

--=20
Love Respect Linux
###########################################################################=
#####
	"Has anyone had problems with the computer accounts?"
	"Yes, I don't have one."
	"Okay, you can send mail to one of the tutors ..."
		-- E. D'Azevedo, Computer Science 372
###########################################################################=
#####
Tongu=E7 Yumruk

--k1lZvvs/B4yU6o8G
Content-Type: application/pgp-signature
Content-Disposition: inline

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

iD8DBQE+0epX1xWu4MLSyoYRAlAOAKDvr2UrGukn7RlWuRJ1VszEojpWbwCg4OSp
3FHDlVrFz/D57+xyihmduG8=
=ETtg
-----END PGP SIGNATURE-----

--k1lZvvs/B4yU6o8G--


From markusjais@yahoo.de  Mon May 26 13:01:49 2003
From: markusjais@yahoo.de (=?iso-8859-1?q?Markus=20Jais?=)
Date: Mon, 26 May 2003 14:01:49 +0200 (CEST)
Subject: [XML-SIG] DOM -> String ?
In-Reply-To: <20030526102007.GA1281@Serafettin.fazlamesai.net>
Message-ID: <20030526120149.46630.qmail@web12401.mail.yahoo.com>

thanks
this helps.

but I still need a method to turn it into a string
because I need a string for my programm. And I have to
determine the length of the XML Document.

Markus

 --- Tonguç Yumruk <trooper@ttnet.net.tr> schrieb: >
from xml.dom.ext import Print
> 
> Print(document, file_descriptor)
> 
> This writes the dom document to that file
> descriptor. I never tried
> socket programming under python but as sockets are
> simple file
> descriptors (at least under Unix) this may work
> 
> Mon, May 26, 2003 at 12:10:52PM +0200 Tarihinde
> Markus Jais Demiþki :
> > hello
> > 
> > is there a way to transform a DOM Tree into a
> Python string ???
> > identation is  not necessary. I just want to send
> the DOM Tree over
> > a socket.
> > 
> > Markus
> > 
> > -- 
> > Markus Jais
> > Software Developer
> > GMX Aktiengesellschaft
> > Riesstraße 17, 80992 München
> > Phone: +49 89 14 339-514
> > mailto:mjais@gmx-gmbh.de
> > http://www.gmx.de
> > 
> > 
> > 
> > 
> > _______________________________________________
> > XML-SIG maillist  -  XML-SIG@python.org
> > http://mail.python.org/mailman/listinfo/xml-sig
> 
> -- 
> Love Respect Linux
>
################################################################################
> 	"Has anyone had problems with the computer
> accounts?"
> 	"Yes, I don't have one."
> 	"Okay, you can send mail to one of the tutors ..."
> 		-- E. D'Azevedo, Computer Science 372
>
################################################################################
> Tonguç Yumruk
> 

> ATTACHMENT part 2 application/pgp-signature 
 

__________________________________________________________________

Gesendet von Yahoo! Mail - http://mail.yahoo.de
Logos und Klingeltöne fürs Handy bei http://sms.yahoo.de


From fredrik@pythonware.com  Mon May 26 14:17:38 2003
From: fredrik@pythonware.com (Fredrik Lundh)
Date: Mon, 26 May 2003 15:17:38 +0200
Subject: [XML-SIG] Re: DOM -> String ?
References: <20030526102007.GA1281@Serafettin.fazlamesai.net> <20030526120149.46630.qmail@web12401.mail.yahoo.com>
Message-ID: <bat41q$748$1@main.gmane.org>

Markus Jais wrote:

> but I still need a method to turn it into a string
> because I need a string for my programm. And I have to
> determine the length of the XML Document.

write it to a memory file before writing it to the socket:

http://www.python.org/doc/current/lib/module-StringIO.html

    import StringIO
    fp = StringIO.StringIO()
    Print(document, fp)
    s = fp.getvalue()

</F>





From snowball3@softhome.net  Mon May 26 14:46:14 2003
From: snowball3@softhome.net (Mark E.)
Date: Mon, 26 May 2003 09:46:14 -0400
Subject: [XML-SIG] Handling of character entity references
Message-ID: <3ED1E266.2202.1C3C1E@localhost>

<?xml  version="1.0" ?><html>
<head>
<title></title>
</head>
<body>
<div align="left"><font face="Arial" color="#7f0000"><span style="font-size:9pt">&gt; So essentially what I'm asking is how do I get PyXML to preserve</span></font></div>
<div align="left"><font face="Arial" color="#7f0000"><span style="font-size:9pt">&gt; &quot;&amp;eacute;&quot; as-is and output it in the same manner when I PrettyPrint() it?</span></font></div>
<div align="left"><font face="Arial" color="#7f0000"><span style="font-size:9pt">&gt; (Or, equivalently, convert it to its Unicode representation on input and</span></font></div>
<div align="left"><font face="Arial" color="#7f0000"><span style="font-size:9pt">&gt; back to an entity reference on output.)</span></font></div>
<div align="left"><font face="Arial" color="#7f0000"><span style="font-size:9pt">&gt; </span></font></div>
<div align="left"><br/>
</div>
<div align="left"><font face="Arial"><span style="font-size:9pt">It can be done with the expat parser. Below is an example:</span></font></div>
<div align="left"><br/>
</div>
<div align="left"><font face="Arial"><span style="font-size:9pt">from xml.sax.expatreader import ExpatParser</span></font></div>
<div align="left"><font face="Arial"><span style="font-size:9pt">from xml.sax.handler import ContentHandler, property_lexical_handler, \</span></font></div>
<div align="left"><font face="Arial"><span style="font-size:9pt">&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160; 
feature_external_ges, feature_namespaces</span></font></div>
<div align="left"><br/>
</div>
<div align="left"><font face="Arial"><span style="font-size:9pt">class MyExpatParser(ExpatParser):</span></font></div>
<div align="left"><font face="Arial"><span style="font-size:9pt">&#160;&#160;&#160; def reset(self):</span></font></div>
<div align="left"><font face="Arial"><span style="font-size:9pt">&#160;&#160;&#160;&#160;&#160;&#160;&#160; ExpatParser.reset(self)</span></font></div>
<div align="left"><font face="Arial"><span style="font-size:9pt">&#160;&#160;&#160;&#160;&#160;&#160;&#160; parser = self._parser</span></font></div>
<div align="left"><font face="Arial"><span style="font-size:9pt">&#160;&#160;&#160;&#160;&#160;&#160;&#160; parser.UseForeignDTD(True)</span></font></div>
<div align="left"><br/>
</div>
<div align="left"><br/>
</div>
<div align="left"><font face="Arial"><span style="font-size:9pt">class MyContentHandler(ContentHandler):</span></font></div>
<div align="left"><font face="Arial"><span style="font-size:9pt">&#160;&#160;&#160; &quot;&quot;&quot;Build a tree from the elements, comments, and processing instructions</span></font></div>
<div align="left"><font face="Arial"><span style="font-size:9pt">&#160;&#160;&#160;&#160;&#160;&#160; in an XML formatted document.</span></font></div>
<div align="left"><font face="Arial"><span style="font-size:9pt">&#160;&#160;&#160; &quot;&quot;&quot;</span></font></div>
<div align="left"><font face="Arial"><span style="font-size:9pt">&#160;&#160;&#160; def __init__(self):</span></font></div>
<div align="left"><font face="Arial"><span style="font-size:9pt">&#160;&#160;&#160;&#160;&#160;&#160;&#160; pass</span></font></div>
<div align="left"><br/>
</div>
<div align="left"><font face="Arial"><span style="font-size:9pt">&#160;&#160;&#160; def skippedEntity(self, name):</span></font></div>
<div align="left"><font face="Arial"><span style="font-size:9pt">&#160;&#160;&#160;&#160;&#160;&#160;&#160; &quot;&quot;&quot;Found an undefined entity. Preserve it here.&quot;&quot;&quot;</span></font></div>
<div align="left"><font face="Arial"><span style="font-size:9pt">&#160;&#160;&#160;&#160;&#160;&#160;&#160; print &quot;Skipping entity %s&quot; % name</span></font></div>
<div align="left"><br/>
</div>
<div align="left"><br/>
</div>
<div align="left"><font face="Arial"><span style="font-size:9pt">def create_parser():</span></font></div>
<div align="left"><font face="Arial"><span style="font-size:9pt">&#160;&#160;&#160; parser = MyExpatParser()</span></font></div>
<div align="left"><font face="Arial"><span style="font-size:9pt">&#160;&#160;&#160; ch = MyContentHandler()</span></font></div>
<div align="left"><font face="Arial"><span style="font-size:9pt">&#160;&#160;&#160; parser.setContentHandler(ch)</span></font></div>
<div align="left"><font face="Arial"><span style="font-size:9pt">&#160;&#160;&#160; # Comment next line to cause a traceback with the test code below.</span></font></div>
<div align="left"><font face="Arial"><span style="font-size:9pt">&#160;&#160;&#160; parser.setFeature(feature_external_ges, False)</span></font></div>
<div align="left"><font face="Arial"><span style="font-size:9pt">&#160;&#160;&#160; return parser</span></font></div>
<div align="left"><br/>
</div>
<div align="left"><br/>
</div>
<div align="left"><font face="Arial"><span style="font-size:9pt">def fromString(data):</span></font></div>
<div align="left"><font face="Arial"><span style="font-size:9pt">&#160;&#160;&#160; import cStringIO</span></font></div>
<div align="left"><br/>
</div>
<div align="left"><font face="Arial"><span style="font-size:9pt">&#160;&#160;&#160; parser = create_parser()</span></font></div>
<div align="left"><font face="Arial"><span style="font-size:9pt">&#160;&#160;&#160; f = cStringIO.StringIO(data)</span></font></div>
<div align="left"><font face="Arial"><span style="font-size:9pt">&#160;&#160;&#160; parser.parse(f)</span></font></div>
<div align="left"><font face="Arial"><span style="font-size:9pt">&#160;&#160;&#160; f.close()</span></font></div>
<div align="left"><br/>
</div>
<div align="left"><br/>
</div>
<div align="left"><font face="Arial"><span style="font-size:9pt">if __name__ == &quot;__main__&quot;:</span></font></div>
<div align="left"><font face="Arial"><span style="font-size:9pt">&#160;&#160;&#160; fromString(&quot;&lt;html&gt;&lt;body&gt;some text &amp;eacute; more text &amp;foo;&lt;/body&gt;&lt;/html&gt;&quot;)</span></font></div>
<div align="left"></div>
</body>
</html>


From subscribed@red56.co.uk  Mon May 26 15:24:44 2003
From: subscribed@red56.co.uk (Tim Diggins)
Date: Mon, 26 May 2003 15:24:44 +0100
Subject: [XML-SIG] Handling of character entity references
Message-ID: <000101c32392$8e948000$3202a8c0@timxe3>

It struck me that another way of looking at the reported problem is that =
if
one does want to include a **character sequence** like "&eacute;" (ie =
the
characters and not the entity they represent) in an XML element's =
content
and then to get that back when parsed, well, then the correct solution =
is to
escape the & thus: "&amp;eacute;" within the XML element.=20

What the original correspondent may have misunderstood is that "&amp;" =
is a
representation of a single unicode character, and so is "&eacute;".
"& e a c u t e ;" as a series of 8 unicode characters is represented by
"&amp;eacute;"

On the other hand everyone's commentary on the correct way to "design =
out"
the reported problem are correct - and most likely better solutions than =
the
above.

But considering editing applications (and other cases where one wants to
preserve the characters "& e a c u t e ;") - isn't it easier (better?) =
to
represent the characters (by escaping the magic &) than to use PIs or a
<char> entity?

just my 7.5p worth=20

best

Tim

---------------------------
  Tim Diggins
  mailto:tim@red56.co.uk
  http://www.red56.co.uk/people/tim


> -----Original Message-----
> From: xml-sig-admin@python.org=20
> [mailto:xml-sig-admin@python.org] On Behalf Of Paul Tremblay
> Sent: 26 May 2003 07:12
> To: xml-sig@python.org
> Subject: Re: [XML-SIG] Handling of character entity references
>=20
>=20
> On Sun, May 25, 2003 at 05:42:11PM -0600, Mike Brown wrote:
> > From: Mike Brown <mike@skew.org>
> > Subject: Re: [XML-SIG] Handling of character entity references
> > To: Tamito KAJIYAMA <kajiyama@grad.sccs.chukyo-u.ac.jp>
> > Cc: xml-sig@python.org
> > Date: Sun, 25 May 2003 17:42:11 -0600 (MDT)
> >=20
> > Tamito KAJIYAMA wrote:
> > > "Thomas B. Passin" <tpassin@comcast.net> writes:
> > > |
> > > | [<pyxml@wonderclown.com>]
> > > |=20
> > > | > I am trying to produce XHTML files from input XML=20
> files which contain
> > > | > a mixture of XHTML and custom markup.
> > > | >...
> > > | > I'm
> > > | > having a problem, though, getting character entity=20
> references in the
> > > | > source document to pass through to the output. Things=20
> like &amp;,
> > > | > &lt;, and &gt; work fine, but &eacute; does not.
> > > | >
> > > |=20



From randall@wonderclown.com  Mon May 26 16:14:58 2003
From: randall@wonderclown.com (Randall Nortman)
Date: Mon, 26 May 2003 10:14:58 -0500
Subject: [XML-SIG] Handling of character entity references
In-Reply-To: <001001c322e1$87653a10$6401a8c0@tbp1>
References: <20030525144723.GD14154@aerosol> <001001c322e1$87653a10$6401a8c0@tbp1>
Message-ID: <20030526151457.GE14154@aerosol>

On Sun, May 25, 2003 at 01:17:32PM -0400, Thomas B. Passin wrote:
> [<pyxml@wonderclown.com>]
> 
> > I am trying to produce XHTML files from input XML files which contain
> > a mixture of XHTML and custom markup.
> >...
> > I'm
> > having a problem, though, getting character entity references in the
> > source document to pass through to the output. Things like &amp;,
> > &lt;, and &gt; work fine, but &eacute; does not.
> >
> 
> This sounds like a fine job for XSLT, rather than custom code...
[...]

I have done similar projects using XSLT in the past, since that is
clearly the "right" tool for this job. However, I find XSLT's syntax
to be so abhorrent to good taste as to be nausea-inducing. I think its
processing model is really quite good for most applications, but I
cannot stomach actually reading and writing code in it. I have
considered designing my own syntax based on the same processing model
and a compiler to translate it to XSLT, but I haven't had the time.

So that's why I decided to try Python/PyXml for this project, to see
how it works. I have to say that I like it quite a lot, at least when
combined with the XPath module, which brings in the majority of the
power of XSLT without the nightmarish syntax. (XPath is the most
elegant and useful aspect of XSLT IMO.) Also, having the full power of
a real programming language (notably being able to use complex data
structures outside of the DOM itself) is very handy when doing more
complex work (e.g., automatically building site navigation
menus). Also, Python is faster in my experience.


> 3) If you know the actual output encoding, put a meta element in the head of
> the document that specifies the correct encoding.  You can find out the
> syntax through Google.  This is not really an independent alternative as it
> is good practice anyway.
[...]

I was already specifying the encoding as utf-8 on the output, but I
customized PrintVisitor to remove the <?xml version='1.0'
encoding='utf=8'?> prolog because it was confusing some older
browsers.  So, per your suggestion, I added a <meta> in the <head>
section to specify the character set which seems to work in most
browsers. However, I found that some browsers (notably w3m, a
text-only browser) does not support utf-8 without patches, and so I
switched to iso-8859-1, which seems to work just about anywhere.

Or at least, that works for "&eacute;". "&nbsp;" is still not
working. When I use it in my source, the output just has nothing where
there should be a "&#160;". This is true whether I use iso-8859-1 or
utf-8. Any ideas on that?


> This question comes up a lot.  Look at the various xslt FAQs and try Google
> for more discussion.  Look in the archive of this list, too.
[...]

I hate asking FAQ's on mailing lists, so I'm sorry that I apparently
ended up doing just that. I tried to find the answer via google
without luck, and alas the archives of this list are not searchable
online as far as I could find. I browsed through the subject headings
for the past couple of months but didn't see any discussion. (I
suppose I could have downloaded the 28 MB archive and grep'ed through
it myself.)


> > This brings in the XHTML Latin-1 entities, which seems to work well
> > enough to get the parser to accept the source, but then &eacute; gets
> > translated to the following two-byte sequence on output: 0xC3
> > 0xA9.
> 
> Well, that is interesting because it is the utf-8 encoding of the value E9,
> which is the latin-1 encoding of eacute.  However, the unicode character for
> &eacute; (you can see this in your DTD) is U+00C9, which would be encoded in
> utf-8 as C3 89.  Therefore your code is not decoding and encoding the input
> correctly.  You seem to be taking the sequence of bytes of a latin-1 source
> and encoding it into utf-8 as if the source were really in unicode instead
> of latin-1.
[...]

Are you sure that it should be C3 89 instead of C3 A9? The latter
seems to work, so long as I direct the browser to expect utf-8.

Thanks for your suggestions,

Randall Nortman


From randall@wonderclown.com  Mon May 26 16:20:22 2003
From: randall@wonderclown.com (Randall Nortman)
Date: Mon, 26 May 2003 10:20:22 -0500
Subject: [XML-SIG] Handling of character entity references
In-Reply-To: <000101c32392$8e948000$3202a8c0@timxe3>
References: <000101c32392$8e948000$3202a8c0@timxe3>
Message-ID: <20030526152022.GF14154@aerosol>

On Mon, May 26, 2003 at 03:24:44PM +0100, Tim Diggins wrote:
> It struck me that another way of looking at the reported problem is that if
> one does want to include a **character sequence** like "&eacute;" (ie the
> characters and not the entity they represent) in an XML element's content
> and then to get that back when parsed, well, then the correct solution is to
> escape the & thus: "&amp;eacute;" within the XML element. 
[...]

I had exactly the same thought, but ampersands are correctly replaced
by "&amp;" on output, and so "&amp;eacute;" ends up as just that in
the output, causing the browser to display the literal string
"&eacute;" rather than an e with an acute accent.

Randall Nortman


From randall@wonderclown.com  Mon May 26 16:51:08 2003
From: randall@wonderclown.com (Randall Nortman)
Date: Mon, 26 May 2003 10:51:08 -0500
Subject: [XML-SIG] Handling of character entity references
In-Reply-To: <3ED1E266.2202.1C3C1E@localhost>
References: <3ED1E266.2202.1C3C1E@localhost>
Message-ID: <20030526155107.GG14154@aerosol>

On Mon, May 26, 2003 at 09:46:14AM -0400, Mark E. wrote:
> > So essentially what I'm asking is how do I get PyXML to
> preserve
> > "&eacute;" as-is and output it in the same manner when I
> PrettyPrint() it?
> > (Or, equivalently, convert it to its Unicode representation on
> input and
> > back to an entity reference on output.)
> >
> It can be done with the expat parser. Below is an example:
[...]

This is a good suggestion, but unfortunately my code uses DOM
extensively, and your example is only useful for an application based
on SAX events. xml.dom.ext.reader.PyExpat creates its own parser, so
that's no help. I tried creating a parser as in your example, but for
the content handler I inherited from xml.dom.ext.Sax2.XmlDomGenerator
instead. I then passed my parser as the parser argument to
xml.dom.ext.reader.Sax2.Reader.__init__() and MyContentHandler as the
saxHandlerClass.

Everything parsed fine, but "&eacute;" was translated to nothing (no
character in that spot at all) on output. I suspect the skippedEntity
method needs to actually *do* something other than just print that it
is skipping an entity (which it does, so I know my version is being
used), but I am completely ignorant about how to XmlDomGenerator works
internally, and I've never really written SAX-based parsers anyway.
Can you give me a hint?

Thanks for your help,

Randall Nortman


From snowball3@softhome.net  Mon May 26 18:54:10 2003
From: snowball3@softhome.net (Mark E.)
Date: Mon, 26 May 2003 13:54:10 -0400
Subject: [XML-SIG] Handling of character entity references
In-Reply-To: <20030526155107.GG14154@aerosol>
References: <3ED1E266.2202.1C3C1E@localhost> <20030526155107.GG14154@aerosol>
Message-ID: <3ED254C2.3000008@softhome.net>

Randall Nortman wrote:
> On Mon, May 26, 2003 at 09:46:14AM -0400, Mark E. wrote:

> Everything parsed fine, but "&eacute;" was translated to nothing (no
> character in that spot at all) on output. I suspect the skippedEntity
> method needs to actually *do* something other than just print that it
> is skipping an entity

I'm not familiar with the DOM part of pyxml, but from a quick 
examination of the DOM code, it seems to me like the skippedEntity 
handler should create a "entity reference" object and add it to the 
document.

If you still have difficulties after this hint, you might want to post 
your expat DOM sample code so perhaps someone can point out where you've 
gone wrong.

Mark



From dalke@dalkescientific.com  Mon May 26 19:41:13 2003
From: dalke@dalkescientific.com (Andrew Dalke)
Date: Mon, 26 May 2003 12:41:13 -0600
Subject: [XML-SIG] Re: fixes for PyXML and Python2.3
Message-ID: <A08CF014-8FA9-11D7-A91C-000393C92466@dalkescientific.com>

Andrew Straw:
 > Here's a diff of what I had to do against a CVS checkout of PyXML to
 > get it to build with Python 2.3b1.

Yep - looks like that should fix my problem, though the code has
changed enough in CVS since the release I'm using that I can't
simply test the patch.

					Andrew



From phthenry@earthlink.net  Mon May 26 19:16:51 2003
From: phthenry@earthlink.net (Paul Tremblay)
Date: Mon, 26 May 2003 14:16:51 -0400
Subject: [XML-SIG] using PyXML on a string
In-Reply-To: <3ED1BA0E.8040207@v.loewis.de>; from martin@v.loewis.de on Mon, May 26, 2003 at 08:54:06AM +0200
References: <20030522235356.B1316@supermac600.earthlink.net> <00c701c320ea$e2eced40$6401a8c0@tbp1> <20030526015823.B1006@supermac600.earthlink.net> <3ED1BA0E.8040207@v.loewis.de>
Message-ID: <20030526141651.B3408@supermac600.earthlink.net>

On Mon, May 26, 2003 at 08:54:06AM +0200, "Martin v. Löwis" wrote:
> 
> Hmm. There is no such thing as a "string containing unicode", atleast 
> not if, by "string", you really mean <type 'string'>. You only can pass
> <type 'string'> to cStringIO, not <type 'unicode'>. I usually call 
> objects of <type 'string'> 'byte strings', and objects of <type 
> 'unicode'> 'Unicode strings'. IOW, cStringIO supports only byte strings,
> whereas StringIO supports both byte strings and Unicode strings. In one
> Python release, there was a bug and StringIO rejected Unicode strings. 
> cStringIO has never supported Unicode strings, and never will.
> 

This is from my code:


    file = cStringIO.StringIO(u'<doc>\u00f6data</doc>')   
    parser_obj.parse(file)             

The result is:

<doc>data</doc><doc>ödata</doc>

Am I passing <type 'string'> or <type 'unicode'>?

Paul


--


************************
*Paul Tremblay         *
*phthenry@earthlink.net*
************************


From sp3xcjbjw@net4u.com  Tue May 27 12:38:19 2003
From: sp3xcjbjw@net4u.com (Natasha Sears)
Date: Tue, 27 May 03 11:38:19 GMT
Subject: [XML-SIG] Have more energy hsvaldjdlh jfuka bwy
Message-ID: <63$-mv73$3-8@3ga.b.wqby>

This is a multi-part message in MIME format.

--9A3FA3E..FCBDE
Content-Type: text/html;
Content-Transfer-Encoding: quoted-printable

<A href=3D"http://Python-list@offbeat.healthproductsnow.net/human/index.=
php?id=3D785"><IMG 
alt=3D"" src=3D"http://eyelid@motherhoodimages.healthproductsnow.n=
et/image.php"></A>







fgzg yvl brzdkabwy   eefzfswg bvpmm gcppk

--9A3FA3E..FCBDE--



From randall@wonderclown.com  Mon May 26 20:46:23 2003
From: randall@wonderclown.com (Randall Nortman)
Date: Mon, 26 May 2003 14:46:23 -0500
Subject: [XML-SIG] Handling of character entity references
In-Reply-To: <3ED254C2.3000008@softhome.net>
References: <3ED1E266.2202.1C3C1E@localhost> <20030526155107.GG14154@aerosol> <3ED254C2.3000008@softhome.net>
Message-ID: <20030526194623.GA29588@aerosol>

On Mon, May 26, 2003 at 01:54:10PM -0400, Mark E. wrote:
> Randall Nortman wrote:
> >On Mon, May 26, 2003 at 09:46:14AM -0400, Mark E. wrote:
> 
> >Everything parsed fine, but "&eacute;" was translated to nothing (no
> >character in that spot at all) on output. I suspect the skippedEntity
> >method needs to actually *do* something other than just print that it
> >is skipping an entity
> 
> I'm not familiar with the DOM part of pyxml, but from a quick 
> examination of the DOM code, it seems to me like the skippedEntity 
> handler should create a "entity reference" object and add it to the 
> document.

Well, I dug around until I figured out how XmlDomGenerator works, and
the following code was what was necessary:

    def skippedEntity(self, name):
        """Found an undefined entity. Preserve it here."""
        self._completeTextNode()
        self._nodeStack[-1].appendChild(self._ownerDoc\
                                        .createEntityReference(name))

The rest of the code was essentially as you had provided. Of course,
now it seems to pass ALL entities through unchanged; skippedEntity
seems to be called even if I pull in the XHTML Latin-1 entity set in
my DOCTYPE section. I suspect this is due to the feature_external_ges
and UseForeignDTD magic you performed in your example, which I do not
fully understand. This behavior is OK for now, but what if I actually
want to enable some entities to be parsed and substituted in the
future? I may wish to break my source files into pieces, for example,
and have them reassembled on parse. Will this affect external entities
like that?

Thanks for your help,

Randall Nortman


From martin@v.loewis.de  Mon May 26 21:48:48 2003
From: martin@v.loewis.de (Martin v. =?iso-8859-15?q?L=F6wis?=)
Date: 26 May 2003 22:48:48 +0200
Subject: [XML-SIG] Handling of character entity references
In-Reply-To: <20030526155107.GG14154@aerosol>
References: <3ED1E266.2202.1C3C1E@localhost> <20030526155107.GG14154@aerosol>
Message-ID: <m365nx77tb.fsf@mira.informatik.hu-berlin.de>

Randall Nortman <randall@wonderclown.com> writes:

> Everything parsed fine, but "&eacute;" was translated to nothing (no
> character in that spot at all) on output. I suspect the skippedEntity
> method needs to actually *do* something other than just print that it
> is skipping an entity (which it does, so I know my version is being
> used), but I am completely ignorant about how to XmlDomGenerator works
> internally, and I've never really written SAX-based parsers anyway.
> Can you give me a hint?

You have to create an EntityReference node, to represent an
EntityReference. The document provides .createEntityReference to
create this kind of node.

Regards,
Martin


From martin@v.loewis.de  Mon May 26 21:50:06 2003
From: martin@v.loewis.de (Martin v. =?iso-8859-15?q?L=F6wis?=)
Date: 26 May 2003 22:50:06 +0200
Subject: [XML-SIG] fixes for PyXML and Python2.3
In-Reply-To: <3B47C56D-8F4F-11D7-8B82-00039311EA24@adelaide.edu.au>
References: <3B47C56D-8F4F-11D7-8B82-00039311EA24@adelaide.edu.au>
Message-ID: <m31xyl77r5.fsf@mira.informatik.hu-berlin.de>

Andrew Straw <andrew.straw@adelaide.edu.au> writes:

> Here's a diff of what I had to do against a CVS checkout of PyXML to
> get it to build with Python 2.3b1.  Hopefully someone can check these
> trivial changes into CVS to save other poor souls from tracking down
> little bugs like this.

Please submit patches to sf.net/projects/xml-sig. They often get lost
on the mailing list.

Regards,
Martin



From martin@v.loewis.de  Mon May 26 22:26:50 2003
From: martin@v.loewis.de (=?ISO-8859-1?Q?=22Martin_v=2E_L=F6wis=22?=)
Date: Mon, 26 May 2003 23:26:50 +0200
Subject: [XML-SIG] using PyXML on a string
In-Reply-To: <20030526141651.B3408@supermac600.earthlink.net>
References: <20030522235356.B1316@supermac600.earthlink.net> <00c701c320ea$e2eced40$6401a8c0@tbp1> <20030526015823.B1006@supermac600.earthlink.net> <3ED1BA0E.8040207@v.loewis.de> <20030526141651.B3408@supermac600.earthlink.net>
Message-ID: <3ED2869A.2080902@v.loewis.de>

Paul Tremblay wrote:

> This is from my code:
> 
> 
>     file = cStringIO.StringIO(u'<doc>\u00f6data</doc>')   
>     parser_obj.parse(file)             
> 
> The result is:
> 
> <doc>data</doc><doc>ödata</doc>
> 
> Am I passing <type 'string'> or <type 'unicode'>?

You are passing a Unicode string. However, cStringIO only
supports byte strings, so the system default encoding is
applied to convert the Unicode string to a byte string.

Regards,
Martin



From tpassin@comcast.net  Tue May 27 00:00:52 2003
From: tpassin@comcast.net (Thomas B. Passin)
Date: Mon, 26 May 2003 19:00:52 -0400
Subject: [XML-SIG] Handling of character entity references
References: <20030525144723.GD14154@aerosol>
 <001001c322e1$87653a10$6401a8c0@tbp1> <20030526151457.GE14154@aerosol>
Message-ID: <008c01c323da$a84c6f10$6401a8c0@tbp1>

[Randall Nortman

> I have done similar projects using XSLT in the past, since that is
> clearly the "right" tool for this job. However, I find XSLT's syntax
> to be so abhorrent to good taste as to be nausea-inducing.

Strangely enough, I have come to be very fond of xslt, and I am fine with
its syntax.  This has come as a surprise to me.

> I was already specifying the encoding as utf-8 on the output, but I
> customized PrintVisitor to remove the <?xml version='1.0'
> encoding='utf=8'?> prolog because it was confusing some older
> browsers.

Yes, HTML does not know about the xml declaration.

> So, per your suggestion, I added a <meta> in the <head>
> section to specify the character set which seems to work in most
> browsers. However, I found that some browsers (notably w3m, a
> text-only browser) does not support utf-8 without patches, and so I
> switched to iso-8859-1, which seems to work just about anywhere.
>

Pretty safe most of the time.

> Or at least, that works for "&eacute;". "&nbsp;" is still not
> working. When I use it in my source, the output just has nothing where
> there should be a "&#160;". This is true whether I use iso-8859-1 or
> utf-8. Any ideas on that?
>

No, except to just use & # 160 ;
>
> > This question comes up a lot.  Look at the various xslt FAQs and try
Google
> > for more discussion.  Look in the archive of this list, too.
> [...]
>
> I hate asking FAQ's on mailing lists, so I'm sorry that I apparently
> ended up doing just that.

Sorry, I meant to say the Mulberry xslt list, and maybe xml-dev as well.

> >
> > Well, that is interesting because it is the utf-8 encoding of the value
E9,
> > which is the latin-1 encoding of eacute.  However, the unicode character
for
> > &eacute; (you can see this in your DTD) is U+00C9, which would be
encoded in
> > utf-8 as C3 89.  Therefore your code is not decoding and encoding the
input
> > correctly.  You seem to be taking the sequence of bytes of a latin-1
source
> > and encoding it into utf-8 as if the source were really in unicode
instead
> > of latin-1.
> [...]
>
> Are you sure that it should be C3 89 instead of C3 A9? The latter
> seems to work, so long as I direct the browser to expect utf-8.
>

I misunderstood the legend of one column on the reference table I was
looking at, and ended up thinking the code point was something else,
although actually it is the same as the Latin-1 encoding value, which is E9
byte after all.  It took me some time testing and looking for better
character charts before I got my head squared away.  Sorry about that.

Cheers,

Tom P




From logologics@wanadoo.nl  Thu May 29 13:37:38 2003
From: logologics@wanadoo.nl (Alexander Kaiser)
Date: Thu, 29 May 2003 13:37:38 +0100
Subject: [XML-SIG] newby installation problems
Message-ID: <200305291336.48359.logologics@wanadoo.nl>

=2D----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

I have spent quite some time on this, but can't figure it out,
probably because i am a Python newby.=20

When I tried to install pyxml 8.2 on python 2.1 (Suse Linux),
I got the mesagge

	ImportError: No module named xml.sax

when running tests from the test directory after a seemingly=20
smooth installation (python setup.py install). In fact none of
the packages from pyxml could be imported. I then upgraded my=20
pyhton to 2.2, hoping things would improve.

The installation still seems to work fine, but the error message remains=20
the same. Can anyone tell me, why? All installed packages seem to
live in site_packages/_xmlplus, but obviously cannot be found by python.

There is a lot of confusing stuff on the PYTHONPATH on the web, but=20
to a newby all this remains very cryptic!

Alex
=2D----BEGIN PGP SIGNATURE-----
Version: PGP 6.5.8

iQA/AwUBPtX/E2TTbRxyplwoEQKKFwCeNVr+Iczhw9BTJ8x7VR5XsmeZ8pQAnitt
COoJZhb1XPorrjuQtaTDGGJE
=3DmuX9
=2D----END PGP SIGNATURE-----



From snowball3@softhome.net  Tue May 27 00:08:12 2003
From: snowball3@softhome.net (Mark E.)
Date: Mon, 26 May 2003 19:08:12 -0400
Subject: [XML-SIG] Handling of character entity references
In-Reply-To: <20030526194623.GA29588@aerosol>
References: <3ED1E266.2202.1C3C1E@localhost> <20030526155107.GG14154@aerosol> <3ED254C2.3000008@softhome.net> <20030526194623.GA29588@aerosol>
Message-ID: <3ED29E5C.6020805@softhome.net>

Randall Nortman wrote:

> On Mon, May 26, 2003 at 01:54:10PM -0400, Mark E. wrote:
> 
>>Randall Nortman wrote:
>>
>>>On Mon, May 26, 2003 at 09:46:14AM -0400, Mark E. wrote:
>>
>>>Everything parsed fine, but "&eacute;" was translated to nothing (no
>>>character in that spot at all) on output. I suspect the skippedEntity
>>>method needs to actually *do* something other than just print that it
>>>is skipping an entity
>>
>>I'm not familiar with the DOM part of pyxml, but from a quick 
>>examination of the DOM code, it seems to me like the skippedEntity 
>>handler should create a "entity reference" object and add it to the 
>>document.
> 
> 
> Well, I dug around until I figured out how XmlDomGenerator works, and
> the following code was what was necessary:
> 
>     def skippedEntity(self, name):
>         """Found an undefined entity. Preserve it here."""
>         self._completeTextNode()
>         self._nodeStack[-1].appendChild(self._ownerDoc\
>                                         .createEntityReference(name))
> 
> The rest of the code was essentially as you had provided. Of course,
> my DOCTYPE section. I suspect this is due to the feature_external_ges
> and UseForeignDTD magic you performed in your example, which I do not
> fully understand.

UseForeignDTD is documented xml-ref.txt. feature_external_ges is 
document in the Python docs (including 
http://www.python.org/doc/current/lib/module-xml.sax.handler.html).

 >This behavior is OK for now, but what if I actually
> want to enable some entities to be parsed and substituted in the
> future?

The problem is that PyXML and UseForeignDTD(true) are currently 
incompatible unless feature_external_ges is turned off. You can 
experience the problem firsthand by commenting out the line in my 
original sample that turns off feature_external_ges.

Mark




From mike@skew.org  Tue May 27 05:16:16 2003
From: mike@skew.org (Mike Brown)
Date: Mon, 26 May 2003 22:16:16 -0600
Subject: [XML-SIG] Handling of character entity references
In-Reply-To: <200305260750.h4Q7oOX05758@grad.sccs.chukyo-u.ac.jp>
References: <200305252342.h4PNgBaJ010381@chilled.skew.org> <200305260750.h4Q7oOX05758@grad.sccs.chukyo-u.ac.jp>
Message-ID: <3ED2E690.4060003@skew.org>

Tamito KAJIYAMA wrote:

>Mike Brown <mike@skew.org> writes:
>|
>| > I've used a SAX-based Python script for years to convert a set
>| > of XML files into an HTML file.  The file encodings of the input
>| > and output files are EUC-JP and ISO-2022-JP, respectively.
>| > I also had a need to use Latin-1 characters in the input and
>| > output files.  However, because of the Japanese file encodings,
>| > raw character codes (say, 0xe9 in ISO-8859-1 for &eacute;) were
>| > not acceptable.  Therefore, I needed a way to represent Latin-1
>| > characters in the input XML files and to produce character
>| > references in the output HTML file.
>|=20
>| This wouldn't be needed today, since python is now Unicode friendly. Y=
ou have
>| Unicode strings being passed to your SAX methods, and on the output si=
de, the
>| EUC-JP or ISO-2022-JP codec used by the XML serializer will convert to=
 bytes
>| all the characters supported by those encodings. The non-ASCII range o=
f
>| ISO-8859-1 (\u00A0-\u00FF) would not be handled by the codecs, but the=
 XML
>| serializer will simply deal with that by emitting numeric character re=
ferences
>| automatically.
>|=20
>| > So, I decided to use a special markup to represent Latin-1
>| > characters in the input XML files, as illustrated below:
>| >=20
>| > <char name=3D"eacute" />
>
>Thank you for the tip, but I was not able to figure out how to
>realize what you suggested.  To the best of my knowledge, the
>method ContentHandler.characters() determines how characters are
>to be handled on the output side.  So, encoding-related things
>won't be _automatically_ done.  I've missed something important?
>
>Thanks,
>
> =20
>
You said you're using SAX to produce HTML from XML, so I assume the XML=20
parser is calling the event handler methods in your ContentHandler. When=20
ContentHandler.characters() is called by the parser to notify your=20
application about character data, a Unicode string is passed as the=20
content argument (as long as expat is your underlying parser). This is=20
probably not how it worked when your application was originally written,=20
prior to the omnipresence of Unicode in Python.

Whatever mechanism you are using to produce HTML (I'm not going to guess=20
how you're doing that) will be running the Unicode string through an=20
encoder, perhaps just using the built-in encode() method on the Unicode=20
string object, to produce EUC-JP or ISO-2022-JP byte strings for output.

Of course this isn't automatic, but my point is that (hopefully) your=20
HTML-producing SAX application will be written (by you) such that it=20
does do the encoding (at the last step before output, preferably), and=20
will be smart enough (because you wrote it that way) to write character=20
references when the codec doesn't handle a particular Unicode character.=20
Someone (on this list, I think) once suggested this approach:

''.join([c.encode('ascii', 'ignore') or "&#%d;" % ord(c) for c in u'\u831=
4=E4=F6=FC=DF?abc'])

...although you could use some of the character data translation=20
functions in PyXML's xml.dom.html or xml.dom.ext.Printer modules. I'm=20
stepping beyond my own personal experience in this matter, though. :)



From kajiyama@grad.sccs.chukyo-u.ac.jp  Tue May 27 09:52:39 2003
From: kajiyama@grad.sccs.chukyo-u.ac.jp (Tamito KAJIYAMA)
Date: Tue, 27 May 2003 17:52:39 +0900
Subject: [XML-SIG] Handling of character entity references
In-Reply-To: <3ED2E690.4060003@skew.org> (message from Mike Brown on Mon, 26
 May 2003 22:16:16 -0600)
References: <BAF84430.23691%hayakawa@sam.hi-ho.ne.jp>
Message-ID: <200305270852.h4R8qdI08939@grad.sccs.chukyo-u.ac.jp>

Mike Brown <mike@skew.org> writes:
|
| You said you're using SAX to produce HTML from XML, so I assume the XML 
| parser is calling the event handler methods in your ContentHandler. When 
| ContentHandler.characters() is called by the parser to notify your 
| application about character data, a Unicode string is passed as the 
| content argument (as long as expat is your underlying parser). This is 
| probably not how it worked when your application was originally written, 
| prior to the omnipresence of Unicode in Python.
| 
| Whatever mechanism you are using to produce HTML (I'm not going to guess 
| how you're doing that) will be running the Unicode string through an 
| encoder, perhaps just using the built-in encode() method on the Unicode 
| string object, to produce EUC-JP or ISO-2022-JP byte strings for output.
| 
| Of course this isn't automatic, but my point is that (hopefully) your 
| HTML-producing SAX application will be written (by you) such that it 
| does do the encoding (at the last step before output, preferably), and 
| will be smart enough (because you wrote it that way) to write character 
| references when the codec doesn't handle a particular Unicode character. 

Hmm, I've still missed the point.  Do you mean that there is a
codec with an error handling scheme that translates undefined
characters into appropriate character references?  The SAX
application of mine does not have (of course) such a mechanism
that would "write character references when the codec doesn't
handle a particular Unicode character," since it does not rely
on Unicode support at all.

Let me make the discussion a bit more concrete.  The following
script effectively reproduces the problem that I encountered.
(I rewrote the same conversion logic in SAX2.)

--------------------------------------------------------------
import StringIO, string

from xml.sax import saxutils, sax2exts

class MyHandler(saxutils.DefaultHandler):
    def characters(self, content):
        if string.strip(content):
            print "DEBUG:", repr(content)
            print content

DOC = """\
<?xml version="1.0" encoding="EUC-JP" ?>
<!DOCTYPE doc [
<!ENTITY eacute "&#233;">
]>
<doc>
<p>Isto &eacute; uma caneta.</p>
<p>\244\263\244\354\244\317\245\332\245\363\244\307\244\271\241\243</p>
</doc>
"""

parser = sax2exts.make_parser(["xml.sax.drivers2.drv_xmlproc"])
parser.setContentHandler(MyHandler())
parser.parse(StringIO.StringIO(DOC))
--------------------------------------------------------------

In Python 1.5.2, the method ContentHandler.characters() ends up
receiving byte strings in both EUC-JP and Latin-1 encodings.
That's why I had to reinvent the wheel (namely, the "char" tag).
On the other hand, in Python 2.x, the script will raise an error
like this:

UnicodeEncodeError: 'ascii' codec can't encode character '\ue9' in position 0: ordinal not in range(128)

AFAIK, the standard "ascii" codec does not have such a nifty
feature that would automatically translate unknown characters
into appropriate character references.  So, I can't see what you
meant in the last paragraph quoted above.  Could you please
elaborate your assumption in the last paragraph?  (What I'm
afraid is that I might miss something new and important in
recent versions of Python and PyXML.)

Thanks,

-- 
KAJIYAMA, Tamito <kajiyama@grad.sccs.chukyo-u.ac.jp>


From mike@skew.org  Tue May 27 10:40:00 2003
From: mike@skew.org (Mike Brown)
Date: Tue, 27 May 2003 03:40:00 -0600
Subject: [XML-SIG] Handling of character entity references
In-Reply-To: <200305270852.h4R8qdI08939@grad.sccs.chukyo-u.ac.jp>
References: <BAF84430.23691%hayakawa@sam.hi-ho.ne.jp> <200305270852.h4R8qdI08939@grad.sccs.chukyo-u.ac.jp>
Message-ID: <3ED33270.7090906@skew.org>

Tamito KAJIYAMA wrote:

>Mike Brown <mike@skew.org> writes:
>|
>| You said you're using SAX to produce HTML from XML, so I assume the XML 
>| parser is calling the event handler methods in your ContentHandler. When 
>| ContentHandler.characters() is called by the parser to notify your 
>| application about character data, a Unicode string is passed as the 
>| content argument (as long as expat is your underlying parser). This is 
>| probably not how it worked when your application was originally written, 
>| prior to the omnipresence of Unicode in Python.
>| 
>| Whatever mechanism you are using to produce HTML (I'm not going to guess 
>| how you're doing that) will be running the Unicode string through an 
>| encoder, perhaps just using the built-in encode() method on the Unicode 
>| string object, to produce EUC-JP or ISO-2022-JP byte strings for output.
>| 
>| Of course this isn't automatic, but my point is that (hopefully) your 
>| HTML-producing SAX application will be written (by you) such that it 
>| does do the encoding (at the last step before output, preferably), and 
>| will be smart enough (because you wrote it that way) to write character 
>| references when the codec doesn't handle a particular Unicode character. 
>
>Hmm, I've still missed the point.  Do you mean that there is a
>codec with an error handling scheme that translates undefined
>characters into appropriate character references?
>

No.

>  The SAX
>application of mine does not have (of course) such a mechanism
>that would "write character references when the codec doesn't
>handle a particular Unicode character," since it does not rely
>on Unicode support at all.
>  
>
And that's a problem now, as your script below demonstrates

>Let me make the discussion a bit more concrete.  The following
>script effectively reproduces the problem that I encountered.
>(I rewrote the same conversion logic in SAX2.)
>
>--------------------------------------------------------------
>import StringIO, string
>
>from xml.sax import saxutils, sax2exts
>
>class MyHandler(saxutils.DefaultHandler):
>    def characters(self, content):
>        if string.strip(content):
>            print "DEBUG:", repr(content)
>            print content
>
>DOC = """\
><?xml version="1.0" encoding="EUC-JP" ?>
><!DOCTYPE doc [
><!ENTITY eacute "&#233;">
>]>
><doc>
><p>Isto &eacute; uma caneta.</p>
><p>\244\263\244\354\244\317\245\332\245\363\244\307\244\271\241\243</p>
></doc>
>"""
>
>parser = sax2exts.make_parser(["xml.sax.drivers2.drv_xmlproc"])
>parser.setContentHandler(MyHandler())
>parser.parse(StringIO.StringIO(DOC))
>--------------------------------------------------------------
>
>In Python 1.5.2, the method ContentHandler.characters() ends up
>receiving byte strings in both EUC-JP and Latin-1 encodings.
>That's why I had to reinvent the wheel (namely, the "char" tag).
>  
>
Right.

>On the other hand, in Python 2.x, the script will raise an error
>like this:
>
>UnicodeEncodeError: 'ascii' codec can't encode character '\ue9' in position 0: ordinal not in range(128)
>
>AFAIK, the standard "ascii" codec does not have such a nifty
>feature that would automatically translate unknown characters
>into appropriate character references.  So, I can't see what you
>meant in the last paragraph quoted above.  Could you please
>elaborate your assumption in the last paragraph?  (What I'm
>afraid is that I might miss something new and important in
>recent versions of Python and PyXML.)
>  
>
I am trying to say that your application does not have to rely on your 
'char' tag hack under Python 2.x because you are now *able* to write it 
in such a way that it doesn't do something foolish like "print content" 
when content is a Unicode string and sys.stdout is an ASCII console. :)

For example, if you change that print to

print ''.join([c.encode('ascii', 'ignore') or "&#%d;" % ord(c) for c in 
content])

then you will at least be able to see it on your terminal, serialized 
with all non-ASCII characters represented by NCRs.

If you were writing to a file rather than sys.stdout, you would want to 
change the 'ascii' in the line to 'EUC-JP' or whatever.



From kajiyama@grad.sccs.chukyo-u.ac.jp  Tue May 27 11:50:27 2003
From: kajiyama@grad.sccs.chukyo-u.ac.jp (Tamito KAJIYAMA)
Date: Tue, 27 May 2003 19:50:27 +0900
Subject: [XML-SIG] Handling of character entity references
In-Reply-To: <3ED33270.7090906@skew.org> (message from Mike Brown on Tue, 27
 May 2003 03:40:00 -0600)
References: <3ED33270.7090906@skew.org>
Message-ID: <200305271050.h4RAoRk09118@grad.sccs.chukyo-u.ac.jp>

Mike Brown <mike@skew.org> writes:
|
| I am trying to say that your application does not have to rely on your 
| 'char' tag hack under Python 2.x because you are now *able* to write it 
| in such a way that it doesn't do something foolish like "print content" 
| when content is a Unicode string and sys.stdout is an ASCII console. :)

I see.  Thank you for the elaboration.

| For example, if you change that print to
| 
| print ''.join([c.encode('ascii', 'ignore') or "&#%d;" % ord(c) for c in 
| content])
| 
| then you will at least be able to see it on your terminal, serialized 
| with all non-ASCII characters represented by NCRs.

Cool.

| If you were writing to a file rather than sys.stdout, you would want to 
| change the 'ascii' in the line to 'EUC-JP' or whatever.

FYI: In Japan, a terminal emulator called kterm is widely used
on X Window System.  The terminal emulator is fully capable of
EUC-JP as well as Shift_JIS and ISO-2022-JP, so that I'm able to
directly write Japanese byte strings to sys.stdout within Python
scripts and our lovely interactive Python interpreter ;-)

Best regards,

-- 
KAJIYAMA, Tamito <kajiyama@grad.sccs.chukyo-u.ac.jp>


From martin@v.loewis.de  Tue May 27 12:42:19 2003
From: martin@v.loewis.de (Martin v. =?iso-8859-15?q?L=F6wis?=)
Date: 27 May 2003 13:42:19 +0200
Subject: [XML-SIG] newby installation problems
In-Reply-To: <200305291336.48359.logologics@wanadoo.nl>
References: <200305291336.48359.logologics@wanadoo.nl>
Message-ID: <m3y90s8vl0.fsf@mira.informatik.hu-berlin.de>

Alexander Kaiser <logologics@wanadoo.nl> writes:

> The installation still seems to work fine, but the error message remains 
> the same. Can anyone tell me, why? 

You will have to provide more details. What is the specific command
that you have invoked to produce the error message

   ImportError: No module named xml.sax

In that command, what is the precise path to the Python interpreter?

For that Python interpreter, what is the contents of the site-packages
directory?

When you invoked 'python setup.py install', which Python interpreter
did you use?

Do you have any environment variables set that start with PYTHON?

Regards,
Martin


From grobinson@transpose.com  Tue May 27 13:23:59 2003
From: grobinson@transpose.com (Gary Robinson)
Date: Tue, 27 May 2003 08:23:59 -0400
Subject: [XML-SIG] pyxml wants Internet connection?
Message-ID: <BAF8D11F.2566B%grobinson@transpose.com>

I'm trying to use Python to read an Apple property list XML file that
contains:

<!DOCTYPE plist PUBLIC "-//Apple Computer//DTD PLIST 1.0//EN"
"http://www.apple.com/DTDs/PropertyList-1.0.dtd">

It appears to be the case Python's XML parsing libraries connect to the
Internet in order to read the DTD. If my computer is not connected to the
Internet, an exception is raised and the XML isn't parsed.

Is there something I can do to tell Python not to check the DTD?

--Gary

-- 
<http://ThisURLEnablesEmailToGetThroughOverzealousSpamFilters.org>

Gary Robinson
CEO
Transpose, LLC
grobinson@transpose.com
207-942-3463
http://www.transpose.com
http://radio.weblogs.com/0101454




From martin@v.loewis.de  Tue May 27 13:39:25 2003
From: martin@v.loewis.de (=?ISO-8859-1?Q?=22Martin_v=2E_L=F6wis=22?=)
Date: Tue, 27 May 2003 14:39:25 +0200
Subject: [XML-SIG] pyxml wants Internet connection?
In-Reply-To: <BAF8D11F.2566B%grobinson@transpose.com>
References: <BAF8D11F.2566B%grobinson@transpose.com>
Message-ID: <3ED35C7D.6030208@v.loewis.de>

Gary Robinson wrote:

> Is there something I can do to tell Python not to check the DTD?

Yes.

What exactly this is depends on what kind of parsing
technology you use.

Regards,
Martin



From grobinson@transpose.com  Tue May 27 13:42:27 2003
From: grobinson@transpose.com (Gary Robinson)
Date: Tue, 27 May 2003 08:42:27 -0400
Subject: [XML-SIG] pyxml wants Internet connection?
In-Reply-To: <3ED35C7D.6030208@v.loewis.de>
Message-ID: <BAF8D573.25677%grobinson@transpose.com>

Thanks -- I'm using xml.sax's make_parser to make a parser, and I'm doing m=
y
parsing with that. I have pyXML installed. This is on OS X.

--Gary

--=20
<http://ThisURLEnablesEmailToGetThroughOverzealousSpamFilters.org>

Gary Robinson
CEO
Transpose, LLC
grobinson@transpose.com
207-942-3463
http://www.transpose.com
http://radio.weblogs.com/0101454


> From: "Martin v. L=F6wis" <martin@v.loewis.de>
> Date: Tue, 27 May 2003 14:39:25 +0200
> To: Gary Robinson <grobinson@transpose.com>
> Cc: "xml-sig@python.org" <xml-sig@python.org>
> Subject: Re: [XML-SIG] pyxml wants Internet connection?
>=20
> Gary Robinson wrote:
>=20
>> Is there something I can do to tell Python not to check the DTD?
>=20
> Yes.
>=20
> What exactly this is depends on what kind of parsing
> technology you use.
>=20
> Regards,
> Martin
>=20



From martin@v.loewis.de  Tue May 27 13:51:08 2003
From: martin@v.loewis.de (=?ISO-8859-1?Q?=22Martin_v=2E_L=F6wis=22?=)
Date: Tue, 27 May 2003 14:51:08 +0200
Subject: [XML-SIG] pyxml wants Internet connection?
In-Reply-To: <BAF8D573.25677%grobinson@transpose.com>
References: <BAF8D573.25677%grobinson@transpose.com>
Message-ID: <3ED35F3C.7060709@v.loewis.de>

Gary Robinson wrote:

> Thanks -- I'm using xml.sax's make_parser to make a parser, and I'm doing my
> parsing with that. I have pyXML installed. This is on OS X.

I see. After invoking the parser's reset, and before invoking feed, you 
need to invoke
 
parser._parser.SetParamEntityParsing(xml.parsers.expat.XML_PARAM_ENTITY_PARSING_NEVER)

Regards,
Martin




From walter@livinglogic.de  Tue May 27 14:25:23 2003
From: walter@livinglogic.de (=?ISO-8859-1?Q?Walter_D=F6rwald?=)
Date: Tue, 27 May 2003 15:25:23 +0200
Subject: [XML-SIG] Handling of character entity references
In-Reply-To: <200305270852.h4R8qdI08939@grad.sccs.chukyo-u.ac.jp>
References: <BAF84430.23691%hayakawa@sam.hi-ho.ne.jp> <200305270852.h4R8qdI08939@grad.sccs.chukyo-u.ac.jp>
Message-ID: <3ED36743.1090104@livinglogic.de>

Tamito KAJIYAMA wrote:

> [...]
> 
> In Python 1.5.2, the method ContentHandler.characters() ends up
> receiving byte strings in both EUC-JP and Latin-1 encodings.
> That's why I had to reinvent the wheel (namely, the "char" tag).
> On the other hand, in Python 2.x, the script will raise an error
> like this:
> 
> UnicodeEncodeError: 'ascii' codec can't encode character '\ue9' in position 0: ordinal not in range(128)
> 
> AFAIK, the standard "ascii" codec does not have such a nifty
> feature that would automatically translate unknown characters
> into appropriate character references.

The "ascii" codec doesn't, but Python 2.3 (which you seem to be
using) will introduce codec error callbacks (see PEP 293),
so Mikes example:

     ''.join([c.encode('ascii', 'ignore') or "&#%d;" % ord(c) \
                 for c in u'\u8314äöüß?abc'])

could be shortened to:

     u'\u8314äöüß?abc'.encode('ascii', 'xmlcharrefreplace')

with Python 2.3.

> So, I can't see what you
> meant in the last paragraph quoted above.  Could you please
> elaborate your assumption in the last paragraph?  (What I'm
> afraid is that I might miss something new and important in
> recent versions of Python and PyXML.)

You might want to read the PEP at:
    http://www.python.org/peps/pep-0293.html
and maybe the test script:
http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/python/python/dist/src/Lib/test/test_codeccallbacks.py

Bye,
    Walter Dörwald




From k75930@ky.hkkk.fi  Tue May 27 14:44:35 2003
From: k75930@ky.hkkk.fi (Kai Hendry)
Date: Tue, 27 May 2003 16:44:35 +0300
Subject: [XML-SIG] xml.dom.minidom unwanted escaping
Message-ID: <20030527134435.GG1047@cs.helsinki.fi>

This is a MIME-formatted message.  If you see this text it means that your
E-mail software does not support MIME-formatted messages.

--=_courier-11959-1054043106-0001-2
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

I have a little code sample attached.

I do not want:
$ ./domtest.py
<?xml version="1.0" ?>
<test>
        <keywords>
                foo &amp; bar
        </keywords>
        <title>
                &quot;work&quot;
        </title>
</test>

I want: 
$ ./domtest.py
<?xml version="1.0" ?>
<test>
        <keywords>
                foo &amp; bar
        </keywords>
        <title>
                "work"
        </title>
</test>

Any ideas folks?

The joys of XML. :)

Kind regards,
-Kai Hendry

--=_courier-11959-1054043106-0001-2
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment; filename="domtest.py"

#!/usr/bin/env python2
import re
import xml.dom.minidom
import os
import string

def create(dict, file_object):
	newdoc = xml.dom.minidom.Document()
	testdoc = newdoc.createElement("test") 

	newdoc.appendChild(testdoc) 

	for key, value in dict.items():
		key = newdoc.createElement("%s" % string.lower(key)) 
		key.appendChild(newdoc.createTextNode(value))
		testdoc.appendChild(key)

	newdoc.writexml(file_object)
	return newdoc.toprettyxml()


if __name__ == "__main__":
	
	dict = {'title': '"work"', 'keywords': 'foo & bar'}

	os.umask(022)
	file = open('/tmp/test.xml', 'w')
	
	print create(dict, file)
	
	file.flush()
	file.close()



--=_courier-11959-1054043106-0001-2--


From martin@v.loewis.de  Tue May 27 15:25:26 2003
From: martin@v.loewis.de (=?ISO-8859-1?Q?=22Martin_v=2E_L=F6wis=22?=)
Date: Tue, 27 May 2003 16:25:26 +0200
Subject: [XML-SIG] xml.dom.minidom unwanted escaping
In-Reply-To: <20030527134435.GG1047@cs.helsinki.fi>
References: <20030527134435.GG1047@cs.helsinki.fi>
Message-ID: <3ED37556.5090006@v.loewis.de>

Kai Hendry wrote:

> I have a little code sample attached.
[...]
> I do not want:
[...]
> I want: 
[...]

It might be easiest if you adjust your wishes. The resulting XML is 
well-formed, and contains the contents you want it to contain.

If that is not acceptable, you cannot use toxml; it just supports a 
single way of printing. You can:

a) try one of the PyXML printers, i.e. xml.dom.ext.[Pretty]Print
b) write your own printer

Regards,
Martin




From uche.ogbuji at fourthought.com  Wed May 28 21:33:04 2003
From: uche.ogbuji at fourthought.com (Uche Ogbuji)
Date: Wed May 28 16:33:05 2003
Subject: [XML-SIG] Re: [Support] Problem with Sgmlop.py
In-Reply-To: <vgznl6ooca.fsf@dfki.uni-sb.de>
References: <vgznl6ooca.fsf@dfki.uni-sb.de>
Message-ID: <1054132300.29101.0.camel@localhost.localdomain>

On Wed, 2003-05-28 at 13:36, Alastair Burt wrote:
> In order to print HTML code using the PyXML pretty printer, the comments in
> the DOM tree must be Unicode. I therefore needed the following patch to my
> version of the Sgmlop.py:
> 
> *** Sgmlop.py	2003/05/28 19:30:36	1.2
> --- Sgmlop.py	2003/05/28 19:08:18	1.1
> ***************
> *** 230,237 ****
>           return
> 
>       def handle_comment(self, data):
> !         unidata = unicode(data, self._charset)
> !         comment = self._ownerDoc.createComment(unidata)
>           self._stack[-1].appendChild(comment)
>           return
> 
> --- 230,236 ----
>           return
> 
>       def handle_comment(self, data):
> !         comment = self._ownerDoc.createComment(data)
>           self._stack[-1].appendChild(comment)
>           return

Thanks, but this is a matter for the XML SIG, which I've copied
accordingly.


-- 
Uche Ogbuji                                    Fourthought, Inc.
http://uche.ogbuji.net    http://4Suite.org    http://fourthought.com
Using libxml in Python - http://www.xml.com/pub/a/2003/05/14/py-xml.html
Charming Jython - http://www-106.ibm.com/developerworks/java/library/j-jython.html
The commons of creativity - http://www-106.ibm.com/developerworks/xml/library/x-think18.html
Is XQuery an omni-tool? - http://www.adtmag.com/article.asp?id=7620


From fredrik at pythonware.com  Thu May 29 14:34:41 2003
From: fredrik at pythonware.com (Fredrik Lundh)
Date: Thu May 29 07:35:00 2003
Subject: [XML-SIG] ANN: ElementTree 1.2 alpha 1
Message-ID: <bb4r4p$8sg$1@main.gmane.org>

The Element type is a simple but flexible container object, designed
to store hierarchical data structures, such as simplified XML infosets,
in memory.  The ElementTree package provides a Python implementation
of this type, plus code to serialize element trees to and from XML files.

The 1.2 alpha 1 release adds limited XPath support to the find/findtext
and findall methods.

You can get the ElementTree toolkit from:

    http://effbot.org/downloads

Brief documentation and some code samples (including an
XML-RPC unmarshaller in 16 lines) are available from:

    http://effbot.org/zone/element-index.htm

For information on the XPath subset supported by Element-
Tree 1.2, see:

    http://effbot.org/zone/element-xpath.htm

For more background on ElementTrees, see Uche Ogbuji's
xml.com article:

    "Simple XML Processing With elementtree"
    http://www.xml.com/pub/a/2003/02/12/py-xml.html

Report bugs to this list, and/or (preferred) directly to me.

enjoy /F