Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.python > #85382 > unrolled thread
| Started by | Skip Montanaro <skip.montanaro@gmail.com> |
|---|---|
| First post | 2015-02-09 11:30 -0600 |
| Last post | 2015-02-09 11:30 -0600 |
| Articles | 1 — 1 participant |
Back to article view | Back to comp.lang.python
This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by
below is the oldest one visible, not the original post.
Re: Python 3.x stuffing utf-8 into SQLite db Skip Montanaro <skip.montanaro@gmail.com> - 2015-02-09 11:30 -0600
| From | Skip Montanaro <skip.montanaro@gmail.com> |
|---|---|
| Date | 2015-02-09 11:30 -0600 |
| Subject | Re: Python 3.x stuffing utf-8 into SQLite db |
| Message-ID | <mailman.18566.1423503049.18130.python-list@python.org> |
On Sun, Feb 8, 2015 at 9:58 PM, Chris Angelico <rosuav@gmail.com> wrote: > Those three characters are the CP-1252 decode of the bytes for U+2019 > in UTF-8 (E2 80 99). Not sure if that helps any, but given that it was > an XLSX file, Windows codepages are reasonably likely to show up. Thanks, Chris. Are you telling me I should have defined the input file encoding for my CSV file as CP-1252, or that something got hosed on the export from XLSX to CSV? Or something else? Skip
Back to top | Article view | comp.lang.python
csiph-web