[
https://issues.apache.org/jira/browse/PDFBOX-5363?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andreas Lehmkühler resolved PDFBOX-5363.
----------------------------------------
Fix Version/s: 2.0.26
3.0.0 PDFBox
Resolution: Fixed
I've simplified the proposal, such as the whole caching code is skipped if
there aren't any fonts. But in the end most likely such a configuration without
local fonts will produce more or less issues when processing pdfs as in many
cases such external fonts are needed.
However, thanks for the contribution, it makes the logging more precise.
> Don't log warnings if there are not fonts to cache
> --------------------------------------------------
>
> Key: PDFBOX-5363
> URL: https://issues.apache.org/jira/browse/PDFBOX-5363
> Project: PDFBox
> Issue Type: Improvement
> Affects Versions: 2.0.25
> Reporter: Falko Modler
> Assignee: Andreas Lehmkühler
> Priority: Minor
> Fix For: 2.0.26, 3.0.0 PDFBox
>
>
> I'm seeing these warnings:
> {noformat}
> 2022-01-16 16:49:05,723 WARN [org.apa.pdf.pdm.fon.FileSystemFontProvider]
> (executor-thread-10) Building on-disk font cache, this may take a while
> 2022-01-16 16:49:05,724 WARN [org.apa.pdf.pdm.fon.FileSystemFontProvider]
> (executor-thread-10) Finished building on-disk font cache, found 0 fonts
> {noformat}
> which are pretty much useless because creating a basically empty cache will
> *not* take a while.
> These warnings should only be logged if there actually are font files.
> PS: My case is a Quarkus app running as a docker container based on
> [azul/zulu-openjdk-alpine:17.0.1-jre-headless|https://hub.docker.com/layers/azul/zulu-openjdk-alpine/17.0.1-jre-headless/images/sha256-e248739ad4723f184b62616677979c32beeb36f33f71139dc1d0ff43add04e89?context=explore].
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
