Re: Two emails for every Jira issue update

I still get two, a few minutes apart... Looking at the headers only the message ID and time are different between the two messages. Any suggestion? On 12/17/12 1:10 PM, Alexios Giotis wrote: I was waiting until somebody updates an issue. Notifications are now received only once. Thank you G

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

[ https://issues.apache.org/jira/browse/FOP-2173?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris Bowditch updated FOP-2173: Fix Version/s: trunk > [PATCH] Invalid Postscript created with SVG and custom fonts > ---

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

[ https://issues.apache.org/jira/browse/FOP-2173?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris Bowditch resolved FOP-2173. - Resolution: Fixed > [PATCH] Invalid Postscript created with SVG and custom fonts >

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

[ https://issues.apache.org/jira/browse/FOP-2173?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13534019#comment-13534019 ] Chris Bowditch commented on FOP-2173: - Hi Simon, Thanks for your patch. When running yo

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

[ https://issues.apache.org/jira/browse/FOP-2173?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris Bowditch resolved FOP-2173. - Resolution: Fixed > [PATCH] Invalid Postscript created with SVG and custom fonts >

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

[ https://issues.apache.org/jira/browse/FOP-2173?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris Bowditch updated FOP-2173: Fix Version/s: trunk > [PATCH] Invalid Postscript created with SVG and custom fonts > ---

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

[ https://issues.apache.org/jira/browse/FOP-2173?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13534019#comment-13534019 ] Chris Bowditch commented on FOP-2173: - Hi Simon, Thanks for your patch. When running yo

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

[ https://issues.apache.org/jira/browse/FOP-2173?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13534019#comment-13534019 ] Chris Bowditch commented on FOP-2173: - Hi Simon, Thanks for your patch. When running yo

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

[ https://issues.apache.org/jira/browse/FOP-2173?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris Bowditch updated FOP-2173: Description: When more than 255 characters are used from within SVG and a custom Font the Postscript

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

[ https://issues.apache.org/jira/browse/FOP-2173?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris Bowditch updated FOP-2173: Description: When more than 255 characters are used from within SVG and a custom Font the Postscript

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

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 does that matter? If a bug is fixed then in v3 say, then its obvious its also

[jira] [Assigned] (FOP-2173) [PATCH] SVG postscript crash

[ https://issues.apache.org/jira/browse/FOP-2173?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris Bowditch reassigned FOP-2173: --- Assignee: Chris Bowditch > [PATCH] SVG postscript crash > > >

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

Hmm, 2012/12/17 Glenn Adams : > 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; I'm not sure if you speak about the [Affect] field, or the [Fix] field. The former can be used with the "

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

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; if the issue isn't fixed by the time the release occurs, then it is unlikely to be fixed in the release version as much as being fixed in trun

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

Hi, Well, the fixed list has become not empty! I've added a link to JIRA in changes list. You can see it on http://xmlgraphics.staging.apache.org/fop/changes.html. If there is no objection, I'll commit it on site prod tomorrow. 2012/12/17 Chris Bowditch : > On 17/12/2012 09:08, Pascal Sancho wr

[jira] [Resolved] (FOP-1840) [PATCH] Region-Body Column balancing incorrect if content is table with header

[ https://issues.apache.org/jira/browse/FOP-1840?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexis Giotis resolved FOP-1840. Resolution: Fixed Fix Version/s: trunk > [PATCH] Region-Body Column balancing incorrect if

[jira] [Resolved] (FOP-1840) [PATCH] Region-Body Column balancing incorrect if content is table with header

[ https://issues.apache.org/jira/browse/FOP-1840?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexis Giotis resolved FOP-1840. Resolution: Fixed Fix Version/s: trunk > [PATCH] Region-Body Column balancing incorrect if

[jira] [Closed] (FOP-1840) [PATCH] Region-Body Column balancing incorrect if content is table with header

[ https://issues.apache.org/jira/browse/FOP-1840?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexis Giotis closed FOP-1840. -- > [PATCH] Region-Body Column balancing incorrect if content is table with header > --

[jira] [Closed] (FOP-1840) [PATCH] Region-Body Column balancing incorrect if content is table with header

[ https://issues.apache.org/jira/browse/FOP-1840?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexis Giotis closed FOP-1840. -- > [PATCH] Region-Body Column balancing incorrect if content is table with header > --

[jira] [Reopened] (FOP-1840) [PATCH] Region-Body Column balancing incorrect if content is table with header

[ https://issues.apache.org/jira/browse/FOP-1840?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexis Giotis reopened FOP-1840: > [PATCH] Region-Body Column balancing incorrect if content is table with header > --

[jira] [Reopened] (FOP-1840) [PATCH] Region-Body Column balancing incorrect if content is table with header

[ https://issues.apache.org/jira/browse/FOP-1840?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexis Giotis reopened FOP-1840: > [PATCH] Region-Body Column balancing incorrect if content is table with header > --

Re: Two emails for every Jira issue update

I was waiting until somebody updates an issue. Notifications are now received only once. Thank you Glenn ! On 16 Dec 2012, at 17:32, Glenn Adams wrote: > I've removed the fop-dev user from the "Developers" role since there is > already a separate notification to that reflector. This should t

[jira] [Commented] (FOP-2171) [PATCH] Missing Glyph in Postscript using DejaVuSans

[ https://issues.apache.org/jira/browse/FOP-2171?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13533902#comment-13533902 ] simon steiner commented on FOP-2171: committed http://svn.apache.org/viewvc?view=revisio

[jira] [Resolved] (FOP-2171) [PATCH] Missing Glyph in Postscript using DejaVuSans

[ https://issues.apache.org/jira/browse/FOP-2171?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] simon steiner resolved FOP-2171. Resolution: Fixed Fix Version/s: trunk > [PATCH] Missing Glyph in Postscript using DejaVuS

[jira] [Updated] (FOP-2171) [PATCH] Missing Glyph in Postscript using DejaVuSans

[ https://issues.apache.org/jira/browse/FOP-2171?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] simon steiner updated FOP-2171: --- Summary: [PATCH] Missing Glyph in Postscript using DejaVuSans (was: Missing Glyph in Postscript using

[jira] [Updated] (FOP-2172) [PATCH] PDF image not rotated in PS/AFP

[ https://issues.apache.org/jira/browse/FOP-2172?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] simon steiner updated FOP-2172: --- Summary: [PATCH] PDF image not rotated in PS/AFP (was: PDF image not rotated in PS/AFP) > [PATCH]

[jira] [Updated] (FOP-2173) [PATCH] SVG postscript crash

[ https://issues.apache.org/jira/browse/FOP-2173?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] simon steiner updated FOP-2173: --- Summary: [PATCH] SVG postscript crash (was: SVG postscript crash) > [PATCH] SVG postscript crash >

[jira] [Updated] (FOP-2173) SVG postscript crash

[ https://issues.apache.org/jira/browse/FOP-2173?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] simon steiner updated FOP-2173: --- Attachment: fop.xconf test.fo svgcrash.patch > SVG postscript crash

[jira] [Created] (FOP-2173) SVG postscript crash

simon steiner created FOP-2173: -- Summary: SVG postscript crash Key: FOP-2173 URL: https://issues.apache.org/jira/browse/FOP-2173 Project: Fop Issue Type: Bug Reporter: simon steiner

Re: Two emails for every Jira issue update

Hi Glenn, On 14/12/2012 22:12, Glenn Adams wrote: I've created https://issues.apache.org/jira/browse/INFRA-5658 to track this. Thanks for solving the duplicate -email issue. It was becoming quite annoying. Thanks, Chris On Fri, Dec 14, 2012 at 12:17 PM, Glenn Adams

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

On 17/12/2012 09:08, Pascal Sancho wrote: Hi list, Hi Pascal, In order to keep trace about works on versions, we should use the Jira feature to indicate what version is fixed. I agree. in almost cases, fixes are against the trunk. Since in Jira one can rename the version name (see [1]),

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

Hi list, In order to keep trace about works on versions, we should use the Jira feature to indicate what version is fixed. in almost cases, fixes are against the trunk. Since in Jira one can rename the version name (see [1]), during the FOP release process (at branching or tagging stage), we coul