Re: BOM mark from Windows notepad
On 19 Nov 2009, at 13:28, Hans Aberg wrote: One can also use pipes and RPC - files can be made looking like streams and vice versa. Sorry, it should be IPC - interprocess communications. Though RPC - remote process call - is a type of IPC. :-) Hans ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: BOM mark from Windows notepad
On 19 Nov 2009, at 11:14, Francisco Vila wrote: I think that it was changed. If the BOM is only allowed in the beginning of the file, it becomes a state-dependent character. For example, if one includes two files verbatim in another, then the BOMs will no longer be in the beginning of the combined stream. So therefore this state-less definition is to be preferred. This problem is more frequent than you may think, at least in my environment. Last week I promised to bring a case of faulty LY from Windows notepad; now I realize that all cases which might have failed were previously edited by me, putting the BOM away from the start of the file. All my students work on Windows and every instance of their documents that I edited did fail. On UNIX-like systems, one can chain commands that only handle byte sequences though often used for text processing. UTF-9 was invented to make such usage possible. For example, cat file1 file2 > file3 will concatenate file1 and file2 into file3. It is not feasible to change 'cat', as it is a part of the operative system one will then have to asses the impact on all tools that may use 'cat'. One can also use pipes and RPC - files can be made looking like streams and vice versa. A state-dependent BOM (only accepted at the beginning of a file) does not really work on UNIX-like platforms. So I think that state-less definition was triggered by requirement for those platforms, though it has wider applicability. Hans ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: BOM mark from Windows notepad
2009/11/19 Patrick McCarty : > I'll try to address this issue eventually, but I can't promise > anything right away. Why should'n work just commenting out the line in the code which issues the error when it finds a BOM? Some things are a mystery for a non-programmer and they always be. I used to program simple compilers and I remember that breaking on an error was a decision of mine, but I always could have NOT to have taken that decision and just resume the parsing. -- Francisco Vila. Badajoz (Spain) www.paconet.org www.csmbadajoz.com ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: BOM mark from Windows notepad
2009/11/19 Hans Aberg : > I think that it was changed. If the BOM is only allowed in the beginning of > the file, it becomes a state-dependent character. For example, if one > includes two files verbatim in another, then the BOMs will no longer be in > the beginning of the combined stream. So therefore this state-less > definition is to be preferred. This problem is more frequent than you may think, at least in my environment. Last week I promised to bring a case of faulty LY from Windows notepad; now I realize that all cases which might have failed were previously edited by me, putting the BOM away from the start of the file. All my students work on Windows and every instance of their documents that I edited did fail. I'm sorry for having incorrectly defined the problem at first place; at the same time, I am very thankful for you to spend time on this. The program will gain on stability. I think that editors like xfce mousepad or emacs should take the starting BOM as a mark only and then discard it, i.e. not trying to show or let us to move it. After all, Windows notepad does that with its own files, as it seems. -- Francisco Vila. Badajoz (Spain) www.paconet.org www.csmbadajoz.com ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: BOM mark from Windows notepad
On 19 Nov 2009, at 00:41, Patrick McCarty wrote:
Also, the conditions and the stuff following might possibly be
removed. Something like:
{BOM_UTF8} {}
or
{BOM_UTF8}+ {}
If a language always zips out spaces, one can have rules:
[ \f\r\t\v]+ {}
\n+ { \* Maybe action here counting lines */ }
Then the BOM should just be treated as the other spaces and tabs.
This follows the behavior recommended by RFC 3629, so this is the
behavior LilyPond should follow, too.
More specifically, 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..."
I think that it was changed. If the BOM is only allowed in the
beginning of the file, it becomes a state-dependent character. For
example, if one includes two files verbatim in another, then the BOMs
will no longer be in the beginning of the combined stream. So
therefore this state-less definition is to be preferred.
So once upon the time, BOMs were intended to be used only in the
beginning if the file, and LilyPond conforms to that. But not to this
later definition. - My impression. :-)
Hans
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: BOM mark from Windows notepad
On Thu, Nov 19, 2009 at 8:47 AM, Patrick McCarty wrote: > Yes, please, if you don't mind. There you go: http://code.google.com/p/lilypond/issues/detail?id=905 Cheers, Valentin ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: BOM mark from Windows notepad
On 2009-11-19, Valentin Villenave wrote: > On Thu, Nov 19, 2009 at 12:41 AM, Patrick McCarty wrote: > > I'll try to address this issue eventually, but I can't promise > > anything right away. > > Do you want me to add an issue to the tracker in the meantime? Yes, please, if you don't mind. Thanks, Patrick ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: BOM mark from Windows notepad
On Thu, Nov 19, 2009 at 12:41 AM, Patrick McCarty wrote: > I'll try to address this issue eventually, but I can't promise > anything right away. Do you want me to add an issue to the tracker in the meantime? Cheers, Valentin ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: BOM mark from Windows notepad
On 2009-11-13, Hans Aberg wrote:
> On 13 Nov 2009, at 12:25, Bertalan Fodor (LilyPondTool) wrote:
>
> >{BOM_UTF8}/.* {
> >if (this->lexloc->line_number () != 1 ||
> >this->lexloc->column_number () != 0)
> > {
> > LexerError (_ ("stray UTF-8 BOM encountered").c_str ());
> > exit (1);
>
> Also, the conditions and the stuff following might possibly be
> removed. Something like:
> {BOM_UTF8} {}
> or
> {BOM_UTF8}+ {}
>
> If a language always zips out spaces, one can have rules:
> [ \f\r\t\v]+ {}
> \n+ { \* Maybe action here counting lines */ }
> Then the BOM should just be treated as the other spaces and tabs.
This follows the behavior recommended by RFC 3629, so this is the
behavior LilyPond should follow, too.
More specifically, 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..."
I'll try to address this issue eventually, but I can't promise
anything right away.
Thanks,
Patrick
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: BOM mark from Windows notepad
On 13 Nov 2009, at 12:25, Bertalan Fodor (LilyPondTool) wrote:
{BOM_UTF8}/.* {
if (this->lexloc->line_number () != 1 || this->lexloc->column_number
() != 0)
{
LexerError (_ ("stray UTF-8 BOM encountered").c_str ());
exit (1);
Also, the conditions and the stuff following might possibly be
removed. Something like:
{BOM_UTF8} {}
or
{BOM_UTF8}+ {}
If a language always zips out spaces, one can have rules:
[ \f\r\t\v]+ {}
\n+ { \* Maybe action here counting lines */ }
Then the BOM should just be treated as the other spaces and tabs.
Hans
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: BOM mark from Windows notepad
On 13 Nov 2009, at 12:25, Bertalan Fodor (LilyPondTool) wrote:
Hehe, we've got this:
{BOM_UTF8}/.* {
if (this->lexloc->line_number () != 1 || this->lexloc->column_number
() != 0)
{
LexerError (_ ("stray UTF-8 BOM encountered").c_str ());
exit (1);
That means, we correctly parse the BOM, but exit if it is not the
first char.
This link says that, though there is no Unicode protocol for those of
BOMs, they suggest to treat them as a zero-width space (the non-
breaking part is not relevant here):
http://unicode.org/faq/utf_bom.html#bom6
So to follow that suggestion, that error-code should be removed, if
you now want to admit BOMs.
Hans
Hans Aberg wrote:
On 13 Nov 2009, at 10:08, Bertalan Fodor (LilyPondTool) wrote:
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.
Why would that be? Did you not have a Flex generated .l file? If
the input .l file is in UTF-8 and Flex in 8-bit mode, add a rule
"" {}
where is the UTF-8 representation of the BOM. It will than
add act as space, breaking tokens, but otherwise ignored. So it
acts a zero-width space.
Hans
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: BOM mark from Windows notepad
2009/11/13 Bertalan Fodor (LilyPondTool) :
> Hehe, we've got this:
>
> {BOM_UTF8}/.* {
> if (this->lexloc->line_number () != 1 || this->lexloc->column_number () !=
> 0)
> {
> LexerError (_ ("stray UTF-8 BOM encountered").c_str ());
> exit (1);
>
> That means, we correctly parse the BOM, but exit if it is not the first
> char.
So, one of:
a) Supress the rule. Anyway, what do we do with the BOM once
encountered? Handle it as a space as Unicode says
c) Change the rule so that we don't exit
--
Francisco Vila. Badajoz (Spain)
www.paconet.org
www.csmbadajoz.com
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: BOM mark from Windows notepad
Hehe, we've got this:
{BOM_UTF8}/.* {
if (this->lexloc->line_number () != 1 || this->lexloc->column_number
() != 0)
{
LexerError (_ ("stray UTF-8 BOM encountered").c_str ());
exit (1);
That means, we correctly parse the BOM, but exit if it is not the first
char.
Hans Aberg wrote:
On 13 Nov 2009, at 10:08, Bertalan Fodor (LilyPondTool) wrote:
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.
Why would that be? Did you not have a Flex generated .l file? If the
input .l file is in UTF-8 and Flex in 8-bit mode, add a rule
"" {}
where is the UTF-8 representation of the BOM. It will than add
act as space, breaking tokens, but otherwise ignored. So it acts a
zero-width space.
Hans
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: BOM mark from Windows notepad
On 13 Nov 2009, at 10:08, Bertalan Fodor (LilyPondTool) wrote:
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.
Why would that be? Did you not have a Flex generated .l file? If the
input .l file is in UTF-8 and Flex in 8-bit mode, add a rule
"" {}
where is the UTF-8 representation of the BOM. It will than add
act as space, breaking tokens, but otherwise ignored. So it acts a
zero-width space.
Hans
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: BOM mark from Windows notepad
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
000: efbb bf5c 7665 7273 696f 6e20 2232 2e31 ...\version "2.1
010: 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
Re: BOM mark from Windows notepad
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 : 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
Re: BOM mark from Windows notepad
2009/11/13 Francisco Vila : > 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 -- Francisco Vila. Badajoz (Spain) www.paconet.org www.csmbadajoz.com ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: BOM mark from Windows notepad
Hello again,
Still looking for a test case which reproduces the error; anyway, here
is another case, IIRC not exactly what I encountered, but a case in
which I think the expureous BOM could well be ignored for the sake of
a happy ending. Here, suppose the user unexpectedly inserted a blank
before the BOM.
$ xxd bom-mark-test-space.ly
000: 20ef bbbf 5c76 6572 7369 6f6e 2022 322e ...\version "2.
010: 3132 2e31 220d 0a0d 0a7b 2063 207d 12.1"{ c }
$ lilypond bom-mark-test-space.ly
GNU LilyPond 2.13.8
Processing `bom-mark-test-space.ly'
Parsing...
bom-mark-test-space.ly:1:1: error: stray UTF-8 BOM encountered
\version "2.12.1"
%
And no PDF. Attached for your convenience. Comments?
--
Francisco Vila. Badajoz (Spain)
www.paconet.org
www.csmbadajoz.com
\version "2.12.1"
{ c }___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: BOM mark from Windows notepad
On 2009-11-12, Patrick McCarty wrote: > On 2009-11-12, Hans Aberg wrote: > > On 12 Nov 2009, at 12:34, Francisco Vila 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. Never mind, I thought you were referring to me. :-) Sorry for the noise. -Patrick ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: BOM mark from Windows notepad
On 2009-11-12, Hans Aberg wrote:
> On 12 Nov 2009, at 12:34, Francisco Vila 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.
Here is a hexdump:
$ xxd bom-mark-test.ly
000: efbb bf5c 7665 7273 696f 6e20 2232 2e31 ...\version "2.1
010: 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.
-Patrick
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: BOM mark from Windows notepad
On 12 Nov 2009, at 15:22, David Kastrup wrote:
On Mac OS X 10.5.8, I can see it using 'less'; it looks like:
\version "2.12.1"
{ c }
But emacs 23.1.1 does not show it at all.
C-h C RET RET
gives
Coding system for saving this buffer:
U -- utf-8-with-signature-unix
Notice the "with-signature" part.
With only one "RET", I get a buffer:
Coding system for saving this buffer:
U -- utf-8-with-signature-dos
- It's -dos. Perhaps because the file has a \r\l in it.
If I copy make a new UNIX file without the BOM, I get
Coding system for saving this buffer:
- -- undecided-unix (alias: unix)
Perhaps "undecided" means it has no bytes with the high bit.
Hans
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: BOM mark from Windows notepad
Hans Aberg writes:
> On 12 Nov 2009, at 12:34, Francisco Vila wrote:
>
>>> The attached LY file was created in Windows Notepad, saved in UTF-8
>>> encoding, and I compiled it on Linux with no errors or warnings.
>>>
>>> Do you see an error message when compiling this file? If so, can you
>>> post the error?
>>
>> I'm afraid I cannot reproduce it with your file. I see the white
>> rectangle with emacs, as I saw on the others which give errors, but
>> right now I don't keep those problematic files.
>
> On Mac OS X 10.5.8, I can see it using 'less'; it looks like:
> \version "2.12.1"
>
> { c }
>
> But emacs 23.1.1 does not show it at all.
C-h C RET RET
gives
Coding system for saving this buffer:
U -- utf-8-with-signature-unix
Notice the "with-signature" part.
--
David Kastrup
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: BOM mark from Windows notepad
On 12 Nov 2009, at 12:34, Francisco Vila wrote:
The attached LY file was created in Windows Notepad, saved in UTF-8
encoding, and I compiled it on Linux with no errors or warnings.
Do you see an error message when compiling this file? If so, can you
post the error?
I'm afraid I cannot reproduce it with your file. I see the white
rectangle with emacs, as I saw on the others which give errors, but
right now I don't keep those problematic files.
On Mac OS X 10.5.8, I can see it using 'less'; it looks like:
\version "2.12.1"
{ c }
But emacs 23.1.1 does not show it at all.
It compiled using lilypond 2.13.7.
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?
Hans
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: BOM mark from Windows notepad
2009/11/11 Patrick McCarty : > The attached LY file was created in Windows Notepad, saved in UTF-8 > encoding, and I compiled it on Linux with no errors or warnings. > > Do you see an error message when compiling this file? If so, can you > post the error? I'm afraid I cannot reproduce it with your file. I see the white rectangle with emacs, as I saw on the others which give errors, but right now I don't keep those problematic files. Please keep on touch until I get a sample again from one of my students. Thank you for your time, -- Francisco Vila. Badajoz (Spain) www.paconet.org www.csmbadajoz.com ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: BOM mark from Windows notepad
The corresponding code in lily/lexer.ll which takes care of the BOM hasn't been changed for many years as far as I know. /Mats Bertalan Fodor (LilyPondTool) wrote: It is a regression. BOM was supported for sure. Patrick McCarty wrote: On 2009-11-11, Francisco Vila wrote: Hello. When LilyPond for Linux encounters a BOM from files made with the Windows notepad, it issues an error. Has this always been the case, or is this a new issue with 2.13.7? I think it should continue making the PDF anyway, because the file has an otherwise correct syntax; what do you think? Yes, definitely. The BOM is permitted by the UTF-8 spec, so an error should not be issued. Thanks, Patrick ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel -- = Mats Bengtsson Signal Processing School of Electrical Engineering Royal Institute of Technology (KTH) SE-100 44 STOCKHOLM Sweden Phone: (+46) 8 790 8463 Fax: (+46) 8 790 7260 Email: mats.bengts...@ee.kth.se WWW: http://www.s3.kth.se/~mabe = ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: BOM mark from Windows notepad
On Wed, Nov 11, 2009 at 1:53 PM, Bertalan Fodor (LilyPondTool) wrote: > It is a regression. BOM was supported for sure. Have you experienced this problem, too? -Patrick ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: BOM mark from Windows notepad
On Wed, Nov 11, 2009 at 11:57 AM, Francisco Vila wrote:
> 2009/11/11 Patrick McCarty :
>> On 2009-11-11, Francisco Vila wrote:
>>> Hello. When LilyPond for Linux encounters a BOM from files made with
>>> the Windows notepad, it issues an error.
>>
>> Has this always been the case, or is this a new issue with 2.13.7?
>
> I vaguely remember it happening from 2005.
>
>>
>>> I think it should continue making the PDF anyway, because the file has
>>> an otherwise correct syntax; what do you think?
>>
>> Yes, definitely. The BOM is permitted by the UTF-8 spec, so an error
>> should not be issued.
>
> The problem is that young starters receive perfectly detailed
> instructions and they give me working files except for this; it is
> embrassing for me having still to edit their files to produce a PDF in
> my Linux system. A warning would suffice; is there a way to convert
> an error into a warning?
Not easily. I'm actually having trouble reproducing this problem on
my Linux system.
The attached LY file was created in Windows Notepad, saved in UTF-8
encoding, and I compiled it on Linux with no errors or warnings.
Do you see an error message when compiling this file? If so, can you
post the error?
Thanks,
Patrick
\version "2.12.1"
{ c }___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: BOM mark from Windows notepad
It is a regression. BOM was supported for sure. Patrick McCarty wrote: On 2009-11-11, Francisco Vila wrote: Hello. When LilyPond for Linux encounters a BOM from files made with the Windows notepad, it issues an error. Has this always been the case, or is this a new issue with 2.13.7? I think it should continue making the PDF anyway, because the file has an otherwise correct syntax; what do you think? Yes, definitely. The BOM is permitted by the UTF-8 spec, so an error should not be issued. Thanks, Patrick ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: BOM mark from Windows notepad
2009/11/11 Patrick McCarty : > On 2009-11-11, Francisco Vila wrote: >> Hello. When LilyPond for Linux encounters a BOM from files made with >> the Windows notepad, it issues an error. > > Has this always been the case, or is this a new issue with 2.13.7? I vaguely remember it happening from 2005. > >> I think it should continue making the PDF anyway, because the file has >> an otherwise correct syntax; what do you think? > > Yes, definitely. The BOM is permitted by the UTF-8 spec, so an error > should not be issued. The problem is that young starters receive perfectly detailed instructions and they give me working files except for this; it is embrassing for me having still to edit their files to produce a PDF in my Linux system. A warning would suffice; is there a way to convert an error into a warning? -- Francisco Vila. Badajoz (Spain) www.paconet.org www.csmbadajoz.com ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: BOM mark from Windows notepad
On 2009-11-11, Francisco Vila wrote: > Hello. When LilyPond for Linux encounters a BOM from files made with > the Windows notepad, it issues an error. Has this always been the case, or is this a new issue with 2.13.7? > I think it should continue making the PDF anyway, because the file has > an otherwise correct syntax; what do you think? Yes, definitely. The BOM is permitted by the UTF-8 spec, so an error should not be issued. Thanks, Patrick ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
BOM mark from Windows notepad
Hello. When LilyPond for Linux encounters a BOM from files made with the Windows notepad, it issues an error. I think it should continue making the PDF anyway, because the file has an otherwise correct syntax; what do you think? -- Francisco Vila. Badajoz (Spain) www.paconet.org www.csmbadajoz.com ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
