Re: Unreleased versions in Jira

2012-12-18 Thread Glenn Adams
On Tue, Dec 18, 2012 at 1:20 AM, Alexios Giotis wrote: > I noticed that in Jira all versions are considered to be "Unreleased". > Glenn, or any other administrator of the FOP project, you should be able to > access a "Manage Versions" link. There, you could "Release" versions 0.95, > 1.0 & 1.1 and

Re: JIRA: How to manage resolved versions (Was: [jira] [Commented] (FOP-1840) [PATCH] Region-Body Column balancing incorrect if content is table with header)

2012-12-18 Thread Glenn Adams
On Mon, Dec 17, 2012 at 7:54 AM, Chris Bowditch wrote: > Hi Glenn, > > > On 17/12/2012 15:24, Glenn Adams wrote: > >> but after a new release, the issue would effectively apply to both trunk >> and the new release, and an issue can only be associated with one version >> in JIRA; >> > > But why doe

[jira] [Created] (FOP-2176) Different number of lines placed in a balanced two column layout before page break

2012-12-18 Thread Alexis Giotis (JIRA)
Alexis Giotis created FOP-2176: -- Summary: Different number of lines placed in a balanced two column layout before page break Key: FOP-2176 URL: https://issues.apache.org/jira/browse/FOP-2176 Project: Fop

[jira] [Updated] (FOP-2176) Different number of lines placed in a balanced two column layout before page break

2012-12-18 Thread Alexis Giotis (JIRA)
[ https://issues.apache.org/jira/browse/FOP-2176?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexis Giotis updated FOP-2176: --- Attachment: output-expected.pdf output-actual.pdf input.fo.xml > Di

[jira] [Updated] (FOP-2175) [PATCH] Dependant on FOP-2174 - Change to XGC to support the changes in FOP for image scaling. Scaling by resolution is removed to avoid duplicate scaling.

2012-12-18 Thread Robert Meyer (JIRA)
[ https://issues.apache.org/jira/browse/FOP-2175?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Meyer updated FOP-2175: -- Summary: [PATCH] Dependant on FOP-2174 - Change to XGC to support the changes in FOP for image scaling. S

[jira] [Updated] (FOP-2175) Dependant on FOP-2174 - Change to XGC to support the changes in FOP for image scaling. Scaling by resolution is removed to avoid duplicate scaling.

2012-12-18 Thread Robert Meyer (JIRA)
[ https://issues.apache.org/jira/browse/FOP-2175?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Meyer updated FOP-2175: -- Attachment: patch.diff Attached a patch containing a small change to remove scaling from XGC when gettin

[jira] [Created] (FOP-2175) Dependant on FOP-2174 - Change to XGC to support the changes in FOP for image scaling. Scaling by resolution is removed to avoid duplicate scaling.

2012-12-18 Thread Robert Meyer (JIRA)
Robert Meyer created FOP-2175: - Summary: Dependant on FOP-2174 - Change to XGC to support the changes in FOP for image scaling. Scaling by resolution is removed to avoid duplicate scaling. Key: FOP-2175 URL: https://

[jira] [Updated] (FOP-2174) [PATCH] When using SVG drawings, if no content-width and content-height is specified, 72 will be used instead of the source-resolution option.

2012-12-18 Thread Robert Meyer (JIRA)
[ https://issues.apache.org/jira/browse/FOP-2174?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Meyer updated FOP-2174: -- Summary: [PATCH] When using SVG drawings, if no content-width and content-height is specified, 72 will be

[jira] [Updated] (FOP-2174) When using SVG drawings, if no content-width and content-height is specified, 72 will be used instead of the source-resolution option.

2012-12-18 Thread Robert Meyer (JIRA)
[ https://issues.apache.org/jira/browse/FOP-2174?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Meyer updated FOP-2174: -- Attachment: test.fo output-144.pdf patch.diff Here is the patch with the

[jira] [Created] (FOP-2174) When using SVG drawings, if no content-width and content-height is specified, 72 will be used instead of the source-resolution option.

2012-12-18 Thread Robert Meyer (JIRA)
Robert Meyer created FOP-2174: - Summary: When using SVG drawings, if no content-width and content-height is specified, 72 will be used instead of the source-resolution option. Key: FOP-2174 URL: https://issues.apache

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

2012-12-18 Thread Pascal Sancho (JIRA)
[ https://issues.apache.org/jira/browse/FOP-2173?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pascal Sancho updated FOP-2173: --- Affects Version/s: 1.1 0.95 > [PATCH] Invalid Postscript created with SVG an

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

2012-12-18 Thread Pascal Sancho (JIRA)
[ https://issues.apache.org/jira/browse/FOP-2173?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pascal Sancho updated FOP-2173: --- Affects Version/s: (was: 1.1) (was: 0.95) > [PATCH] Invalid Postscri

Unreleased versions in Jira

2012-12-18 Thread Alexios Giotis
Hi, I noticed that in Jira all versions are considered to be "Unreleased". Glenn, or any other administrator of the FOP project, you should be able to access a "Manage Versions" link. There, you could "Release" versions 0.95, 1.0 & 1.1 and set their release date. I would also delete the "all"

Re: Two emails for every Jira issue update

2012-12-18 Thread Alexios Giotis
If the emails were related to FOP-1840, then this is because it was assigned to fop-dev and I reopened it, changed the fix version, resolved & closed. Alexis On 18 Dec 2012, at 02:12, Luis Bernardo wrote: > > I still get two, a few minutes apart... Looking at the headers only the > message