Sam Barker (JIRA | 25 May 01:06 2016
Picon

[jira] [Commented] (FOP-2364) Keep-with-next integer value: Illegal value for breakClass: 75


    [
https://issues.apache.org/jira/browse/FOP-2364?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15299120#comment-15299120
] 

Sam Barker commented on FOP-2364:
---------------------------------

Thanks for the update [~adelmelle], 

While I can't see any direct references to {code}.within-line{code}. I've not managed to make the time to
check for and try the other options. 

> Keep-with-next integer value: Illegal value for breakClass: 75
> --------------------------------------------------------------
>
>                 Key: FOP-2364
>                 URL: https://issues.apache.org/jira/browse/FOP-2364
>             Project: FOP
>          Issue Type: Bug
>          Components: layout/unqualified
>    Affects Versions: trunk
>            Reporter: Matthias Reischenbacher
>         Attachments: illegal_break_class_75.xml
>
>
> The attached sample FO file causes an IllegalArgumentException: Illegal value for breakClass: 75.
> It seems to be related to the integer value within the keep-with-next property.

--
(Continue reading)

Andreas L. Delmelle (JIRA | 21 May 22:10 2016
Picon

[jira] [Comment Edited] (FOP-2364) Keep-with-next integer value: Illegal value for breakClass: 75


    [
https://issues.apache.org/jira/browse/FOP-2364?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15295232#comment-15295232
] 

Andreas L. Delmelle edited comment on FOP-2364 at 5/21/16 8:09 PM:
-------------------------------------------------------------------

I quickly checked the code, and this comment is entirely to the point. I suspect the explanation is that at
some point, some dev started mixing the concepts of "enum values for the {{break-*}} properties" on the
one hand and "break classes" on the other. The latter is internal to FOP, so one could argue that,
architecturally, it is actually improper to use the same symbolic literals, defined in
{{org.apache.fop.fo.Constants}}, for something that is strictly internal to the
{{org.apache.fop.layoutmgr}} package. For that matter, I am not sure what the rationale was for putting
that {{BreakUtil}} class in the _general_ utilities package. I cannot immediately imagine where that
would be useful outside of the layout context, but maybe that's just me...

Now, the result is that a literal EN_LINE, which represents the enum value "line" -- and note: cannot even be
used as a value in said {{break-*}} properties; it is meant for the more exotic, float-related
{{intrusion-displace}} property (see: http://www.w3.org/TR/xsl/#intrusion-displace ) -- is being
used, in the FOP layout code, to represent a "break class" that I would guess to have the highest priority...?

EDIT - ... or better, a "keep class" with the lowest priority; see {{org.apache.fop.layoutmgr.Keep}}.

A "break class" is roughly the result in the layout code of merging the different {{break-\*}} *and*
{{keep-\*}} properties at different levels. Since there is a specific
{{keep-with-next.within-line}} property that is implicitly set via the shorthand, that now
translates into a "break class" of EN_LINE... Pretty sure the {{.within-line}} component is not
officially supported, though (read: not included in the test cases). The general workaround given on
fop-users <at>  is usually to avoid using the shorthand for specifying keeps, and mostly useful to avoid
(Continue reading)

Andreas L. Delmelle (JIRA | 21 May 21:47 2016
Picon

[jira] [Commented] (FOP-2364) Keep-with-next integer value: Illegal value for breakClass: 75


    [
https://issues.apache.org/jira/browse/FOP-2364?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15295232#comment-15295232
] 

Andreas L. Delmelle commented on FOP-2364:
------------------------------------------

I quickly checked the code, and this comment is entirely to the point. I suspect the explanation is that at
some point, some dev started mixing the concepts of "enum values for the {{break-*}} properties" on the
one hand and "break classes" on the other. The latter is internal to FOP, so one could argue that,
architecturally, it is actually improper to use the same symbolic literals, defined in
{{org.apache.fop.fo.Constants}}, for something that is strictly internal to the
{{org.apache.fop.layoutmgr}} package. For that matter, I am not sure what the rationale was for putting
that {{BreakUtil}} class in the _general_ utilities package. I cannot immediately imagine where that
would be useful outside of the layout context, but maybe that's just me...

Now, the result is that a literal EN_LINE, which represents the enum value "line" -- and note: cannot even be
used as a value in said {{break-*}} properties; it is meant for the more exotic, float-related
{{intrusion-displace}} property (see: http://www.w3.org/TR/xsl/#intrusion-displace ) -- is being
used, in the FOP layout code, to represent a "break class" that I would guess to have the highest priority...?

A "break class" is roughly the result in the layout code of merging the different {{break-\*}} *and*
{{keep-\*}} properties at different levels. Since there is a specific
{{keep-with-next.within-line}} property that is implicitly set via the shorthand, that now
translates into a "break class" of EN_LINE... Pretty sure the {{.within-line}} component is not
officially supported, though (read: not included in the test cases). The general workaround given on
fop-users <at>  is usually to avoid using the shorthand for specifying keeps, and mostly useful to avoid
accidentally setting {{keep-together.within-line}} to "always". Perhaps worth a try to check here
whether explicitly setting only the {{.within-page}} and/or {{.within-column}} to the integer value
(Continue reading)

djibril (JIRA | 21 May 12:26 2016
Picon

[jira] [Commented] (FOP-2364) Keep-with-next integer value: Illegal value for breakClass: 75


    [
https://issues.apache.org/jira/browse/FOP-2364?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15294893#comment-15294893
] 

djibril commented on FOP-2364:
------------------------------

Dear,

I have the same problem. All PDF creation failed with the error message : 
GRAVE: Exception
org.apache.fop.apps.FOPException: Illegal value for breakClass: 75
java.lang.IllegalArgumentException: Illegal value for breakClass: 75
	at org.apache.fop.cli.InputHandler.transformTo(InputHandler.java:288)
	at org.apache.fop.cli.InputHandler.renderTo(InputHandler.java:115)
	at org.apache.fop.cli.Main.startFOP(Main.java:186)
	at org.apache.fop.cli.Main.main(Main.java:217)
Caused by: java.lang.IllegalArgumentException: Illegal value for breakClass: 75
	at org.apache.fop.util.BreakUtil.getBreakClassPriority(BreakUtil.java:39)
	at org.apache.fop.util.BreakUtil.compareBreakClasses(BreakUtil.java:58)
	at org.apache.fop.layoutmgr.list.ListItemLayoutManager.getCombinedKnuthElementsForListItem(ListItemLayoutManager.java:413)
	at org.apache.fop.layoutmgr.list.ListItemLayoutManager.getNextKnuthElements(ListItemLayoutManager.java:326)
	at org.apache.fop.layoutmgr.BlockStackingLayoutManager.getNextKnuthElements(BlockStackingLayoutManager.java:239)
	at org.apache.fop.layoutmgr.BlockStackingLayoutManager.getNextChildElements(BlockStackingLayoutManager.java:498)
	at org.apache.fop.layoutmgr.BlockStackingLayoutManager.getNextKnuthElements(BlockStackingLayoutManager.java:289)
	at org.apache.fop.layoutmgr.list.ListBlockLayoutManager.getNextKnuthElements(ListBlockLayoutManager.java:103)
	at org.apache.fop.layoutmgr.BlockStackingLayoutManager.getNextKnuthElements(BlockStackingLayoutManager.java:239)
	at org.apache.fop.layoutmgr.BlockLayoutManager.getNextChildElements(BlockLayoutManager.java:141)
	at org.apache.fop.layoutmgr.BlockStackingLayoutManager.getNextKnuthElements(BlockStackingLayoutManager.java:289)
(Continue reading)

Apache Jenkins Server | 17 May 15:39 2016
Picon

Build failed in Jenkins: xmlgraphics-fop #39

See <https://builds.apache.org/job/xmlgraphics-fop/39/changes>

Changes:

[ssteiner] FOP-2608: Convert OTF to Type 1 in postscript

------------------------------------------
[...truncated 967 lines...]
Downloading: https://repository.apache.org/content/repositories/snapshots/org/apache/xmlgraphics/batik-swing/1.9.0-SNAPSHOT/maven-metadata.xml
[WARNING] Could not transfer metadata
org.apache.xmlgraphics:batik-swing:1.9.0-SNAPSHOT/maven-metadata.xml from/to
apache.snapshots.https (https://repository.apache.org/content/repositories/snapshots):
Failed to transfer file:
https://repository.apache.org/content/repositories/snapshots/org/apache/xmlgraphics/batik-swing/1.9.0-SNAPSHOT/maven-metadata.xml.
Return code is: 503, ReasonPhrase:Service Unavailable.
Downloading: https://repository.apache.org/content/repositories/snapshots/org/apache/xmlgraphics/batik-squiggle/1.9.0-SNAPSHOT/maven-metadata.xml
[WARNING] Could not transfer metadata
org.apache.xmlgraphics:batik-squiggle:1.9.0-SNAPSHOT/maven-metadata.xml from/to
apache.snapshots.https (https://repository.apache.org/content/repositories/snapshots):
Failed to transfer file:
https://repository.apache.org/content/repositories/snapshots/org/apache/xmlgraphics/batik-squiggle/1.9.0-SNAPSHOT/maven-metadata.xml.
Return code is: 503, ReasonPhrase:Service Unavailable.
Downloading: https://repository.apache.org/content/repositories/snapshots/org/apache/xmlgraphics/batik-svgpp/1.9.0-SNAPSHOT/maven-metadata.xml
[WARNING] Could not transfer metadata
org.apache.xmlgraphics:batik-svgpp:1.9.0-SNAPSHOT/maven-metadata.xml from/to
apache.snapshots.https (https://repository.apache.org/content/repositories/snapshots):
Failed to transfer file:
https://repository.apache.org/content/repositories/snapshots/org/apache/xmlgraphics/batik-svgpp/1.9.0-SNAPSHOT/maven-metadata.xml.
Return code is: 503, ReasonPhrase:Service Unavailable.
Downloading: https://repository.apache.org/content/repositories/snapshots/org/apache/xmlgraphics/batik-ttf2svg/1.9.0-SNAPSHOT/maven-metadata.xml
(Continue reading)

simon steiner (JIRA | 17 May 15:47 2016
Picon

[jira] [Closed] (FOP-2608) Convert OTF to Type 1 in postscript


     [
https://issues.apache.org/jira/browse/FOP-2608?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

simon steiner closed FOP-2608.
------------------------------
    Resolution: Fixed

> Convert OTF to Type 1 in postscript
> -----------------------------------
>
>                 Key: FOP-2608
>                 URL: https://issues.apache.org/jira/browse/FOP-2608
>             Project: FOP
>          Issue Type: Bug
>            Reporter: simon steiner
>            Assignee: simon steiner
>         Attachments: fop.xconf, test.fo
>
>
> Support for OTF in printers is buggy so convert font to type 1
> fop test.fo -c fop.conf -ps out.ps
> Print using:
> lpr -S IPAddress -P IPAddress out.ps

--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

(Continue reading)

simon steiner (JIRA | 17 May 15:36 2016
Picon

[jira] [Commented] (FOP-2608) Convert OTF to Type 1 in postscript


    [
https://issues.apache.org/jira/browse/FOP-2608?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15286625#comment-15286625
] 

simon steiner commented on FOP-2608:
------------------------------------

Added http://svn.apache.org/viewvc?view=revision&revision=1744262

> Convert OTF to Type 1 in postscript
> -----------------------------------
>
>                 Key: FOP-2608
>                 URL: https://issues.apache.org/jira/browse/FOP-2608
>             Project: FOP
>          Issue Type: Bug
>            Reporter: simon steiner
>            Assignee: simon steiner
>         Attachments: fop.xconf, test.fo
>
>
> Support for OTF in printers is buggy so convert font to type 1
> fop test.fo -c fop.conf -ps out.ps
> Print using:
> lpr -S IPAddress -P IPAddress out.ps

--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
(Continue reading)

simon steiner (JIRA | 17 May 15:32 2016
Picon

[jira] [Updated] (FOP-2608) Convert OTF to Type 1 in postscript


     [
https://issues.apache.org/jira/browse/FOP-2608?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

simon steiner updated FOP-2608:
-------------------------------
    Attachment: test.fo
                fop.xconf

> Convert OTF to Type 1 in postscript
> -----------------------------------
>
>                 Key: FOP-2608
>                 URL: https://issues.apache.org/jira/browse/FOP-2608
>             Project: FOP
>          Issue Type: Bug
>            Reporter: simon steiner
>            Assignee: simon steiner
>         Attachments: fop.xconf, test.fo
>
>
> Support for OTF in printers is buggy so convert font to type 1
> fop test.fo -c fop.conf -ps out.ps
> Print using:
> lpr -S IPAddress -P IPAddress out.ps

--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

(Continue reading)

simon steiner (JIRA | 17 May 15:28 2016
Picon

[jira] [Updated] (FOP-2608) Convert OTF to Type 1 in postscript


     [
https://issues.apache.org/jira/browse/FOP-2608?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

simon steiner updated FOP-2608:
-------------------------------
    Summary: Convert OTF to Type 1 in postscript  (was: OTF in postscript can't be printed)

> Convert OTF to Type 1 in postscript
> -----------------------------------
>
>                 Key: FOP-2608
>                 URL: https://issues.apache.org/jira/browse/FOP-2608
>             Project: FOP
>          Issue Type: Bug
>            Reporter: simon steiner
>            Assignee: simon steiner
>
> Support for OTF in printers is buggy so convert font to type 1
> fop test.fo -c fop.conf -ps out.ps
> Print using:
> lpr -S IPAddress -P IPAddress out.ps

--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

simon steiner (JIRA | 17 May 15:27 2016
Picon

[jira] [Created] (FOP-2608) OTF in postscript can't be printed

simon steiner created FOP-2608:
----------------------------------

             Summary: OTF in postscript can't be printed
                 Key: FOP-2608
                 URL: https://issues.apache.org/jira/browse/FOP-2608
             Project: FOP
          Issue Type: Bug
            Reporter: simon steiner
            Assignee: simon steiner

Support for OTF in printers is buggy so convert font to type 1

fop test.fo -c fop.conf -ps out.ps

Print using:
lpr -S IPAddress -P IPAddress out.ps

--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Chris Bowditch (JIRA | 12 May 15:04 2016
Picon

[jira] [Closed] (FOP-2607) PDF encryption encrypts the link target


     [
https://issues.apache.org/jira/browse/FOP-2607?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Chris Bowditch closed FOP-2607.
-------------------------------
    Resolution: Duplicate

FOP-2279 was closed as a duplicate of FOP-916. Why have you opened a new ticket. If you want an update on
FOP-916 it makes more sense to comment there as the fop-dev list receives copies of comments on any bug in
the bug tracker.

Closing this as a duplicate of FOP-916

> PDF encryption encrypts the link target
> ---------------------------------------
>
>                 Key: FOP-2607
>                 URL: https://issues.apache.org/jira/browse/FOP-2607
>             Project: FOP
>          Issue Type: Bug
>          Components: unqualified
>    Affects Versions: 1.0, 1.1, 2.0, 2.1
>         Environment: Linux, running JDK-1.8
>            Reporter: Darryl Beckett
>
> When using the <fo:basic-link> element to create an external link, the link content is encrypted when
encryption is enabled.
> This has previously been brought up in issue FOP-2279, where examples were given, and a solution was
proposed but as of the latest release (2.1) this still seems to be an issue.
(Continue reading)


Gmane