[jira] [Commented] (FOP-2173) [PATCH] Invalid Postscript created with SVG and custom fonts

classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view
|

[jira] [Commented] (FOP-2173) [PATCH] Invalid Postscript created with SVG and custom fonts

Andreas Joseph Krogh (Jira)

    [ https://issues.apache.org/jira/browse/FOP-2173?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13534019#comment-13534019 ]

Chris Bowditch commented on FOP-2173:
-------------------------------------

Hi Simon,

Thanks for your patch. When running your test file I didn't get a crash as you originally described using Ghostview. Instead I got the following warnings:

Can't find (or can't open) font file C:\Program Files\gs\gs8.53\Resource/Font/DejaVuSans_1.
Can't find (or can't open) font file DejaVuSans_1.
Querying operating system for font files...
Didn't find this font on the system!
Substituting font Courier for DejaVuSans_1.

Visually I noticed that some characters were missing from the second set.

Looking at the code changes themselves, I can see you've introduced a couple of checkstyle errors related to the order of imports. That's easy to fix but please check that yourself next time.

Committed in revision 1422992
               

> [PATCH] Invalid Postscript created with SVG and custom fonts
> ------------------------------------------------------------
>
>                 Key: FOP-2173
>                 URL: https://issues.apache.org/jira/browse/FOP-2173
>             Project: Fop
>          Issue Type: Bug
>            Reporter: simon steiner
>            Assignee: Chris Bowditch
>         Attachments: fop.xconf, svgcrash.patch, test.fo
>
>
> When more than 255 characters are used from within SVG and a custom Font the Postscript generated is invalid. This is evident either as a crash in evince (Linux) or missing characters in Windows version of Ghostview. The problem is likely to be evident on printers as well.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira