On 17/03/14 01:19, Luis Bernardo wrote:
I performed some further tests, still on Mac, but with a couple of ghostscript
type1 fonts, which are probably the same one finds in Linux.
The test was successful in that the output looked good (for the record I has
some unpredictable output between different runs which I could not reliably
reproduce so I attribute that to an environment issue, maybe the .fop
directory).
My example included characters not present in the font. Instead of # for the
missing glyph I got z (see example attached), which probably is not intended
(i.e., looks like a bug). I was also expecting that Adobe would indicate that
the fonts are subset but it doesn't but this could be a wrong expectation (the
this is probably because the font’s PostScript name doesn’t start with
a subset tag (6 uppercase letters followed by a +) like it should. Also,
it may be necessary to add a CharSet entry to the font descriptor.
subset file is nevertheless considerably smaller -- 64KB versus 219 KB).
Finally I ran a simple performance test. With the patched code (that produces
subset) the time was 175 msecs. With the current trunk 83 msecs.
So I think the suggestion that Vincent put forward to not make subset the
default for type1 makes sense for now. I think this requires a new vote with a
new patch.
Vincent
On 3/12/14, 12:06 AM, Luis Bernardo wrote:
Since apparently Macs have no type1 fonts I had to look for some and I tried
the first one from http://www.ctan.org/tex-archive/fonts/cm/ps-type1/bakoma
(cmb10) which gave a problem:
java.util.NoSuchElementException
at java.util.Scanner.throwFor(Scanner.java:907)
at java.util.Scanner.next(Scanner.java:1530)
at java.util.Scanner.nextInt(Scanner.java:2160)
at java.util.Scanner.nextInt(Scanner.java:2119)
at
org.apache.fop.fonts.type1.PostscriptParser$PSFixedArray.addEntry(PostscriptParser.java:379)
at
org.apache.fop.fonts.type1.PostscriptParser$PSFixedArray.parseToken(PostscriptParser.java:329)
.....
So it seems this needs to be tested with more fonts. But I will test next in
with the default Linux type1 fonts.
On 3/7/14, 11:23 AM, Robert wrote:
Hi All,
About a week ago I posted a patch to add Type 1 subset support to FOP. All
referenced Type 1 fonts (unless set to embedding-mode="full") will now be
subset by default much like the behaviour exhibited by TrueType and
OpenType. As this is a big feature and quite involved I think it is
necessary to vote on whether to add this feature in it's current state to
FOP. I'm not sure if anyone has taken a look at what has gone into this or
tried it out yet, but it might be worth doing so before making your decision.
I am going to be away for the next week or so but will tally up the votes
and post the result once I am back.
Here is a link to the patch and issue:
https://issues.apache.org/jira/browse/FOP-2354
Regards,
Robert Meyer
