[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: GSoC 2017
From: |
Urs Liska |
Subject: |
Re: GSoC 2017 |
Date: |
Mon, 6 Mar 2017 23:22:07 +0100 |
User-agent: |
Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Icedove/45.6.0 |
Am 06.03.2017 um 23:16 schrieb tisimst:
> On Mon, Mar 6, 2017 at 2:34 PM, Noeck [via Lilypond] <
> address@hidden> 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
>> name. So pretty much all you could do without touching lilypond directly.
>> I guess for the GSoC the approach would be quite different and I hope
>> Abraham can point into the right direction.
>>
> Personally, I think there's not much more that can be done with what is
> already in OLL, but I don't think that's what we want done anyway. Full
> SMuFL integration would be a more substantial improvement, IMHO.
Indeed. We want to make that OLL approach obsolete by not only
"supporting" SMuFL natively but by switching completely to *using* it as
LilyPond's notation font encoding.
Urs
>
> Best,
> Abraham
>
>
>
>
> --
> View this message in context:
> http://lilypond.1069038.n5.nabble.com/GSoC-2017-tp200631p200799.html
> Sent from the Dev mailing list archive at Nabble.com.
> _______________________________________________
> lilypond-devel mailing list
> address@hidden
> https://lists.gnu.org/mailman/listinfo/lilypond-devel
--
address@hidden
https://openlilylib.org
http://lilypondblog.org
- Re: GSoC 2017, (continued)
- Re: GSoC 2017, Werner LEMBERG, 2017/03/06
- Re: GSoC 2017, Urs Liska, 2017/03/06
- Re: GSoC 2017, tisimst, 2017/03/06
- Re: GSoC 2017, Urs Liska, 2017/03/06
- Re: GSoC 2017, tisimst, 2017/03/06
- Re: GSoC 2017, Urs Liska, 2017/03/06
- Re: GSoC 2017, Werner LEMBERG, 2017/03/11
- Font loading (was: GSoC 2017), Urs Liska, 2017/03/11
- Re: GSoC 2017, Noeck, 2017/03/06
- Re: GSoC 2017, tisimst, 2017/03/06
- Re: GSoC 2017,
Urs Liska <=
- Re: GSoC 2017, Werner LEMBERG, 2017/03/06