Re: getting data with proper encoding to the finish

2005-03-23 Thread Bob Kline
On Wed Mar 16 22:21:42 CET 2005 John Machin wrote: > Apparently pyXLWriter doesn't handle Unicode at all. Although > Unicode came in with Excel 1997 (BIFF8 format file), pyXLWriter > appears to support only Excel 5(?) (BIFF5 format file). As > Serge suggested, appeal to the porter to appeal to the

Re: getting data with proper encoding to the finish

2005-03-16 Thread John Machin
Ksenia Marasanova wrote: > John, Serge, thanks for your help! Thank *you* for having interesting problems :-) > > utf-16le encoding didn't help. I had however to solve it yesterday, > so I used csv module to create CSV file and then import it in Excel. > Excel still had troubles with accented ch

Re: getting data with proper encoding to the finish

2005-03-16 Thread Serge Orlov
Ksenia Marasanova wrote: > John, Serge, thanks for your help! > > utf-16le encoding didn't help. I had however to solve it yesterday, > so I used csv module to create CSV file and then import it in Excel. > Excel still had troubles with accented characters, but this is another > story: it seems t

Re: getting data with proper encoding to the finish

2005-03-16 Thread Ksenia Marasanova
John, Serge, thanks for your help! utf-16le encoding didn't help. I had however to solve it yesterday, so I used csv module to create CSV file and then import it in Excel. Excel still had troubles with accented characters, but this is another story: it seems that Office 2004 Excel (for Mac, but I

Re: getting data with proper encoding to the finish

2005-03-14 Thread John Machin
Serge Orlov wrote: > Looking at the following function in pyXLWriter > def _asc2ucs(s): > """Convert ascii string to unicode.""" > return "\x00".join(s) + "\x00" > > I can guess several things: > a) pyXLWriter author is an ascii guy :) Shrewd guess :-) > b) unicode strings are not suppor

Re: getting data with proper encoding to the finish

2005-03-14 Thread Serge Orlov
John Machin wrote: > Ksenia Marasanova wrote: >> Sorry, I meant: I use field of the type 'text' in a Postgres table to >> store my data. The data is a XML string. >> >>> Instead of "print data", do "print repr(data)" and show us what you >>> get. What *you* see on the screen is not much use for dia

Re: getting data with proper encoding to the finish

2005-03-14 Thread John Machin
Ksenia Marasanova wrote: > Sorry, I meant: I use field of the type 'text' in a Postgres table to > store my data. The data is a XML string. > > > Instead of "print data", do "print repr(data)" and show us what you > > get. What *you* see on the screen is not much use for diagnosis; it's > > the va

Re: getting data with proper encoding to the finish

2005-03-14 Thread John Machin
Ksenia Marasanova wrote: > > > There is some amount of data in a database (PG) that must be inserted > > > into Excel sheet and emailed. Nothing special, everything works. > > > Except that non-ascii characters are not displayed properly. > > > The data is stored as XML into a text field. > > > >

Re: getting data with proper encoding to the finish

2005-03-14 Thread Ksenia Marasanova
> > There is some amount of data in a database (PG) that must be inserted > > into Excel sheet and emailed. Nothing special, everything works. > > Except that non-ascii characters are not displayed properly. > > The data is stored as XML into a text field. > > This sentence doesn't make much sense

Re: getting data with proper encoding to the finish

2005-03-14 Thread John Machin
Ksenia Marasanova wrote: > Hi, > > I have a little problem with encoding. Was hoping maybe anyone can > help me to solve it. > > There is some amount of data in a database (PG) that must be inserted > into Excel sheet and emailed. Nothing special, everything works. > Except that non-ascii characte