Re: [CODE4LIB] Q.: MARC8 vs. MARC/Unicode and pymarc and misencoded III records

2012-03-12 Thread Ed Summers
On Fri, Mar 9, 2012 at 12:12 PM, Godmar Back god...@gmail.com wrote: Here's my hand ||*(  [1]. ||*) I'm sorry that I was so unhelpful w/ the patches welcome message on your docfix. You're right, it was antagonistic of me to suggest you send a patch for something so simple. Plus, it wasn't even

Re: [CODE4LIB] Q.: MARC8 vs. MARC/Unicode and pymarc and misencoded III records

2012-03-12 Thread Lemann, Alexander
for Libraries [mailto:CODE4LIB@LISTSERV.ND.EDU] On Behalf Of Brian Kennison Sent: Friday, March 09, 2012 9:17 AM To: CODE4LIB@LISTSERV.ND.EDU Subject: Re: [CODE4LIB] Q.: MARC8 vs. MARC/Unicode and pymarc and misencoded III records On Mar 8, 2012, at 1:46 PM, Terray, James wrote: UnicodeDecodeError

Re: [CODE4LIB] Q.: MARC8 vs. MARC/Unicode and pymarc and misencoded III records

2012-03-12 Thread Godmar Back
On Mon, Mar 12, 2012 at 3:38 AM, Ed Summers e...@pobox.com wrote: On Fri, Mar 9, 2012 at 12:12 PM, Godmar Back god...@gmail.com wrote: Here's my hand ||*( [1]. ||*) I'm sorry that I was so unhelpful w/ the patches welcome message on your docfix. You're right, it was antagonistic of me to

Re: [CODE4LIB] Q.: MARC8 vs. MARC/Unicode and pymarc and misencoded III records

2012-03-12 Thread Ed Summers
On Mon, Mar 12, 2012 at 10:14 AM, Godmar Back god...@gmail.com wrote: Here's a make-up pull request especially made for you :-) https://github.com/edsu/pymarc/pull/25 Merged! :-D //Ed

Re: [CODE4LIB] Q.: MARC8 vs. MARC/Unicode and pymarc and misencoded III records

2012-03-09 Thread Brian Kennison
On Mar 8, 2012, at 1:46 PM, Terray, James wrote: UnicodeDecodeError: 'ascii' codec can't decode byte 0xe8 in position 9: ordinal not in range(128) Hello everyone, I just ran into this the other day when trying to write to a file. I searched the documentation and found this: fp =

Re: [CODE4LIB] Q.: MARC8 vs. MARC/Unicode and pymarc and misencoded III records

2012-03-09 Thread Tom Keays
I'm out of my depth here, but I'm curious how this all works. Is it true that, in MARC8 records, there is supposed to be an 066 field included that defines non-Latin character sets? I'm making this conclusion from some things I read on the LOC website. ANSEL is mentioned as one of the instances

Re: [CODE4LIB] Q.: MARC8 vs. MARC/Unicode and pymarc and misencoded III records

2012-03-09 Thread Mark A. Matienzo
On Fri, Mar 9, 2012 at 7:23 AM, Godmar Back god...@gmail.com wrote: Mark, while I would be able to contribute code to pymarc, I probably won't (unless my collaborators' needs in respect to pymarc become urgent.) Such is our conundrum. Most of my uses of pymarc only involve reading records, not

Re: [CODE4LIB] Q.: MARC8 vs. MARC/Unicode and pymarc and misencoded III records

2012-03-09 Thread Michael B. Klein
The internal discussion then becomes, I have a need, and I've written something that satisfies it. I think it could also be useful to others, but I'm not going to have time to make major changes or implement features others need. Should I open source this or keep it to myself? Does freeing my code

Re: [CODE4LIB] Q.: MARC8 vs. MARC/Unicode and pymarc and misencoded III records

2012-03-09 Thread Godmar Back
On Fri, Mar 9, 2012 at 10:37 AM, Michael B. Klein mbkl...@gmail.com wrote: The internal discussion then becomes, I have a need, and I've written something that satisfies it. I think it could also be useful to others, but I'm not going to have time to make major changes or implement features

Re: [CODE4LIB] Q.: MARC8 vs. MARC/Unicode and pymarc and misencoded III records

2012-03-09 Thread Jon Gorman
It used to be that way, at least it was this way when I grew up in open source (in the 90s, before Eric Raymond invented the term). And it makes sense, for successful projects that have at least a moderate number of users. Just dumping your code on github helps very few people. You realize

Re: [CODE4LIB] Q.: MARC8 vs. MARC/Unicode and pymarc and misencoded III records

2012-03-09 Thread Godmar Back
On Fri, Mar 9, 2012 at 11:48 AM, Jon Gorman jonathan.gor...@gmail.comwrote: Can't we all just shake hands virtually or something? Here's my hand ||*( [1]. I overreacted, for which I'm sorry. (Also, I didn't see the entire github conversation until I just now visited the website, the github

[CODE4LIB] Q.: MARC8 vs. MARC/Unicode and pymarc and misencoded III records

2012-03-08 Thread Godmar Back
Hi, a few days ago, I showed pymarc to a group of technical librarians to demonstrate how easily certain tasks can be scripted/automated. Unfortunately, it blew up at me when I tried to write a record: UnicodeDecodeError: 'ascii' codec can't decode byte 0xe8 in position 9: ordinal not in

Re: [CODE4LIB] Q.: MARC8 vs. MARC/Unicode and pymarc and misencoded III records

2012-03-08 Thread Terray, James
[god...@gmail.com] Sent: Thursday, March 08, 2012 1:02 PM To: CODE4LIB@LISTSERV.ND.EDU Subject: [CODE4LIB] Q.: MARC8 vs. MARC/Unicode and pymarc and misencoded III records Hi, a few days ago, I showed pymarc to a group of technical librarians to demonstrate how easily certain tasks can

Re: [CODE4LIB] Q.: MARC8 vs. MARC/Unicode and pymarc and misencoded III records

2012-03-08 Thread David Jones
On 3/8/2012 at 10:02 AM, Godmar Back god...@gmail.com wrote: My question is how others, especially pymarc users dealing with III records, deal with this issue or whatever other experiences/hints/practices/kludges exist in this area. Suggestions: 1) Get the library to have Innovative verify

Re: [CODE4LIB] Q.: MARC8 vs. MARC/Unicode and pymarc and misencoded III records

2012-03-08 Thread Godmar Back
On Thu, Mar 8, 2012 at 1:46 PM, Terray, James james.ter...@yale.edu wrote: Hi Godmar, UnicodeDecodeError: 'ascii' codec can't decode byte 0xe8 in position 9: ordinal not in range(128) Having seen my fair share of these kinds of encoding errors in Python, I can speculate (without seeing the

Re: [CODE4LIB] Q.: MARC8 vs. MARC/Unicode and pymarc and misencoded III records

2012-03-08 Thread Reese, Terry
Message- From: Code for Libraries [mailto:CODE4LIB@LISTSERV.ND.EDU] On Behalf Of Godmar Back Sent: Thursday, March 08, 2012 11:01 AM To: CODE4LIB@LISTSERV.ND.EDU Subject: Re: [CODE4LIB] Q.: MARC8 vs. MARC/Unicode and pymarc and misencoded III records On Thu, Mar 8, 2012 at 1:46 PM, Terray, James

Re: [CODE4LIB] Q.: MARC8 vs. MARC/Unicode and pymarc and misencoded III records

2012-03-08 Thread Ed Summers
Hi Terry, On Thu, Mar 8, 2012 at 2:36 PM, Reese, Terry terry.re...@oregonstate.edu wrote: This is one of the reasons you really can't trust the information found in position 9.  This is one of the reasons why when I wrote MarcEdit, I utilize a mixed process when working with data and

Re: [CODE4LIB] Q.: MARC8 vs. MARC/Unicode and pymarc and misencoded III records

2012-03-08 Thread Gabriel Farrell
[mailto:CODE4LIB@LISTSERV.ND.EDU] On Behalf Of Godmar Back Sent: Thursday, March 08, 2012 11:01 AM To: CODE4LIB@LISTSERV.ND.EDU Subject: Re: [CODE4LIB] Q.: MARC8 vs. MARC/Unicode and pymarc and misencoded III records On Thu, Mar 8, 2012 at 1:46 PM, Terray, James james.ter...@yale.edu wrote: Hi Godmar

Re: [CODE4LIB] Q.: MARC8 vs. MARC/Unicode and pymarc and misencoded III records

2012-03-08 Thread Godmar Back
On Thu, Mar 8, 2012 at 3:18 PM, Ed Summers e...@pobox.com wrote: Hi Terry, On Thu, Mar 8, 2012 at 2:36 PM, Reese, Terry terry.re...@oregonstate.edu wrote: This is one of the reasons you really can't trust the information found in position 9. This is one of the reasons why when I wrote

Re: [CODE4LIB] Q.: MARC8 vs. MARC/Unicode and pymarc and misencoded III records

2012-03-08 Thread Reese, Terry
-Original Message- From: Code for Libraries [mailto:CODE4LIB@LISTSERV.ND.EDU] On Behalf Of Ed Summers Sent: Thursday, March 08, 2012 12:19 PM To: CODE4LIB@LISTSERV.ND.EDU Subject: Re: [CODE4LIB] Q.: MARC8 vs. MARC/Unicode and pymarc and misencoded III records Hi Terry, On Thu, Mar 8, 2012 at 2:36

Re: [CODE4LIB] Q.: MARC8 vs. MARC/Unicode and pymarc and misencoded III records

2012-03-08 Thread Reese, Terry
Of Gabriel Farrell Sent: Thursday, March 08, 2012 12:19 PM To: CODE4LIB@LISTSERV.ND.EDU Subject: Re: [CODE4LIB] Q.: MARC8 vs. MARC/Unicode and pymarc and misencoded III records Sounds like what you do, Terry, and what we need in PyMARC, is something like UnicodeDammit [0]. Actually handling all

Re: [CODE4LIB] Q.: MARC8 vs. MARC/Unicode and pymarc and misencoded III records

2012-03-08 Thread Jonathan Rochkind
: Thursday, March 08, 2012 11:01 AM To: CODE4LIB@LISTSERV.ND.EDU Subject: Re: [CODE4LIB] Q.: MARC8 vs. MARC/Unicode and pymarc and misencoded III records On Thu, Mar 8, 2012 at 1:46 PM, Terray, Jamesjames.ter...@yale.edu wrote: Hi Godmar, UnicodeDecodeError: 'ascii' codec can't decode byte 0xe8

Re: [CODE4LIB] Q.: MARC8 vs. MARC/Unicode and pymarc and misencoded III records

2012-03-08 Thread Jonathan Rochkind
Sent: Thursday, March 08, 2012 11:01 AM To: CODE4LIB@LISTSERV.ND.EDU Subject: Re: [CODE4LIB] Q.: MARC8 vs. MARC/Unicode and pymarc and misencoded III records On Thu, Mar 8, 2012 at 1:46 PM, Terray, Jamesjames.ter...@yale.edu wrote: Hi Godmar, UnicodeDecodeError: 'ascii' codec can't decode byte

Re: [CODE4LIB] Q.: MARC8 vs. MARC/Unicode and pymarc and misencoded III records

2012-03-08 Thread Mark A. Matienzo
On Thu, Mar 8, 2012 at 3:32 PM, Godmar Back god...@gmail.com wrote: One side comment here; while smart handling/automatic detection of encodings would be a nice feature to have, it would help if pymarc could operate in an 'agnostic', or 'raw' mode where it would simply preserve the encoding

Re: [CODE4LIB] Q.: MARC8 vs. MARC/Unicode and pymarc and misencoded III records

2012-03-08 Thread Jeremy Nelson
for Libraries [mailto:CODE4LIB@LISTSERV.ND.EDU] On Behalf Of Jonathan Rochkind Sent: Thursday, March 08, 2012 1:51 PM To: CODE4LIB@LISTSERV.ND.EDU Subject: Re: [CODE4LIB] Q.: MARC8 vs. MARC/Unicode and pymarc and misencoded III records Oh, and why do I favor this solution? Compared to passing input

Re: [CODE4LIB] Q.: MARC8 vs. MARC/Unicode and pymarc and misencoded III records

2012-03-08 Thread Michael B. Klein
For what it's worth, my patch was a stopgap measure, and acknowledged as such at the time. My proposal for a real, comprehensive solution was detailed in a comment in a (now-closed) issue Github ticket[1]. If I'd had the time and the knowledge, I would have implemented it that way. If I'd had the