Urs Liska writes:
> The issues discussed in this thread have quite diversified:
>
> - Updating GUB to a newer Ghostscript
> - Ligatures not being produced on all platforms
> - Updating Pango which solved this
> - Pango picking system fonts, resulting in unpredictable output
> - thinking about cho
Am 26.03.2015 um 16:12 schrieb David Kastrup:
Masamichi HOSODA writes:
I've succeed GUB's ``make lilypond'' by pango-1.28.3 in this branch.
https://github.com/trueroad/gub/tree/pango-1.28
I've checked again.
I've installed DejaVuSans to all environments.
linux-64 binary on Ubuntu 14.04
Masamichi HOSODA writes:
> I've succeed GUB's ``make lilypond'' by pango-1.28.3 in this branch.
> https://github.com/trueroad/gub/tree/pango-1.28
>
> I've checked again.
> I've installed DejaVuSans to all environments.
>
> linux-64 binary on Ubuntu 14.04 LTS 64 bit:
> linux-x86 binary on Ubun
Am 26.03.2015 um 15:55 schrieb Masamichi HOSODA:
I've succeed GUB's ``make lilypond'' by pango-1.28.3 in this branch.
https://github.com/trueroad/gub/tree/pango-1.28
I've checked again.
I've installed DejaVuSans to all environments.
linux-64 binary on Ubuntu 14.04 LTS 64 bit:
linux-x86
I've succeed GUB's ``make lilypond'' by pango-1.28.3 in this branch.
https://github.com/trueroad/gub/tree/pango-1.28
I've checked again.
I've installed DejaVuSans to all environments.
linux-64 binary on Ubuntu 14.04 LTS 64 bit:
linux-x86 binary on Ubuntu 14.04 LTS 64 bit:
linux-x86 binary o
Am 2015-03-26 um 00:11 schrieb Marc Hohl :
> Is there any recommendation whether to use sans serif fonts for chord names?
> I used the text font (serif) in the latest projects of mine where chord
> symbols were needed.
I don’t know, but I tried several fonts for chord names, and if you use a s
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 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
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
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
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
Henning Hraban Ramm writes:
> Am 2015-03-24 um 20:35 schrieb Masamichi HOSODA :
>
>> I've succeed to upgrade GUB's pango to 1.28.3.
>> https://github.com/trueroad/gub/tree/pango-1.28
>>
>> Then, I've checked some environments.
>> The results are following:
>>
>> linux-64 binary on Ubuntu 14.04
Am 2015-03-24 um 20:35 schrieb Masamichi HOSODA :
> I've succeed to upgrade GUB's pango to 1.28.3.
> https://github.com/trueroad/gub/tree/pango-1.28
>
> Then, I've checked some environments.
> The results are following:
>
> linux-64 binary on Ubuntu 14.04 LTS 64 bit:
>ligatured pdf is gener
>> I still suspect a Pango bug that has probably been fixed in the not
>> too distant past. What version are you using? Can you upgrade to the
>> most recent one? On my 32bit GNU/Linux I use a quite recent git
>> version of Pango, which should behave identically to the last release
>> (1.36.8),
>> linux-64: Ubuntu 14.04 LTS 64 bit
>> ligatured pdf is generated.
>>
>> linux-x86: Ubuntu 14.04 LTS 32 bit (minimal install, no GUI, console only)
>> non-ligatured pdf is generated.
>
> Ah, this is surprising, since up to now exactly the opposite behaviour
> was reported (this is, w
On Sun, Mar 22, 2015 at 8:44 PM, David Kastrup wrote:
> Masamichi HOSODA writes:
>
>> I've succeed to upgrade GUB's ghostscript to 9.15 in this branch.
>> https://github.com/trueroad/gub/tree/ghostscript-9.15
>>
>> I've succeed GUB's ``ma
> linux-64: Ubuntu 14.04 LTS 64 bit
> ligatured pdf is generated.
>
> linux-x86: Ubuntu 14.04 LTS 32 bit (minimal install, no GUI, console only)
> non-ligatured pdf is generated.
Ah, this is surprising, since up to now exactly the opposite behaviour
was reported (this is, working on
>>> Have you checked ligatures? I think we were able to correlate our
>>> ligature problems (don't know the issue right now) to the use of 64bit
>>> architecture. It may be related to GhostScript.
>>
>> I haven't.
>> Is it here?
>> http://code.google.com/p/lilypond/issues/detail?id=2656
>>
>> I'l
Masamichi HOSODA writes:
>> Have you checked ligatures? I think we were able to correlate our
>> ligature problems (don't know the issue right now) to the use of 64bit
>> architecture. It may be related to GhostScript.
>
> I haven't.
> Is it here?
> http://code.google.com/p/lilypond/issues/deta
> Have you checked ligatures? I think we were able to correlate our
> ligature problems (don't know the issue right now) to the use of 64bit
> architecture. It may be related to GhostScript.
I haven't.
Is it here?
http://code.google.com/p/lilypond/issues/detail?id=2656
I'll check it.
_
Masamichi HOSODA writes:
> I've succeed to upgrade GUB's ghostscript to 9.15 in this branch.
> https://github.com/trueroad/gub/tree/ghostscript-9.15
>
> I've succeed GUB's ``make lilypond'' by ghostscript-9.15.
> All lilypond installers have been bui
I've succeed to upgrade GUB's ghostscript to 9.15 in this branch.
https://github.com/trueroad/gub/tree/ghostscript-9.15
I've succeed GUB's ``make lilypond'' by ghostscript-9.15.
All lilypond installers have been build.
In mingw (Windows):
Ghostscript can handle
36 matches
Mail list logo
