Hi Keith,
my reactions are between the lines
> Maurits Lamers weidestraat.nl> writes:
>
>> I might be wrong, but I don't think creating a separate Braille context
> will work, as it would require the
>> same music to be defined twice, one as normal music and one as Braille.
>
> I do not know
Maurits Lamers weidestraat.nl> writes:
> I might be wrong, but I don't think creating a separate Braille context
will work, as it would require the
> same music to be defined twice, one as normal music and one as Braille.
I do not know what you mean by 'defining' the music, but I suspect you
c
Hi Keith,
Thanks for answering!
After reading your reply I became aware that I didn't mention that the way of
triggering the Braille output should be similar to the way midi export is done,
for example in the form of a \braille tag.
I might be wrong, but I don't think creating a separate Brail
Maurits Lamers weidestraat.nl> writes:
> This is a new initiative to bring Braille music output to Lilypond.
Maybe let LilyPond read the input, iterate through the timing, and
prepare the music streams as she does to send to each context such
as 'Staff'.
You might make a new context(s) ('Brail
Hi all,
This subject has already been discussed a quite a few times on this list and
other lists in the past.
This is a new initiative to bring Braille music output to Lilypond. I have been
asked by a few Dutch organisations for people with a visual handicap to look
into how much work it would
