Chris Bowditch wrote:
Although changing configuration files in a backwards incompatible way is
not likely to be popular with the users!
Given that not embedding fonts never really worked (except for
fonts specifically installed using the Acrobat font manager),
there is not really an incompatibi
Just some details on what is currently possible and what not (for PDF
output):
Type 1: embedded or referenced, WinAnsi only
TrueType:
- embedded subset, CID (default mode)
- embedded WinAnsi (full font is embedded 1:1, no subset)
- referenced WinAnsi (works, but is restricted to WinAnsi)
-
Andreas L Delmelle wrote:
As far as I can judge, /if/ the names of embedded fonts forcibly need
to be altered because they would be overridden by local fonts in the
PDF viewer, then it could turn out to be pretty simple --for someone
who knows what he's doing :/
Leave the font-family name
On Jul 12, 2007, at 21:00, Loran Kary wrote:
I would imagine that support for additional fonts beyond the Base14
would be pretty fundamental to PDF formatting and therefore if it
isn't fully implemented there must be a pretty good reason.
What I do seem to remember is that, when you use emb
Thanks Andreas,
I got a brief and vague response on the users group that left me
wanting more information. Whether or not I could contribute to a
potential solution, and that is a possibility, would depend on
whether the work involved would be major or minor. So I am trying to
get some
On Jul 12, 2007, at 20:12, Loran Kary wrote:
Hi
Perhaps I am posting this question on the wrong list or perhaps my
question has been asked and answered before.
The latter, in a way...
You asked the same question on fop-users a couple of days ago, where
the response was that FOP currently d
Perhaps I am posting this question on the wrong list or perhaps my
question has been asked and answered before.
But to state my question again, why is it not sufficient to supply
FOP with a font metrics file and the font triplets in the
configuration file? Why does it seem that FOP needs t
