This bug is marked as fixed upstream in fop 2.0 and we have fop 2.1 in
testing/unstable. Are you sure the package in unstable is still affected?

Emmanuel Bourg

Reply via email to