> Here's a caveat (but I'm not sure if that relates to the GSoC
> project). Some time ago I worked on a modified system to load the
> notation font from system installed fonts too, which would
> substantially reduce the amount of housekeeping when using
> alternative notation fonts. But I got stu
Am 06.03.2017 um 23:46 schrieb tisimst:
> On Mon, Mar 6, 2017 at 3:34 PM, Urs Liska [via Lilypond] <
> ml-node+s1069038n200802...@n5.nabble.com> wrote:
>
>> Of course it is good to have optical sizes - even if the vast majority
>> of LilyPond users may not even be aware of it. And it's not depend
On Mon, Mar 6, 2017 at 3:34 PM, Urs Liska [via Lilypond] <
ml-node+s1069038n200802...@n5.nabble.com> wrote:
> Of course it is good to have optical sizes - even if the vast majority
> of LilyPond users may not even be aware of it. And it's not depending on
> the number of different sizes in a score
Am 06.03.2017 um 17:32 schrieb tisimst:
> On Mon, Mar 6, 2017 at 1:42 AM, ul [via Lilypond] <
> ml-node+s1069038n200762...@n5.nabble.com> wrote:
>
>>
>> Am 06.03.2017 um 07:44 schrieb Werner LEMBERG:
> Not yet :-) I can only second what Urs said.
I think we (i.e. Abraham and you) should
> 3. IIUC, this was just a set of overrides and callback functions
>picking up the correct symbols from a smufl font, doing the
>mapping by glyph name.
I think this helps already a lot – such a mapping has to be
implemented anyway, at least in `convert-ly'.
Werner
__
Am 06.03.2017 um 23:16 schrieb tisimst:
> On Mon, Mar 6, 2017 at 2:34 PM, Noeck [via Lilypond] <
> ml-node+s1069038n200797...@n5.nabble.com> wrote:
>
>> 3. IIUC, this was just a set of overrides and callback functions picking
>> up the correct symbols from a smufl font, doing the mapping by glyph
On Mon, Mar 6, 2017 at 2:34 PM, Noeck [via Lilypond] <
ml-node+s1069038n200797...@n5.nabble.com> wrote:
> 1. Nathan was coding this, I just included this into oll and wrote the
> post.
Correct.
> 2. I guess it still works.
>
Yep. Mostly without problems, but it does have its limitations.
>
Hi,
Am 06.03.2017 um 09:41 schrieb Urs Liska:
>> http://lilypondblog.org/2014/01/smufl-fonts-in-lilypond/
>>
>> I don't know whether this is still up to date.
> Oh, me neither.
> Joram?
1. Nathan was coding this, I just included this into oll and wrote the post.
2. I guess it still works.
3. II
On Mon, Mar 6, 2017 at 1:42 AM, ul [via Lilypond] <
ml-node+s1069038n200762...@n5.nabble.com> wrote:
>
>
> Am 06.03.2017 um 07:44 schrieb Werner LEMBERG:
> >>> Not yet :-) I can only second what Urs said.
> >> I think we (i.e. Abraham and you) should give Matthew some more
> >> concrete pointers
Am 06.03.2017 um 07:44 schrieb Werner LEMBERG:
>>> Not yet :-) I can only second what Urs said.
>> I think we (i.e. Abraham and you) should give Matthew some more
>> concrete pointers on where to start investigating.
> Can you send him our e-mail conversation regarding this topic?
> Currently, I
>> Not yet :-) I can only second what Urs said.
>
> I think we (i.e. Abraham and you) should give Matthew some more
> concrete pointers on where to start investigating.
Can you send him our e-mail conversation regarding this topic?
Currently, I'm abroad, not having time to do that by myself.
>
Hi Matthew,
Am 06.03.2017 um 05:02 schrieb Werner LEMBERG:
>
>> The first thing will be to get an idea about what happens when
>> LilyPond uses glyphs from the notation font. How does it locate the
>> font, how does it identify the glyph to choose? And on the other
>> side, how is the notation
>> I also would appreciate any help defining this project so I can
>> write an effective proposal. I am new to LillyPond development, but
>> I have used the program many years ago.
s/LillyPond/LilyPond/
> The first thing will be to get an idea about what happens when
> LilyPond uses glyphs from
13 matches
Mail list logo
