You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@pdfbox.apache.org by "Andreas Lehmkühler (JIRA)" <ji...@apache.org> on 2016/05/26 13:33:12 UTC
[jira] [Updated] (PDFBOX-3089) Investigate why glyph path caching
does not always cache glyph accesses
[ https://issues.apache.org/jira/browse/PDFBOX-3089?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andreas Lehmkühler updated PDFBOX-3089:
---------------------------------------
Attachment: PDFBOX-3089_createPoint.txt
I've moved the creation of point to the GlyphDescription classes which reduces the getGlyph calls by nearly 200, see the attached patch.
[~tilman] Did you have something like that in mind?
> Investigate why glyph path caching does not always cache glyph accesses
> -----------------------------------------------------------------------
>
> Key: PDFBOX-3089
> URL: https://issues.apache.org/jira/browse/PDFBOX-3089
> Project: PDFBox
> Issue Type: Task
> Components: FontBox
> Affects Versions: 2.0.0
> Reporter: Tilman Hausherr
> Priority: Minor
> Labels: Optimization
> Fix For: 2.1.0
>
> Attachments: PDFBOX-3089_createPoint.txt
>
>
> Work in PDFBOX-3088 shows that despite caching glyph paths in TTFGlyph2D.getPathForGID(), there are repeated accesses for the same gid in GlyphTable (which is why that one is now cached as well).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@pdfbox.apache.org
For additional commands, e-mail: dev-help@pdfbox.apache.org