[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: proposal: second style for quartertone accidentals
From: |
Orm Finnendahl |
Subject: |
Re: proposal: second style for quartertone accidentals |
Date: |
Sun, 28 Jan 2007 09:27:43 +0100 |
User-agent: |
Mutt/1.5.12-2006-07-14 |
Hi all,
thanks for pointing that out. That's exactly along the lines I was
thinking. Is anybody capable of doing the scheme/lilypond code? I
don't know Metafont yet but I think I could handle that part and throw
in the glyphs (they are currently PS Type1).
--
Orm
Am 28. Januar 2007, 05:19 Uhr (+0100) schrieb Juergen Reuter:
> Hi, all!
>
> Please note that we already have a style property for Accidental grobs.
> For example, for yielding ancient notation accidentals, you may say:
>
> \override Accidental #'style = #'vaticana
>
> Hence, the natural way is to introduce another style for
> different microtonal glyphs. They are not present in standard western
> europe ancient notation and therefore do not collide with ancient
> accidental styles. Hence, it is natural to introduce a new Accidental
> style, say, for example:
>
> \override Accidental #'style = #'arrowed
>
> or maybe even better
>
> \override Accidental #'style = #'default-arrowed
>
> to indicate that the non-microtonal accidentals are still to be taken
> from the default font, i.e. default and default-arrowed only differ in
> microtonal glyphs.
>
> Unfortunately, the code for checking and handling the Accidental style
> property is still hardcoded in lily/accidental.cc in method
>
> string
> Accidental_interface::get_fontcharname (string style, int alteration)
>
> rather than being handled at runtime through scheme code, as is done with
> notehead style in the scheme function note-head::calc-glyph-name in file
> scm/output-lib.scm.
>
> The input syntax ("aeh", "aesih", "gisih", etc.) should probably be
> independent from the above selection of glyphs, as we usually try to
> strictly separate musical content and engraving style. Considering this
> principle, maybe the right thing is -- similarly to including proper
> internationalized notenames -- the user to \include his/her favourite
> naming scheme at the beginning of the user's .ly file.
>
> Greetings,
> Juergen
>
>
> On Sat, 27 Jan 2007, Trevor Ba?~Ma wrote:
>
> >On 1/27/07, Orm Finnendahl <address@hidden> wrote:
> >>Am 27. Januar 2007, 12:06 Uhr (-0600) schrieb Trevor Bača:
> >>>
> >>> Question: would it be possible to have access to *both* sets of
> >>> glyphs? It seems to me that I've seen both types of glyphs mixed
> >>> together in single scores; usually the existing quartertone glyphs
> >>> show exact quartertone alterations while the arrowed glyphs show
> >>> approximate alterations.
> >>>
> >>
> >>Well, my proposal meant to be completely backwards compatible. I
> >>thought about something similar to the "notehead-style" property like
> >>saying
> >>
> >>\override #'accidental-style = "arrowed"
> >>
> >>for getting the arrowed accidentals and
> >>
> >>\revert #'accidental-style
> >>
> >>for switching back.
> >
> >Ah, OK. I very much vote yes. I've wanted the arrowed glyphs for quite
> >some time and would like to see them as part of the standard
> >distribution.
> >
> >
> >
> _______________________________________________
> lilypond-devel mailing list
> address@hidden
> http://lists.gnu.org/mailman/listinfo/lilypond-devel
- proposal: second style for quartertone accidentals, Orm Finnendahl, 2007/01/27
- Re: proposal: second style for quartertone accidentals, Trevor Bača, 2007/01/27
- Re: proposal: second style for quartertone accidentals, v!ctor address@hidden, 2007/01/28
- Re: proposal: second style for quartertone accidentals, Orm Finnendahl, 2007/01/29
- Re: proposal: second style for quartertone accidentals, Mats Bengtsson, 2007/01/29