Hi,
FOP is an open source project, and everybody can contribute in his own
way, so you can reopen closed issues as you want if needed, and submit
patches as you want.
That said, IMHO, apart in a company quality context, testing closed
issues will not help very much (typically, an issue is closed
Actually, I would encourage testing closed issues, or at least those issues
that were resolved without creating a test data set that demonstrates both
the bug and the fix, and maintains non-regression.
I have noticed a number of issues fixed without adding such tests, which
should be the norm,
https://issues.apache.org/bugzilla/show_bug.cgi?id=18801
Chris Bowditch bowditch_ch...@hotmail.com changed:
What|Removed |Added
Summary|visibility property is|[PATCH]
https://issues.apache.org/bugzilla/show_bug.cgi?id=51144
Bug #: 51144
Summary: ToUnicode table for subset font contains invalid
entries
Product: Fop
Version: 1.0
Platform: All
OS/Version: Linux
Status:
https://issues.apache.org/bugzilla/show_bug.cgi?id=51144
--- Comment #1 from Mehdi Houshmand med1...@gmail.com 2011-05-03 12:35:04 UTC
---
Created attachment 26954
-- https://issues.apache.org/bugzilla/attachment.cgi?id=26954
Removed 2 reserved glyphs from the CIDSubset
This patch seeks to
