Laurent Pointal wrote:
> John Machin a écrit :
> > The customer should be very happy if you do
> > text.decode('utf-8').encode('cp1252') -- not only should the file
> > import into Excel OK, he should be able to view it in
> > Word/Notepad/whatever.
>
> +
> text.decode('utf-8').encode('cp1252',erro
John Machin a écrit :
> The customer should be very happy if you do
> text.decode('utf-8').encode('cp1252') -- not only should the file
> import into Excel OK, he should be able to view it in
> Word/Notepad/whatever.
+
text.decode('utf-8').encode('cp1252',errors='replace')
As cp1252 may not cover
thebjorn wrote:
> I'm working with a MS SQL Server database created by a program from a
> fine US company who seems to have gotten run over by the Unicode truck.
> In their infinite wisdom they've decided to store Unicode data directly
> in regular varchar fields, utf-8 encoded! (on the bright sid
bjorn:
> I also
> tried creating an Excel VB macro using the StrConv function, but (a) it
> isn't entirely clear to me that this function can do this, and (b) the
> third argument to the function is an LCID, a Locale ID, which is
> numeric and not defined anywhere I can find it...
http://www.micr
