[
https://issues.apache.org/jira/browse/PDFBOX-3001?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14992567#comment-14992567
]
John Hewson commented on PDFBOX-3001:
-------------------------------------
The font metadata cache is now saved to a file using a simple custom format.
This avoids problems with the Preferences API and restores TTC caching. It also
avoid's the slowness of Java's Serializable. An added benefit is that the font
cache is now plain-text and can be read by a human, the format is simple, one
font per line:
{code}
Arial-Black|TTF||384|805|2000009f|dfd70000|0|020b0a04020102020204|/Library/Fonts/Arial
Black.ttf
{code}
> FileSystemFontProvider cache instability
> ----------------------------------------
>
> Key: PDFBOX-3001
> URL: https://issues.apache.org/jira/browse/PDFBOX-3001
> Project: PDFBox
> Issue Type: Bug
> Affects Versions: 2.0.0
> Reporter: John Hewson
> Assignee: John Hewson
> Priority: Blocker
> Fix For: 2.0.0
>
> Attachments: md5.diff, patch, patch
>
>
> FileSystemFontProvider uses Java's Preferences API to cache font metadata,
> however it doesn't seem to work out of the box on Windows (due to file
> permissions) and one user on the mailing list has complained that on Linux
> file paths with more than 80 characters can't be handed. Serializable is also
> slow.
> It looks like Preferences wasn't a good choice here. We're going to need to
> roll our own cache file format and save it somewhere we have write access to.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@pdfbox.apache.org
For additional commands, e-mail: dev-h...@pdfbox.apache.org
