LGTM
https://codereview.appspot.com/217260043/
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
Am 25.03.2015 um 18:58 schrieb Carl Sorensen:
On 3/25/15 6:54 AM, "u...@openlilylib.org" wrote:
I think the fonts we're looking for should have a similarly classic or
old-fashioned look as Century.
Maybe we should look for fonts that (optionally) ship with texlive.
Hunting around for sans
Hello,
Here is the current patch countdown list. The next countdown will be on
March 28th.
You can always view the most current countdown list here:
http://code.google.com/p/lilypond/issues/list?q=Patch%3Apush%2Ccountdown%2Creview%2Cnew%2Cwaiting&colspec=Patch%20Owner%20ID%20Summary&sort=patch
_
Patch on countdown for March 28th
https://codereview.appspot.com/220090043/
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
On 03/25/2015 06:58 PM, Carl Sorensen wrote:
On 3/25/15 6:54 AM, "u...@openlilylib.org" wrote:
I think the fonts we're looking for should have a similarly classic or
old-fashioned look as Century.
Maybe we should look for fonts that (optionally) ship with texlive.
[...]
I think that the foll
Am 25.03.2015 um 18:58 schrieb Carl Sorensen:
On 3/25/15 6:54 AM, "u...@openlilylib.org" wrote:
I think the fonts we're looking for should have a similarly classic or
old-fashioned look as Century.
Maybe we should look for fonts that (optionally) ship with texlive.
Hunting around for sans
On 3/25/15 6:54 AM, "u...@openlilylib.org" wrote:
>I think the fonts we're looking for should have a similarly classic or
>old-fashioned look as Century.
>
>Maybe we should look for fonts that (optionally) ship with texlive.
Hunting around for sans-serif fonts that work well with CenturySchool
On 2015/03/25 05:35:28, ul_openlilylib.org wrote:
>Well, it's not much code of course. Would it even be reloaded?
>Anyway,
>I wonder if "redundant" use-modules invocations should be removed, or
>at
>least reduced to comments.
Scheme modules are loaded only once so thee is no overhead involv
https://codereview.appspot.com/217260043/diff/1/scm/output-lib.scm
File scm/output-lib.scm (right):
https://codereview.appspot.com/217260043/diff/1/scm/output-lib.scm#newcode165
scm/output-lib.scm:165: (use-modules (ice-9 pretty-print))
On 2015/03/24 21:58:28, thomasmorley651 wrote:
I always re
Am 25.03.2015 um 13:32 schrieb Carl Sorensen:
On 3/25/15 3:06 AM, "Urs Liska" wrote:
2) Find suitable fonts and include them in the distribution
I know this is a more difficult issue than 1) but I think it would be
worth it. By default LilyPond scores don't use sans or monospace (IISC)
but
>> So that’s probably a matter of the font, not of its style - not every font
>> defines ligatures, and the name „TakaoPGothic“ tells me its main focus would
>> be Japanese (is this true?), so the designers probably didn’t put so much
>> work in features of Latin script.
>>
>> Would you care to
Masamichi HOSODA writes:
>> So that’s probably a matter of the font, not of its style - not
>> every font defines ligatures, and the name „TakaoPGothic“ tells me
>> its main focus would be Japanese (is this true?), so the designers
>> probably didn’t put so much work in features of Latin script.
> So that’s probably a matter of the font, not of its style - not every font
> defines ligatures, and the name „TakaoPGothic“ tells me its main focus would
> be Japanese (is this true?), so the designers probably didn’t put so much
> work in features of Latin script.
>
> Would you care to try a
>>> Chord names are Sans Serif I think.
>>
>> A yes, that's right. And IIRC there is sort of an agreement that
>> they are not the most appealing part of LilyPond's default
>> appearance ...
>
> Very much so. And if that happened because Pango picks a default
> system font, I would not really be
Urs Liska writes:
> Am 25.03.2015 um 10:36 schrieb David Kastrup:
>> Urs Liska writes:
>>
>>> 2) Find suitable fonts and include them in the distribution
>>> I know this is a more difficult issue than 1) but I think it would be
>>> worth it. By default LilyPond scores don't use sans or monospace
Urs Liska writes:
> 2) Find suitable fonts and include them in the distribution
> I know this is a more difficult issue than 1) but I think it would be
> worth it. By default LilyPond scores don't use sans or monospace
> (IISC)
Chord names are Sans Serif I think.
> but I think LilyPond should a
Am 25.03.2015 um 10:36 schrieb David Kastrup:
Urs Liska writes:
2) Find suitable fonts and include them in the distribution
I know this is a more difficult issue than 1) but I think it would be
worth it. By default LilyPond scores don't use sans or monospace
(IISC)
Chord names are Sans Seri
Am 25.03.2015 um 09:35 schrieb David Kastrup:
Urs Liska writes:
Am 25.03.2015 um 09:01 schrieb Werner LEMBERG:
We don't use any particular font for sans-serif and
monospace. LilyPond simply calls the OS's default here. Which is
something I'd like to raise (once more?): Would it be an optio
At 00:03 on 25 Mar 2015, Thomas Morley wrote:
>I disagree.
>\set Score.skipBars = ##t _is_ intended to affect notes _and_ useful!
>Don't limit your thoughts to modern music.
>
>Below I retyped (quick'n dirty) the last bar from Missa Papae
>Marcelli, Sanctus by Palestrina taken from an edition which
Sorry, this had accidentally gone private ...
Weitergeleitete Nachricht
Betreff:Re: Ghostscript 9.15
Datum: Wed, 25 Mar 2015 09:31:49 +0100
Von:David Kastrup
An: Urs Liska
Urs Liska writes:
Am 25.03.2015 um 08:51 schrieb David Kastrup:
Urs Liska write
Urs Liska writes:
> Am 25.03.2015 um 09:01 schrieb Werner LEMBERG:
We don't use any particular font for sans-serif and
monospace. LilyPond simply calls the OS's default here. Which is
something I'd like to raise (once more?): Would it be an option to
find suitable complementi
Am 25.03.2015 um 09:01 schrieb Werner LEMBERG:
We don't use any particular font for sans-serif and
monospace. LilyPond simply calls the OS's default here. Which is
something I'd like to raise (once more?): Would it be an option to
find suitable complementing fonts here, ship them with LilyPond
>> We don't use any particular font for sans-serif and
>> monospace. LilyPond simply calls the OS's default here. Which is
>> something I'd like to raise (once more?): Would it be an option to
>> find suitable complementing fonts here, ship them with LilyPond and
>> make them the default?
>
> As
Urs Liska writes:
> Am 25.03.2015 um 07:50 schrieb David Kastrup:
>>> So that’s probably a matter of the font, not of its style - not every
>>> >font defines ligatures, and the name „TakaoPGothic“ tells me its main
>>> >focus would be Japanese (is this true?), so the designers probably
>>> >didn’
Am 25.03.2015 um 07:50 schrieb David Kastrup:
So that’s probably a matter of the font, not of its style - not every
>font defines ligatures, and the name „TakaoPGothic“ tells me its main
>focus would be Japanese (is this true?), so the designers probably
>didn’t put so much work in features of
25 matches
Mail list logo
