On Sat, Dec 6, 2008 at 2:59 PM, Rob Hudson <[EMAIL PROTECTED]> wrote:
>
> Wow, thanks so much Karen, for slicing and dicing the problem like
> that.
>
> On Dec 6, 10:36 am, "Karen Tracey" <[EMAIL PROTECTED]> wrote:
> > You could also just convert the character set used on the MySQL side:
> >
> >
Wow, thanks so much Karen, for slicing and dicing the problem like
that.
On Dec 6, 10:36 am, "Karen Tracey" <[EMAIL PROTECTED]> wrote:
> You could also just convert the character set used on the MySQL side:
>
> http://dev.mysql.com/doc/refman/5.0/en/charset-conversion.html
>
> Presumably since
On Sat, Dec 6, 2008 at 1:36 PM, Karen Tracey <[EMAIL PROTECTED]> wrote:
>
> You can see how this works better than the latin1 code in a Python shell:
>
> >>> x = 'Bullet ->\x95<- and curly apostrophe ->\x92<- in a cp1252
> bytestring'
> >>> ulatin1 = x.decode('latin1')
> >>> ulatin1
> u'Bullet
On Sat, Dec 6, 2008 at 11:10 AM, Rob Hudson <[EMAIL PROTECTED]> wrote:
> [snip debug info]
>
> Now instead of \x95 I get \u2022 (which is a bullet).
>
> From here I'm not sure what the best way to proceed is... do I want
> the \u2022 version instead, in which case, should I not pass in
>
Thanks Malcolm,
On Dec 4, 6:12 pm, Malcolm Tredinnick <[EMAIL PROTECTED]>
wrote:
> Now you might well be able to have this happen automatically using the
> "unicode" option to MySQLdb -- it knows how to convert between various
> server-side encodings and Python unicode. So look at that parameter
On Thu, 2008-12-04 at 16:34 -0800, Rob Hudson wrote:
> I'm migrating a site to Django. The old site was PHP/MySQL with MySQL
> having a default encoding of latin1. It seems like there are also
> Windows 1252 encodings but I'm not sure.
>
> I have the old database and the new Django UTF8 one
6 matches
Mail list logo
