On Thu, Nov 19, 2009 at 8:47 AM, Patrick McCarty pnor...@gmail.com 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
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
2009/11/19 Hans Aberg hab...@math.su.se:
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
2009/11/19 Patrick McCarty pnor...@gmail.com:
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
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
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
On 2009-11-13, Hans Aberg wrote:
On 13 Nov 2009, at 12:25, Bertalan Fodor (LilyPondTool) wrote:
INITIAL,chords,lyrics,figures,notes{BOM_UTF8}/.* {
if (this-lexloc-line_number () != 1 ||
this-lexloc-column_number () != 0)
{
LexerError (_ (stray UTF-8 BOM encountered).c_str ());
exit
On Thu, Nov 19, 2009 at 12:41 AM, Patrick McCarty pnor...@gmail.com 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
___
On 2009-11-19, Valentin Villenave wrote:
On Thu, Nov 19, 2009 at 12:41 AM, Patrick McCarty pnor...@gmail.com 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
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
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
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
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
Hehe, we've got this:
INITIAL,chords,lyrics,figures,notes{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
On 13 Nov 2009, at 12:25, Bertalan Fodor (LilyPondTool) wrote:
Hehe, we've got this:
INITIAL,chords,lyrics,figures,notes{BOM_UTF8}/.* {
if (this-lexloc-line_number () != 1 || this-lexloc-column_number
() != 0)
{
LexerError (_ (stray UTF-8 BOM encountered).c_str ());
exit (1);
On 13 Nov 2009, at 12:25, Bertalan Fodor (LilyPondTool) wrote:
INITIAL,chords,lyrics,figures,notes{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
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
2009/11/11 Patrick McCarty pnor...@gmail.com:
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
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
Hans Aberg hab...@math.su.se 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
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:
U+FEFF\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
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
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
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
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
2009/11/11 Patrick McCarty pnor...@gmail.com:
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
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?
On Wed, Nov 11, 2009 at 11:57 AM, Francisco Vila paconet@gmail.com wrote:
2009/11/11 Patrick McCarty pnor...@gmail.com:
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
On Wed, Nov 11, 2009 at 1:53 PM, Bertalan Fodor (LilyPondTool)
lilypondt...@organum.hu 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
29 matches
Mail list logo
