Details
-
Bug
-
Status: Resolved
-
Resolution: Fixed
-
1.8
-
None
-
Operating System: All
Platform: All
Description
The attached patch does three things:
1. Internally register not only the font families but also the actual font names (FontFamilyResolver).
Example: Where "Univers" is a font family, the font name "Univers 45 Light" is not currently registered. So if this is used, no match is found and the fallback "SansSerif" is used.
2. Handle all CSS font weights for Java VMs >= 1.5 (TextUtilities).
There was a simplification in place for handling cases in JVMs prior to 1.5.
3. Handle the case where a font family with spaces contains an integer value (ex. "Univers 45 Light"), but is not in quotes (FontFamilyManager).
Until now, only the case style="font-family: Univers Bold" would be handled but not style="font-family: Univers 45 Light".
Attachments
Attachments
Issue Links
- is duplicated by
-
BATIK-825 Font Family names with digits in them cause Batik to throw exception
- Resolved
-
BATIK-940 Opening a drawing using fonts with blanks in name causes errors
- Resolved
-
BATIK-1006 The "font-family" property does not support integer values.
- Resolved
Attachment batik-font-matching.diff has been added with description: Patch to improve font matching