[jira] [Created] (FOP-2375) Problem while generating ps output in arabic

2014-05-26 Thread Swapnil Khante (JIRA)
Swapnil Khante created FOP-2375:
---

 Summary: Problem while generating ps output in arabic 
 Key: FOP-2375
 URL: https://issues.apache.org/jira/browse/FOP-2375
 Project: Fop
  Issue Type: Bug
  Components: ps
Affects Versions: 1.1
 Environment: Windows 7, 2 GBram
Reporter: Swapnil Khante
 Fix For: 1.1


We are generation a ps and pdf output using Apache FOP 1.1. We are using .ttf 
fonts for the same. PDF output seems to be fine but we are getting some garbage 
text while generation ps output. As per Apache documentation, ps output format 
only supports type 1 fonts so we have tried using .pfb fonts but problem is not 
resolved. When output is generated text on first page of output is fine but 
from page 2 onward we are getting garbage text. Observation was that if some 
text is outputted on first page and again on next pages it displays fine but if 
some text is first time used on second page or onwards we are facing this 
issue. Below is the entry that we are using in our .xconf file
renderer mime=application/postscript
  !-- This option forces the PS renderer to rotate landscape pages --
  !--auto-rotate-landscapetrue/auto-rotate-landscape--
  
  !-- This option lets you specify additional options on an XML handler --
  !--xml-handler namespace=http://www.w3.org/2000/svg;
stroke-textfalse/stroke-text
  /xml-handler--
  filterList
valuenull/value
/filterList
filterList type=image
valueflate/value
valueascii-85/value
/filterList
  fontstripleFilepfb;/fonts
  disable-srgb-colorspacetrue/disable-srgb-colorspace
/renderer

where tripleFilepfb points refers to .xml file containing .ttf fonts



--
This message was sent by Atlassian JIRA
(v6.2#6252)


[jira] [Commented] (FOP-2369) Call javax.imageio.ImageReader.canReadRaster() before attempt to read raster

2014-05-26 Thread Radu Coravu (JIRA)

[ 
https://issues.apache.org/jira/browse/FOP-2369?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14008699#comment-14008699
 ] 

Radu Coravu commented on FOP-2369:
--

Hi Luis,

In that case the 
org.apache.xmlgraphics.image.loader.impl.imageio.ImageLoaderImageIO.getFallbackBufferedImage(ImageReader,
 int, ImageReadParam) should return null.

The code already has fallbacks for this:

{code} if (firstException != null) {
throw new ImageException(Error while loading image: 
+ firstException.getMessage(), firstException);
}
if (imageData == null) {
throw new ImageException(No ImageIO ImageReader found .);
}{code}

I'm sorry, I cannot provide a patch, I do not have a checkout of the latest FOP 
Java sources but the fix should be pretty simple and straight forward.

 Call javax.imageio.ImageReader.canReadRaster() before attempt to read raster
 --

 Key: FOP-2369
 URL: https://issues.apache.org/jira/browse/FOP-2369
 Project: Fop
  Issue Type: Bug
  Components: images
Affects Versions: 1.1
Reporter: Radu Coravu
   Original Estimate: 3h
  Remaining Estimate: 3h

 The method:
 org.apache.xmlgraphics.image.loader.impl.imageio.ImageLoaderImageIO.getFallbackBufferedImage(ImageReader,
  int, ImageReadParam)
 calls:
 reader.readRaster(pageIndex, param);
 but it should first call javax.imageio.ImageReader.canReadRaster() to see 
 if the reader can render the raster.
 Otherwise if the image reader cannot render rasters such exceptions may occur:
 {code}  [fop] Caused by: java.lang.UnsupportedOperationException
   [fop]   at 
 com.oxygenxml.media.imageioimpl.plugins.tiff.TIFFImageReader.readRaster(Unknown
  Source)
   [fop]   at 
 org.apache.xmlgraphics.image.loader.impl.imageio.ImageLoaderImageIO.getFallbackBufferedImage(ImageLoaderImageIO.java:356)
   [fop]   at 
 org.apache.xmlgraphics.image.loader.impl.imageio.ImageLoaderImageIO.loadImage(ImageLoaderImageIO.java:157)
   [fop]   at 
 org.apache.xmlgraphics.image.loader.pipeline.ImageProviderPipeline.execute(ImageProviderPipeline.java:154)
   [fop]   at 
 org.apache.xmlgraphics.image.loader.pipeline.ImageProviderPipeline.execute(ImageProviderPipeline.java:99){code}



--
This message was sent by Atlassian JIRA
(v6.2#6252)


[jira] [Updated] (FOP-2375) Problem while generating ps output in arabic

2014-05-26 Thread Swapnil Khante (JIRA)

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

Swapnil Khante updated FOP-2375:


Description: 
We are generating a ps and pdf arabic output using Apache FOP 1.1. We are using 
.ttf fonts for the same. PDF output seems to be fine but we are getting some 
garbage text while generation ps output. As per Apache documentation, ps output 
format only supports type 1 fonts so we have tried using .pfb fonts but problem 
has not resolved. When we tried generating output, text on first page of output 
is fine but from page 2 onward we are getting garbage text. Observation was 
that if some text is outputted on first page and again on next pages it 
displays fine but when we try to output something directly on second page or 
onwards we are facing this issue. Below is the entry that we are using in our 
.xconf file.
renderer mime=application/postscript
  !-- This option forces the PS renderer to rotate landscape pages --
  !--auto-rotate-landscapetrue/auto-rotate-landscape--
  
  !-- This option lets you specify additional options on an XML handler --
  !--xml-handler namespace=http://www.w3.org/2000/svg;
stroke-textfalse/stroke-text
  /xml-handler--
  filterList
valuenull/value
/filterList
filterList type=image
valueflate/value
valueascii-85/value
/filterList
  fontstripleFilepfb;/fonts
  disable-srgb-colorspacetrue/disable-srgb-colorspace
/renderer

where tripleFilepfb points refers to .xml file containing .ttf fonts

  was:
We are generation a ps and pdf output using Apache FOP 1.1. We are using .ttf 
fonts for the same. PDF output seems to be fine but we are getting some garbage 
text while generation ps output. As per Apache documentation, ps output format 
only supports type 1 fonts so we have tried using .pfb fonts but problem is not 
resolved. When output is generated text on first page of output is fine but 
from page 2 onward we are getting garbage text. Observation was that if some 
text is outputted on first page and again on next pages it displays fine but if 
some text is first time used on second page or onwards we are facing this 
issue. Below is the entry that we are using in our .xconf file
renderer mime=application/postscript
  !-- This option forces the PS renderer to rotate landscape pages --
  !--auto-rotate-landscapetrue/auto-rotate-landscape--
  
  !-- This option lets you specify additional options on an XML handler --
  !--xml-handler namespace=http://www.w3.org/2000/svg;
stroke-textfalse/stroke-text
  /xml-handler--
  filterList
valuenull/value
/filterList
filterList type=image
valueflate/value
valueascii-85/value
/filterList
  fontstripleFilepfb;/fonts
  disable-srgb-colorspacetrue/disable-srgb-colorspace
/renderer

where tripleFilepfb points refers to .xml file containing .ttf fonts


 Problem while generating ps output in arabic 
 -

 Key: FOP-2375
 URL: https://issues.apache.org/jira/browse/FOP-2375
 Project: Fop
  Issue Type: Bug
  Components: ps
Affects Versions: 1.1
 Environment: Windows 7, 2 GBram
Reporter: Swapnil Khante
 Fix For: 1.1


 We are generating a ps and pdf arabic output using Apache FOP 1.1. We are 
 using .ttf fonts for the same. PDF output seems to be fine but we are getting 
 some garbage text while generation ps output. As per Apache documentation, ps 
 output format only supports type 1 fonts so we have tried using .pfb fonts 
 but problem has not resolved. When we tried generating output, text on first 
 page of output is fine but from page 2 onward we are getting garbage text. 
 Observation was that if some text is outputted on first page and again on 
 next pages it displays fine but when we try to output something directly on 
 second page or onwards we are facing this issue. Below is the entry that we 
 are using in our .xconf file.
 renderer mime=application/postscript
   !-- This option forces the PS renderer to rotate landscape pages --
   !--auto-rotate-landscapetrue/auto-rotate-landscape--
   
   !-- This option lets you specify additional options on an XML handler 
 --
   !--xml-handler namespace=http://www.w3.org/2000/svg;
 stroke-textfalse/stroke-text
   /xml-handler--
 filterList
   valuenull/value
   /filterList
   filterList type=image
   valueflate/value
   valueascii-85/value
   /filterList
   

[jira] [Updated] (FOP-2375) Problem while generating ps output in arabic

2014-05-26 Thread Swapnil Khante (JIRA)

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

Swapnil Khante updated FOP-2375:


Description: 
We are generating a ps and pdf Arabic output using Apache FOP 1.1. We are using 
.ttf fonts for the same. PDF output seems to be fine but we are getting some 
garbage text while generation ps output. As per Apache documentation, ps output 
format only supports type 1 fonts so we have tried using .pfb fonts but problem 
has not resolved. When we tried generating output, text on first page of output 
is fine but from page 2 onward we are getting garbage text. Observation was 
that if some text is outputted on first page and again on next pages it 
displays fine but when we try to output something directly on second page or on 
wards we are facing this issue. Below is the entry that we are using in our 
.xconf file.
renderer mime=application/postscript
  !-- This option forces the PS renderer to rotate landscape pages --
  !--auto-rotate-landscapetrue/auto-rotate-landscape--
  
  !-- This option lets you specify additional options on an XML handler --
  !--xml-handler namespace=http://www.w3.org/2000/svg;
stroke-textfalse/stroke-text
  /xml-handler--
  filterList
valuenull/value
/filterList
filterList type=image
valueflate/value
valueascii-85/value
/filterList
  fontstripleFilepfb;/fonts
  disable-srgb-colorspacetrue/disable-srgb-colorspace
/renderer

where tripleFilepfb points refers to .XML file containing .ttf fonts.
Could you please help here? Please let me know if you need any more information.
Thanks and regards,
Swapnil

  was:
We are generating a ps and pdf arabic output using Apache FOP 1.1. We are using 
.ttf fonts for the same. PDF output seems to be fine but we are getting some 
garbage text while generation ps output. As per Apache documentation, ps output 
format only supports type 1 fonts so we have tried using .pfb fonts but problem 
has not resolved. When we tried generating output, text on first page of output 
is fine but from page 2 onward we are getting garbage text. Observation was 
that if some text is outputted on first page and again on next pages it 
displays fine but when we try to output something directly on second page or 
onwards we are facing this issue. Below is the entry that we are using in our 
.xconf file.
renderer mime=application/postscript
  !-- This option forces the PS renderer to rotate landscape pages --
  !--auto-rotate-landscapetrue/auto-rotate-landscape--
  
  !-- This option lets you specify additional options on an XML handler --
  !--xml-handler namespace=http://www.w3.org/2000/svg;
stroke-textfalse/stroke-text
  /xml-handler--
  filterList
valuenull/value
/filterList
filterList type=image
valueflate/value
valueascii-85/value
/filterList
  fontstripleFilepfb;/fonts
  disable-srgb-colorspacetrue/disable-srgb-colorspace
/renderer

where tripleFilepfb points refers to .xml file containing .ttf fonts


 Problem while generating ps output in arabic 
 -

 Key: FOP-2375
 URL: https://issues.apache.org/jira/browse/FOP-2375
 Project: Fop
  Issue Type: Bug
  Components: ps
Affects Versions: 1.1
 Environment: Windows 7, 2 GBram
Reporter: Swapnil Khante
 Fix For: 1.1


 We are generating a ps and pdf Arabic output using Apache FOP 1.1. We are 
 using .ttf fonts for the same. PDF output seems to be fine but we are getting 
 some garbage text while generation ps output. As per Apache documentation, ps 
 output format only supports type 1 fonts so we have tried using .pfb fonts 
 but problem has not resolved. When we tried generating output, text on first 
 page of output is fine but from page 2 onward we are getting garbage text. 
 Observation was that if some text is outputted on first page and again on 
 next pages it displays fine but when we try to output something directly on 
 second page or on wards we are facing this issue. Below is the entry that we 
 are using in our .xconf file.
 renderer mime=application/postscript
   !-- This option forces the PS renderer to rotate landscape pages --
   !--auto-rotate-landscapetrue/auto-rotate-landscape--
   
   !-- This option lets you specify additional options on an XML handler 
 --
   !--xml-handler namespace=http://www.w3.org/2000/svg;
 stroke-textfalse/stroke-text
   /xml-handler--
 filterList
   valuenull/value
   /filterList
   

[jira] [Commented] (FOP-2375) Problem while generating ps output in arabic

2014-05-26 Thread Glenn Adams (JIRA)

[ 
https://issues.apache.org/jira/browse/FOP-2375?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14009159#comment-14009159
 ] 

Glenn Adams commented on FOP-2375:
--

No I cannot help you, because you haven't provided adequate information to 
determine if there is a problem or not. Common sense dictates that you provide 
an input FO file, an output PDF file, an output PS file, your FOP config file, 
and any console log, both invocation command and output. It never ceases to 
amaze me how people think any sense can be made of a bug report without full 
data context.

Furthermore, you appear to have failed to read the documentation at [1], under 
Other Limitations which states:

| Only the PDF output format fully supports complex scripts features at the 
present time.

I would suggest you use FOP to create output PDF containing Arabic, and then 
use an external conversion tool to translate to PS.

[1] http://xmlgraphics.apache.org/fop/1.1/complexscripts.html

 Problem while generating ps output in arabic 
 -

 Key: FOP-2375
 URL: https://issues.apache.org/jira/browse/FOP-2375
 Project: Fop
  Issue Type: Bug
  Components: ps
Affects Versions: 1.1
 Environment: Windows 7, 2 GBram
Reporter: Swapnil Khante
 Fix For: 1.1


 We are generating a ps and pdf Arabic output using Apache FOP 1.1. We are 
 using .ttf fonts for the same. PDF output seems to be fine but we are getting 
 some garbage text while generation ps output. As per Apache documentation, ps 
 output format only supports type 1 fonts so we have tried using .pfb fonts 
 but problem has not resolved. When we tried generating output, text on first 
 page of output is fine but from page 2 onward we are getting garbage text. 
 Observation was that if some text is outputted on first page and again on 
 next pages it displays fine but when we try to output something directly on 
 second page or on wards we are facing this issue. Below is the entry that we 
 are using in our .xconf file.
 renderer mime=application/postscript
   !-- This option forces the PS renderer to rotate landscape pages --
   !--auto-rotate-landscapetrue/auto-rotate-landscape--
   
   !-- This option lets you specify additional options on an XML handler 
 --
   !--xml-handler namespace=http://www.w3.org/2000/svg;
 stroke-textfalse/stroke-text
   /xml-handler--
 filterList
   valuenull/value
   /filterList
   filterList type=image
   valueflate/value
   valueascii-85/value
   /filterList
 fontstripleFilepfb;/fonts
 disable-srgb-colorspacetrue/disable-srgb-colorspace
 /renderer
 where tripleFilepfb points refers to .XML file containing .ttf fonts.
 Could you please help here? Please let me know if you need any more 
 information.
 Thanks and regards,
 Swapnil



--
This message was sent by Atlassian JIRA
(v6.2#6252)


[jira] [Created] (FOP-2376) PS rendering does not support complex scripts

2014-05-26 Thread Glenn Adams (JIRA)
Glenn Adams created FOP-2376:


 Summary: PS rendering does not support complex scripts
 Key: FOP-2376
 URL: https://issues.apache.org/jira/browse/FOP-2376
 Project: Fop
  Issue Type: New Feature
  Components: ps
Affects Versions: 1.1, trunk
Reporter: Glenn Adams


The PS renderer does not support complex scripts.



--
This message was sent by Atlassian JIRA
(v6.2#6252)


[jira] [Created] (FOP-2377) AFP rendering doesn't support complex scripts

2014-05-26 Thread Glenn Adams (JIRA)
Glenn Adams created FOP-2377:


 Summary: AFP rendering doesn't support complex scripts
 Key: FOP-2377
 URL: https://issues.apache.org/jira/browse/FOP-2377
 Project: Fop
  Issue Type: New Feature
Affects Versions: 1.1, trunk
Reporter: Glenn Adams


The AFP renderer does not support complex scripts.



--
This message was sent by Atlassian JIRA
(v6.2#6252)


[jira] [Created] (FOP-2378) PCL rendering doesn't support complex scripts

2014-05-26 Thread Glenn Adams (JIRA)
Glenn Adams created FOP-2378:


 Summary: PCL rendering doesn't support complex scripts
 Key: FOP-2378
 URL: https://issues.apache.org/jira/browse/FOP-2378
 Project: Fop
  Issue Type: New Feature
  Components: pcl
Affects Versions: 1.1, trunk
Reporter: Glenn Adams


The PCL renderer does not support complex scripts.



--
This message was sent by Atlassian JIRA
(v6.2#6252)


[jira] [Created] (FOP-2379) RTF rendering doesn't support complex scripts

2014-05-26 Thread Glenn Adams (JIRA)
Glenn Adams created FOP-2379:


 Summary: RTF rendering doesn't support complex scripts
 Key: FOP-2379
 URL: https://issues.apache.org/jira/browse/FOP-2379
 Project: Fop
  Issue Type: New Feature
  Components: rtf
Affects Versions: 1.1, trunk
Reporter: Glenn Adams
Priority: Minor


The RTF renderer does not support complex scripts.



--
This message was sent by Atlassian JIRA
(v6.2#6252)


[jira] [Created] (FOP-2381) TXT rendering doesn't support complex scripts

2014-05-26 Thread Glenn Adams (JIRA)
Glenn Adams created FOP-2381:


 Summary: TXT rendering doesn't support complex scripts
 Key: FOP-2381
 URL: https://issues.apache.org/jira/browse/FOP-2381
 Project: Fop
  Issue Type: New Feature
Affects Versions: 1.1, trunk
Reporter: Glenn Adams
Priority: Minor


The TXT renderer does not support complex scripts.



--
This message was sent by Atlassian JIRA
(v6.2#6252)


[jira] [Created] (FOP-2380) AWT rendering doesn't support complex scripts

2014-05-26 Thread Glenn Adams (JIRA)
Glenn Adams created FOP-2380:


 Summary: AWT rendering doesn't support complex scripts
 Key: FOP-2380
 URL: https://issues.apache.org/jira/browse/FOP-2380
 Project: Fop
  Issue Type: New Feature
  Components: awt renderer
Affects Versions: 1.1, trunk
Reporter: Glenn Adams
Priority: Minor


The AWT renderer does not support complex scripts.



--
This message was sent by Atlassian JIRA
(v6.2#6252)


[jira] [Resolved] (FOP-2375) Problem while generating ps output in arabic

2014-05-26 Thread Glenn Adams (JIRA)

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

Glenn Adams resolved FOP-2375.
--

Resolution: Duplicate

 Problem while generating ps output in arabic 
 -

 Key: FOP-2375
 URL: https://issues.apache.org/jira/browse/FOP-2375
 Project: Fop
  Issue Type: Bug
  Components: ps
Affects Versions: 1.1
 Environment: Windows 7, 2 GBram
Reporter: Swapnil Khante
 Fix For: 1.1


 We are generating a ps and pdf Arabic output using Apache FOP 1.1. We are 
 using .ttf fonts for the same. PDF output seems to be fine but we are getting 
 some garbage text while generation ps output. As per Apache documentation, ps 
 output format only supports type 1 fonts so we have tried using .pfb fonts 
 but problem has not resolved. When we tried generating output, text on first 
 page of output is fine but from page 2 onward we are getting garbage text. 
 Observation was that if some text is outputted on first page and again on 
 next pages it displays fine but when we try to output something directly on 
 second page or on wards we are facing this issue. Below is the entry that we 
 are using in our .xconf file.
 renderer mime=application/postscript
   !-- This option forces the PS renderer to rotate landscape pages --
   !--auto-rotate-landscapetrue/auto-rotate-landscape--
   
   !-- This option lets you specify additional options on an XML handler 
 --
   !--xml-handler namespace=http://www.w3.org/2000/svg;
 stroke-textfalse/stroke-text
   /xml-handler--
 filterList
   valuenull/value
   /filterList
   filterList type=image
   valueflate/value
   valueascii-85/value
   /filterList
 fontstripleFilepfb;/fonts
 disable-srgb-colorspacetrue/disable-srgb-colorspace
 /renderer
 where tripleFilepfb points refers to .XML file containing .ttf fonts.
 Could you please help here? Please let me know if you need any more 
 information.
 Thanks and regards,
 Swapnil



--
This message was sent by Atlassian JIRA
(v6.2#6252)


[jira] [Created] (FOP-2382) SVG rendering doesn't support complex scripts

2014-05-26 Thread Glenn Adams (JIRA)
Glenn Adams created FOP-2382:


 Summary: SVG rendering doesn't support complex scripts
 Key: FOP-2382
 URL: https://issues.apache.org/jira/browse/FOP-2382
 Project: Fop
  Issue Type: New Feature
Affects Versions: 1.1, trunk
Reporter: Glenn Adams


The SVG renderer does not support complex scripts.



--
This message was sent by Atlassian JIRA
(v6.2#6252)


JIRA Component Labels

2014-05-26 Thread Glenn Adams
I have long been unsatisfied with the set of component labels previously
used with Bugzilla, which we inherited in JIRA. I've finally gotten around
to relabeling many of the existing components and adding more specific
components.

I have relabeled as follows:

awt renderer : renderer/awt
fo tree : fo/unqualified
fonts : fonts/unqualified
general : unqualified
images : images/unqualified
page-master/layout : layout/unqualified
pcl : renderer/pcl
pdf : renderer/pdf
ps : renderer/ps
rtf : renderer/rtf
svg : renderer/svg

I have added the following:

fo/block
fo/inline
fo/page
fonts/opentype
fonts/postscript
images/jpeg
images/png
images/tiff
images/svg
layout/block
layout/inline
layout/line
layout/page
renderer/afp
renderer/txt

When you edit an existing issue, if its component contains unqualified,
then please take the opportunity to review and preferably select a more
qualified component name. If you don't find a suitably named alternative,
then please suggest one to this list so I can add it.

Note also, regarding the former svg component, I have relabeled that as
renderer/svg, which may not be appropriate depending on the issue. If the
issue is related to input from SVG (as opposed to output to SVG), then I
have created the images/svg component for the issues related to SVG input.


[jira] [Updated] (FOP-2381) TXT rendering doesn't support complex scripts

2014-05-26 Thread Glenn Adams (JIRA)

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

Glenn Adams updated FOP-2381:
-

Component/s: renderer/txt

 TXT rendering doesn't support complex scripts
 -

 Key: FOP-2381
 URL: https://issues.apache.org/jira/browse/FOP-2381
 Project: Fop
  Issue Type: New Feature
  Components: renderer/txt
Affects Versions: 1.1, trunk
Reporter: Glenn Adams
Priority: Minor

 The TXT renderer does not support complex scripts.



--
This message was sent by Atlassian JIRA
(v6.2#6252)


[jira] [Updated] (FOP-2382) SVG rendering doesn't support complex scripts

2014-05-26 Thread Glenn Adams (JIRA)

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

Glenn Adams updated FOP-2382:
-

Component/s: renderer/svg

 SVG rendering doesn't support complex scripts
 -

 Key: FOP-2382
 URL: https://issues.apache.org/jira/browse/FOP-2382
 Project: Fop
  Issue Type: New Feature
  Components: renderer/svg
Affects Versions: 1.1, trunk
Reporter: Glenn Adams

 The SVG renderer does not support complex scripts.



--
This message was sent by Atlassian JIRA
(v6.2#6252)


[jira] [Updated] (FOP-2377) AFP rendering doesn't support complex scripts

2014-05-26 Thread Glenn Adams (JIRA)

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

Glenn Adams updated FOP-2377:
-

Component/s: renderer/afp

 AFP rendering doesn't support complex scripts
 -

 Key: FOP-2377
 URL: https://issues.apache.org/jira/browse/FOP-2377
 Project: Fop
  Issue Type: New Feature
  Components: renderer/afp
Affects Versions: 1.1, trunk
Reporter: Glenn Adams

 The AFP renderer does not support complex scripts.



--
This message was sent by Atlassian JIRA
(v6.2#6252)


[jira] [Updated] (FOP-1359) Problem with tiff gray render

2014-05-26 Thread Glenn Adams (JIRA)

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

Glenn Adams updated FOP-1359:
-

Component/s: renderer/tiff

 Problem with tiff gray render
 -

 Key: FOP-1359
 URL: https://issues.apache.org/jira/browse/FOP-1359
 Project: Fop
  Issue Type: Bug
  Components: renderer/tiff
Affects Versions: 0.93
 Environment: Operating System: Linux
 Platform: Other
Reporter: Vitali
 Attachments: tiff.patch


 I wrote some code
final TIFFRenderer render = new TIFFRenderer() {
   protected BufferedImage getBufferedImage(int w, int h) {
 return new BufferedImage(w, h, BufferedImage.TYPE_BYTE_GRAY);
   }
 };
 render.setUserAgent(userAgent);
 userAgent.setRendererOverride(render);
 ... and try exception
 javax.xml.transform.TransformerException: java.lang.ClassCastException
 at
 org.apache.xalan.transformer.TransformerImpl.transformNode(TransformerImpl.java:1430)
 at
 org.apache.xalan.transformer.TransformerImpl.transform(TransformerImpl.java:709)
 at
 org.apache.xalan.transformer.TransformerImpl.transform(TransformerImpl.java:1284)
 at
 org.apache.xalan.transformer.TransformerImpl.transform(TransformerImpl.java:1262)
 at
 com.academsoft.printing.PrintingProtocol.processOutData(PrintingProtocol.java:206)
 at
 com.academsoft.printing.PrintingProtocol.processInput(PrintingProtocol.java:173)
 at com.academsoft.printing.Worker.process(Worker.java:48)
 at com.academsoft.printing.Worker.run(Worker.java:68)
 Caused by: java.lang.ClassCastException
 at
 org.apache.fop.render.bitmap.TIFFRenderer$LazyPageImagesIterator.next(TIFFRenderer.java:234)
 at
 org.apache.fop.render.bitmap.TIFFRenderer.stopRenderer(TIFFRenderer.java:166)
 at
 org.apache.fop.area.RenderPagesModel.endDocument(RenderPagesModel.java:241)
 at 
 org.apache.fop.area.AreaTreeHandler.endDocument(AreaTreeHandler.java:426)
 at org.apache.fop.fo.FOTreeBuilder.endDocument(FOTreeBuilder.java:171)
 at
 org.apache.xml.serializer.ToXMLSAXHandler.endDocument(ToXMLSAXHandler.java:181)
 at
 org.apache.xalan.transformer.TransformerImpl.transformNode(TransformerImpl.java:1378)
 ... 7 more
 wrote patch
 diff -rNu fop-0.93/src/java/org/apache/fop/render/bitmap/TIFFRenderer.java
 fop-0.93.orig/src/java/org/apache/fop/render/bitmap/TIFFRenderer.java
 --- fop-0.93/src/java/org/apache/fop/render/bitmap/TIFFRenderer.java   
 2007-05-08 16:51:02.0 +0700
 +++ fop-0.93.orig/src/java/org/apache/fop/render/bitmap/TIFFRenderer.java 
  
 2007-01-04 02:44:43.0 +0600
 @@ -230,11 +230,10 @@
  return pageImage;
  } else {
  //Decorate the image with a packed sample model for encoding 
 by
 the codec
 -  final SampleModel sampleModel = pageImage.getSampleModel();
 -//  SinglePixelPackedSampleModel sppsm;
 -//sppsm = 
 (SinglePixelPackedSampleModel)pageImage.getSampleModel();
 +SinglePixelPackedSampleModel sppsm;
 +sppsm = 
 (SinglePixelPackedSampleModel)pageImage.getSampleModel();
 -int bands = sampleModel.getNumBands();
 +int bands = sppsm.getNumBands();
  int[] off = new int[bands];
  int w = pageImage.getWidth();
  int h = pageImage.getHeight();
 and all works.
 ps. 
 Product:  Fop.
  Component: - no tiff.



--
This message was sent by Atlassian JIRA
(v6.2#6252)


[jira] [Updated] (FOP-1359) Problem with tiff gray render

2014-05-26 Thread Glenn Adams (JIRA)

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

Glenn Adams updated FOP-1359:
-

Component/s: (was: renderer/svg)

 Problem with tiff gray render
 -

 Key: FOP-1359
 URL: https://issues.apache.org/jira/browse/FOP-1359
 Project: Fop
  Issue Type: Bug
  Components: renderer/tiff
Affects Versions: 0.93
 Environment: Operating System: Linux
 Platform: Other
Reporter: Vitali
 Attachments: tiff.patch


 I wrote some code
final TIFFRenderer render = new TIFFRenderer() {
   protected BufferedImage getBufferedImage(int w, int h) {
 return new BufferedImage(w, h, BufferedImage.TYPE_BYTE_GRAY);
   }
 };
 render.setUserAgent(userAgent);
 userAgent.setRendererOverride(render);
 ... and try exception
 javax.xml.transform.TransformerException: java.lang.ClassCastException
 at
 org.apache.xalan.transformer.TransformerImpl.transformNode(TransformerImpl.java:1430)
 at
 org.apache.xalan.transformer.TransformerImpl.transform(TransformerImpl.java:709)
 at
 org.apache.xalan.transformer.TransformerImpl.transform(TransformerImpl.java:1284)
 at
 org.apache.xalan.transformer.TransformerImpl.transform(TransformerImpl.java:1262)
 at
 com.academsoft.printing.PrintingProtocol.processOutData(PrintingProtocol.java:206)
 at
 com.academsoft.printing.PrintingProtocol.processInput(PrintingProtocol.java:173)
 at com.academsoft.printing.Worker.process(Worker.java:48)
 at com.academsoft.printing.Worker.run(Worker.java:68)
 Caused by: java.lang.ClassCastException
 at
 org.apache.fop.render.bitmap.TIFFRenderer$LazyPageImagesIterator.next(TIFFRenderer.java:234)
 at
 org.apache.fop.render.bitmap.TIFFRenderer.stopRenderer(TIFFRenderer.java:166)
 at
 org.apache.fop.area.RenderPagesModel.endDocument(RenderPagesModel.java:241)
 at 
 org.apache.fop.area.AreaTreeHandler.endDocument(AreaTreeHandler.java:426)
 at org.apache.fop.fo.FOTreeBuilder.endDocument(FOTreeBuilder.java:171)
 at
 org.apache.xml.serializer.ToXMLSAXHandler.endDocument(ToXMLSAXHandler.java:181)
 at
 org.apache.xalan.transformer.TransformerImpl.transformNode(TransformerImpl.java:1378)
 ... 7 more
 wrote patch
 diff -rNu fop-0.93/src/java/org/apache/fop/render/bitmap/TIFFRenderer.java
 fop-0.93.orig/src/java/org/apache/fop/render/bitmap/TIFFRenderer.java
 --- fop-0.93/src/java/org/apache/fop/render/bitmap/TIFFRenderer.java   
 2007-05-08 16:51:02.0 +0700
 +++ fop-0.93.orig/src/java/org/apache/fop/render/bitmap/TIFFRenderer.java 
  
 2007-01-04 02:44:43.0 +0600
 @@ -230,11 +230,10 @@
  return pageImage;
  } else {
  //Decorate the image with a packed sample model for encoding 
 by
 the codec
 -  final SampleModel sampleModel = pageImage.getSampleModel();
 -//  SinglePixelPackedSampleModel sppsm;
 -//sppsm = 
 (SinglePixelPackedSampleModel)pageImage.getSampleModel();
 +SinglePixelPackedSampleModel sppsm;
 +sppsm = 
 (SinglePixelPackedSampleModel)pageImage.getSampleModel();
 -int bands = sampleModel.getNumBands();
 +int bands = sppsm.getNumBands();
  int[] off = new int[bands];
  int w = pageImage.getWidth();
  int h = pageImage.getHeight();
 and all works.
 ps. 
 Product:  Fop.
  Component: - no tiff.



--
This message was sent by Atlassian JIRA
(v6.2#6252)


[jira] [Updated] (FOP-1842) integration of barcode in fop 1.0

2014-05-26 Thread Glenn Adams (JIRA)

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

Glenn Adams updated FOP-1842:
-

Component/s: (was: renderer/svg)
 foreign/barcode

 integration of barcode in fop 1.0
 -

 Key: FOP-1842
 URL: https://issues.apache.org/jira/browse/FOP-1842
 Project: Fop
  Issue Type: Bug
  Components: foreign/barcode
Affects Versions: 1.0
 Environment: Operating System: Linux
 Platform: PC
Reporter: marc-andre.marion
 Attachments: test.fo


 Hi,
 I tried to generate a pdf including a barcode with fop 1.0 and barcode4j 2.0.
 The following error was generated during the integration of bar code in the 
 pdf : 
 [ERROR] FOUserAgent - Image not available. URI: (instream-object). Reason: 
 org.apache.xmlgraphics.image.loader.ImageException: The file format is not 
 supported. No ImagePreloader found for null (No context info available)
 This works very well with fop 0.95 and with the same configuration.
 If I replace the fop.jar by that of fop 0.95 it works.



--
This message was sent by Atlassian JIRA
(v6.2#6252)


[jira] [Updated] (FOP-1789) [PATCH] java.lang.NoClassDefFoundError: org/apache/batik/util/XMLResourceDescriptor

2014-05-26 Thread Glenn Adams (JIRA)

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

Glenn Adams updated FOP-1789:
-

Component/s: (was: renderer/svg)
 images/svg

 [PATCH] java.lang.NoClassDefFoundError: 
 org/apache/batik/util/XMLResourceDescriptor
 ---

 Key: FOP-1789
 URL: https://issues.apache.org/jira/browse/FOP-1789
 Project: Fop
  Issue Type: Bug
  Components: images/svg
Affects Versions: 0.95
 Environment: Operating System: All
 Platform: All
Reporter: Yannick Majoros
 Attachments: fop.patch


 While starting fop without batik jar, this error is shown in the logs:
 Error while initializing the Batik SVG extensions
 java.lang.NoClassDefFoundError: org/apache/batik/util/XMLResourceDescriptor 
at 
 org.apache.fop.fo.extensions.svg.SVGElementMapping.initialize(SVGElementMapping.java:80)
  
 (+long stack trace)
 This is a warning, but is confusing some developers of my team. A quick check 
 on the web shows many people are confused with this.
 This is not consistent with what other extensions do.
 If the only consequence is that batik is disabled, the complete stack trace 
 should not be shown. A warning is enough, and debug info with complete stack 
 trace should be made available.
 This quick patch fixes that.



--
This message was sent by Atlassian JIRA
(v6.2#6252)


[jira] [Updated] (FOP-1789) [PATCH] java.lang.NoClassDefFoundError: org/apache/batik/util/XMLResourceDescriptor

2014-05-26 Thread Glenn Adams (JIRA)

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

Glenn Adams updated FOP-1789:
-

Component/s: (was: image/svg)
 foreign/svg

 [PATCH] java.lang.NoClassDefFoundError: 
 org/apache/batik/util/XMLResourceDescriptor
 ---

 Key: FOP-1789
 URL: https://issues.apache.org/jira/browse/FOP-1789
 Project: Fop
  Issue Type: Bug
  Components: foreign/svg
Affects Versions: 0.95
 Environment: Operating System: All
 Platform: All
Reporter: Yannick Majoros
 Attachments: fop.patch


 While starting fop without batik jar, this error is shown in the logs:
 Error while initializing the Batik SVG extensions
 java.lang.NoClassDefFoundError: org/apache/batik/util/XMLResourceDescriptor 
at 
 org.apache.fop.fo.extensions.svg.SVGElementMapping.initialize(SVGElementMapping.java:80)
  
 (+long stack trace)
 This is a warning, but is confusing some developers of my team. A quick check 
 on the web shows many people are confused with this.
 This is not consistent with what other extensions do.
 If the only consequence is that batik is disabled, the complete stack trace 
 should not be shown. A warning is enough, and debug info with complete stack 
 trace should be made available.
 This quick patch fixes that.



--
This message was sent by Atlassian JIRA
(v6.2#6252)


Re: JIRA Component Labels

2014-05-26 Thread Glenn Adams
Additional minor changes:

fonts/* changed to font/*
images/* changed to image/*

Added:

foreign/barcode
foreign/svg

There are now 3 SVG components:

foreign/svg -  for SVG input via instream-foreign-object
image/svg - for SVG input via external-graphic
renderer/svg - for SVG output



On Tue, May 27, 2014 at 9:56 AM, Glenn Adams gl...@skynav.com wrote:

 I have long been unsatisfied with the set of component labels previously
 used with Bugzilla, which we inherited in JIRA. I've finally gotten around
 to relabeling many of the existing components and adding more specific
 components.

 I have relabeled as follows:

 awt renderer : renderer/awt
 fo tree : fo/unqualified
 fonts : fonts/unqualified
 general : unqualified
 images : images/unqualified
 page-master/layout : layout/unqualified
 pcl : renderer/pcl
 pdf : renderer/pdf
 ps : renderer/ps
 rtf : renderer/rtf
 svg : renderer/svg

 I have added the following:

 fo/block
 fo/inline
 fo/page
 fonts/opentype
 fonts/postscript
 images/jpeg
 images/png
 images/tiff
 images/svg
 layout/block
 layout/inline
 layout/line
 layout/page
 renderer/afp
 renderer/txt

 When you edit an existing issue, if its component contains unqualified,
 then please take the opportunity to review and preferably select a more
 qualified component name. If you don't find a suitably named alternative,
 then please suggest one to this list so I can add it.

 Note also, regarding the former svg component, I have relabeled that as
 renderer/svg, which may not be appropriate depending on the issue. If the
 issue is related to input from SVG (as opposed to output to SVG), then I
 have created the images/svg component for the issues related to SVG input.