The correct way to do this, which incidentally lily uses, is to use
binary search over the glyphs, until you've found the closest one.
On Sat, Nov 29, 2008 at 6:19 PM, Mats Bengtsson
<[EMAIL PROTECTED]> wrote:
> Quoting Neil Puttock <[EMAIL PROTECTED]>:
>
>> 2008/11/28 Mats Bengtsson <[EMAIL PROTE
Quoting Neil Puttock <[EMAIL PROTECTED]>:
2008/11/28 Mats Bengtsson <[EMAIL PROTECTED]>:
Mats Bengtsson wrote:
Now that I've looked a bit more careful, I see that the total height of
braceN is given by
10.5*(1+1/150)^N
so in other words, if the desired height is H, you can get the number of
2008/11/28 Mats Bengtsson <[EMAIL PROTECTED]>:
>
>
> Mats Bengtsson wrote:
>
> Now that I've looked a bit more careful, I see that the total height of
> braceN is given by
> 10.5*(1+1/150)^N
> so in other words, if the desired height is H, you can get the number of the
> corresponding
> brace glyph
Mats Bengtsson wrote:
It would be nice if the argument was the desired height measured in
points (or perhaps in staff spaces)
instead of the current numerical argument where you need a lot of
trial and error.
If it was in points, then you could easily relate it to the height of
one staff, whi
It would be nice if the argument was the desired height measured in
points (or perhaps in staff spaces)
instead of the current numerical argument where you need a lot of trial
and error.
If it was in points, then you could easily relate it to the height of
one staff, which is 20pt by default.
]>; "Lily-Devel List"
Sent: Friday, November 28, 2008 12:06 AM
Subject: Re: Using \lookup to extract glyphs
2008/11/27 Trevor Daniels <[EMAIL PROTECTED]>:
Valentin Villenave wrote Thursday, November 27, 2008 8:41 AM
... either two commands with the size as an argu
2008/11/27 Trevor Daniels <[EMAIL PROTECTED]>:
>
> Valentin Villenave wrote Thursday, November 27, 2008 8:41 AM
>> ... either two commands with the size as an argument,
>>
>> \left-brace #20
>> \right-brace #40
>
> This is my preference. The functions would need to check
> the size for validity,
[This is a rather long email with a lot of technical details, covering
much more than just \lookup. I spent almost two days with writing
due to the necessary research in the lilypond sources since I'm not
very acquainted with those tricky details. If you are interested in
lilypond's font han
Quoting Trevor Daniels <[EMAIL PROTECTED]>:
Valentin Villenave wrote Thursday, November 27, 2008 8:41 AM
2008/11/27 Neil Puttock <[EMAIL PROTECTED]>:
How about \left-brace and (rotated) \right-brace? This would make it
much simpler to embed them within text that has font-name overrides.
Valentin Villenave wrote Thursday, November 27, 2008 8:41 AM
2008/11/27 Neil Puttock <[EMAIL PROTECTED]>:
How about \left-brace and (rotated) \right-brace? This would make it
much simpler to embed them within text that has font-name overrides.
Great idea!
I agree.
... either two comma
2008/11/27 Neil Puttock <[EMAIL PROTECTED]>:
> How about \left-brace and (rotated) \right-brace? This would make it
> much simpler to embed them within text that has font-name overrides.
Great idea!
... either two commands with the size as an argument,
\left-brace #20
\right-brace #40
either
I2008/11/25 Trevor Daniels <[EMAIL PROTECTED]>:
> AFAICS the only fonts immediately available to \lookup which are not more
> easily accessible via \musicglyph are the myriad of braces of different
> sizes. The Internal Reference suggests that font-encoding may be set to
> fetaMusic, fetaNumber, T
AFAICS the only fonts immediately available to \lookup which are not more
easily accessible via \musicglyph are the myriad of braces of different
sizes. The Internal Reference suggests that font-encoding may be set to
fetaMusic, fetaNumber, TeX-text, TeX-math, fetaBraces, fetaDynamic, but the
13 matches
Mail list logo
