[jira] [Resolved] (FOP-2378) PCL rendering doesn't support complex scripts

[ https://issues.apache.org/jira/browse/FOP-2378?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luis Bernardo resolved FOP-2378. Resolution: Duplicate FOP-2250 addresses this but it has only been partially tested. > PCL rendering

[jira] [Resolved] (FOP-2376) PS rendering does not support complex scripts

[ https://issues.apache.org/jira/browse/FOP-2376?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luis Bernardo resolved FOP-2376. Resolution: Duplicate I think this has been addressed in FOP-2206. > PS rendering does not support c

[jira] [Updated] (FOP-1099) [PATCH] footnotes within tables and lists get lost

[ https://issues.apache.org/jira/browse/FOP-1099?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vincent Hennebert updated FOP-1099: --- Attachment: inverted-footnotes.pdf inverted-footnotes.fo footnot

Re: FOP Release Automation

Hi All, I certainly use the web interface when making small tweaks to the docs. As you know users occasionally report small mistakes that require minor tweaks. I'd like to streamline the updating of the website for release purposes but I don't want to disable/prevent the current web interface

Re: FOP Release Automation

Hi, If we go to an svn:externals set in CMS repo, pointing to FOP trunk doc, and 2 last FOP tagged doc, we should take care about having no change in TAGs. Perhaps a pre-commit hook can do the job here, warning the committer, or forbidding the commit propagation. 2014-05-30 23:34 GMT+02:00 Robert