Hi everybody
I'm new to XSL-FO and apache fop. I'm trying to create a report with a left
margin of 1cm for the header and body. The footer (region-after) should have a
left margin of 0. The header contains a table. I tried tot achive this with a
left margin of 1cm for the region-body and the
Hi,
The font subsystem has been widely improved in the latest FOP TRUNK (see
[1] and [2] for build, [3] for changes).
It should give you better result than released FOP on that part.
[1] http://xmlgraphics.apache.org/fop/download.html#source
[2]
Hi,
by default, region-start and region-end have the precedence over the 2
other static regions.
if you want, you can change this by explicitely set the precedence as
you want for any region:
in your case, you may use precedence=true for the fo:region-after.
HTH,
Pascal
philippe voncken a écrit
Hi Josh,
As far as I understood, it works like this (in trunk, as Pascal already said):
For each character in a word, FOP checks the first font. If the character is
not available, the second font is checked. And so on. The font with the most
available characters is used for this word. So you
Hi,
visibility affects the boxes generated by the Formatting object, but...
fo:table-column generates no area, so this property has no direct effect
as it.
However, since this property is inheritable in XSL-FO, this can be
referenced by the (supported) function from-table-column().
If you want
Hi Gregory,
Can you please post a small XSL-FO file exhibiting the problem?
Thanks,
Vincent
Gregory Buchenberger wrote:
Hello,
I'm getting the following error when running FOP 1.0dev:
STDERR: (Location of error unknown)java.lang.IllegalArgumentException:
Only non-null Positions with an
Jonathan Levinson wrote:
Hi,
A colleague reports that documents generated using the fop-trunk are
much larger than documents generated using fop-0.95.
“Using the same xml xsl, with FOP-0.95 I get a file size of 785kb, but
using the fop trak version with your fop.xconf file, I get a file
See also bug 48481,
https://issues.apache.org/bugzilla/show_bug.cgi?id=48481.
Simon
On Fri, Mar 05, 2010 at 09:36:08AM +0100, Pascal Sancho wrote:
Hi,
The font subsystem has been widely improved in the latest FOP TRUNK (see
[1] and [2] for build, [3] for changes).
It should give you better
Hi,
I've tested the new support for Symbol and Wingdings fonts with the
latest FOP trunk and wanted to share with you two observations:
1. In my fop config file font auto detection is enabled. Nevertheless
Wingdings and Symbol fonts are not automatically detected inside the
Windows Fonts
Hi Matthias
On 05.03.2010 15:22:02 Matthias Reischenbacher wrote:
Hi,
I've tested the new support for Symbol and Wingdings fonts with the
latest FOP trunk and wanted to share with you two observations:
1. In my fop config file font auto detection is enabled. Nevertheless
Wingdings and
I would start with a basic fop.xconf with nothing modified yet and in the
default fonts element, why dont you try as a test to turn off auto-detect
(i dont like it anyway cause I get a million warning messages about windows
fonts collections i never use when I was testing trunk font stuff)...
and
Vincent,
Unfortunately, the FO file is over 2MB and is accompanied by over
400MB of images. In addition, it is copyrighted primary grade textbook
material that I can't distribute on a mailing list. Can you give me an
idea of where to look? If I can find the offending XSL I will happily
send a
Thanks for the input. Sounds like I had a few assumptions wrong about the
font cascade. It looks like bug 48481 is pretty close to what I'm having
trouble with, so I'll study that a bit more. Two additional questions:
1. How stable is the code in the trunk, and when will it be released as a
FOP
Hi,
I'd like to mark the resulting PDF by the stylesheet with
information about the generation process, i. e. this file
was generated by stylesheet.xsl version 1.2 with the setting
'abstracts_only=yes' and 'date=2010-03-05'. This informa-
tion doesn't need to and shouldn't be printable per se,
On 03/05/2010 05:11 PM, JoshC wrote:
Thanks for the input. Sounds like I had a few assumptions wrong about the
font cascade. It looks like bug 48481 is pretty close to what I'm having
trouble with, so I'll study that a bit more. Two additional questions:
1. How stable is the code in the trunk,
Hi Jeremias,
I've tested the new support for Symbol and Wingdings fonts with the
latest FOP trunk and wanted to share with you two observations:
1. In my fop config file font auto detection is enabled. Nevertheless
Wingdings and Symbol fonts are not automatically detected inside the
Windows
16 matches
Mail list logo