On 13 Nov 2009, at 02:27, Patrick McCarty wrote:
Please keep on touch
until I get a sample again from one of my students.
Perhaps they created it in another encoding, and the filled the file
with UTF-8?
No, I just used Windows Notepad (on Windows XP) to create the file,
and saved it with UTF-8 encoding from the drop-down menu.
It would be unlikely that something like that would happen.
Here is a hexdump:
$ xxd bom-mark-test.ly
0000000: efbb bf5c 7665 7273 696f 6e20 2232 2e31 ...\version "2.1
0000010: 322e 3122 0d0a 0d0a 7b20 6320 7d 2.1"....{ c }
I see the BOM mark (ef bb bf), two DOS-style line endings (0d 0a), and
no newline at the end of file.
So one will have to wait for a a file reproducing the problem. :-)
Subsequent discussions suggest perhaps it is a BOm in the middle of
the text - if it now is the BOM. In some circumstances, it is easy to
get spurious invisible characters into a file.
Hans
_______________________________________________
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel