LISTSERV mailing list manager LISTSERV 16.5

Help for CODE4LIB Archives


CODE4LIB Archives

CODE4LIB Archives


CODE4LIB@LISTS.CLIR.ORG


View:

Message:

[

First

|

Previous

|

Next

|

Last

]

By Topic:

[

First

|

Previous

|

Next

|

Last

]

By Author:

[

First

|

Previous

|

Next

|

Last

]

Font:

Monospaced Font

LISTSERV Archives

LISTSERV Archives

CODE4LIB Home

CODE4LIB Home

CODE4LIB  March 2013

CODE4LIB March 2013

Subject:

Re: XML Parsing and Python

From:

Al Matthews <[log in to unmask]>

Reply-To:

Code for Libraries <[log in to unmask]>

Date:

Thu, 7 Mar 2013 11:53:28 -0500

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (179 lines)

Hello Mike,

I realize minidom is a pure python library, but I wonder if elementtree
isn't "preferred" here since you're already using lxml?

I think the latter must be based on the former.

Or for a bit of a snark, try, e.g.
http://blog.ianbicking.org/2008/03/30/python-html-parser-performance/ ..
Bicking: "I don't recommend using minidom for anything."


--
Al Matthews

Software Developer, Digital Services Unit
Atlanta University Center, Robert W. Woodruff Library
email: [log in to unmask]; office: 1 404 978 2057





On 3/7/13 10:49 AM, "Michael Beccaria" <[log in to unmask]> wrote:

>I ended up doing a regular expression find and replace function to
>replace all illegal xml characters with a dash or something. I was more
>disappointed in the fact that on the xml creation end, minidom was able
>to create non-compliant xml files. I assumed that if minidom could make
>it, it would be compliant but that doesn't seem to be the case. Now I
>have to add a find and replace function on the creation side to avoid
>this issue in the future. Good learning experience I guess. Thanks for
>all your suggestions.
>
>Mike Beccaria
>Systems Librarian
>Head of Digital Initiative
>Paul Smith's College
>518.327.6376
>[log in to unmask]
>Become a friend of Paul Smith's Library on Facebook today!
>
>
>-----Original Message-----
>From: Code for Libraries [mailto:[log in to unmask]] On Behalf Of
>Chris Beer
>Sent: Tuesday, March 05, 2013 1:48 PM
>To: [log in to unmask]
>Subject: Re: [CODE4LIB] XML Parsing and Python
>
>I'll note that 0xFFFF is a UTF-8 non-character, and " these noncharacters
>should never be included in text interchange between implementations."
>[1] I assume the OCR engine maybe using 0xFFFF when it can't recognize a
>character? So, it's not wrong for a parser to complain (or, not complain)
>about 0xFFFF, and you can just scrub the string like Jon suggests.
>
>Chris
>
>
>[1]
>http://en.wikipedia.org/wiki/Mapping_of_Unicode_characters#Noncharacters
>
>On 5 Mar, 2013, at 9:16 , Jon Stroop <[log in to unmask]> wrote:
>
>> Mike,
>> I haven't used minidom extensively but my guess is that
>>doc.toprettyxml(indent=" ",encoding="utf-8") isn't actually changing the
>>encoding because it can't parse the string in your content variable. I'm
>>surprised that you're not getting tossed a UnicodeError, but The docs
>>for Node.toxml() [1] might shed some light:
>>
>>> To avoid UnicodeError exceptions in case of unrepresentable text data,
>>>the encoding argument should be specified as "utf-8".
>>
>> So what happens if you're not explicit about the encoding, i.e. just
>>doc.toprettyxml()? This would hopefully at least move your exception to
>>a more appropriate place.
>>
>> In any case, one solution would be to scrub the string in your content
>>variable to get rid of the invalid characters (hopefully they're
>>insignificant). Maybe something like this:
>>
>> def unicode_filter(char):
>> try:
>> unicode(char, encoding='utf-8', errors='strict')
>> return char
>> except UnicodeDecodeError:
>> return ''
>>
>> content = 'abc\xFF'
>> content = ''.join(map(unicode_filter, content)) print content
>>
>> Not really my area of expertise, but maybe worth a shot....
>> -Jon
>>
>> 1.
>> http://docs.python.org/2/library/xml.dom.minidom.html#xml.dom.minidom.
>> Node.toxml
>>
>> --
>> Jon Stroop
>> Digital Initiatives Programmer/Analyst Princeton University Library
>> [log in to unmask]
>>
>>
>>
>>
>> On 03/04/2013 03:00 PM, Michael Beccaria wrote:
>>> I'm working on a project that takes the ocr data found in a pdf and
>>>places it in a custom xml file.
>>>
>>> I use Python scripts to create the xml file. Something like this
>>>(trimmed down a bit):
>>>
>>> from xml.dom.minidom import Document
>>> doc = Document()
>>> Page = doc.createElement("Page")
>>> doc.appendChild(Page)
>>> f = StringIO(txt)
>>> lines = f.readlines()
>>> for line in lines:
>>> word = doc.createElement("String")
>>> ...
>>> word.setAttribute("CONTENT",content)
>>> Page.appendChild(word)
>>> return doc.toprettyxml(indent=" ",encoding="utf-8")
>>>
>>>
>>> This creates a file, simply, that looks like this:
>>> <?xml version="1.0" encoding="utf-8"?> <Page HEIGHT="3296"
>>> WIDTH="2609">
>>> <String CONTENT="BuffaloLaunch" />
>>> <String CONTENT="Club" />
>>> <String CONTENT="Offices" />
>>> <String CONTENT="Installed" />
>>> ...
>>> </Page>
>>>
>>> I am able to get this document to be created ok and saved to an xml
>>>file. The problem occurs when I try and have it read using the lxml
>>>library:
>>>
>>> from lxml import etree
>>> doc = etree.parse(filename)
>>>
>>>
>>> I am running across errors like "XMLSyntaxError: Char 0xFFFF out of
>>>allowed range, line 94, column 19". Which when I look at the file, is
>>>true. There is a 0XFFFF character in the content field.
>>>
>>> How is a file able to be created using minidom (which I assume would
>>>create a valid xml file) and then failing when parsing with lxml? What
>>>should I do to fix this on the encoding side so that errors don't show
>>>up on the parsing side?
>>> Thanks,
>>> Mike
>>>
>>> How is the
>>> Mike Beccaria
>>> Systems Librarian
>>> Head of Digital Initiative
>>> Paul Smith's College
>>> 518.327.6376
>>> [log in to unmask]
>>> Become a friend of Paul Smith's Library on Facebook today!


-----------------------------------------
**************************************************************************************************
The contents of this email and any attachments are confidential.
They are intended for the named recipient(s) only.
If you have received this email in error please notify the system
manager or the
sender immediately and do not disclose the contents to anyone or
make copies.

** IronMail scanned this email for viruses, vandals and malicious
content. **
**************************************************************************************************

Top of Message | Previous Page | Permalink

Advanced Options


Options

Log In

Log In

Get Password

Get Password


Search Archives

Search Archives


Subscribe or Unsubscribe

Subscribe or Unsubscribe


Archives

March 2024
February 2024
January 2024
December 2023
November 2023
October 2023
September 2023
August 2023
July 2023
June 2023
May 2023
April 2023
March 2023
February 2023
January 2023
December 2022
November 2022
October 2022
September 2022
August 2022
July 2022
June 2022
May 2022
April 2022
March 2022
February 2022
January 2022
December 2021
November 2021
October 2021
September 2021
August 2021
July 2021
June 2021
May 2021
April 2021
March 2021
February 2021
January 2021
December 2020
November 2020
October 2020
September 2020
August 2020
July 2020
June 2020
May 2020
April 2020
March 2020
February 2020
January 2020
December 2019
November 2019
October 2019
September 2019
August 2019
July 2019
June 2019
May 2019
April 2019
March 2019
February 2019
January 2019
December 2018
November 2018
October 2018
September 2018
August 2018
July 2018
June 2018
May 2018
April 2018
March 2018
February 2018
January 2018
December 2017
November 2017
October 2017
September 2017
August 2017
July 2017
June 2017
May 2017
April 2017
March 2017
February 2017
January 2017
December 2016
November 2016
October 2016
September 2016
August 2016
July 2016
June 2016
May 2016
April 2016
March 2016
February 2016
January 2016
December 2015
November 2015
October 2015
September 2015
August 2015
July 2015
June 2015
May 2015
April 2015
March 2015
February 2015
January 2015
December 2014
November 2014
October 2014
September 2014
August 2014
July 2014
June 2014
May 2014
April 2014
March 2014
February 2014
January 2014
December 2013
November 2013
October 2013
September 2013
August 2013
July 2013
June 2013
May 2013
April 2013
March 2013
February 2013
January 2013
December 2012
November 2012
October 2012
September 2012
August 2012
July 2012
June 2012
May 2012
April 2012
March 2012
February 2012
January 2012
December 2011
November 2011
October 2011
September 2011
August 2011
July 2011
June 2011
May 2011
April 2011
March 2011
February 2011
January 2011
December 2010
November 2010
October 2010
September 2010
August 2010
July 2010
June 2010
May 2010
April 2010
March 2010
February 2010
January 2010
December 2009
November 2009
October 2009
September 2009
August 2009
July 2009
June 2009
May 2009
April 2009
March 2009
February 2009
January 2009
December 2008
November 2008
October 2008
September 2008
August 2008
July 2008
June 2008
May 2008
April 2008
March 2008
February 2008
January 2008
December 2007
November 2007
October 2007
September 2007
August 2007
July 2007
June 2007
May 2007
April 2007
March 2007
February 2007
January 2007
December 2006
November 2006
October 2006
September 2006
August 2006
July 2006
June 2006
May 2006
April 2006
March 2006
February 2006
January 2006
December 2005
November 2005
October 2005
September 2005
August 2005
July 2005
June 2005
May 2005
April 2005
March 2005
February 2005
January 2005
December 2004
November 2004
October 2004
September 2004
August 2004
July 2004
June 2004
May 2004
April 2004
March 2004
February 2004
January 2004
December 2003
November 2003

ATOM RSS1 RSS2



LISTS.CLIR.ORG

CataList Email List Search Powered by the LISTSERV Email List Manager