Issue 905 in lilypond: LilyPond should accept UTF-8 BOM signatures even if preceded with other chars

[lilypond]

Status: Accepted
Owner: v.villenave
Labels: Type-Defect Priority-Medium Encoding

New issue 905 by v.villenave: LilyPond should accept UTF-8 BOM signatures  
even if preceded with other chars
http://code.google.com/p/lilypond/issues/detail?id=905

Currently, LilyPond fails to parse UTF-8 files when a BOM signature is
found in the middle of other chars: see the attached file provided by
Francisco.

Instead, this character should simply be left alone as a ZWNBS and the file
should compile properly.

As Patrick noted, "RFC 3629 states that

 "It is important to understand that the character U+FEFF appearing
 at any position other than the beginning of a stream MUST be
 interpreted with the semantics for the zero-width non-breaking
 space..."
"

See also
http://lists.gnu.org/archive/html/lilypond-devel/2009-11/msg00331.html


Attachments:
        bom-mark-test-space.ly  30 bytes

--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings