[
https://issues.apache.org/jira/browse/FOP-2156?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13561292#comment-13561292
]
Luis Bernardo commented on FOP-2156:
the issue is not understood at the moment. but add
[
https://issues.apache.org/jira/browse/FOP-2198?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Luis Bernardo closed FOP-2198.
--
typo corrected
> misspelled word an
> --
>
> Key: FOP-2198
>
[
https://issues.apache.org/jira/browse/FOP-2198?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Luis Bernardo resolved FOP-2198.
Resolution: Fixed
http://svn.apache.org/viewvc?rev=1437802&view=rev
> misspelled wor
[
https://issues.apache.org/jira/browse/FOP-2198?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sebul updated FOP-2198:
---
Priority: Minor (was: Major)
Fix Version/s: (was: 1.1)
> misspelled word an
> --
>
>
I never looked at this part of the code but I would guess that this is
due to Batik since it uses the system fonts? So I suspect this auto
detection may be needed.
On 1/22/13 7:30 PM, Glenn Adams wrote:
While debugging FOP-2197 [1], I learned that:
* junit-transcoder tests all end up perf
Sebul created FOP-2198:
--
Summary: misspelled word an
Key: FOP-2198
URL: https://issues.apache.org/jira/browse/FOP-2198
Project: Fop
Issue Type: Bug
Components: documentation
Affects Versio
Hi Glenn,
2013/1/22 Glenn Adams :
> While debugging FOP-2197 [1], I learned that:
>
> junit-transcoder tests all end up performing auto font detection, which
> seems questionable [is this needed?]
> auto font detection performs recursion on the font base directory even
> though the code comment in