Re: Problem with PARAGRAPH SEPARATOR

2008-03-20 Thread Matt Nordhoff
[EMAIL PROTECTED] wrote: > Actually that's what I tried to do, for example: > outputString = myString.encode('iso-8859-1','ignore') > > However, I always get such messages (the character, that's causing problems > varies, but its always higher than 127 ofc...) > > 'ascii' codec can't decode byte

Re: Problem with PARAGRAPH SEPARATOR

2008-03-20 Thread Richard Brodie
<[EMAIL PROTECTED]> wrote in message news:[EMAIL PROTECTED] > Would that mean that the string "myString" is an ascii-string or what? It would mean it was a byte encoded string already, yes. When you try to encode it, Python tries to coerce it to Unicode and it's equivalent to: myString.decode(

RE: Problem with PARAGRAPH SEPARATOR

2008-03-20 Thread Dominique . Holzwarth
here's still the message about the 'ascii' codec... Would that mean that the string "myString" is an ascii-string or what? -Original Message- From: Marc 'BlackJack' Rintsch [mailto:[EMAIL PROTECTED] Sent: Donnerstag, 20. März 2008 15:24 To: python-list

Re: Problem with PARAGRAPH SEPARATOR

2008-03-20 Thread Marc 'BlackJack' Rintsch
On Thu, 20 Mar 2008 13:03:17 +, Dominique.Holzwarth wrote: > The output of the transformation (a big string containg the whole file) > contains a so called 'paragraph separator' (unicode: 2029). If I want to > pring that string (file) to the std out or a file object then I get a > "UnicodeErro