[jira] [Updated] (FOP-2813) Internal Links break when using page-number-citiation

2019-10-31 Thread Simon Steiner (Jira)


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

Simon Steiner updated FOP-2813:
---
Fix Version/s: (was: 2.3)

> Internal Links break when using page-number-citiation
> -
>
> Key: FOP-2813
> URL: https://issues.apache.org/jira/browse/FOP-2813
> Project: FOP
>  Issue Type: Bug
>  Components: fo/block, fo/page
> Environment: XALAN
> XSL 2.0
>Reporter: Dennis
>Priority: Major
> Attachments: minimal_report.xsl, out.pdf
>
>
> Internal page links break when used in conjunction with 
> pager-number-citiation.
> I made a minimal sheet which generates a ToC and 4 data sites. Links to 
> data1-data3 do not work. Link to data4 works. The breaking point is in the 
> footer with the call to "page-number-citiation-last" ("page-number-citiation" 
> breaks it too). All links to pages AFTER the call (In this case its the id of 
> data3) work. All before do not.
> This issue is not limited to using page-number-citiation in static content 
> but also in page flow. As soon as an id is referenced via this call all 
> internal links that point to the id or any id before in the document break.
> Stylesheet (Also attached with generated pdf):
> {code:java}
> 
> http://www.w3.org/1999/XSL/Transform;
> xmlns:fo="http://www.w3.org/1999/XSL/Format;
> xmlns:java="http://xml.apache.org/xalan/java;
> version="2.0">
>   
>   
> 
>   
>  page-width="21.0cm" margin="2cm">
>   
>   
>   
> 
>   
>   
> 
>   
> data1
>   
>   
> data2
>   
>   
> data3
>   
>   
> data4
>   
> 
>   
>   
> 
> 
>   data 1
> 
>   
>   
> 
> 
>   data 2
> 
>   
>   
> 
> 
>   data 3
> 
>   
>   
> 
> 
>   data 4
> 
>   
> 
>   
>   
> 
> 
>   
> 
>   
> 
>   
>   
>   
> 
>   
>  /
> 
>   
> 
>   
> {code}
> Output when generating:
> {code:java}
> 2018-09-05 14:03:33,829 - WARN  - The contents of fo:region-after on page 2 
> exceed the available area in the block-progression direction by 11566 
> millipoints. (No context info available)
> 2018-09-05 14:03:33,835 - WARN  - The contents of fo:region-after on page 3 
> exceed the available area in the block-progression direction by 11566 
> millipoints. (No context info available)
> 2018-09-05 14:03:33,837 - WARN  - The contents of fo:region-after on page 4 
> exceed the available area in the block-progression direction by 11566 
> millipoints. (No context info available)
> 2018-09-05 14:03:33,840 - WARN  - The contents of fo:region-after on page 5 
> exceed the available area in the block-progression direction by 11566 
> millipoints. (No context info available)
> 2018-09-05 14:03:33,844 - INFO  - Rendered page #1.
> 2018-09-05 14:03:33,845 - INFO  - Rendered page #2.
> 2018-09-05 14:03:33,846 - INFO  - Rendered page #3.
> 2018-09-05 14:03:33,847 - INFO  - Rendered page #4.
> 2018-09-05 14:03:33,847 - INFO  - Rendered page #5.
> 2018-09-05 14:03:33,848 - WARN  - 4 link targets could not be fully resolved 
> and now points to the top of the page or are dysfunctional.{code}



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Updated] (FOP-2813) Internal Links break when using page-number-citiation

2018-09-05 Thread Dennis (JIRA)


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

Dennis updated FOP-2813:

Description: 
Internal page links break when used in conjunction with pager-number-citiation.

I made a minimal sheet which generates a ToC and 4 data sites. Links to 
data1-data3 do not work. Link to data4 works. The breaking point is in the 
footer with the call to "page-number-citiation-last" ("page-number-citiation" 
breaks it too). All links to pages AFTER the call (In this case its the id of 
data3) work. All before do not.

This issue is not limited to using page-number-citiation in static content but 
also in page flow. As soon as an id is referenced via this call all internal 
links that point to the id or any id before in the document break.

Stylesheet (Also attached with generated pdf):
{code:java}

http://www.w3.org/1999/XSL/Transform;
xmlns:fo="http://www.w3.org/1999/XSL/Format;
xmlns:java="http://xml.apache.org/xalan/java;
version="2.0">

  

  


  

  
  
  

  

  

  
data1
  
  
data2
  
  
data3
  
  
data4
  

  

  


  data 1

  

  


  data 2

  

  


  data 3

  

  


  data 4

  

  

  


  

  

  

  
  

  
 /

  

  

{code}
Output when generating:
{code:java}
2018-09-05 14:03:33,829 - WARN  - The contents of fo:region-after on page 2 
exceed the available area in the block-progression direction by 11566 
millipoints. (No context info available)
2018-09-05 14:03:33,835 - WARN  - The contents of fo:region-after on page 3 
exceed the available area in the block-progression direction by 11566 
millipoints. (No context info available)
2018-09-05 14:03:33,837 - WARN  - The contents of fo:region-after on page 4 
exceed the available area in the block-progression direction by 11566 
millipoints. (No context info available)
2018-09-05 14:03:33,840 - WARN  - The contents of fo:region-after on page 5 
exceed the available area in the block-progression direction by 11566 
millipoints. (No context info available)
2018-09-05 14:03:33,844 - INFO  - Rendered page #1.
2018-09-05 14:03:33,845 - INFO  - Rendered page #2.
2018-09-05 14:03:33,846 - INFO  - Rendered page #3.
2018-09-05 14:03:33,847 - INFO  - Rendered page #4.
2018-09-05 14:03:33,847 - INFO  - Rendered page #5.
2018-09-05 14:03:33,848 - WARN  - 4 link targets could not be fully resolved 
and now points to the top of the page or are dysfunctional.{code}

  was:
Internal page links break when used in conjunction with pager-number-citiation.

I made a minimal sheet which generates a ToC and 4 data sites. Links to 
data1-data3 do not work. Link to data4 works. The breaking point is in the 
footer with the call to "page-number-citiation-last" ("page-number-citiation" 
breaks it too). All links to pages AFTER the call (In this case its the id of 
data3) work. All before do not.

This issue is not limited to using page-number-citiation in static content but 
also in page flow. As soon as an id is referenced via this call all internal 
links that point to the id or any id before in the document break.
{code:java}

http://www.w3.org/1999/XSL/Transform;
xmlns:fo="http://www.w3.org/1999/XSL/Format;
xmlns:java="http://xml.apache.org/xalan/java;
version="2.0">

  

  


  

  
  
  

  

  

  
data1
  
  
data2
  
  
data3
  
  
data4
  

  

  


  data 1

  

  


  data 2

  

  


  data 3

  

  


  data 4

  

  

  


  

  

  

  
  

  
 /

  

  

{code}
Output when generating:
{code:java}
2018-09-05 14:03:33,829 - WARN  - The contents of fo:region-after on page 2 
exceed the available area in the block-progression direction by 11566 
millipoints. (No context info available)
2018-09-05 14:03:33,835 - WARN  - The contents of fo:region-after on page 3 
exceed the available area in the block-progression direction by 11566 
millipoints. (No context info available)
2018-09-05 14:03:33,837 - WARN  - The contents of fo:region-after on page 4 
exceed the available area in the block-progression direction by 11566 
millipoints. (No context info available)