Hi,
OK, if you think so.
As it stands, I have implemented notes (inc. chords) and rests.
Currently, the note engraver spits out Braille each timestep, and collects all note events within that timestep. If there is more than one note event in the timestep, it constructs a chord out of them.
This actually covers a large proportion of what I need to set up a framework for Braille rendering. I have encapsulated the main Braille code in a covering class called Braille and derived my engraver classes from that and Engraver. So far, I have been able to map all the braille to their respective note events.
However, in doing multi-voice music, the voices are split up, and the notes are rendered in a way that makes this impossible to continue.
The reason I asked the question was that it grieved me to depart from a framework that has worked fine so far. I've looked ahead in the Braille standard and it seems to me that multi-voice rendering is the only "fly in the ointment" so-to-speak, so it would be good to get this tackled now rather than later.
Regards,
Ralph
-----Original Message-----
From: Han-Wen Nienhuys [mailto:[EMAIL PROTECTED]]
Sent: Sun 02/05/2004 22:08
To: Ralph Little
Cc: [EMAIL PROTECTED]
Subject: Way to go.
[EMAIL PROTECTED] writes:
i> To get around this, I was going to collect the notes for each voice in
> the Braille_note_engraver separately in BrailleVoice, then at the end of
> the measure, copy these strings to the end of a property in the
> BrailleStaff parent context, and get an engraver in BrailleStaff
> (Braille_measure_engraver) to actually put the text together for the
> measure.
>
> This method sounds a bit mad, but I cannot think of a better way to do
> this.
That sounds like a viable method, but I would postpone handling it
when you have monophonic braille support fully going.
--
Han-Wen Nienhuys | [EMAIL PROTECTED] | http://www.xs4all.nl/~hanwen
Tribal Data Solutions has moved, please visit our website for more details http://www.tribaldata.co.uk.
This e-mail and any attachments are confidential and are sent on the basis of our copyright, e-mail and security policy which can be inspected by visiting http://www.tribaldata.co.uk/policies.asp.
If you are not the intended recipient, please notify the sender and delete this message. Thank you.
_______________________________________________ lilypond-devel mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/lilypond-devel
