GSoC 2017 - Improve internal chord structure

Hello! My name is Diogo Canut, a computer science student at Federal University of Uberlandia. I am interested in improve internal chord structure project for Google Summer of Code. I have a background with functional languages like Haskell and Common Lisp. I already builded the lilypound

Interested in GsoC 2017

Hello, I am interested in applying to Google Summer of Code and in contributing to LilyPond this summer. Specifically, I'm intrigued by improving internal chord structure as listed on the project ideas page, and I was wondering if anyone could give me some advice as to familiarizing myself with

Font loading (was: GSoC 2017)

Am 11. März 2017 12:48:55 MEZ schrieb Werner LEMBERG : >> 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

Re: GSoC 2017

> 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

Re: GSoC 2017

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

Re: GSoC 2017

handle fonts that only have a single size and those that have multiple sizes? -- View this message in context: http://lilypond.1069038.n5.nabble.com/GSoC-2017-tp200631p200805.html Sent from the Dev mailing list archive at Nabble.com. ___ lilypond-devel

Re: GSoC 2017

New Roman. I think the implication for GSoC is: If we don't find a solution to fix this issue (maybe fontconfig has been updated in the meantime, or we can convince the developers to do something about it) we will probably have to load the SMuFL fonts from the LilyPon

Re: GSoC 2017

> 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

Re: GSoC 2017

ng 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. >

Re: GSoC 2017

st, 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 lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: GSoC 2017

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.

Re: GSoC 2017

pointing to them. SMuFL fonts are installed in the system font folder just like any normal text font. Those are just some thoughts to keep the conversation going. Best, Abraham [1] https://w3c.github.io/smufl/gitbook/ -- View this message in context: http://lilypond.1069038.n5.nabble.com

Re: Obsolete GSoC page (was: GSoC 2017)

Il giorno lun 6 mar 2017 alle 7:20, Urs Liska ha scritto: Am 06.03.2017 um 05:02 schrieb Werner LEMBERG: PS: If I do a google search for `lilypond gsoc', the first hit is the old http://lilypond.org/gsoc.html and only the second hit is the

Re: GSoC 2017

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,

Re: GSoC 2017

>> 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.

Re: GSoC 2017

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

Obsolete GSoC page (was: GSoC 2017)

Am 06.03.2017 um 05:02 schrieb Werner LEMBERG: > PS: If I do a google search for `lilypond gsoc', the first hit is the > old > > http://lilypond.org/gsoc.html > > and only the second hit is the current > > http://lilypond.org/google-summer-of-code.html > > Any chance to

Re: GSoC 2017

>> 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

GSoC 2017

Hello everyone! My name is Matthew Sedam, and I am interested in LillyPond for Google Summer of Code 2017. I am particularly interested in the "Adopt the SMuFL music font encoding standard" idea. I would like to know what progress, if any, has been done on this project. I also would appreciate

GSoC 2017

Dear LilyPond community, I'm happy to inform you that both LilyPond (as part of GNU) and Frescobaldi have been accepted as mentoring organizations for Google Summer of Code 2017 :-) This means we have the chance to get up to four (realistically) students to work on improving LilyPond and