Re: [Tutor] Confusing Unicode Conversion Problem.

2006-12-13 Thread Chris Hengge
You fixed it! Kudos and a cookie! (Name Brand even!) Thanks a lot, seems to be moving along fine now.. :] On 12/13/06, Tim Golden <[EMAIL PROTECTED]> wrote: [Chris H] > The reason I an forcing each line to string and splitting it is because the > pure numeric values coming from the excel sheet

[Tutor] Confusing Unicode Conversion Problem.

2006-12-13 Thread Tim Golden
[Chris H] > The reason I an forcing each line to string and splitting it is because the > pure numeric values coming from the excel sheet all come in a decimal, and > have an appended .0 at the end. Ah! You're using str to convert a number to a string. I see. And you're relying on the fact that

Re: [Tutor] Confusing Unicode Conversion Problem.

2006-12-13 Thread Chris Hengge
Thanks for the detailed reply. The reason I an forcing each line to string and splitting it is because the pure numeric values coming from the excel sheet all come in a decimal, and have an appended .0 at the end. So 123456 in Excel is becoming 123456.0 when using the loop to extract it. I was to

Re: [Tutor] Confusing Unicode Conversion Problem.

2006-12-13 Thread Tim Golden
[Chris Hengge] | 'ascii' codec can't encode character u'\xa0' in position 11: | ordinal not in range(128) | Error with: FRAMEMRISER of type: | Excel Row : 6355 OK. Let's get to the basics first: import unicodedata print unicodedata.name (u'\xa0') # outputs: NO-BREAK SPACE So somewhere (ma

[Tutor] Confusing Unicode Conversion Problem.

2006-12-12 Thread Chris Hengge
I've got a script that uses com to read columns from an excel workbook(very slow for 6500ish items :/ ) and I'm getting this error: 'ascii' codec can't encode character u'\xa0' in position 11: ordinal not in range(128) Error with: FRAMEMRISER of type: Excel Row : 6355 FRAMEMRISER is exactly ho