On Wed, May 30, 2012 at 5:15 PM, R. Mattes <rm@mh-freiburg.de> wrote:
> I cannot cope with this at the level of encoding, because that would
> break Unix applications and would make ECL work differently on Windows
> and on Unix. Instead I have hacked a simpler solution: BOM is
> interpreted by the Lisp reader as a whitespace.

 ... but this is not a hack - the BOM _is_ zero-width nonbreaking space and hence
should be treated as whitespace.

A Windows programmer might consider it a "hack" in the sense that Windows libraries ignore the initial BOM and only use it to signal the UTF-8 encoding -- when you read the file, the character is discarded (it is not returned for the programmer to interpret it as a whitespace).


Instituto de Física Fundamental, CSIC
c/ Serrano, 113b, Madrid 28006 (Spain)