[
https://issues.apache.org/jira/browse/FOP-3010?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Bickford closed FOP-3010.
-------------------------------
Fix Version/s: 2.6
Resolution: Not A Problem
Delving further into this I discovered that the naming information google
provides for the Bitter font weights has inconsistent font-family naming. At
this point I consider this a google fonts problem and not an FOP problem.
The problem can be avoided by custom defining the font-triplet's
> Google Font Bitter weight errors
> --------------------------------
>
> Key: FOP-3010
> URL: https://issues.apache.org/jira/browse/FOP-3010
> Project: FOP
> Issue Type: Bug
> Components: font/opentype
> Affects Versions: 2.6
> Environment: Windows 10, Issue occurs in embedded java code and in
> the latest OxygenXML V. 23.1
> Reporter: David Bickford
> Priority: Critical
> Fix For: 2.6
>
> Attachments: _bitter400Font RenderX XEP.pdf, _bitter400Font apache
> fop.pdf, _bitter400Font.fo
>
>
> The Bitter Font from google ([https://fonts.google.com/specimen/Bitter)]
> renders the wrong weight for 100,200,300,400
> The font itself and the test .fo file have been tested in RenderX XEP and it
> works there.
> Fonts were directly downloaded from google and tested with the default xconf
> (with the correct directory added and <auto-detect/>
>
> We have tried many other google fonts and as yet this is the only one we know
> of with this issue.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
