lilypond-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

address@hidden [Bug 692241] pdf creation fails with Error: /typecheck in


From: Jan Nieuwenhuizen
Subject: address@hidden [Bug 692241] pdf creation fails with Error: /typecheck in --readonly-- with sans font windows 7 SP1
Date: Sat, 28 May 2011 23:59:57 +0200
User-agent: Gnus/5.110018 (No Gnus v0.18) Emacs/23.2 (gnu/linux)

re: bug http://code.google.com/p/lilypond/issues/detail?id=1562

Hi Werner,

It seems as if LilyPond is erroneously using glyph names with a
spaces in it (when using the sans font on windows 7 sp1).

Before I try removing spaces from glyph names; I presume that these
names come from freetype (either that or lily does something really
stupid), does this ring a bell somewhere?

Greetings, Jan


--- Begin Message --- Subject: [Bug 692241] pdf creation fails with Error: /typecheck in --readonly-- with sans font windows 7 SP1 Date: Sat, 28 May 2011 21:34:39 +0000 (UTC)
http://bugs.ghostscript.com/show_bug.cgi?id=692241

Chris Liddell <address@hidden> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
                 CC|                            |address@hidden
         Resolution|                            |INVALID

--- Comment #3 from Chris Liddell <address@hidden> 2011-05-28 21:34:38 UTC ---
Definitely not a Ghostscript problem.

If you look at line 8271 of the non-working file, it looks like:
/pi 570 def /glyph 571 571 def /glyph 572 572 def /glyph573 573 def /uni2074
574 def


compared with the equivalent line from the working file:
/pi 570 def /uniF006 571 def /uniF007 572 def /uniF008 573 def /uni2074 574 def



You'll note that the non-working file repeats the values for two key/value
pairs: 571 and 572, thus leaving two instances of the name /glyph on the top of
the stack at the end of the CharStrings definition. Judging by the definition
following those (/glyph573 573 def) I would assume that there are two spurious
spaces added, and that the line is intended to be:

/pi 570 def /glyph571 571 def /glyph572 572 def /glyph573 573 def /uni2074 574
def

With that change hand applied, the file runs without error and /looks/ right to
me (but I don't have LilyPond to view the intended appearance, so I can't be
totally sure).

-- 
Configure bugmail: http://bugs.ghostscript.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You reported the bug.


--- End Message ---

-- 
Jan Nieuwenhuizen <address@hidden> | GNU LilyPond http://lilypond.org
Freelance IT http://JoyofSource.com | AvatarĀ®  http://AvatarAcademy.nl  

reply via email to

[Prev in Thread] Current Thread [Next in Thread]