> 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
Urs Liska writes:
> Am 23.03.2015 um 17:30 schrieb David Kastrup:
>> Ok thanks. If you want to have more of a go at reproducing the problem,
>> it's clearly also related to the use of \include, possibly in connection
>> with some
>> #(ly:parser-[whatever] "\\include ...")
>> call. It may be th
Am 23.03.2015 um 17:30 schrieb David Kastrup:
Urs Liska writes:
Am 23.03.2015 um 17:18 schrieb David Kastrup:
Urs Liska writes:
Hi David,
thank you for taking the time looking into this.
Am 23.03.2015 um 10:19 schrieb David Kastrup:
Urs Liska writes:
Well, I do have a minimal examp
Urs Liska writes:
> Am 23.03.2015 um 17:18 schrieb David Kastrup:
>> Urs Liska writes:
>>
>>> Hi David,
>>>
>>> thank you for taking the time looking into this.
>>>
>>> Am 23.03.2015 um 10:19 schrieb David Kastrup:
Urs Liska writes:
> Well, I do have a minimal example outlining wh
Am 23.03.2015 um 17:18 schrieb David Kastrup:
Urs Liska writes:
Hi David,
thank you for taking the time looking into this.
Am 23.03.2015 um 10:19 schrieb David Kastrup:
Urs Liska writes:
Well, I do have a minimal example outlining what I want to do, but
"unfortunately" this works exact
Urs Liska writes:
> Hi David,
>
> thank you for taking the time looking into this.
>
> Am 23.03.2015 um 10:19 schrieb David Kastrup:
>> Urs Liska writes:
>>
>>> Well, I do have a minimal example outlining what I want to do, but
>>> "unfortunately" this works exactly as expected:
>>>
>>> \version
Hi David,
thank you for taking the time looking into this.
Am 23.03.2015 um 10:19 schrieb David Kastrup:
Urs Liska writes:
Well, I do have a minimal example outlining what I want to do, but
"unfortunately" this works exactly as expected:
\version "2.19.16"
testDotList =
#(define-void-func
>>> 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
Urs Liska writes:
> Well, I do have a minimal example outlining what I want to do, but
> "unfortunately" this works exactly as expected:
>
> \version "2.19.16"
>
> testDotList =
> #(define-void-function (parser location opts path)
>((ly:context-mod?) list?)
>(for-each
> (lambda (p)
> 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.
_
11 matches
Mail list logo