Hi Chris,
> I tried editing the feta mf sources, but I
> can't seem to get the modified fonts to load into lilypond (2.11.20).
> i.e. I've edited "feta11.mf", saved as feta11.svg and replaced the
> default one in the lilypond installation, but a lilypond score with
> #(set-global-staff-size 11.22)
Hello,
I'm excited to see people working on arrowed accidentals. I could
really use this feature. I tried editing the feta mf sources, but I
can't seem to get the modified fonts to load into lilypond (2.11.20).
i.e. I've edited "feta11.mf", saved as feta11.svg and replaced the
default one in th
On 2/4/07, Maximilian Albert <[EMAIL PROTECTED]> wrote:
Hi everyone,
motivated by Orm's proposal to make arrowed accidental glyphs available,
I have started a few experiments with the feta mf-sources. They seem to
be quite promising, and I think that we will soon be able to provide the
"arrowed"
Maximilian Albert escreveu:
> Wow, that was both very fast and very helpful. Thanks a lot, Han-Wen!
>
>> I think it's best if all arrowheads have the same size.
>
> That was my plan anyway. This is all still very experimental.
>
>> Also, the brushed stem with the arrowed flat looks awkward. I'd
Wow, that was both very fast and very helpful. Thanks a lot, Han-Wen!
> I think it's best if all arrowheads have the same size.
That was my plan anyway. This is all still very experimental.
> Also, the brushed stem with the arrowed flat looks awkward. I'd also
> try making it straight.
Even if
Maximilian Albert escreveu:
> For purposes of illustration, I attached a small example of the glyphs
> in (one of) their current preliminary shape(s). Please note that the
> arrowheads of the flat signs are larger (resp. smaller when pointing
> down) than those of the sharp signs because their size
Hi everyone,
motivated by Orm's proposal to make arrowed accidental glyphs available,
I have started a few experiments with the feta mf-sources. They seem to
be quite promising, and I think that we will soon be able to provide the
"arrowed" style as an alternative -- for a suitable meaning of "soo
On Mon, 29 Jan 2007, Han-Wen Nienhuys wrote:
. So it seems that the use of "Accidental #'style" is deprecated and one
should set the alteration-alist directly. (But changing the style
property still works in v2.11.13, even if I don't know why, given that I
couldn't find the code handling it). Wh
Han-Wen Nienhuys wrote:
Maximilian Albert escreveu:
. So it seems that the use of "Accidental #'style" is deprecated and one
should set the alteration-alist directly. (But changing the style
property still works in v2.11.13, even if I don't know why, given that I
couldn't find the code handli
Maximilian Albert escreveu:
> Orm Finnendahl schrieb:
>
>> 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 c
I don't really see the problem. What you already have proposed is to
use property settings to change between the different styles. To save
some typing, it will then be easy to add macros such as
\arrowQuarterToneAccidentals (please make up something shorter)
and \...whatever, to easily change betw
Hi,
we use additional simple up/down arrows placed left to normal
accidentals, giving a concise way to specify the complete eighth tone
scale. The glyphs are actually included in the font. This would make
even more changing of alteration syntax necessary, though.
I don't mind to be able to combin
I agree %100 with the addition of accidentals with arrows. However, I also
think that both, the standard 1/4 and 3/4 tone signs Lilypond already has
and the new ones should both be accessible, and, ideally, within the same
"notehead-style". Otherwise combining them in a single score would require
Orm Finnendahl schrieb:
> 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).
Well, I'd be de
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
On Sun, 28 Jan 2007, Juergen Reuter wrote:
...
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
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
On 1/27/07, Orm Finnendahl <[EMAIL PROTECTED]> 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
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
On 1/27/07, Orm Finnendahl <[EMAIL PROTECTED]> wrote:
Hi,
for a while I wanted to suggest adding the option of using a different
style for microtone accidentals. I personally prefer the use of up or
down arrows on extended vertical lines of the standard accidentals
(see attached example). The ad
Am 27. Januar 2007, 15:33 Uhr (+0100) schrieb Ole Schmidt:
> Hi,
>
> I did not understand if these accidentals are already implemented so
> that I can use them? If not, I'am interested strongly in using them,
> they are indeed much easier to read and to handle...
No, They aren't implemented
Hi,
for a while I wanted to suggest adding the option of using a different
style for microtone accidentals. I personally prefer the use of up or
down arrows on extended vertical lines of the standard accidentals
(see attached example). The advantage of this style is a better
differentiation of enh
22 matches
Mail list logo
