[jira] [Commented] (FOP-2425) FOP dependencies in Tomcat endorsed

2018-05-16 Thread Matthew Broadhead (JIRA)

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

Matthew Broadhead commented on FOP-2425:


i am on version 2.2 now which seems to play nicely with TomEE dependencies

> FOP dependencies in Tomcat endorsed
> ---
>
> Key: FOP-2425
> URL: https://issues.apache.org/jira/browse/FOP-2425
> Project: FOP
>  Issue Type: Bug
>  Components: unqualified
>Affects Versions: 1.1
> Environment: TomEE Plume 1.7.1, eclipse luna, maven
>Reporter: Matthew Broadhead
>Priority: Major
>
> Any attempt to put fop dependencies in the server endorsed directory (to 
> reduce war size) results in various conflicts and errors.  Particularly 
> clashes between commons-logging-1.0.4 and commons-logging-1.1.1 and xml-apis 
> are the main problems.
> Maybe the TomEE team could also consider including FOP in the server as 
> standard



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Resolved] (FOP-687) referencing a custom font (TTF or Adobe Type 1) for a pdf document fails witch fop-0.20.4

2018-05-16 Thread simon steiner (JIRA)

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

simon steiner resolved FOP-687.
---
Resolution: Invalid

> referencing a custom font (TTF or Adobe Type 1) for a pdf document fails 
> witch fop-0.20.4
> -
>
> Key: FOP-687
> URL: https://issues.apache.org/jira/browse/FOP-687
> Project: FOP
>  Issue Type: Bug
>  Components: unqualified
>Affects Versions: 0.20.4
> Environment: Operating System: All
> Platform: PC
> URL: http://marc.theaimsgroup.com/?l=fop-user=105696996918699=2
>Reporter: Markus Sch
>
> Fop fails by trying to use a ttf font and reference it within a pdf document.
> I first embedded a True Type Font into my documents. Thats works great. Here 
> is 
> a snippet from my userconfig.xml file:
>  metrics-file="file:D:/Asfr/unchangedfopsrc/fop-0.20.4/conf/ARIALUNI.XML" 
>kerning="yes" 
>embed-file="file:D:/Asfr/unchangedfopsrc/fop-0.20.4/conf/ARIALUNI.TTF">
>   
>   
>   
>   
> 
> But if I remove the embed-file attribute I end up with an error.
> This is my changed userconfig.xml file:
>  metrics-file="file:D:/Asfr/unchangedfopsrc/fop-0.20.4/conf/ARIALUNI.XML" 
>kerning="yes" 
>   
>   
>   
>   
> 
> This is the error message I get:
> [INFO] FOP 0.20.4
> [INFO] building formatting object tree
> [ERROR] Failed to read font metrics file
> D:/Asfr/unchangedfopsrc/fop-0.20.4/conf
> /ARIALUNI.XML : null
> [INFO] [1]
> [ERROR] unknown font ArialUnicodeMS,normal,normal so defaulted font to any
> [ERROR] unknown font ArialUnicodeMS,normal,normal so defaulted font to any
> [ERROR] unknown font ArialUnicodeMS,normal,normal so defaulted font to any
> [INFO] [2]
> Please note: I only changed the userconfig.xml. The font-metrics file is
> still there.
> If I use
>  metrics-file="file:D:/Asfr/unchangedfopsrc/fop-0.20.4/conf/ARIALUNI.XML" 
>kerning="yes" 
>embed-file=""
>   
>   
>   
>   
> 
> fop generates the pdf document, but with this error message at the end:
> [INFO] Parsing of document complete, stopping renderer
> [ERROR] Failed to embed font [65] ArialUnicodeMS:
> D:\Asfr\unchangedfopsrc\fop-0.
> 20.4 (Access is denied)
> I can open the pdf document, but I get the error message "A font required
> for font substitution is missing".
> And if I use the following in my userconfig.xml I end up with the same error
> message as the one above.
>  metrics-file="file:D:/Asfr/unchangedfopsrc/fop-0.20.4/conf/ARIALUNI.XML" 
>kerning="yes" 
>embed-file="*.ttf"
>   
>   
>   
>   
> 
> I'm using jdk 1.4.0.
> I also tested this with fop-0.20.5rc3a and it seems that the issue has been 
> fixed for Adobe Type 1 fonts. But with True Type fonts it still doesn't work. 
> Just the fop error messages are different with 0.20.5rc3a.
> I tested the issue with arialuni.ttf and tahoma.ttf



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Resolved] (FOP-1718) PCL Painter not thread safe.

2018-05-16 Thread simon steiner (JIRA)

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

simon steiner resolved FOP-1718.

Resolution: Cannot Reproduce

> PCL Painter not thread safe.
> 
>
> Key: FOP-1718
> URL: https://issues.apache.org/jira/browse/FOP-1718
> Project: FOP
>  Issue Type: Bug
>  Components: renderer/pcl
>Affects Versions: trunk
> Environment: Operating System: Windows XP
> Platform: PC
>Reporter: Chris Bowditch
> Attachments: input.if
>
>
> When using multiple threads to render the attached IF XML to PCL using the
> Painter the following exception occurs. The exception does not occur when only
> a single thread is used. In a quick debugging session we observed that when 
> the
> error occurs the method PCLPainter.getTextBoundingBox returns a rectangle with
> negative width
> java.lang.NegativeArraySizeException
> at java.awt.image.DataBufferByte.(DataBufferByte.java:42)
> at java.awt.image.Raster.createInterleavedRaster(Raster.java:253)
> at java.awt.image.Raster.createInterleavedRaster(Raster.java:194)
> at
> org.apache.xmlgraphics.image.loader.impl.ImageConverterG2D2Bitmap.createGrayBufferedImageWithAlpha(ImageConve
> rterG2D2Bitmap.java:170)
> at
> org.apache.xmlgraphics.image.loader.impl.ImageConverterG2D2Bitmap.paintToBufferedImage(ImageConverterG2D2Bitm
> ap.java:108)
> at
> org.apache.xmlgraphics.image.loader.impl.ImageConverterG2D2Bitmap.convert(ImageConverterG2D2Bitmap.java:74)
> at
> org.apache.xmlgraphics.image.loader.pipeline.ImageProviderPipeline.execute(ImageProviderPipeline.java:173)
> at
> org.apache.xmlgraphics.image.loader.ImageManager.convertImage(ImageManager.java:330)
> at
> org.apache.fop.render.intermediate.AbstractIFPainter.drawImage(AbstractIFPainter.java:209)
> at
> org.apache.fop.render.pcl.PCLPainter.paintMarksAsBitmap(PCLPainter.java:304)
> at
> org.apache.fop.render.pcl.PCLPainter.drawTextAsBitmap(PCLPainter.java:489)
> at org.apache.fop.render.pcl.PCLPainter.drawText(PCLPainter.java:329)
> at
> org.apache.fop.render.intermediate.IFParser$Handler$TextHandler.endElement(IFParser.java:487)
> at
> org.apache.fop.render.intermediate.IFParser$Handler.endElement(IFParser.java:277)



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Resolved] (FOP-856) problem displaying Japanese fonts in PDF.

2018-05-16 Thread simon steiner (JIRA)

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

simon steiner resolved FOP-856.
---
Resolution: Cannot Reproduce

> problem displaying Japanese fonts in PDF.
> -
>
> Key: FOP-856
> URL: https://issues.apache.org/jira/browse/FOP-856
> Project: FOP
>  Issue Type: Bug
>  Components: renderer/pdf
>Affects Versions: 0.15
> Environment: Operating System: All
> Platform: HP
>Reporter: shyama
>
> I have a problem while rendering XML containing unicode characters into 
> japanese
> characters.
>I am working on Weblogic 8.1 on NT OS. When the font
> file(Msmincho.ttf) is placed in c:/winnt/fonts
> directory the rendering works fine and pdf is
> generated with Japanese Characters. But when the ttf
> file is place in a different folder I get the
> following exception even though I have made an entry in basedir element of
> userconfig file.
> java.lang.NullPointerException
> at
> org.apache.fop.render.pdf.fonts.LazyFont.getAscender(LazyFont.java:82)
> at
> org.apache.fop.layout.FontState.getAscender(FontState.java:56)
> at
> org.apache.fop.layout.LineArea.(LineArea.java:111)
> at
> org.apache.fop.layout.BlockArea.start(BlockArea.java:181)
> at
> org.apache.fop.fo.flow.Block.layout(Block.java:251)
> at
> org.apache.fop.fo.flow.TableCell.layout(TableCell.java:269)
> at
> org.apache.fop.fo.flow.TableRow.layout(TableRow.java:344)
> at
> org.apache.fop.fo.flow.TableBody.layout(TableBody.java:172)
> at
> org.apache.fop.fo.flow.Table.layout(Table.java:247)
> at
> org.apache.fop.fo.flow.Flow.layout(Flow.java:156)
> at
> org.apache.fop.fo.flow.Flow.layout(Flow.java:113)
> at
> org.apache.fop.fo.pagination.PageSequence.format(PageSequence.java:296)
> at
> org.apache.fop.apps.StreamRenderer.render(StreamRenderer.java:200)
> at
> org.apache.fop.fo.FOTreeBuilder.endElement(FOTreeBuilder.java:182)
> at
> org.apache.xerces.parsers.AbstractSAXParser.endElement(Unknown
> Source)
> at
> org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanEndElement(Unknown
> Source)
> at
> org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown
> Source)
> at
> org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown
> Source)
> at
> org.apache.xerces.parsers.DTDConfiguration.parse(Unknown
> Source)
> at
> org.apache.xerces.parsers.DTDConfiguration.parse(Unknown
> Source)
> at
> org.apache.xerces.parsers.XMLParser.parse(Unknown
> Source)
> at
> org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown
> Source)
> at
> org.apache.fop.apps.Driver.render(Driver.java:481)
> at
> org.apache.fop.apps.Driver.run(Driver.java:554)
> at
> com.db.eqr.ger.ui.web.company.pdf.GenerateMYPDF.createPDF(GenerateMYPDF.java:150)
> at
> com.db.eqr.ger.ui.web.company.pdf.CompanyPDFAction.execute(CompanyPDFAction.java:146)
> at
> org.apache.struts.action.RequestProcessor.processActionPerform(RequestProcessor.java:465)
> at
> org.apache.struts.action.RequestProcessor.process(RequestProcessor.java:274)
> at
> org.apache.struts.action.ActionServlet.process(ActionServlet.java:1422)
> at
> org.apache.struts.action.ActionServlet.doPost(ActionServlet.java:523)
> at
> javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
> at
> javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
> at
> weblogic.servlet.internal.ServletStubImpl$ServletInvocationAction.run(ServletStubImpl.java:1053)
> at
> weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:387)
> at
> weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:28)
> at
> weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:27)
> Can anyone help me out and let me know what could be the problem here.
>  I have used the following userconfig file.
> 
> 
> 
> 
>   
> baseDir
> c:/shyamajoshi/conf/fop
>   
> 
>   
> 
> 
> 
> 
>  
>  
>  
> embed-file="msmincho.ttf" kerning="yes">
>weight="normal"/>
>weight="bold"/>
>weight="normal"/>
>weight="bold"/>
>
>   
> 
> 
> Regards,
> Shyama



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Resolved] (FOP-1617) FOP gets an error for Windows Japanese font.

2018-05-16 Thread simon steiner (JIRA)

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

simon steiner resolved FOP-1617.

Resolution: Cannot Reproduce

> FOP gets an error for Windows Japanese font.
> 
>
> Key: FOP-1617
> URL: https://issues.apache.org/jira/browse/FOP-1617
> Project: FOP
>  Issue Type: Bug
>  Components: font/unqualified
>Affects Versions: 0.95
> Environment: Operating System: Windows XP
> Platform: PC
>Reporter: Mamoru Asagami
> Attachments: fopdoc.zip
>
>
> Problem:
> You get:  
>[Fatal Error] msmincho.xml:1:171: Character reference "" is an invalid 
> XML character
> if you make font metrics files from msmincho.ttc and msgothic.ttc of Windows 
> and use them.
> To reproduce it, set up the attached file: fopdoc.zip as c:\fopdoc, 
> fop.xconf.xml(one of the zip)  as ${fop.home}/conf/fop.xconf.xml, and run ant 
> as follows:
> c:\fopdoc>ant
> For your convenience, I included ant's error message as err.txt in the 
> attached file: fopdoc.zip.
> Solution:
> I found something in "public final String readTTFString(int len)" of  
> org.apache.fop.fonts.truetype.FontFileReader.
> When I replaced the character encoding discerning heuristic:
>  
> final String encoding;
> if ((tmp.length > 0) && (tmp[0] == 0)) {
> encoding = "UTF-16BE";
> } else {
> encoding = "ISO-8859-1";
> }
> with the following:
> String encoding = "ISO-8859-1";
> for(int c: tmp) {
> c &= 0xff;
> if(c==0 || c >= 0x80) {
> encoding = "UTF-16BE";
> break;
> }
> }
> everything went fine.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Resolved] (FOP-1609) Add configuration option to encode TTF fonts as single byte fonts

2018-05-16 Thread simon steiner (JIRA)

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

simon steiner resolved FOP-1609.

Resolution: Fixed

> Add configuration option to encode TTF fonts as single byte fonts
> -
>
> Key: FOP-1609
> URL: https://issues.apache.org/jira/browse/FOP-1609
> Project: FOP
>  Issue Type: Improvement
>  Components: font/unqualified
>Affects Versions: trunk
> Environment: Operating System: All
> Platform: All
>Reporter: Jeremias Maerki
>
> TTF Fonts configured without XML font metrics file are always embedded as CID 
> fonts. They are generated as single byte fonts if the font is not embedded 
> (because FOP doesn't currently support non-embedded CID fonts). This may need 
> to be made configurable to force single byte handling for certain cases.
> See http://markmail.org/message/2dakokitggdrf4vn (and replies)



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Resolved] (FOP-2026) Cannot generate JPEG as output format

2018-05-16 Thread simon steiner (JIRA)

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

simon steiner resolved FOP-2026.

Resolution: Cannot Reproduce

> Cannot generate JPEG as output format
> -
>
> Key: FOP-2026
> URL: https://issues.apache.org/jira/browse/FOP-2026
> Project: FOP
>  Issue Type: Bug
>  Components: image/unqualified
>Affects Versions: 1.0
> Environment: Operating System: All
> Platform: PC
>Reporter: Paul
>
> Selecting JPEG as output format by using TIFF output with JPEG compression 
> and running FOP in embedded mode results in exception even though 24 bit mode 
> selected in FOP configuration file (rbg):  
> Caused by: javax.imageio.IIOException: Can only JPEG compress 8- and 24-bit 
> images!
>   at 
> com.sun.media.imageioimpl.plugins.tiff.TIFFBaseJPEGCompressor.encode(TIFFBaseJPEGCompressor.java:385)
>   at 
> com.sun.media.imageioimpl.plugins.tiff.TIFFImageWriter.writeTile(TIFFImageWriter.java:2309)
>   at 
> com.sun.media.imageioimpl.plugins.tiff.TIFFImageWriter.write(TIFFImageWriter.java:2686)
>   ... 28 more



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Resolved] (FOP-1879) Images being created with a blueish tint in the PDF

2018-05-16 Thread simon steiner (JIRA)

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

simon steiner resolved FOP-1879.

Resolution: Cannot Reproduce

> Images being created with a blueish tint in the PDF
> ---
>
> Key: FOP-1879
> URL: https://issues.apache.org/jira/browse/FOP-1879
> Project: FOP
>  Issue Type: Bug
>  Components: image/unqualified
>Affects Versions: 0.95
> Environment: Operating System: Linux
> Platform: Other
>Reporter: jeremy.grant
> Attachments: nils_disc.png, nils_pdf.png
>
>
> When PDF is generated, some images are appearing with a blue hue to them. 
> Example attached.
> System specifics...
> OS
> RHEL
> OS Version
> Red Hat Enterprise Linux Server release 5.3
> Server
> VMWare
> CPU
> 4 2.40GHz Intel(R) Xeon(R) CPU E7450



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Resolved] (FOP-1895) NOP position in AFP output

2018-05-16 Thread simon steiner (JIRA)

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

simon steiner resolved FOP-1895.

Resolution: Incomplete

> NOP position in AFP output
> --
>
> Key: FOP-1895
> URL: https://issues.apache.org/jira/browse/FOP-1895
> Project: FOP
>  Issue Type: Improvement
>  Components: renderer/pcl
>Affects Versions: trunk
> Environment: Operating System: Windows XP
> Platform: PC
>Reporter: Sandeep
> Attachments: NOP_Position.JPG
>
>
> Hi Everyone,
> I am using FOP 1.0 tool to render an AFP output document with multiple pages. 
> I am using afp extension elements  to insert information 
> with each logical page in the output. The current implementation inserts the 
> NOP within/inside the logical page, but my requirement is to put the NOP 
> above/before the logical page in AFP output. This seems to be a valid 
> requirement as per MO: DCA format but I could not find any way to configure 
> this in current FOP 1.0 version.
> My request is to provide an attribute or configuration parameter to define 
> the position of NOP in afp output. I have attached an image file for 
> reference.
> Is it possible to get this feature added/fixed and delivered as a patch if 
> this is a simple change? I am currently stuck with this and need to figure 
> out my options.
> Appreciate your help.
> Thanks & Regards,
> Sandeep



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Resolved] (FOP-2425) FOP dependencies in Tomcat endorsed

2018-05-16 Thread simon steiner (JIRA)

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

simon steiner resolved FOP-2425.

Resolution: Won't Fix

> FOP dependencies in Tomcat endorsed
> ---
>
> Key: FOP-2425
> URL: https://issues.apache.org/jira/browse/FOP-2425
> Project: FOP
>  Issue Type: Bug
>  Components: unqualified
>Affects Versions: 1.1
> Environment: TomEE Plume 1.7.1, eclipse luna, maven
>Reporter: Matthew Broadhead
>Priority: Major
>
> Any attempt to put fop dependencies in the server endorsed directory (to 
> reduce war size) results in various conflicts and errors.  Particularly 
> clashes between commons-logging-1.0.4 and commons-logging-1.1.1 and xml-apis 
> are the main problems.
> Maybe the TomEE team could also consider including FOP in the server as 
> standard



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Resolved] (FOP-2700) There is a problem about directory line feed

2018-05-16 Thread simon steiner (JIRA)

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

simon steiner resolved FOP-2700.

Resolution: Cannot Reproduce

> There is a problem about directory line feed
> 
>
> Key: FOP-2700
> URL: https://issues.apache.org/jira/browse/FOP-2700
> Project: FOP
>  Issue Type: Bug
>Reporter: 梁雨石
>Priority: Minor
>
> When I make a catalog,I set up a attribute:text-align-last="justify".In order 
> to making the catalog align at both ends.But if the title include a full 
> space,and after the full space there are more than one line 
> text(Language:JA),there will be a line feed at the full space.
>so,is there any body could tell me how can I do to make the catalog align 
> at both ends and don't make line feed.
>If there is no way to achieve what I want.Could you please tell me the 
> rules of the line feed.Besides the full space ,is there any other symbol can 
> make this things? 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Resolved] (FOP-2524) FOP 2.0: target-resolution not set in FoUserAgent

2018-05-16 Thread simon steiner (JIRA)

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

simon steiner resolved FOP-2524.

Resolution: Cannot Reproduce

> FOP 2.0: target-resolution not set in FoUserAgent
> -
>
> Key: FOP-2524
> URL: https://issues.apache.org/jira/browse/FOP-2524
> Project: FOP
>  Issue Type: Bug
>  Components: renderer/png
>Affects Versions: 2.0
> Environment: Java 1.8.0_51, 64 Bit, Windows 7, Windows 2008 R2
>Reporter: MH
>Priority: Major
> Attachments: screenshot-FOP-PNG-Renderer.png
>
>
> We upgraded from FOP 1.0 to FOP 2.0 (as we had to skip FOP 1.1 due to a 
> blocker bug in 1.1). After converting all Java embedding code, we are now in 
> test phase. Almost everything looks good, but our PNG rendered documents 
> suddenly all look very blurry (see atachement). We had the same problem with 
> FOP 1.0 but "solved" it by setting the target resolution to 288:
> 288
> We still have this setting in the fop user config XML file, but it seems that 
> it has no effect anymore!



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Resolved] (FOP-2568) Apache PDF issue while rendering images

2018-05-16 Thread simon steiner (JIRA)

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

simon steiner resolved FOP-2568.

Resolution: Cannot Reproduce

> Apache PDF issue while rendering images
> ---
>
> Key: FOP-2568
> URL: https://issues.apache.org/jira/browse/FOP-2568
> Project: FOP
>  Issue Type: Bug
>  Components: image/jpeg
>Affects Versions: 1.0
> Environment: Linux, windows
>Reporter: Sushmitha
>Priority: Minor
> Attachments: FO.xml, file0.jpg, file1.png, file6.png
>
>
> Hi,
> I'm facing issue while rendering images. Some images are failing to render in 
> the generated PDF. Please suggest me if anything i missed here or any 
> workaround is there.
> Please find the below details
> FOP version - 1.0
> OS - Unix, Windows
> XSL-FO desc:
>  margin-bottom="0px" margin-left="0px" padding-top="0px" padding-right="0px" 
> padding-bottom="0px" padding-left="0px" font-size="100%">
>border-bottom-width="0px" border-left-width="0px" border-right-width="0px" 
> src="url('http://document.int.nextcanada.westlaw.com/Blob/V1/I070f7ddba9430301e0540021280d79ee.png?targetType=inlineoriginationContext=document')"
>  role="Image 1 within Option Consommateurs c. Infineon Technologie, a.g." 
> content-width="486" content-height="411">
> 
> Error message: Raster ByteInterleavedRaster: width = 486 height = 411 
> #numDataElements 3 dataOff[0] = 2 is incompatible with ColorModel ColorModel: 
> #pixelBits = 8 numComponents = 1 color space = 
> java.awt.color.ICC_ColorSpace@1aef205 transparency = 1 has alpha = false 
> isAlphaPre = false



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Resolved] (FOP-2622) Maerski FOP extension incompatible with latest Oracle Rest Data Service distribution

2018-05-16 Thread simon steiner (JIRA)

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

simon steiner resolved FOP-2622.

Resolution: Cannot Reproduce

> Maerski FOP extension incompatible with latest Oracle Rest Data Service 
> distribution
> 
>
> Key: FOP-2622
> URL: https://issues.apache.org/jira/browse/FOP-2622
> Project: FOP
>  Issue Type: Bug
> Environment: Oracle Rest Data Services (ORDS) comes with an fop.jar
>Reporter: Hayden Hudson
>Priority: Major
>
> I use Jeremias Maerski's fop extension in combination with Oracle Rest Data 
> Services (ORDS). When I upgraded from ORDS 3.0.2 to 3.0.5, the fop extension 
> ceased working. The issue was fixed when I replaced the fop.jar from the 
> 3.0.2 distribution with that of the 3.0.5 distribution.
> I reported the issue to both Oracle and Jeremias. I wish I better understood 
> what the issue was.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Resolved] (FOP-1663) ImageIO-based images are blurry when rendering a PDF

2018-05-16 Thread simon steiner (JIRA)

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

simon steiner resolved FOP-1663.

Resolution: Cannot Reproduce

> ImageIO-based images are blurry when rendering a PDF
> 
>
> Key: FOP-1663
> URL: https://issues.apache.org/jira/browse/FOP-1663
> Project: FOP
>  Issue Type: Bug
>  Components: renderer/pdf
>Affects Versions: trunk
> Environment: Operating System: All
> Platform: All
>Reporter: David Green
> Attachments: Picture 2.png, test-image.png, test.fo, test.pdf
>
>
> When using PNG or JPG images are blurry when rendering PDF output.  The 
> problem appears to be related to image size computations even when scaling is 
> not used, however this may not be the only factor.  Running with a patched 
> version of FOP (with a fix for bug 27151) images are still blurry (though 
> slightly better than running without the patch).



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Resolved] (FOP-2428) Apache PDF issue with Wingdings characters

2018-05-16 Thread simon steiner (JIRA)

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

simon steiner resolved FOP-2428.

Resolution: Cannot Reproduce

> Apache PDF issue with Wingdings characters
> --
>
> Key: FOP-2428
> URL: https://issues.apache.org/jira/browse/FOP-2428
> Project: FOP
>  Issue Type: Bug
>  Components: fo/inline
>Affects Versions: 1.0
> Environment: Windows, Unix
>Reporter: PRAVAT
>Priority: Major
>  Labels: ApachePDf, Wingding
> Attachments: Sample.pdf, Sample.rtf, Sample.xml, Wingdings.ttf, 
> fop.xconf, myfop.xconf, test.1.0.pdf, test.1.0.rtf, test.fo.xml, 
> test.trunk.pdf, test.trunk.rtf
>
>
> The below unicode Character   s give different results for Apache RTF 
> and PDF format. The font used here is Winfdings. RTF gives the correct 
> output, where as the PDF does not find these characters. I am using APache 
> FOP 1.0.
> U+00FDý      
> U+00FEþ   



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Resolved] (FOP-2500) Low performance of PCL printing

2018-05-16 Thread simon steiner (JIRA)

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

simon steiner resolved FOP-2500.

Resolution: Cannot Reproduce

> Low performance of PCL printing
> ---
>
> Key: FOP-2500
> URL: https://issues.apache.org/jira/browse/FOP-2500
> Project: FOP
>  Issue Type: Bug
>Affects Versions: trunk
> Environment: N/A
>Reporter: Konrad Gajewski
>Priority: Major
> Attachments: FopFontConfig.xml, ipp_default.xsl, receipt.xml
>
>
> Hi,
> Generating of the whole PCL page is taking too long. 
> Check by the Java Visual VM shows that more time is consumed by following 
> method:
> org.apache.fop.util.bitmap.DefaultMonochromeBitmapConverter.convertToMonochrome()
>  1200 ms



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Resolved] (FOP-2705) FOP 2.2 Doesn't Compile Due to Batik Dependencies

2018-05-16 Thread simon steiner (JIRA)

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

simon steiner resolved FOP-2705.

Resolution: Fixed

> FOP 2.2 Doesn't Compile Due to Batik Dependencies
> -
>
> Key: FOP-2705
> URL: https://issues.apache.org/jira/browse/FOP-2705
> Project: FOP
>  Issue Type: Bug
>Affects Versions: 2.2
>Reporter: Chris Hannah
>Priority: Critical
>
> I switched to FOP 2.2 so that I could get the fix for FOP-2525. When I 
> changed my FOP dependency to 2.2 my project would not compile. FOP 2.2 uses 
> version 1.9 for Batik dependencies. It appears that some Batik dependencies 
> reference a parent in their POM which does not exist. I resolved the issue in 
> my project by excluding all Batik dependencies for the FOP, and pulling in 
> version 1.8 for all Batik dependencies. I assume that using the Batik 1.9 
> dependencies is desire, so, maybe this should be a BATIK issue instead.
> I pulled the FOP 2.2 dependency from Maven Central. Here is the error that I 
> get when running my build.
> Failed to collect dependencies at org.apache.xmlgraphics:fop:jar:2.2 -> 
> org.apache.xmlgraphics:batik-svg-dom:jar:1.9 -> 
> org.apache.xmlgraphics:batik-awt-util:jar:1.9: Failed to read artifact 
> descriptor for org.apache.xmlgraphics:batik-awt-util:jar:1.9: Could not find 
> artifact org.apache.xmlgraphics:batik:pom:1.9



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Resolved] (FOP-2717) FOP 2.2 did not contain FOP-2300 patch

2018-05-16 Thread simon steiner (JIRA)

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

simon steiner resolved FOP-2717.

Resolution: Cannot Reproduce

> FOP 2.2 did not contain FOP-2300 patch
> --
>
> Key: FOP-2717
> URL: https://issues.apache.org/jira/browse/FOP-2717
> Project: FOP
>  Issue Type: Bug
>Affects Versions: 2.1, 2.2
>Reporter: Duncan Jauncey
>Priority: Major
>  Labels: patch
>
> The patch provided by Seifeddine Dridi in FOP-2300 has a Fix Version of 2.2, 
> implying that it went into the FOP 2.2 release.  On comparing the source, I 
> find that this patch is not present.
> (This is a problem for my customer, as the project that I am working on uses 
> FOP, and does sometimes encounter this NullPointerException.  I have added 
> the patched version of FObj.class to our codebase, which fixes our immediate 
> problem, but we would like to be able to rely on an officially-released 
> version of FOP containing this patch.)



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Resolved] (FOP-2734) issue in Printing emoji symbols in pdf by using fo.ftl

2018-05-16 Thread simon steiner (JIRA)

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

simon steiner resolved FOP-2734.

Resolution: Cannot Reproduce

> issue in Printing emoji symbols in pdf by using fo.ftl
> --
>
> Key: FOP-2734
> URL: https://issues.apache.org/jira/browse/FOP-2734
> Project: FOP
>  Issue Type: Bug
>  Components: fo/block
>Affects Versions: 2.2
> Environment: Ubuntu, Windows , Java, FTL
>Reporter: Nagendra
>Priority: Major
>  Labels: EmojiOne, FOP, Java7, documentation, emoji, fonts
> Attachments: MessageCard-22-08-2017-17-54-18.pdf
>
>   Original Estimate: 48h
>  Remaining Estimate: 48h
>
> Issue in printing pdf, By using apache freemarker fo.ftl,  The text to be 
> print in pdf is "☹️藍☺️" , But instead printing 
> "☹️☺️##" .  
> Can you please check the following attachment of pdf which is having the 
> issue.  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Resolved] (FOP-2775) Japanese characters turn into "###" from XML/XSL to PDF conversion

2018-05-16 Thread simon steiner (JIRA)

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

simon steiner resolved FOP-2775.

Resolution: Not A Problem

> Japanese characters turn into "###" from XML/XSL to PDF conversion
> --
>
> Key: FOP-2775
> URL: https://issues.apache.org/jira/browse/FOP-2775
> Project: FOP
>  Issue Type: Bug
>  Components: renderer/pdf
>Affects Versions: 2.0
>Reporter: Neha
>Priority: Major
> Attachments: FOPProject.zip
>
>
> We are having trouble making Japanese language output with FOP when trying to 
> convert XML/XSL file to PDF file. The characters used in Japanese turns into 
> *###* in PDF file.
>  
> Attaching the project for reference.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Resolved] (FOP-2003) UndeclaredThrowableException generating pdf

2018-05-16 Thread simon steiner (JIRA)

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

simon steiner resolved FOP-2003.

Resolution: Cannot Reproduce

> UndeclaredThrowableException generating pdf
> ---
>
> Key: FOP-2003
> URL: https://issues.apache.org/jira/browse/FOP-2003
> Project: FOP
>  Issue Type: Bug
>  Components: renderer/pdf
>Affects Versions: trunk
> Environment: Operating System: Linux
> Platform: PC
>Reporter: Nahuel
>Priority: Blocker
> Attachments: test, undeclaredthrowableexception
>
>
> An error occurs when we generate PDF with some specials PNG images.
> I put as attachment the stacktrace of the error, and the fo file.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Resolved] (FOP-2293) Whitespace management extension

2018-05-16 Thread simon steiner (JIRA)

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

simon steiner resolved FOP-2293.

   Resolution: Fixed
Fix Version/s: 2.0

> Whitespace management extension
> ---
>
> Key: FOP-2293
> URL: https://issues.apache.org/jira/browse/FOP-2293
> Project: FOP
>  Issue Type: New Feature
>  Components: unqualified
>Affects Versions: trunk
>Reporter: Seifeddine Dridi
>Priority: Minor
>  Labels: XSL-FO
> Fix For: 2.0
>
> Attachments: FO_multi-switch_best-fit_ext_rev10.patch, 
> FO_multi-switch_best-fit_ext_rev11.patch, 
> FO_multi-switch_best-fit_ext_rev12.patch, 
> FO_multi-switch_best-fit_ext_rev13.patch, 
> FO_multi-switch_best-fit_ext_rev2.patch, 
> FO_multi-switch_best-fit_ext_rev3.patch, 
> FO_multi-switch_best-fit_ext_rev4.patch, 
> FO_multi-switch_best-fit_ext_rev5.patch, 
> FO_multi-switch_best-fit_ext_rev6.patch, 
> FO_multi-switch_best-fit_ext_rev7.patch, 
> FO_multi-switch_best-fit_ext_rev8.patch, 
> FO_multi-switch_best-fit_ext_rev9.patch, FO_multi-switch_test.fo, 
> FO_multi-switch_with_best-fit_extension.patch, bestfit.fo, 
> bug_page_ipd_change.fo, doc.pdf, empty-last-page.fo, 
> multi-switch-testcases.zip, multi-switch_bestfit.fo, 
> multiple-feasible-nodes.fo, patch-rev1.1.patch, patch-rev1.patch, 
> patch-rev2.patch, patch.patch, rev11_bug.fo, two-valid-variants.fo
>
>
> I have been working on an extension for whitespace management, similar to 
> what's described here: 
> http://wiki.apache.org/xmlgraphics-fop/WhitespaceManagement
> The logic of the extension is very simple: the user defines a set of 
> alternatives that he wishes to insert at the end of a page, then if there is 
> enough space left, FOP will pick the alternative that best matches the user's 
> selection criteria (first fit, smallest fit, biggest fit).
> This is my first work on FOP and it took me almost 2 months to reach this 
> stage in development. But it's not the end of course, so I'm relying on your 
> feedback to improve it.
> Thank you



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Commented] (FOP-2416) Add support for Arabic Joiners (ZWJ/ZWNJ)

2018-05-16 Thread simon steiner (JIRA)

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

simon steiner commented on FOP-2416:


Is this done?

> Add support for Arabic Joiners (ZWJ/ZWNJ)
> -
>
> Key: FOP-2416
> URL: https://issues.apache.org/jira/browse/FOP-2416
> Project: FOP
>  Issue Type: Improvement
>  Components: layout/unqualified
>Affects Versions: trunk
>Reporter: Glenn Adams
>Priority: Major
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Resolved] (FOP-2738) ArrayIndexOutOfBoundsException in GlyphMapping.addToLetterAdjust

2018-05-16 Thread simon steiner (JIRA)

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

simon steiner resolved FOP-2738.

Resolution: Duplicate

> ArrayIndexOutOfBoundsException in GlyphMapping.addToLetterAdjust
> 
>
> Key: FOP-2738
> URL: https://issues.apache.org/jira/browse/FOP-2738
> Project: FOP
>  Issue Type: Bug
>  Components: fo/inline
>Affects Versions: 2.2
> Environment: Java(TM) SE Runtime Environment (build 1.8.0_144-b01)
> Windows
>Reporter: Vlad Ivanov
>Priority: Major
> Attachments: fop.conf, fop1.fo, image.svg
>
>
> The following exception happens while rendering to a PDF file:
> {code}
>   [fop] SEVERE: SVG graphic could not be rendered. Reason: 
> java.lang.ArrayIndexOutOfBoundsException: 5
>   [fop] java.lang.ArrayIndexOutOfBoundsException: 5
>   [fop] at 
> org.apache.fop.fonts.GlyphMapping.addToLetterAdjust(GlyphMapping.java:286)
>   [fop] at 
> org.apache.fop.fonts.GlyphMapping.processWordNoMapping(GlyphMapping.java:248)
>   [fop] at 
> org.apache.fop.fonts.GlyphMapping.doGlyphMapping(GlyphMapping.java:93)
>   [fop] at 
> org.apache.fop.svg.font.FOPGVTGlyphVector.performDefaultLayout(FOPGVTGlyphVector.java:94)
>   [fop] at 
> org.apache.batik.bridge.GlyphLayout.doExplicitGlyphLayout(Unknown Source)
>   [fop] at 
> org.apache.batik.bridge.GlyphLayout.adjustTextSpacing(Unknown Source)
>   [fop] at org.apache.batik.bridge.GlyphLayout.getAdvance2D(Unknown 
> Source)
>   [fop] at 
> org.apache.batik.bridge.StrokingTextPainter.getTextChunk(Unknown Source)
>   [fop] at 
> org.apache.batik.bridge.StrokingTextPainter.computeTextRuns(Unknown Source)
>   [fop] at 
> org.apache.fop.svg.NativeTextPainter.computeTextRuns(NativeTextPainter.java:223)
>   [fop] at 
> org.apache.batik.bridge.StrokingTextPainter.getTextRuns(Unknown Source)
>   [fop] at 
> org.apache.batik.bridge.StrokingTextPainter.getBounds2D(Unknown Source)
>   [fop] at 
> org.apache.batik.bridge.TextNode.getPrimitiveBounds(Unknown Source)
>   [fop] at 
> org.apache.batik.gvt.AbstractGraphicsNode.getTransformedPrimitiveBounds(Unknown
>  Source)
>   [fop] at 
> org.apache.batik.gvt.AbstractGraphicsNode.getTransformedBounds(Unknown Source)
>   [fop] at 
> org.apache.batik.gvt.CompositeGraphicsNode.getPrimitiveBounds(Unknown Source)
>   [fop] at 
> org.apache.batik.gvt.CompositeGraphicsNode.getTransformedPrimitiveBounds(Unknown
>  Source)
>   [fop] at 
> org.apache.batik.gvt.AbstractGraphicsNode.getTransformedBounds(Unknown Source)
>   [fop] at 
> org.apache.batik.gvt.CompositeGraphicsNode.getPrimitiveBounds(Unknown Source)
>   [fop] at 
> org.apache.batik.gvt.CompositeGraphicsNode.getTransformedPrimitiveBounds(Unknown
>  Source)
>   [fop] at 
> org.apache.batik.gvt.AbstractGraphicsNode.getTransformedBounds(Unknown Source)
>   [fop] at 
> org.apache.batik.gvt.CompositeGraphicsNode.getPrimitiveBounds(Unknown Source)
>   [fop] at 
> org.apache.batik.gvt.AbstractGraphicsNode.getBounds(Unknown Source)
>   [fop] at org.apache.batik.gvt.AbstractGraphicsNode.paint(Unknown 
> Source)
>   [fop] at 
> org.apache.fop.render.pdf.PDFImageHandlerSVG.handleImage(PDFImageHandlerSVG.java:208)
>   [fop] at 
> org.apache.fop.render.intermediate.AbstractIFPainter.drawImage(AbstractIFPainter.java:249)
>   [fop] at 
> org.apache.fop.render.intermediate.AbstractIFPainter.drawImage(AbstractIFPainter.java:205)
>   [fop] at 
> org.apache.fop.render.intermediate.AbstractIFPainter.drawImageUsingImageHandler(AbstractIFPainter.java:170)
>   [fop] at 
> org.apache.fop.render.pdf.PDFPainter.drawImageUsingURI(PDFPainter.java:215)
>   [fop] at 
> org.apache.fop.render.pdf.PDFPainter.drawImage(PDFPainter.java:180)
>   [fop] at 
> org.apache.fop.render.intermediate.IFRenderer.drawImage(IFRenderer.java:1296)
>   [fop] at 
> org.apache.fop.render.intermediate.IFRenderer.renderImage(IFRenderer.java:1283)
>   [fop] at 
> org.apache.fop.render.AbstractRenderer.renderInlineViewport(AbstractRenderer.java:858)
>   [fop] at 
> org.apache.fop.render.AbstractPathOrientedRenderer.renderInlineViewport(AbstractPathOrientedRenderer.java:832)
>   [fop] at 
> org.apache.fop.render.intermediate.IFRenderer.renderInlineViewport(IFRenderer.java:864)
>   [fop] at 
> org.apache.fop.render.AbstractRenderer.renderInlineArea(AbstractRenderer.java:715)
>   [fop] at 
> org.apache.fop.render.intermediate.IFRenderer.renderInlineArea(IFRenderer.java:928)
>   [fop] at 
> org.apache.fop.render.AbstractRenderer.renderInlineParent(AbstractRenderer.java:822)
> 

[jira] [Updated] (FOP-2792) Add boundingbox for OTF

2018-05-16 Thread simon steiner (JIRA)

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

simon steiner updated FOP-2792:
---
Fix Version/s: 2.3

> Add boundingbox for OTF
> ---
>
> Key: FOP-2792
> URL: https://issues.apache.org/jira/browse/FOP-2792
> Project: FOP
>  Issue Type: Bug
>Reporter: simon steiner
>Assignee: simon steiner
>Priority: Major
> Fix For: 2.3
>
> Attachments: simplefop.xconf, test.fo
>
>
> fop test.fo -c simplefop.xconf out.pdf
> Text should be inside grey box



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Updated] (FOP-2776) NoSuchElementException for list changing ipd

2018-05-16 Thread simon steiner (JIRA)

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

simon steiner updated FOP-2776:
---
Fix Version/s: 2.3

> NoSuchElementException for list changing ipd
> 
>
> Key: FOP-2776
> URL: https://issues.apache.org/jira/browse/FOP-2776
> Project: FOP
>  Issue Type: Bug
>Reporter: simon steiner
>Assignee: simon steiner
>Priority: Major
> Fix For: 2.3
>
> Attachments: test.fo
>
>
> fop test.fo out.pdf
>  
> java.util.NoSuchElementException
>     at org.apache.fop.layoutmgr.LMiter.next(LMiter.java:69)
>     at org.apache.fop.layoutmgr.LMiter.next(LMiter.java:27)
>     at 
> org.apache.fop.layoutmgr.AbstractLayoutManager.setCurrentChildLM(AbstractLayoutManager.java:132)



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Updated] (FOP-2781) Use unique id for links in merged IF

2018-05-16 Thread simon steiner (JIRA)

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

simon steiner updated FOP-2781:
---
Fix Version/s: 2.3

> Use unique id for links in merged IF
> 
>
> Key: FOP-2781
> URL: https://issues.apache.org/jira/browse/FOP-2781
> Project: FOP
>  Issue Type: Bug
>Reporter: simon steiner
>Assignee: simon steiner
>Priority: Major
> Fix For: 2.3
>
> Attachments: test.fo, test2.fo
>
>
> Should be easy to merge IF files, so links work
> fop test.fo -if application/pdf out.if
> fop test2.fo -if application/pdf out2.if
> Merge IF files together
> fop -ifin out.if out.pdf
> Links should point to correct urls



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Updated] (FOP-2782) Bookmarks point to last page when run via IF

2018-05-16 Thread simon steiner (JIRA)

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

simon steiner updated FOP-2782:
---
Fix Version/s: 2.3

> Bookmarks point to last page when run via IF
> 
>
> Key: FOP-2782
> URL: https://issues.apache.org/jira/browse/FOP-2782
> Project: FOP
>  Issue Type: Bug
>Reporter: simon steiner
>Assignee: simon steiner
>Priority: Major
> Fix For: 2.3
>
> Attachments: simple.fo
>
>
> fop simple.fo -if application/pdf out.if
> fop -ifin out.if out.pdf
> Click left bookmark and it should go to 2nd page



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Updated] (FOP-2760) Make unique links for merged IF

2018-05-16 Thread simon steiner (JIRA)

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

simon steiner updated FOP-2760:
---
Fix Version/s: 2.3

> Make unique links for merged IF
> ---
>
> Key: FOP-2760
> URL: https://issues.apache.org/jira/browse/FOP-2760
> Project: FOP
>  Issue Type: Bug
>Reporter: simon steiner
>Assignee: simon steiner
>Priority: Major
> Fix For: 2.3
>
> Attachments: out.if
>
>
> It should be easy to merge IF files without updating table of contents page 
> links
> fop -ifin out.if out.pdf
> Page 3 link should go to page 4



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Updated] (FOP-2773) Images inside a PDF not shown when goca=print-file

2018-05-16 Thread simon steiner (JIRA)

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

simon steiner updated FOP-2773:
---
Fix Version/s: 2.3

> Images inside a PDF not shown when goca=print-file
> --
>
> Key: FOP-2773
> URL: https://issues.apache.org/jira/browse/FOP-2773
> Project: FOP
>  Issue Type: Bug
>Reporter: simon steiner
>Assignee: simon steiner
>Priority: Major
> Fix For: 2.3
>
> Attachments: fop.xconf, input2.pdf, test.fo
>
>
> fop test.fo -c fop.xconf -afp out.afp
> 2nd image not showing



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Updated] (FOP-2768) Reduced space for content after table

2018-05-16 Thread simon steiner (JIRA)

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

simon steiner updated FOP-2768:
---
Fix Version/s: 2.3

> Reduced space for content after table
> -
>
> Key: FOP-2768
> URL: https://issues.apache.org/jira/browse/FOP-2768
> Project: FOP
>  Issue Type: Bug
>Reporter: simon steiner
>Assignee: simon steiner
>Priority: Major
> Fix For: 2.3
>
> Attachments: test.fo
>
>
> fop test.fo out.pdf
> Output is 4 pages, should be 2



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Updated] (FOP-2770) Merge fonts not handling Truetype MacRomanEncoding

2018-05-16 Thread simon steiner (JIRA)

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

simon steiner updated FOP-2770:
---
Fix Version/s: 2.3

> Merge fonts not handling Truetype MacRomanEncoding
> --
>
> Key: FOP-2770
> URL: https://issues.apache.org/jira/browse/FOP-2770
> Project: FOP
>  Issue Type: Bug
>Reporter: simon steiner
>Assignee: simon steiner
>Priority: Major
> Fix For: 2.3
>
> Attachments: simple.pdf, test.fo
>
>
> fop test.fo -c fop.xconf out.pdf
> No black squares should be seen in the output



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Updated] (FOP-2759) NPE converting OTF to Type1

2018-05-16 Thread simon steiner (JIRA)

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

simon steiner updated FOP-2759:
---
Fix Version/s: 2.3

> NPE converting OTF to Type1
> ---
>
> Key: FOP-2759
> URL: https://issues.apache.org/jira/browse/FOP-2759
> Project: FOP
>  Issue Type: Bug
>Reporter: simon steiner
>Assignee: simon steiner
>Priority: Major
> Fix For: 2.3
>
> Attachments: fop.xconf, simple.fo
>
>
> fop simple.fo -c fop.xconf -ps out.ps
> java.lang.NullPointerException
>   at 
> org.apache.fop.fonts.cff.CFFDataReader.readCharStringIndex(CFFDataReader.java:465)



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Updated] (FOP-2753) PDF to PS allow fop fonts as fallback

2018-05-16 Thread simon steiner (JIRA)

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

simon steiner updated FOP-2753:
---
Fix Version/s: 2.3

> PDF to PS allow fop fonts as fallback
> -
>
> Key: FOP-2753
> URL: https://issues.apache.org/jira/browse/FOP-2753
> Project: FOP
>  Issue Type: Bug
>Reporter: simon steiner
>Assignee: simon steiner
>Priority: Major
> Fix For: 2.3
>
> Attachments: fop.xconf, input.pdf, test.fo
>
>
> If a PDF doesnt embed fonts pdfbox will look into the filesystem to find 
> fallback fonts
> Let user use fop.xconf fonts since you may not have correct fonts installed 
> such as on a server
> fop test.fo -ps out.ps -c fop.xconf
> Output should have bold and italic text



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Updated] (FOP-2756) Merged IF has wrong Table of Contents page links

2018-05-16 Thread simon steiner (JIRA)

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

simon steiner updated FOP-2756:
---
Fix Version/s: 2.3

> Merged IF has wrong Table of Contents page links
> 
>
> Key: FOP-2756
> URL: https://issues.apache.org/jira/browse/FOP-2756
> Project: FOP
>  Issue Type: Bug
>Reporter: simon steiner
>Assignee: simon steiner
>Priority: Major
> Fix For: 2.3
>
> Attachments: test.if.xml
>
>
> It should be easy to merge IF files, updating each link in IF output shouldnt 
> be required
> fop -ifin test.if.xml out.pdf
> Tables of contents link should link to last page



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Updated] (FOP-2755) Unmapped XSL-FO Region can cause extra pages

2018-05-16 Thread simon steiner (JIRA)

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

simon steiner updated FOP-2755:
---
Fix Version/s: 2.3

> Unmapped XSL-FO Region can cause extra pages
> 
>
> Key: FOP-2755
> URL: https://issues.apache.org/jira/browse/FOP-2755
> Project: FOP
>  Issue Type: Bug
>Reporter: simon steiner
>Assignee: simon steiner
>Priority: Major
> Fix For: 2.3
>
> Attachments: test.fo
>
>
> fop test.fo out.pdf
> Output is 10 pages, should be 6



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Updated] (FOP-2752) Show name of font file on error

2018-05-16 Thread simon steiner (JIRA)

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

simon steiner updated FOP-2752:
---
Fix Version/s: 2.3

> Show name of font file on error
> ---
>
> Key: FOP-2752
> URL: https://issues.apache.org/jira/browse/FOP-2752
> Project: FOP
>  Issue Type: Bug
>Reporter: simon steiner
>Assignee: simon steiner
>Priority: Major
> Fix For: 2.3
>
> Attachments: arial.afm, arial.pfb, fop.xconf, test.fo
>
>
> fop test.fo -c fop.xconf out.pdf
> java.util.EmptyStackException
>   at java.util.Stack.peek(Stack.java:102)
>   at java.util.Stack.pop(Stack.java:84)
>   at org.apache.fop.fonts.type1.AFMParser.parse(AFMParser.java:208)



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Updated] (FOP-2747) Acrobat Reader error with some Japanese Fonts

2018-05-16 Thread simon steiner (JIRA)

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

simon steiner updated FOP-2747:
---
Fix Version/s: 2.3

> Acrobat Reader error with some Japanese Fonts
> -
>
> Key: FOP-2747
> URL: https://issues.apache.org/jira/browse/FOP-2747
> Project: FOP
>  Issue Type: Bug
>  Components: font/opentype
>Affects Versions: trunk
> Environment: Operating Systems: Windows 
> JDK: 1.8
>Reporter: Kazuyuki Murakami
>Assignee: simon steiner
>Priority: Major
> Fix For: 2.3
>
> Attachments: dnp.fo, dnp.pdf, dnp_full.pdf, fop.xconf, fot.fo, 
> fot.pdf, fot_full.pdf
>
>
> Some Japanese Fonts cannot be embedded into PDF document.
> How to repeat
> 1. Get FOP from trunk@1810008
> 2. Get Font from the attachment
> 3. Use my config file and generate the PDF, there is no error reported.
> 4. Open the PDF file in Acro-Reader, it will report the "cannot extract the 
> embedded font" error.
> cffpar...@dnp.fo
> {noformat}
> java.io.IOException: invalid DICT data b0 byte: 23
> at org.apache.fontbox.cff.CFFParser.readEntry(CFFParser.java:282)
> at org.apache.fontbox.cff.CFFParser.readDictData(CFFParser.java:240)
> at org.apache.fontbox.cff.CFFParser.parseFont(CFFParser.java:405)
> at org.apache.fontbox.cff.CFFParser.parse(CFFParser.java:145)
> {noformat}
> cffpar...@fot.fo
> {noformat}
> java.io.IOException: invalid DICT data b0 byte: 22
> at org.apache.fontbox.cff.CFFParser.readEntry(CFFParser.java:282)
> at org.apache.fontbox.cff.CFFParser.readDictData(CFFParser.java:240)
> at org.apache.fontbox.cff.CFFParser.parseFont(CFFParser.java:405)
> at org.apache.fontbox.cff.CFFParser.parse(CFFParser.java:145)
> {noformat}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Updated] (FOP-2744) Using a second fo:flow to generate blank front pages causes mapping error

2018-05-16 Thread simon steiner (JIRA)

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

simon steiner updated FOP-2744:
---
Fix Version/s: 2.3

> Using a second fo:flow to generate blank front pages causes mapping error
> -
>
> Key: FOP-2744
> URL: https://issues.apache.org/jira/browse/FOP-2744
> Project: FOP
>  Issue Type: Bug
>Reporter: simon steiner
>Assignee: simon steiner
>Priority: Major
> Fix For: 2.3
>
> Attachments: test2.fo
>
>
> fop test2.fo out.pdf
> java.lang.RuntimeException: The flow-name "CoverPageBody" could not be mapped 
> to a region-name in the layout-master-set



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Updated] (FOP-2750) Use streams for OTF subsetting

2018-05-16 Thread simon steiner (JIRA)

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

simon steiner updated FOP-2750:
---
Fix Version/s: 2.3

> Use streams for OTF subsetting
> --
>
> Key: FOP-2750
> URL: https://issues.apache.org/jira/browse/FOP-2750
> Project: FOP
>  Issue Type: Improvement
>Reporter: simon steiner
>Assignee: simon steiner
>Priority: Major
> Fix For: 2.3
>
>
> Avoid allocating large fixed size arrays and do a clean up



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Updated] (FOP-2751) Acrobat Reader error with some Latin Fonts

2018-05-16 Thread simon steiner (JIRA)

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

simon steiner updated FOP-2751:
---
Fix Version/s: 2.3

> Acrobat Reader error with some Latin Fonts
> --
>
> Key: FOP-2751
> URL: https://issues.apache.org/jira/browse/FOP-2751
> Project: FOP
>  Issue Type: Bug
>  Components: font/opentype
>Affects Versions: trunk
> Environment: Operating Systems: Windows 
> JDK: 1.8
>Reporter: Kazuyuki Murakami
>Assignee: simon steiner
>Priority: Major
> Fix For: 2.3
>
> Attachments: FuturaStd-Book.fo, FuturaStd-Book.pdf, 
> FuturaStd-Book_full.pdf, GillSansStd.fo, GillSansStd.pdf, 
> GillSansStd_Acrobat.png, GillSansStd_full.pdf, TimesNewRomanMTStd-Bold.fo, 
> TimesNewRomanMTStd-Bold.pdf, TimesNewRomanMTStd-Bold_Acrobat.png, 
> TimesNewRomanMTStd-Bold_full.pdf, fop.xconf
>
>
> Some Latin Fonts cannot be embedded into PDF document.
> How to repeat
> 1. Get FOP from trunk@1811797
> 2. Get Font from the attachment
> 3. Use my config file and generate the PDF, there is no error reported.
> 4. Open the PDF file in Acro-Reader, it will report the "cannot extract the 
> embedded font" error.
> cffpar...@futurastd-book.fo
> {noformat}
> java.io.IOException: illegal offset value 2949166 in CFF font
> at 
> org.apache.fontbox.cff.CFFParser.readIndexDataOffsets(CFFParser.java:188)
> at org.apache.fontbox.cff.CFFParser.readIndexData(CFFParser.java:197)
> at org.apache.fontbox.cff.CFFParser.parseFont(CFFParser.java:460)
> at org.apache.fontbox.cff.CFFParser.parse(CFFParser.java:145)
> {noformat}
> GillSansStd.fo and TimesNewRomanMTStd-Bold.fo detects no Error in CFFParser.
> I attached the result of checking the CFF structure in Acrobat.
> [^GillSansStd_Acrobat.png]
> [^TimesNewRomanMTStd-Bold_Acrobat.png]



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Updated] (FOP-2740) PDF to PostScript tiling pattern error in Acrobat

2018-05-16 Thread simon steiner (JIRA)

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

simon steiner updated FOP-2740:
---
Fix Version/s: 2.3

> PDF to PostScript tiling pattern error in Acrobat
> -
>
> Key: FOP-2740
> URL: https://issues.apache.org/jira/browse/FOP-2740
> Project: FOP
>  Issue Type: Bug
>Reporter: simon steiner
>Assignee: simon steiner
>Priority: Major
> Fix For: 2.3
>
> Attachments: fop.xconf, grace.pdf, test.fo
>
>
> fop test.fo -ps out.ps -c fop.xconf
> Open out.ps in Adobe Acrobat and you get a limitcheck error



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Updated] (FOP-2742) SVG to PS NPE/text missing when using PFM file

2018-05-16 Thread simon steiner (JIRA)

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

simon steiner updated FOP-2742:
---
Fix Version/s: 2.3

> SVG to PS NPE/text missing when using PFM file
> --
>
> Key: FOP-2742
> URL: https://issues.apache.org/jira/browse/FOP-2742
> Project: FOP
>  Issue Type: Bug
>Reporter: simon steiner
>Assignee: simon steiner
>Priority: Major
> Fix For: 2.3
>
> Attachments: fop2.xconf, simple.fo
>
>
> fop simple.fo -ps out.ps -c fop2.xconf
> Text should be shown
> java.lang.NullPointerException
>   at 
> org.apache.fop.fonts.SingleByteFont.getBoundingBox(SingleByteFont.java:138)



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Updated] (FOP-2737) Acrobat Reader error with Adobe TypeKit Kozuka Mincho font

2018-05-16 Thread simon steiner (JIRA)

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

simon steiner updated FOP-2737:
---
Fix Version/s: 2.3

> Acrobat Reader error with Adobe TypeKit Kozuka Mincho font
> --
>
> Key: FOP-2737
> URL: https://issues.apache.org/jira/browse/FOP-2737
> Project: FOP
>  Issue Type: Bug
>  Components: font/opentype
>Affects Versions: trunk
> Environment: Operating Systems: Windows
> JDK: 1.8
> OpenFont: Adobe Kozuka Mincho (TypeKit)
>Reporter: Kazuyuki Murakami
>Assignee: simon steiner
>Priority: Major
> Fix For: 2.3
>
> Attachments: CFF_structure1.png, CFF_structure2.png, fop.xconf, 
> test.fo, test_acro.pdf, test_full.pdf, test_subset.pdf, ttx.zip
>
>
> The "Adobe Kozuka Mincho" font cannot be embedded into PDF document.
> How to repeat
> 1. Get FOP from trunk@1806787
> 2. Get Font from the attachment
> 3. Use my config file and generate the PDF, there is no error reported.
> 4. Open the PDF file in Acro-Reader, it will report the "cannot extract the 
> embedded font" error.
> In FOP-2697, Get font from Acrobat Reader Resource Folder,
> This font is got from Adobe TypeKit.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Updated] (FOP-2739) Avoid rastering PDF with Smask to image

2018-05-16 Thread simon steiner (JIRA)

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

simon steiner updated FOP-2739:
---
Fix Version/s: 2.3

> Avoid rastering PDF with Smask to image
> ---
>
> Key: FOP-2739
> URL: https://issues.apache.org/jira/browse/FOP-2739
> Project: FOP
>  Issue Type: Bug
>Reporter: simon steiner
>Assignee: simon steiner
>Priority: Major
> Fix For: 2.3
>
> Attachments: smask.pdf, test.fo
>
>
> fop test.fo -ps out.ps
> Text should be smooth when zoomed in



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Updated] (FOP-2736) Acrobat Reader error with Aoyagi Soseki Font

2018-05-16 Thread simon steiner (JIRA)

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

simon steiner updated FOP-2736:
---
Fix Version/s: 2.3

> Acrobat Reader error with Aoyagi Soseki Font
> 
>
> Key: FOP-2736
> URL: https://issues.apache.org/jira/browse/FOP-2736
> Project: FOP
>  Issue Type: Bug
>  Components: font/opentype
>Affects Versions: trunk
> Environment: Operating Systems: Windows 
> JDK: 1.8 
> OpenFont: AoyagiSosekiFont2OTF
>Reporter: Kazuyuki Murakami
>Assignee: simon steiner
>Priority: Major
> Fix For: 2.3
>
> Attachments: AoyagiSosekiFont2.otf, fop.xconf, test.fo, 
> test_acro.pdf, test_full.pdf, test_subset.pdf
>
>
> The "Aoyagi Soseki Font2" font cannot be embedded into PDF document.
> How to repeat
> 1. Get FOP from trunk@1806787
> 2. Get Font from the attachment
> 3. Use my config file and generate the PDF, there is no error reported.
> 4. Open the PDF file in Acro-Reader, it will report the "cannot extract the 
> embedded font" error.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Updated] (FOP-2735) Acrobat Reader error with Hiragino Fonts

2018-05-16 Thread simon steiner (JIRA)

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

simon steiner updated FOP-2735:
---
Fix Version/s: 2.3

> Acrobat Reader error with Hiragino Fonts
> 
>
> Key: FOP-2735
> URL: https://issues.apache.org/jira/browse/FOP-2735
> Project: FOP
>  Issue Type: Bug
>  Components: font/opentype
>Affects Versions: trunk
> Environment: Operating Systems: Windows 
> JDK: 1.8 
> OpenFont: Hiragino Kaku Gothic StdN
>Reporter: Kazuyuki Murakami
>Assignee: simon steiner
>Priority: Major
> Fix For: 2.3
>
> Attachments: fop.xconf, test.fo, test_full.pdf, test_subset.pdf
>
>
> The "Hiragino Kaku Gothic StdN" font cannot be embedded into PDF document.
> How to repeat
> 1. Get FOP from trunk@1806787
> 2. Get Font from the attachment
> 3. Use my config file and generate the PDF, there is no error reported.
> 4. Open the PDF file in Acro-Reader, it will report the "cannot extract the 
> embedded font" error.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Updated] (FOP-2714) Infinite loop when region name not found

2018-05-16 Thread simon steiner (JIRA)

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

simon steiner updated FOP-2714:
---
Fix Version/s: 2.3

> Infinite loop when region name not found
> 
>
> Key: FOP-2714
> URL: https://issues.apache.org/jira/browse/FOP-2714
> Project: FOP
>  Issue Type: Bug
>Reporter: simon steiner
>Assignee: simon steiner
>Priority: Major
> Fix For: 2.3
>
> Attachments: simple2.fo
>
>
> fop simple2.fo out.pdf



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Updated] (FOP-2730) Invalid output for empty block and border-left-style=dashed

2018-05-16 Thread simon steiner (JIRA)

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

simon steiner updated FOP-2730:
---
Fix Version/s: 2.3

> Invalid output for empty block and border-left-style=dashed
> ---
>
> Key: FOP-2730
> URL: https://issues.apache.org/jira/browse/FOP-2730
> Project: FOP
>  Issue Type: Bug
>Reporter: simon steiner
>Assignee: simon steiner
>Priority: Major
> Fix For: 2.3
>
> Attachments: test.fo
>
>
> fop test.fo out.pdf
> Output page is blank



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Updated] (FOP-2713) Text missing on last page with changing ipd

2018-05-16 Thread simon steiner (JIRA)

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

simon steiner updated FOP-2713:
---
Fix Version/s: 2.3

> Text missing on last page with changing ipd
> ---
>
> Key: FOP-2713
> URL: https://issues.apache.org/jira/browse/FOP-2713
> Project: FOP
>  Issue Type: Bug
>Reporter: simon steiner
>Assignee: simon steiner
>Priority: Major
> Fix For: 2.3
>
> Attachments: test.fo
>
>
> fop test.fo out.pdf



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Updated] (FOP-2718) sRGB.icc is missing from ant jar

2018-05-16 Thread simon steiner (JIRA)

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

simon steiner updated FOP-2718:
---
Fix Version/s: 2.3

> sRGB.icc is missing from ant jar
> 
>
> Key: FOP-2718
> URL: https://issues.apache.org/jira/browse/FOP-2718
> Project: FOP
>  Issue Type: Bug
>Affects Versions: 2.2
>Reporter: Stefan Wismer
>Assignee: simon steiner
>Priority: Major
> Fix For: 2.3
>
>
> The fop-2.2.jar deployed on Maven Central does not contain the sRGB.icc 
> (org/apache/fop/pdf/sRGB.icc) and its related files. When checking out the 
> SVN tag 2.2 and building it locally, the file is included.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Updated] (FOP-2712) NoSuchElementException on changing IPD

2018-05-16 Thread simon steiner (JIRA)

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

simon steiner updated FOP-2712:
---
Fix Version/s: 2.3

> NoSuchElementException on changing IPD 
> ---
>
> Key: FOP-2712
> URL: https://issues.apache.org/jira/browse/FOP-2712
> Project: FOP
>  Issue Type: Bug
>Reporter: simon steiner
>Assignee: simon steiner
>Priority: Major
> Fix For: 2.3
>
> Attachments: test.fo
>
>
> fop test.fo out.pdf
> java.util.NoSuchElementException
>   at java.util.LinkedList$ListItr.previous(LinkedList.java:905)
>   at 
> org.apache.fop.layoutmgr.AbstractBreaker.getNextBlockList(AbstractBreaker.java:783)



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Updated] (FOP-2710) SVG Gradient missing

2018-05-16 Thread simon steiner (JIRA)

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

simon steiner updated FOP-2710:
---
Fix Version/s: 2.3

> SVG Gradient missing
> 
>
> Key: FOP-2710
> URL: https://issues.apache.org/jira/browse/FOP-2710
> Project: FOP
>  Issue Type: Bug
>Reporter: simon steiner
>Assignee: simon steiner
>Priority: Major
> Fix For: 2.3
>
> Attachments: test.fo
>
>
> fop test.fo out.pdf
> Part of logo missing



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Updated] (FOP-2707) Writing mode lost after spanned block

2018-05-16 Thread simon steiner (JIRA)

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

simon steiner updated FOP-2707:
---
Fix Version/s: 2.3

> Writing mode lost after spanned block
> -
>
> Key: FOP-2707
> URL: https://issues.apache.org/jira/browse/FOP-2707
> Project: FOP
>  Issue Type: Bug
>  Components: layout/page
>Reporter: Matthias Reischenbacher
>Priority: Major
> Fix For: 2.3
>
> Attachments: 2707_test_case.xml
>
>
> If writing-mode "rl-tb" is used in a multi column page, the writing-mode is 
> not applied to the multi column layout, if the page starts with a spanned 
> block.
> The expected page layout in right to left writing mode is:
> Spanned Block
> Col3Col2Col1
> But currently the following layout is generated:
> Spanned Block
> Col1Col2Col3



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Updated] (FOP-2708) FOP 2.2 binary release's bundled script to run FOP not set as executable

2018-05-16 Thread simon steiner (JIRA)

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

simon steiner updated FOP-2708:
---
Fix Version/s: 2.3

> FOP 2.2 binary release's bundled script to run FOP not set as executable
> 
>
> Key: FOP-2708
> URL: https://issues.apache.org/jira/browse/FOP-2708
> Project: FOP
>  Issue Type: Bug
>  Components: unqualified
>Affects Versions: 2.2
> Environment: macOS, likely any Unix-like operating system
>Reporter: JCount
>Assignee: simon steiner
>Priority: Minor
> Fix For: 2.3
>
>
> The binary distribution of FOP 2.2 contains the shell script *fop* for 
> running FOP, within the *fop/* subdirectory. In previous versions the mode of 
> this script was *755*, however, in the 2.2 release the mode is set as *644*. 
> This means that individual users, as well as package managers such as 
> Homebrew, need to change the mode of the script as an additional step during 
> setup.
> I suspect that this was not intentional, but rather a side effect of changing 
> the build process for the binary distribution. If this is the case, it likely 
> can only be resolved in the next release.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Updated] (FOP-2602) block content of list-item overlaps next list-item content

2018-05-16 Thread simon steiner (JIRA)

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

simon steiner updated FOP-2602:
---
Fix Version/s: (was: 2.1)
   (was: trunk)

> block content of list-item overlaps next list-item content
> --
>
> Key: FOP-2602
> URL: https://issues.apache.org/jira/browse/FOP-2602
> Project: FOP
>  Issue Type: Bug
>  Components: fo/block, fo/inline
>Affects Versions: 1.1, 2.1
> Environment: server: Linux centOS
>Reporter: Nico Krupp
>Priority: Major
> Attachments: bleeding-list-item.png, fo.xml
>
>
> The block content of a list-item-body inside a list-item, is overlapping the 
> content of the next list-item, when getting wrapped.
> I am glad to provide additional information if needed, but for me it seems 
> that simple.
> E.g.: fo.xml and bleeding-list-item.png



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Updated] (FOP-2702) OTF fonts not working on Mac Preview

2018-05-16 Thread simon steiner (JIRA)

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

simon steiner updated FOP-2702:
---
Fix Version/s: (was: trunk)
   2.3

> OTF fonts not working on Mac Preview
> 
>
> Key: FOP-2702
> URL: https://issues.apache.org/jira/browse/FOP-2702
> Project: FOP
>  Issue Type: Bug
>Reporter: simon steiner
>Assignee: simon steiner
>Priority: Major
> Fix For: 2.3
>
> Attachments: fop.xconf, test.fo
>
>
> Print from Mac OS Preview application and export as PDF has text missing
> fop test.fo -c fop.xconf out.pdf



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Updated] (FOP-2699) Acrobat Reader error with Morisawa Fonts

2018-05-16 Thread simon steiner (JIRA)

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

simon steiner updated FOP-2699:
---
Fix Version/s: 2.3

> Acrobat Reader error with Morisawa Fonts
> 
>
> Key: FOP-2699
> URL: https://issues.apache.org/jira/browse/FOP-2699
> Project: FOP
>  Issue Type: Bug
>  Components: font/opentype
>Affects Versions: trunk
> Environment: Operating Systems: Windows
> JDK: 1.8
> OpenFont: Morisawa ShinGo Pro R
>Reporter: Kazuyuki Murakami
>Assignee: simon steiner
>Priority: Major
> Fix For: 2.3
>
> Attachments: fop.xconf, fop2.xconf, test.fo, test2.fo, test2.pdf, 
> test2_full.pdf, test_full.pdf, test_subset.pdf, workaround.patch
>
>
> The Morisawa ShinGo Pro R font cannot be embedded into PDF document.
> How to repeat
> 1. Get FOP from trunk@1786161
> 2. Get Font from 
> https://github.com/skyavy-cebu/DoubleClick/blob/master/web/fonts/A-OTF-ShinGoPro-Regular.otf?raw=true
> 3. Use my config file and generate the PDF, there is no error reported.
> 4. Open the PDF file in Acro-Reader, it will report the "cannot extract the 
> embedded font" error.
> Notes:
> I can display normally with full embedding.
> (Please refer to test.fo, test_subset.pdf, test_full.pdf)
> When examining the subset font with CFFParser, the following Exception 
> occurred.
> java.io.EOFException
> at org.apache.fontbox.cff.DataInput.readUnsignedShort(DataInput.java:151)
> at org.apache.fontbox.cff.CFFDataInput.readCard16(CFFDataInput.java:55)
> at org.apache.fontbox.cff.CFFParser.readIndexDataOffsets(CFFParser.java:172)
> at org.apache.fontbox.cff.CFFParser.readIndexData(CFFParser.java:193)
> at org.apache.fontbox.cff.CFFParser.parseCIDFontDicts(CFFParser.java:590)
> at org.apache.fontbox.cff.CFFParser.parseFont(CFFParser.java:503)
> at org.apache.fontbox.cff.CFFParser.parse(CFFParser.java:141)



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Resolved] (FOP-2628) [PATCH] Bugfix in URISpecification.java: 'a', not 'A'

2018-05-16 Thread simon steiner (JIRA)

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

simon steiner resolved FOP-2628.

   Resolution: Fixed
Fix Version/s: (was: trunk)
   2.3

> [PATCH] Bugfix in URISpecification.java: 'a', not 'A'
> -
>
> Key: FOP-2628
> URL: https://issues.apache.org/jira/browse/FOP-2628
> Project: FOP
>  Issue Type: Bug
>  Components: unqualified
>Affects Versions: 2.1
>Reporter: Agneta Walterscheidt
>Assignee: Chris Bowditch
>Priority: Trivial
>  Labels: patch
> Fix For: 2.3
>
> Attachments: fixbug.patch
>
>
> [PATCH]
> I fixed a bug in URISpecification.java (an 'A' was used where an 'a' was 
> meant).



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Reopened] (FOP-2628) [PATCH] Bugfix in URISpecification.java: 'a', not 'A'

2018-05-16 Thread simon steiner (JIRA)

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

simon steiner reopened FOP-2628:


> [PATCH] Bugfix in URISpecification.java: 'a', not 'A'
> -
>
> Key: FOP-2628
> URL: https://issues.apache.org/jira/browse/FOP-2628
> Project: FOP
>  Issue Type: Bug
>  Components: unqualified
>Affects Versions: 2.1
>Reporter: Agneta Walterscheidt
>Assignee: Chris Bowditch
>Priority: Trivial
>  Labels: patch
> Fix For: trunk
>
> Attachments: fixbug.patch
>
>
> [PATCH]
> I fixed a bug in URISpecification.java (an 'A' was used where an 'a' was 
> meant).



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Updated] (FOP-2572) [PATCH] Non-breaking space within a Text node causes an Exception.

2018-05-16 Thread simon steiner (JIRA)

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

simon steiner updated FOP-2572:
---
Fix Version/s: 2.3

> [PATCH] Non-breaking space within a Text node causes an Exception.
> --
>
> Key: FOP-2572
> URL: https://issues.apache.org/jira/browse/FOP-2572
> Project: FOP
>  Issue Type: Bug
>  Components: fo/inline
>Affects Versions: 2.0
> Environment: All
>Reporter: Karl Snyder
>Assignee: Matthias Reischenbacher
>Priority: Major
> Fix For: 2.3
>
> Attachments: fop-2572.patch
>
>
> A non-breaking space (Option+Space on the Mac) in content will cause the 
> following exception.
> {code}java.lang.ArrayIndexOutOfBoundsException: 14
>   at 
> org.apache.fop.fonts.GlyphMapping.addToLetterAdjust(GlyphMapping.java:286) 
> ~[fop-2.0.jar:na]
>   at 
> org.apache.fop.fonts.GlyphMapping.processWordNoMapping(GlyphMapping.java:248) 
> ~[fop-2.0.jar:na]
>   at 
> org.apache.fop.fonts.GlyphMapping.doGlyphMapping(GlyphMapping.java:93) 
> ~[fop-2.0.jar:na]
>   at 
> org.apache.fop.svg.font.FOPGVTGlyphVector.performDefaultLayout(FOPGVTGlyphVector.java:94)
>  ~[fop-2.0.jar:na]
>   at org.apache.batik.bridge.GlyphLayout.doExplicitGlyphLayout(Unknown 
> Source) ~[batik-bridge-1.8.jar:1.8]
>   at org.apache.batik.bridge.GlyphLayout.adjustTextSpacing(Unknown 
> Source) ~[batik-bridge-1.8.jar:1.8]
>   at org.apache.batik.bridge.GlyphLayout.getAdvance2D(Unknown Source) 
> ~[batik-bridge-1.8.jar:1.8]
>   at org.apache.batik.bridge.StrokingTextPainter.getTextChunk(Unknown 
> Source) ~[batik-bridge-1.8.jar:1.8]
>   at org.apache.batik.bridge.StrokingTextPainter.computeTextRuns(Unknown 
> Source) ~[batik-bridge-1.8.jar:1.8]
>   at 
> org.apache.fop.svg.NativeTextPainter.computeTextRuns(NativeTextPainter.java:223)
>  ~[fop-2.0.jar:na]
>   at org.apache.batik.bridge.StrokingTextPainter.getTextRuns(Unknown 
> Source) ~[batik-bridge-1.8.jar:1.8]
>   at org.apache.batik.bridge.StrokingTextPainter.getBounds2D(Unknown 
> Source) ~[batik-bridge-1.8.jar:1.8]
>   at org.apache.batik.bridge.TextNode.getPrimitiveBounds(Unknown Source) 
> ~[batik-bridge-1.8.jar:1.8]
>   at 
> org.apache.batik.gvt.AbstractGraphicsNode.getTransformedPrimitiveBounds(Unknown
>  Source) ~[batik-gvt-1.8.jar:1.8]
>   at 
> org.apache.batik.gvt.AbstractGraphicsNode.getTransformedBounds(Unknown 
> Source) ~[batik-gvt-1.8.jar:1.8]
>   at 
> org.apache.batik.gvt.CompositeGraphicsNode.getPrimitiveBounds(Unknown Source) 
> ~[batik-gvt-1.8.jar:1.8]
>   at 
> org.apache.batik.gvt.CompositeGraphicsNode.getTransformedPrimitiveBounds(Unknown
>  Source) ~[batik-gvt-1.8.jar:1.8]
>   at 
> org.apache.batik.gvt.AbstractGraphicsNode.getTransformedBounds(Unknown 
> Source) ~[batik-gvt-1.8.jar:1.8]
>   at 
> org.apache.batik.gvt.CompositeGraphicsNode.getPrimitiveBounds(Unknown Source) 
> ~[batik-gvt-1.8.jar:1.8]
>   at 
> org.apache.batik.gvt.CompositeGraphicsNode.getTransformedPrimitiveBounds(Unknown
>  Source) ~[batik-gvt-1.8.jar:1.8]
>   at 
> org.apache.batik.gvt.AbstractGraphicsNode.getTransformedBounds(Unknown 
> Source) ~[batik-gvt-1.8.jar:1.8]
>   at 
> org.apache.batik.gvt.CompositeGraphicsNode.getPrimitiveBounds(Unknown Source) 
> ~[batik-gvt-1.8.jar:1.8]
>   at 
> org.apache.batik.gvt.CompositeGraphicsNode.getTransformedPrimitiveBounds(Unknown
>  Source) ~[batik-gvt-1.8.jar:1.8]
>   at 
> org.apache.batik.gvt.AbstractGraphicsNode.getTransformedBounds(Unknown 
> Source) ~[batik-gvt-1.8.jar:1.8]
>   at 
> org.apache.batik.gvt.CompositeGraphicsNode.getPrimitiveBounds(Unknown Source) 
> ~[batik-gvt-1.8.jar:1.8]
>   at org.apache.batik.gvt.AbstractGraphicsNode.getBounds(Unknown Source) 
> ~[batik-gvt-1.8.jar:1.8]
>   at org.apache.batik.gvt.AbstractGraphicsNode.paint(Unknown Source) 
> ~[batik-gvt-1.8.jar:1.8]
>   at org.apache.fop.svg.PDFTranscoder.transcode(PDFTranscoder.java:185) 
> ~[fop-2.0.jar:na]
>   at org.apache.batik.transcoder.XMLAbstractTranscoder.transcode(Unknown 
> Source) ~[batik-transcoder-1.8.jar:1.8]
>   at org.apache.batik.transcoder.SVGAbstractTranscoder.transcode(Unknown 
> Source) ~[batik-transcoder-1.8.jar:1.8]
> ...{code}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Updated] (FOP-2570) [PATCH] Misplaced border of spanned table cells in RTL WM context

2018-05-16 Thread simon steiner (JIRA)

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

simon steiner updated FOP-2570:
---
Fix Version/s: 2.3

> [PATCH] Misplaced border of spanned table cells in RTL WM context
> -
>
> Key: FOP-2570
> URL: https://issues.apache.org/jira/browse/FOP-2570
> Project: FOP
>  Issue Type: Bug
>  Components: layout/unqualified
>Reporter: Matthias Reischenbacher
>Assignee: Matthias Reischenbacher
>Priority: Major
> Fix For: 2.3
>
> Attachments: fop-2570.patch, rl-table-border-issue-fixed.pdf, 
> rl-table-border-issue.pdf, rl-table-border-issue.xml
>
>
> FOP-2047 fixed table borders of spanned table cells. Since FOP-2310 some 
> borders are misplaced again.
> I'm adding a patch for a first review. I'll add additional checks in the 
> layout test case of FOP-2047 a bit later.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Updated] (FOP-2251) [PATCH] PDF to Postscript not showing transparency

2018-05-16 Thread simon steiner (JIRA)

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

simon steiner updated FOP-2251:
---
Fix Version/s: (was: trunk)
   2.3

> [PATCH] PDF to Postscript not showing transparency
> --
>
> Key: FOP-2251
> URL: https://issues.apache.org/jira/browse/FOP-2251
> Project: FOP
>  Issue Type: Bug
>Reporter: simon steiner
>Assignee: simon steiner
>Priority: Major
> Fix For: 2.3
>
> Attachments: blend.pdf, libreoffice.pdf, pdftopstrans.patch, 
> pdftopstrans2.patch, test.fo
>
>
> PDF to PS elements missing
> fop test.fo -ps out.ps



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Updated] (FOP-2527) RTF first line indent not being rendered by fo:block text-indent

2018-05-16 Thread simon steiner (JIRA)

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

simon steiner updated FOP-2527:
---
Fix Version/s: 2.3

> RTF first line indent not being rendered by fo:block text-indent
> 
>
> Key: FOP-2527
> URL: https://issues.apache.org/jira/browse/FOP-2527
> Project: FOP
>  Issue Type: Bug
>  Components: renderer/rtf
>Affects Versions: 2.0
> Environment: Linux JDK8 fop 2.0 stable
>Reporter: Stanley Santos de Araújo
>Assignee: simon steiner
>Priority: Major
>  Labels: fo:block, html, rtf, text-indent, xhtml, xslt
> Fix For: 2.3
>
> Attachments: RtfText.java, TestFOP.java, 
> TextAttributesConverter.java, test.fo, test.html, xhtml2fo.xsl
>
>
> I am using FOP to convert from XHTML to RTF using Antennahouse Stylesheet for 
> XHTML to XSL-FO transformation. 
> My scenario is desbribed below:
> I am using stylesheet xhtml2fo.xslt and it works fine when parsing XHTML to 
> PDF, but when I change Fop MIME_TYPE to RTF and execute the same code,  RTF 
> output file does not contain first line indentation according XHTML style. 
> 1) XHTML input:
> BLAH BLAH BLAH
> Stylesheet xhtml2fo.xslt:
> http://www.antennahouse.com/XSLsample/sample-xsl-xhtml2fo/xhtml2fo.xsl
> 2) FO Output:
> BLAH BLAH BLAH
> 3) Expected RTF output:
> { fiXXX BLAH BLAH BLAH }
> 4) I have verified FOP source code and noticed that current version have a 
> bug on RtfText:
> 
> /** constant for left indent first */
> public static final String LEFT_INDENT_FIRST = "fi-";
> 
> 5) Also TextAttributesConverter is not considering text-indent attribute:
> public static RtfAttributes convertAttributes(Block fobj)
> throws FOPException {
> FOPRtfAttributes attrib = new FOPRtfAttributes();
> attrFont(fobj.getCommonFont(), attrib);
> attrFontColor(fobj.getColor(), attrib);
> //attrTextDecoration(fobj.getTextDecoration(), attrib);
> attrBlockBackgroundColor(fobj.getCommonBorderPaddingBackground(), attrib);
> attrBlockMargin(fobj.getCommonMarginBlock(), attrib);
> attrBlockTextAlign(fobj.getTextAlign(), attrib);
> attrBorder(fobj.getCommonBorderPaddingBackground(), attrib, fobj);
> attrBreak(fobj, attrib);
> return attrib;
> }
> 6) I implemented the following patch and it is working fine for me. Check 
> this out:
> - Fixed LEFT_INDENT_FIRST to public static final String LEFT_INDENT_FIRST = 
> "fi";
> - New method to convert text-indent attribute:
> public static RtfAttributes convertAttributes(Block fobj)
> throws FOPException {
> ...
> attrBlockTextIndent(fobj.getTextIndent(), attrib);
> ...
> return attrib;
> }
> private static void attrBlockTextIndent(Length textIndent, 
> FOPRtfAttributes rtfAttr) {
> rtfAttr.setTwips(RtfText.LEFT_INDENT_FIRST, textIndent.getValue());
> }
> Thank you!



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Updated] (FOP-1969) Support for unicode Surrogate pairs

2018-05-16 Thread simon steiner (JIRA)

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

simon steiner updated FOP-1969:
---
Fix Version/s: 2.3

> Support for unicode Surrogate pairs
> ---
>
> Key: FOP-1969
> URL: https://issues.apache.org/jira/browse/FOP-1969
> Project: FOP
>  Issue Type: Improvement
>  Components: unqualified
>Affects Versions: trunk
> Environment: Operating System: All
> Platform: All
>Reporter: Glenn Adams
>Assignee: simon steiner
> Fix For: 2.3
>
> Attachments: AndroidEmoji.ttf, Urdu.zip, fop.xconf, pcltest.zip, 
> single-byte.zip, test.fo, testing.fo, testing.fo, testing.pdf, testing.pdf, 
> testing.xml, testing.xsl, tiffttc.zip
>
>
> unicode codepoints outside of the BMP (base multilingual plane), i.e., whose 
> scalar value is greater than 0x (65535), are coded as UTF-16 surrogate 
> pairs in Java strings, which pair should be treated as a single codepoint for 
> the purpose of mapping to a glyph in a font (that supports extra-BMP 
> mappings);
> at present, FOP does not correctly handle this case in simple (non complex 
> script) rendering paths;
> furthermore, though some support has been added to handle this in the complex 
> script rendering path, it has not yet been tested, so is not necessarily 
> working there either;
>  
> fop test.fo -c fop.xconf out.pdf
> Glyphs should be rendered



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Resolved] (FOP-616) [PATCH] "visibility" property is not implemented

2018-05-16 Thread simon steiner (JIRA)

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

simon steiner resolved FOP-616.
---
Resolution: Fixed

> [PATCH] "visibility" property is not implemented
> 
>
> Key: FOP-616
> URL: https://issues.apache.org/jira/browse/FOP-616
> Project: FOP
>  Issue Type: Bug
>  Components: unqualified
>Affects Versions: trunk
> Environment: Operating System: other
> Platform: Other
>Reporter: Martin Aubele
>Assignee: Chris Bowditch
> Fix For: 2.3
>
> Attachments: FOP616.patch, visibility.patch
>
>
> The property visibility is not implemented.
> I would need especially the visibility="hidden" behavior for block elements.
> Proposal for the fix for Block:
> 1. Change the definition of the visiblity property in foproperties.xml
> to:
>   
> visibility
> false
>
> Enum
> 
>   visible
>   hidden
>   collapse
>   inherit
> 
>   
> 2. Put the following line at the beginning of Block#layout:
> Property visibility = this.properties.get("visibility");
> if (visibility != null && visibility.getEnum() == Visibility.HIDDEN)
>   return new Status(OK);



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Updated] (FOP-616) [PATCH] "visibility" property is not implemented

2018-05-16 Thread simon steiner (JIRA)

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

simon steiner updated FOP-616:
--
Fix Version/s: (was: 2.2)
   2.3

> [PATCH] "visibility" property is not implemented
> 
>
> Key: FOP-616
> URL: https://issues.apache.org/jira/browse/FOP-616
> Project: FOP
>  Issue Type: Bug
>  Components: unqualified
>Affects Versions: trunk
> Environment: Operating System: other
> Platform: Other
>Reporter: Martin Aubele
>Assignee: Chris Bowditch
> Fix For: 2.3
>
> Attachments: FOP616.patch, visibility.patch
>
>
> The property visibility is not implemented.
> I would need especially the visibility="hidden" behavior for block elements.
> Proposal for the fix for Block:
> 1. Change the definition of the visiblity property in foproperties.xml
> to:
>   
> visibility
> false
>
> Enum
> 
>   visible
>   hidden
>   collapse
>   inherit
> 
>   
> 2. Put the following line at the beginning of Block#layout:
> Property visibility = this.properties.get("visibility");
> if (visibility != null && visibility.getEnum() == Visibility.HIDDEN)
>   return new Status(OK);



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Reopened] (FOP-616) [PATCH] "visibility" property is not implemented

2018-05-16 Thread simon steiner (JIRA)

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

simon steiner reopened FOP-616:
---

> [PATCH] "visibility" property is not implemented
> 
>
> Key: FOP-616
> URL: https://issues.apache.org/jira/browse/FOP-616
> Project: FOP
>  Issue Type: Bug
>  Components: unqualified
>Affects Versions: trunk
> Environment: Operating System: other
> Platform: Other
>Reporter: Martin Aubele
>Assignee: Chris Bowditch
> Fix For: 2.3
>
> Attachments: FOP616.patch, visibility.patch
>
>
> The property visibility is not implemented.
> I would need especially the visibility="hidden" behavior for block elements.
> Proposal for the fix for Block:
> 1. Change the definition of the visiblity property in foproperties.xml
> to:
>   
> visibility
> false
>
> Enum
> 
>   visible
>   hidden
>   collapse
>   inherit
> 
>   
> 2. Put the following line at the beginning of Block#layout:
> Property visibility = this.properties.get("visibility");
> if (visibility != null && visibility.getEnum() == Visibility.HIDDEN)
>   return new Status(OK);



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Closed] (FOP-2790) NullPointerException when using pdf-ua-mode in fop.xconf

2018-05-16 Thread Stefan Eike (JIRA)

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

Stefan Eike closed FOP-2790.

Resolution: Cannot Reproduce

I cannot reproduce it anymore. Strange, maybe it was a side-effect. I'm closing 
this issue and would reopen it, if I should be able to reproduce this again.

> NullPointerException when using pdf-ua-mode in fop.xconf
> 
>
> Key: FOP-2790
> URL: https://issues.apache.org/jira/browse/FOP-2790
> Project: FOP
>  Issue Type: Bug
>Reporter: Stefan Eike
>Priority: Major
>
> I'm setting up accessible publication using the Darwin Information Typing 
> Architecture Open Toolkit (DITA-OT) 2.5.4, which ships Apache FOP 2.1.
> When setting {{PDF/UA-1}} in the *fop.xconf*, the 
> build fails with this error:
> {code:java}
> transform.fo2pdf.fop:
>    [fop] [INFO] Default page-height set to: 297mm
>    [fop] [INFO] Default page-width set to: 210mm
>    [fop] [ERROR] Error while rendering page ii. Reason: 
> java.lang.NullPointerException
>    [fop] java.lang.NullPointerException
>    [fop]     at 
> org.apache.fop.render.pdf.PDFPainter.addStructTreeBBox(PDFPainter.java:197)
>    [fop]     at 
> org.apache.fop.render.pdf.PDFPainter.drawImage(PDFPainter.java:179)
>    [fop]     at 
> org.apache.fop.render.intermediate.IFRenderer.drawImage(IFRenderer.java:1296)
>    [fop]     at 
> org.apache.fop.render.intermediate.IFRenderer.renderImage(IFRenderer.java:1283)
>    [fop]     at 
> org.apache.fop.render.AbstractRenderer.renderInlineViewport(AbstractRenderer.java:858)
>    [fop]     at 
> org.apache.fop.render.AbstractPathOrientedRenderer.renderInlineViewport(AbstractPathOrientedRenderer.java:832)
>    [fop]     at 
> org.apache.fop.render.intermediate.IFRenderer.renderInlineViewport(IFRenderer.java:864)
>    [fop]     at 
> org.apache.fop.render.AbstractRenderer.renderInlineArea(AbstractRenderer.java:715)
>    [fop]     at 
> org.apache.fop.render.intermediate.IFRenderer.renderInlineArea(IFRenderer.java:928)
>    [fop]     at 
> org.apache.fop.render.AbstractRenderer.renderLineArea(AbstractRenderer.java:690)
>    [fop]     at 
> org.apache.fop.render.AbstractRenderer.renderBlocks(AbstractRenderer.java:572)
>    [fop]     at 
> org.apache.fop.render.AbstractRenderer.renderBlock(AbstractRenderer.java:613)
>    [fop]     at 
> org.apache.fop.render.intermediate.IFRenderer.renderBlock(IFRenderer.java:1000)
>    [fop]     at 
> org.apache.fop.render.AbstractRenderer.renderBlocks(AbstractRenderer.java:557)
>    [fop]     at 
> org.apache.fop.render.AbstractPathOrientedRenderer.renderReferenceArea(AbstractPathOrientedRenderer.java:757)
>    [fop]     at 
> org.apache.fop.render.AbstractRenderer.renderBlock(AbstractRenderer.java:600)
>    [fop]     at 
> org.apache.fop.render.intermediate.IFRenderer.renderBlock(IFRenderer.java:1000)
>    [fop]     at 
> org.apache.fop.render.AbstractRenderer.renderBlocks(AbstractRenderer.java:557)
>    [fop]     at 
> org.apache.fop.render.AbstractRenderer.renderBlock(AbstractRenderer.java:613)
>    [fop]     at 
> org.apache.fop.render.intermediate.IFRenderer.renderBlock(IFRenderer.java:1000)
>    [fop]     at 
> org.apache.fop.render.AbstractRenderer.renderBlocks(AbstractRenderer.java:557)
>    [fop]     at 
> org.apache.fop.render.AbstractRenderer.renderBlock(AbstractRenderer.java:613)
>    [fop]     at 
> org.apache.fop.render.intermediate.IFRenderer.renderBlock(IFRenderer.java:1000)
>    [fop]     at 
> org.apache.fop.render.AbstractRenderer.renderBlocks(AbstractRenderer.java:557)
>    [fop]     at 
> org.apache.fop.render.AbstractPathOrientedRenderer.renderReferenceArea(AbstractPathOrientedRenderer.java:757)
>    [fop]     at 
> org.apache.fop.render.AbstractRenderer.renderBlock(AbstractRenderer.java:600)
>    [fop]     at 
> org.apache.fop.render.intermediate.IFRenderer.renderBlock(IFRenderer.java:1000)
>    [fop]     at 
> org.apache.fop.render.AbstractRenderer.renderBlocks(AbstractRenderer.java:557)
>    [fop]     at 
> org.apache.fop.render.intermediate.IFRenderer.renderBlockViewport(IFRenderer.java:844)
>    [fop]     at 
> org.apache.fop.render.AbstractRenderer.renderBlock(AbstractRenderer.java:593)
>    [fop]     at 
> org.apache.fop.render.intermediate.IFRenderer.renderBlock(IFRenderer.java:1000)
>    [fop]     at 
> org.apache.fop.render.AbstractRenderer.renderBlocks(AbstractRenderer.java:557)
>    [fop]     at 
> org.apache.fop.render.AbstractRenderer.renderBlock(AbstractRenderer.java:613)
>    [fop]     at 
> org.apache.fop.render.intermediate.IFRenderer.renderBlock(IFRenderer.java:1000)
>    [fop]     at 
>