Re: data truncation: web page field input vs direct manipulation

2007-07-12 Thread qhfgva
Well, somewhere between upgrading to trunk, using smart_unicode and playing around with mysqldb connection settings I'm now getting my data converted. Thanks for your help. On Jul 11, 12:13 am, Malcolm Tredinnick <[EMAIL PROTECTED]> wrote: > On Wed, 2007-07-11 at 05:56 +, qhfgva wrote: > >

Re: data truncation: web page field input vs direct manipulation

2007-07-11 Thread Malcolm Tredinnick
On Wed, 2007-07-11 at 05:56 +, qhfgva wrote: > Well, I upgraded to the trunk version of django and now my error looks > like this: > > UnicodeDecodeError: 'utf8' codec can't decode byte 0x94 in position 6: > unexpected code byte > > Not sure if this is much of an improvement. [...] > > >

Re: data truncation: web page field input vs direct manipulation

2007-07-10 Thread qhfgva
Well, I upgraded to the trunk version of django and now my error looks like this: UnicodeDecodeError: 'utf8' codec can't decode byte 0x94 in position 6: unexpected code byte Not sure if this is much of an improvement. On Jul 10, 2:03 am, Horst Gutmann <[EMAIL PROTECTED]> wrote: > qhfgva wrote:

Re: data truncation: web page field input vs direct manipulation

2007-07-10 Thread Horst Gutmann
qhfgva wrote: > Every time I think I understand string encoding I get reminded that I > don't. > > I have a simple form where I can cut and paste in a value with an > "interesting" character in it (e.g. "Foo(r)" - in case that doesn't come > thru that's "F" "o" "o" followed by a registered

data truncation: web page field input vs direct manipulation

2007-07-10 Thread qhfgva
Every time I think I understand string encoding I get reminded that I don't. I have a simple form where I can cut and paste in a value with an "interesting" character in it (e.g. "Foo(r)" - in case that doesn't come thru that's "F" "o" "o" followed by a registered trademark symbol). It gets