JiriOndrusek opened a new pull request #1793: URL: https://github.com/apache/camel-quarkus/pull/1793
Issue: https://github.com/apache/camel-quarkus/issues/1642 @oscerd There is a true type font among files (integration-tests/fop/src/test/resources/Freedom-10eM.ttf ), downloaded from https://www.fontspace.com/freedom-font-f14832 Font is free and is used only as a test resource. This should be acceptable from licence POV. Do you agree? @ppalaga Fop extension supports only transformation into PDF. As you can see in extensions/fop/runtime/src/main/doc/limitations.adoc, sRGB color space is disabled and font cache has to be disabled for custom fonts. These two limitations are caused by following issues: - Problem with sRGB color space is caused by https://github.com/oracle/graal/issues/2850 - Problem with font cache is caused by https://github.com/oracle/graal/issues/460 [ ] An issue should be filed for the change unless this is a trivial change (fixing a typo or similar). One issue should ideally be fixed by not more than one commit and the other way round, each commit should fix just one issue, without pulling in other changes. [ ] Each commit in the pull request should have a meaningful and properly spelled subject line and body. Copying the title of the associated issue is typically enough. Please include the issue number in the commit message prefixed by #. [ ] The pull request description should explain what the pull request does, how, and why. If the info is available in the associated issue or some other external document, a link is enough. [ ] Phrases like Fix #<issueNumber> or Fixes #<issueNumber> will auto-close the named issue upon merging the pull request. Using them is typically a good idea. [ ] Please run mvn process-resources -Pformat (and amend the changes if necessary) before sending the pull request. [ ] Contributor guide is your good friend: https://camel.apache.org/camel-quarkus/latest/contributor-guide.html ---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
