Re: PDF: Disable converting color to "Device Gray"

On 30/08/10 22:47, Jeremias Maerki wrote:
> FOP doesn't have such an option. The PDF 1.4 spec says in chapter 6.2.1:
> "A gray level is equivalent to an RGB value with all three components
> the same."
> 
> And therefore we render gray values in the DeviceGray color space. That
> this doesn't work in your case is a bit surprising. But I've heard
> something similar just two weeks ago from a company that does photo
> books with FOP/Batik. But they had to do strange things like using CMYK
> and adding Magenta in addition to the K=1.0 value. They still just get
> an approximate black. I guess that's an issue of the printer they use. I
> suspect your case may be similar: a printer issue.

It's often an issue with the RIP or preflight tools, rather than the
printer/press its self.

ICC-aware RIPs will use ICC color space transforms to convert RGB
colours in a given space to the output device space - usually a custom
CMYK profile for the printer/press. /DeviceGray is a different colour
space to /DeviceRGB and the /DeviceGray to CMYK conversion is a
different mapping to the RGB one, potentially done with different
profiles. Some RIPs just convert /DeviceGray to /DeviceRGB then do the
transform from RGB, but that's not necessarily correct, especially in a
tagged document where there are mulitiple colour spaces in the same
co-ordinate system, like sRGB and AdobeRGB.

A proper configuration will use a greyscale profile that matches the RGB
profile. That's not very common, though, and really only works out where
the assumed greyscale curve happens to match the chosen or assumed RGB
profile.

Re: Memory Leak issue -- FOP

On 30/08/10 22:29, Hamed Mohammed wrote:
> Hi,
>  
> This is how I am using FOP to process XSL.FO <http://XSL.FO> into PDF. I
> agree that the issue is to do with too much of memory consumption. Is
> there a better way to process this large FO file into PDF using FOP?

How much memory is too much? Have you used the JVM's tools to find out
*where* the memory is going?

If you don't know Java's profiling tools well, you might want to try the
rather user-friendly memory profiler in NetBeans. NetBeans opens Maven
projects directly, and can be set up for a generic Ant project quite
quickly, so if you're not already using it there's no reason not to just
for this.

> String xml = builder.getReport(); /// gets the XSL:FO file data approx 50mb

If you're concerned about memory consumption, writing your XSL-FO to a
tempfile rather than an in-memory string and passing that to FOP's SAX
engine would be a big help. Or, for that matter, writing directly to the
SAX handler's InputStream, progressively generating the document as it's
required so it never has to exist entirely in memory or on disk.

> PdfStorage pdfHolder = pdfStorageFactory.createStorage(reportRequest,

What's PdfStorage? It doesn't seem to be in fop's packages...

Any chance you can post a self-contained test program that demonstrates
the problem you describe, along with sample input for it?

Re: How to include .fo file into another .fo

Shaki wrote:
> Jeremias Maerki <dev <at> jeremias-maerki.ch> writes:

<snip/>

> 
>> 2. If you have an XInclude-capable XML parser (or a SAX filter for
>> XInclude), you can use XInclude.
>>
>> http://en.wikipedia.org/wiki/XInclude
>> http://www.w3.org/TR/xinclude/

<snip/>

> 
> I am using Apache FOP. My attempt with XInclude failed.
> 
> File to be included: 2.pdf 
> <fo:block font-size="20pt">
>    Address block
> </fo:block>  
> 
> Master file:
> <fo:block>
>   <xi:include href="2.fo" parse="xml" xmlns:xi="http://www.w3.org/2001/XInclude">
>     <xi:fallback>Include Error</xi:fallback>    
>   </xi:include>
> </fo:block>

You are using relative paths in the reference. Did you try specifying a 

Heading Styles

RE: Orientation

Table with spanned-row-header in 2 columned region-body

Hi There!

 Im trying to make a table with a spanned header in a 2 columned region-body.
(Examples attached....)
I would need something like a "span=all" into the table-header... like this:

	<fo:region-body region-name="PageBody" column-count="2"/>

        <fo:table>
              	<fo:table-column>
               	<fo:table-column>
                <fo:table-header >
			<fo:table-row span="all">
	                    <fo:table-cell number-columns-spanned="2">
	                        <fo:block> T1H1</fo:block>
	                    </fo:table-cell>
			</fo:table-row>
			<fo:table-row>
	                    <fo:table-cell>
	                        <fo:block> T1H2C1</fo:block>
	                    </fo:table-cell>
	                    <fo:table-cell>
	                        <fo:block> T1H2C2</fo:block>
	                    </fo:table-cell>
	                </fo:table-row>
                </fo:table-header>
                <fo:table-body >

It should look like this:

"_______Table Header 1______"
"TableHeader2"    "TableHeader2"
"ContentRow _"    "ContentRow _"
"ContentRow _"    "ContentRow _"
"ContentRow _"    "ContentRow _"
...

-Page Break-

"_______Table Header 1______"
"TableHeader2"    "TableHeader2"
"ContentRow _"    "ContentRow _"
"ContentRow _"    "ContentRow _"
"ContentRow _"    "ContentRow _"

Any idea how to do this is really appreciated!!!
Thanks!

Attached is an example XSL/FO and PDF what I would need... (the blue one is the desired one just also over page breaks....)

Adam 
Using FOP 1.0

AW: Table with spanned-row-header in 2 columned region-body

Placing the minus sign(-) to the RIGHT side of the number

RE: Placing the minus sign(-) to the RIGHT side of the number

Re: AW: Table with spanned-row-header in 2 columned region-body