Yeah there are some outstanding encoding issues with fonts which PDFBOX-2149 aims to solve.
-- John On 2 Jul 2014, at 13:57, Tilman Hausherr <[email protected]> wrote: > Good; that's another reason why I haven't been pushing this, because i was > expecting this to happen :-) I made a test with the new FontManager some time > ago, but it didn't work properly for ligatures (fl, fi, etc) so watch out for > these :-) I think it was either in the tracemonkey file or in the "bivariate > contouring problem" file. > > Tilman > > Am 02.07.2014 21:52, schrieb John Hewson: >> I’m going to remove AWT font rendering shortly so I wouldn’t worry. >> >> -- John >> >> On 2 Jul 2014, at 08:22, Tilman Hausherr <[email protected]> wrote: >> >>> I'm wondering whether it would speed up things if the FontRenderContext is >>> done as a static. >>> >>> static private FontRenderContext IDFRC = new FontRenderContext(null, true, >>> true); >>> >>> >>> and in drawString(), >>> >>> // FontRenderContext frc = new FontRenderContext(new >>> AffineTransform(), true, true); >>> // GlyphVector glyphs = awtFont.createGlyphVector(frc, string); >>> GlyphVector glyphs = awtFont.createGlyphVector(IDFRC, string); >>> >>> >>> I didn't propose the change in JIRA because I don't know if this would work >>> properly in a multithread environment like a web server. >>> >>> Curently, drawString() is used for the standard 14 fonts. >>> >>> Tilman >> >
