Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > comp.lang.python > #54717

Re: removing BOM prepended by codecs?

Show all headers | View raw

On Wed, Sep 25, 2013 at 4:43 AM,  <wxjmfauth@gmail.com> wrote:
> - The *mark* (once the Unicode.org terminology in FAQ) indicating
> a unicode encoded raw text file is neither a byte order mark,
> nor a signature, it is an encoded code point, the encoded
> U+FEFF, 'ZERO WIDTH NO-BREAK SPACE', code point. (Note, a
> non breaking space at the start of a text is a non sense.)
>
> - When such a mark exists, it is always possible to work
> 100% safely. No possible error.

I have a file encoded in Latin-1 which begins with LATIN SMALL LETTER
Y WITH DIAERESIS followed by LATIN SMALL LETTER THORN. I also have a
file encoded in EBCDIC (okay, I don't really, but let's pretend) that
begins with the same bytes. But of course, when such a mark exists,
there is no possible error - of that there is no manner of doubt, no
possible, probable shadow of doubt, no possible doubt whatever.

("No possible doubt whatever.")

ChrisA

Back to comp.lang.python | Previous | Next — Previous in thread | Find similar | Unroll thread

Thread

removing BOM prepended by codecs? "J. Bagg" <j.bagg@kent.ac.uk> - 2013-09-24 10:42 +0100
  Re: removing BOM prepended by codecs? Steven D'Aprano <steve@pearwood.info> - 2013-09-24 10:56 +0000
  Re: removing BOM prepended by codecs? wxjmfauth@gmail.com - 2013-09-24 11:43 -0700
    Re: removing BOM prepended by codecs? Chris Angelico <rosuav@gmail.com> - 2013-09-25 08:20 +1000

csiph-web