David Feuer wrote:
On 4/1/06, Han-Wen Nienhuys <[EMAIL PROTECTED]> wrote:
I suspect you may know more about postscript than me, your guess is as
good as mine; If you think it is bug, can you file a bug with
ghostscript development?
I can send you a file with an embedded CFF CID font.
I don't
On 4/1/06, Han-Wen Nienhuys <[EMAIL PROTECTED]> wrote:
> I suspect you may know more about postscript than me, your guess is as
> good as mine; If you think it is bug, can you file a bug with
> ghostscript development?
>
> I can send you a file with an embedded CFF CID font.
I don't actually know
David Feuer schreef:
On 3/31/06, Han-Wen Nienhuys <[EMAIL PROTECTED]> wrote:
According to the Postscript reference, selectfont can be used with CID
resources as well as regular fonts. Unfortunately, I can't make the
utf-8 regression test work either with or without my changes, so I
can't be su
On 3/31/06, Han-Wen Nienhuys <[EMAIL PROTECTED]> wrote:
> > According to the Postscript reference, selectfont can be used with CID
> > resources as well as regular fonts. Unfortunately, I can't make the
> > utf-8 regression test work either with or without my changes, so I
> > can't be sure I got
David Feuer wrote:
(format #f "gsave
- /~a ~a ~a output-scale div scalefont setfont\n~a grestore"
+ /~a ~a output-scale div selectfont\n~a grestore"
postscript-font-name
- (if cid?
- " /CIDFont findresource "
- " findfont")
I don't understand this?
> > But a CID resource is completely useless for us since we don't get
> > the corresponding CID value, AFAIK. In case Pango does the CMap
> > resource handling (this is, we send a Unicode value and Pango
> > returns the CID) we can enable this again.
>
> The current code does
>
> /fontname /CID
David Feuer wrote:
If ggeo.width is the width PostScript uses for glyphshow, we can change it to:
ggeo.width is the kerning info that we get from pango.
--
Han-Wen Nienhuys - [EMAIL PROTECTED] - http://www.xs4all.nl/~hanwen
LilyPond Software Design
-- Code for Music Notation
http://www.li
On 3/28/06, Werner LEMBERG <[EMAIL PROTECTED]> wrote:
> > >>> - (if cid?
> > >>> - " /CIDFont findresource "
> > >>> - " findfont")
> > >> I don't understand this? How are CID resources supposed to be
> > >> loaded now?
> > >
> > > According to the Postscript referen
In pango-font.cc, what are ggeo.width and ggeo.x_offset?
glyph-string, in output-ps.scm, adds the two together to figure out
where to place the next glyph. Is ggeo.width the same as the width
PostScript would use to place the next glyph? If so, it would be much
cleaner not to add it in, and not
> >>> - (if cid?
> >>> - " /CIDFont findresource "
> >>> - " findfont")
> >> I don't understand this? How are CID resources supposed to be
> >> loaded now?
> >
> > According to the Postscript reference, selectfont can be used with
> > CID resources as well as regula
On 3/28/06, Han-Wen Nienhuys <[EMAIL PROTECTED]> wrote:
> David Feuer wrote:
> thanks for you patch. CAn you have a second look; there are some style
> issues
Sure. I can't deal with them right now, but I'll try to fix them up
this evening.
> > I'd like
> > to know if it might be possible to m
David Feuer wrote:
to know if it might be possible to make the backend work at a slightly higher
level, which should allow much smaller files (e.g., Postscript could easily
understand the concept of "filled dotted quarter note in current note font with
upward stem 3 staff spaces long").
That's
David Feuer wrote:
I sent this some hours ago, but haven't seen it yet. Is the mailing list
broken, or just really slow?
The list is a bit slow, and I have been away.
Original message:
I made some changes to the Postscript backend, making the output more readable
(especially for text), arou
I made some changes to the Postscript backend, making the output more
readable (especially for text), around 10% shorter, and, at least in theory,
also faster to interpret. These changes are just a start, but I hope they
help. I'd like to know if it might be possible to make the backend work a
I sent this some hours ago, but haven't seen it yet. Is the mailing list
broken, or just really slow?
Original message:
I made some changes to the Postscript backend, making the output more readable
(especially for text), around 10% shorter, and, at least in theory, also faster
to interpret. Th
15 matches
Mail list logo