[
https://issues.apache.org/jira/browse/FOP-3045?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17488910#comment-17488910
]
J Frank commented on FOP-3045:
------------------------------
I tried with auto detection font for poppins and found it automatically maps to
font weight 400 or normal 200 and not 300 as FOP looks for 400 weight font as
normal and 700 as bold, so this is classified as not a bug.
refer screen shot
!Font and Font weight mapping.png!
Workaround as suggested by Simon is to use explicit font weight mapping.
> Auto Detection does not work for Poppins
> ----------------------------------------
>
> Key: FOP-3045
> URL: https://issues.apache.org/jira/browse/FOP-3045
> Project: FOP
> Issue Type: Bug
> Components: font/opentype, renderer/pdf
> Affects Versions: 2.6
> Environment: openSUSE Leap 15.3
> fop 2.6
> google-poppins-fonts 4.003-6.3.1
> Reporter: Quang Tran
> Priority: Major
> Attachments: Font and Font weight mapping.png, fop.xconf, poppins.fo,
> poppins.pdf
>
>
> The attached reproducer XLST-FO (poppins.fo) has sample text with font
> weights from 100 - 900.
> Although the font-weights 300 and 100 are substituted with the font-weight
> 200 the following font-weight 400 is being rendered much thinner.
> Snippet from output:
> ...
> {{WARNING: Font "Poppins,normal,300" not found. Substituting with
> "Poppins,normal,200".}}
> {{Jan 05, 2022 3:00:31 PM org.apache.fop.apps.FOUserAgent processEvent}}
> {{WARNING: Font "Poppins,normal,100" not found. Substituting with
> "Poppins,normal,200".}}
> {{Jan 05, 2022 3:00:31 PM org.apache.fop.apps.FOUserAgent processEvent}}
> {{WARNING: Font "Poppins,normal,900" not found. Substituting with
> "Poppins,normal,800".}}
> (Also the normal italic seems to be wrong, too. I'm not sure if it's
> correlated to this issue or another.)
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
