Hi,
> Op 2 sep. 2020, om 21:07 heeft David Kastrup het volgende
> geschreven:
>
> Maurits Lamers writes:
>
>> Hi,
>>
>>> convert-ly does text replacements. It is not a full parser. If text
>>> replacements are supposed to work, you need to write your text in a way
>>> that the replacement
David Kastrup writes:
> Maurits Lamers writes:
>
>> Hi,
>>
>>> convert-ly does text replacements. It is not a full parser. If text
>>> replacements are supposed to work, you need to write your text in a way
>>> that the replacement patterns cover. Stuff like putting # on one line
>>> and a
Maurits Lamers writes:
> Hi,
>
>> convert-ly does text replacements. It is not a full parser. If text
>> replacements are supposed to work, you need to write your text in a way
>> that the replacement patterns cover. Stuff like putting # on one line
>> and a corresponding opening paren on the
Hi,
> convert-ly does text replacements. It is not a full parser. If text
> replacements are supposed to work, you need to write your text in a way
> that the replacement patterns cover. Stuff like putting # on one line
> and a corresponding opening paren on the next line are just too weird
>
Maurits Lamers writes:
> Hi all,
>
> In order to have my braille generator not have to support Lilypond 2.14 I
> tried to upgrade my music library I am building this braille generator on.
>
> However, because of (a lot of) specific "hacks" on the layout, simply running
> convert-ly on the
Hi all,
In order to have my braille generator not have to support Lilypond 2.14 I tried
to upgrade my music library I am building this braille generator on.
However, because of (a lot of) specific "hacks" on the layout, simply running
convert-ly on the entire library doesn't completely finish
