2013/12/1 Federico Bruni :
> 2013/12/1 Amreg
>
>> % | <>^\markup { D.S. al Coda } }
>> [...]
>>
>> If you look at the last line above, you'll notice that braces are not
>> balanced. If you were to uncomment this example case, you'll get an error.
>>
>
> thanks for the report
> I won't open
2013/12/1 Amreg
> % | <>^\markup { D.S. al Coda } }
> [...]
>
> If you look at the last line above, you'll notice that braces are not
> balanced. If you were to uncomment this example case, you'll get an error.
>
thanks for the report
I won't open an issue for this minor problem (it does
Le 29/11/2013 22:53, Nigel Kench a écrit :
Good evening, I found an error in the syntax of a Snippet for the following
section of the manual:
I just would like to mention another Snippet bug (which lasts for long,
it was already present in 2.16, 2.14, and maybe even before...).
Snippet : "P
>> Please test the attached patch.
>
> Correct me if I'm wrong, but isn't that a critical issue regarding
> the usability of our PDF files?
It's not critical, AFAIK. In PDF files, only the `emmentaler'
OpenType fonts are used, and we don't refer to any subfont. Missing
glyphs would be critical,
Jay Anderson wrote
> As long as your command line is 'lilypond file.ly' and the eps file is
> imported from file.ly. What's the correct way to get the name of the
> current file? I looked for a little while, but couldn't figure it out.
no idea.
but while we're at these relative includes - I think
2013/12/1 David Kastrup
> Correct me if I'm wrong, but isn't that a critical issue regarding the
> usability of our PDF files? Why has this not been entered into the
> tracker?
>
just added: https://code.google.com/p/lilypond/issues/detail?id=3695
___
Werner LEMBERG writes:
>> Now, for recent versions of emmentaler (same font file), LILC contains:
>> (subfont . "feta20")
>> (subfont . "feta-alphabet20")
>> (subfont . "feta-flags20")
>> (subfont . "feta-noteheads20")
>> (subfont . "parmesan20")
>> (subfont . "parmesan-noteheads20")
