[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
PDF question about FontDescriptor
From: |
Helmar |
Subject: |
PDF question about FontDescriptor |
Date: |
Wed, 08 Dec 2010 15:48:10 -0000 |
User-agent: |
G2/1.0 |
Hi,
I'm curious - why every Font needs an own FontDescriptor with
Ghostscript, even if it can be assumed to be the same for different
character ranges of the same included TTF-file?
I want to have one font (say /F1T0) with WinAnsiEncoding and another
one (say /F1T1) that has some other characters of the font included.
Both should point to the same binary TrueType-font.
With Ghostscript (and only Ghostscript afaik), I've to make two times
something like
xyz 0 obj
<<
/Type /FontDescriptor
...
>>
Why? Is there a point in the standard that forbids to use same
FontDescriptor dictionary for two different Fonts?
Thanks,
-Helmar
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- PDF question about FontDescriptor,
Helmar <=