Re: Python 3.x stuffing utf-8 into SQLite db

References	<CANc-5UwYdoPLKuqRbrfbOrQTVafOaZmWZ+8SnDc-TZp1NEXcQg@mail.gmail.com> <CAPTjJmpJV4KYcL50_=0hv+BLKaGX_X9wqQgMJeszMrHgAK+drA@mail.gmail.com> <CANc-5Uwb51DKan1xgqwWDT2WFAZk-_NcqgLcnQfzYHzQzps3xA@mail.gmail.com> <54D8F438.1060402@case.edu>
Date	2015-02-09 12:52 -0600
Subject	Re: Python 3.x stuffing utf-8 into SQLite db
From	Skip Montanaro <skip.montanaro@gmail.com>
Newsgroups	comp.lang.python
Message-ID	<mailman.18601.1423555315.18130.python-list@python.org> (permalink)

Show all headers | View raw

[Multipart message — attachments visible in raw view] - view raw

On Mon, Feb 9, 2015 at 11:54 AM, Matthew Ruffalo <mmr15@case.edu> wrote:
> I think it's most likely that the encoding issues happened in the export
> from XLSX to CSV (unless the data is malformed in the original XLSX
> file, of course).

Aha! Lookee here... (my apologies to all you HTML mail haters - sometimes
it even comes in handy. :-)

This snapshot was taken against a running LibreOffice instance here at work
(on Linux). It would appear the fancy schmancy apostrophe was hosed up
before the data ever got to me. Had a guy here with Windows pop up the
original file I got in an actual Excel instance. Same bogosity.

Knowing that, I don't feel the least bit timid about just editing the darn
CSV file to correct the encode/decode/encode error before loading the data
into SQLite. I was worried that since I was doing some Python 3.x stuff
involving Unicode for the first time that I'd screwed something up.

Skip

Back to comp.lang.python | Previous | Next | Find similar | Unroll thread

Thread

Re: Python 3.x stuffing utf-8 into SQLite db Skip Montanaro <skip.montanaro@gmail.com> - 2015-02-09 12:52 -0600

csiph-web