I think changing the LilyPond parser to support BOM in the middle (ie
not at the beginning) of the file is very hard. Actually if it is not at
the beginning, then it should be treated as a regular character, which
might not be present just anywhere in the file.
Francisco Vila wrote:
2009/11/13 Francisco Vila <paconet....@gmail.com>:
Here, suppose the user unexpectedly inserted a blank
before the BOM.
%%%%%
And no PDF. Attached for your convenience. Comments?
Following unicode.org[1], one could well handle it as a ZWNBSP. I
mean, BOM is there for a reason, and if it is supported, that should
make lily to behave smartly. Instead, lily seems to behave more as a
dumb, stopping completely by a minor issue.
[1] http://unicode.org/faq/utf_bom.html#bom6
_______________________________________________
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
