Hi Jose,
Whate about something like that:
fo:page-sequence-master master-name=mySeqMaster
fo:repeatable-page-master-alternatives
fo:conditional-page-master-reference
master-reference=lastMaster page-position=last/
fo:conditional-page-master-reference
Hi,
you should read FOP trace (from stdin or stderr).
This reveals what is wrong in your XSL-FO: FOP throws a lot of
exceptions, that prevent it to generate any PDF.
At least, your app should report you if PDF has been generated or not.
Le 03/02/2012 14:32, Theresa Jayne Forster a écrit :
Why
Hi,
As said in XSL-FO REC 1.1 (§7.27.16 at [1]),
precedence=true specifies which region (i.e., region-before,
region-after, region-start, or region-end) takes precedence in terms of
which may extend into the corners of the simple-page-master
So, this will not help Theresa.
The only solution I
Hi,
did you tried FOP latest trunk (or nightly built)? There is some
performance improvement.
Note that table is memory hungry, and unless you need it to layout
arrays, perhaps you can tweak your XSLT to use alternative fo elements,
depending on what your document contains.
Le 26/01/2012 15:12,
Hi,
I don't understand what you want to do.
What is fntsample?
Where is the uploaded file?
Note that with FOP 1.0, metric files are required only when you don't
want to embed font in PDF.
In addition, note also that metrics are the same for both Arial and
Helvetica (witch is part of the 14 PDF
Hi,
1/ you have to first download FOP source from SVN repository (see [1]).
Take care to update with the revision witch patch is based on (1153319
in your case).
2/ apply the patch
3/ Then build FOP using ant (ant package prevents from launching test
suite) (read [2]).
As a starting point on
-alternatives
/fo:page-sequence-master
Does this look correct? Should this work? Thanks for any help with
this!
Pascal Sancho wrote:
Hi,
Page compliance says that partial support concerns only FOP 0.95.
Latter
versions have full support for this property.
After SVN check, the only
-commons-1.4
Thank you.
On 23/1/2012 3:00 PM, Pascal Sancho wrote:
Klearchos,
I cannot reproduce what you get with the provided snippet: too small.
What FOP version do you use?
Le 23/01/2012 10:55, Klearchos Klearchou a écrit :
Hi Pascal,
I copied some of the FO.
In case you want to see more
but 300 x 300. As you can see
FOP fails to scale it.
It overflows out of the box.
Do you have any idea what it could be?
Thank you in advance
On 1/17/2012 5:47 PM, Pascal Sancho wrote:
We use imageMagik
Le 17/01/2012 15:32, Klearchos Klearchou a écrit :
Pascal,
the information
AM, Pascal Sancho wrote:
Hi,
can you provide a short XSL-FO (not XSLT) with equivalent images that
reproduce what you describe here, I cannot figure what you say.
Le 20/01/2012 16:29, Klearchos Klearchou a écrit :
Hello Pascal,
the solution that we talked about works well almost in all
a écrit :
Pascal Sancho pascal.sancho at takoma.fr writes:
Hi Santanu,
on this list we start with XSL-FO as input, so you should explain what
do you expect precisely as output rendering, what do you get, and
provide a short XSL-FO snippet as material if taht can help (see [1]).
Your question
Hi,
I guess that by the result is problematic with very tall images you
mean that image can overflow the page when h/w ratio is too high.
If this is the case, you can use max-height XSL-FO equivalent:
fo:external-graphic src={$imageUrl}
block-progression-dimension.optimum=$my_minimal_height
inside the PDF.
Thank you.
On 17/1/2012 3:42 PM, Pascal Sancho wrote:
Hi,
I guess that by the result is problematic with very tall images you
mean that image can overflow the page when h/w ratio is too high.
If this is the case, you can use max-height XSL-FO equivalent:
fo:external-graphic
image in order to show you
what I mean.
Is it possible to make the green border to fit the image and not leave
this white empty space?
On 1/17/2012 4:18 PM, Pascal Sancho wrote:
Quality loss may depend on PDF viewer settings and capabilities
(anti-aliasing, zoom factor, etc.)
Also
more
but they do not provide em exactly what I want.
I haven't tried yet JMajick.
Thanks again.
On 1/17/2012 4:18 PM, Pascal Sancho wrote:
Quality loss may depend on PDF viewer settings and capabilities
(anti-aliasing, zoom factor, etc.)
Also, the result can seem better if you
Hi Theresa,
IIRC, under FOP 0.2x, body was drawn before other regions, as it was
under other.
With current FOP, the body is drown after other regions, as it is over
other.
You can try to change the region order in simple-page-master
declaration, I don't know if this can help or not.
Note that
Hi Lars,
Le 21/12/2011 22:24, Lars Bjørndal a écrit :
Hi!
[Pascal Sancho]
Lars, are you running FOP on Linux without Xserver?
Yes, I'm blind, and don't need the graphic. Also, I do run from a server
to which I connect through ssh.
If this is the case, you should run FOP (and Batik
Hi Luis,
I tried your initial FO (with negative margin) against FOP 1.0 and FOP
trunk:
FOP 1.0 is buggy while FOP trunk works as expected.
In addition, note that with fo:external-object or
fo:instream-foreign-object, there are half-leading before and after,
that depend on font-size and
Sorry, this was addressed to Samuel
Le 16/12/2011 09:50, Pascal Sancho a écrit :
Hi Luis,
--
Pascal
-
To unsubscribe, e-mail: fop-users-unsubscr...@xmlgraphics.apache.org
For additional commands, e-mail: fop-users-h
Hi Samuel,
I don't understand what you mean by if I take 1mm off the left margin
on right hand pages...
Can you provide a short snippet to illustrate, please?
I know there is a bug in inline-progression-dimension computation when
using 'mm' or 'cm' as unit, that can cause trouble when using
Hi Theresa,
FOP currently doesn't implement clip property. See compliance page at [1].
That said, there is a SGV alternative, try this (replacing XSLT variable
with appropriate values):
fo:instream-foreign-object width=100% content-width=scale-to-fit
svg xmlns=http://www.w3.org/2000/svg;
Hi Vincent,
Le 07/12/2011 10:15, Vincent Hobeïka a écrit :
Hi Pascal,
Thank you for your kind answer.
On Tue, Dec 6, 2011 at 3:33 PM, Pascal Sancho pascal.san...@takoma.fr
wrote:
when you ask on this list, you should provide a shrinked XSL-FO that
demonstrates the problem
I am
Hi,
Le 07/12/2011 15:18, Craig Ringer a écrit :
Hi folks
I've just found out about Jeremias's PDF-image extension for fop. It's
ideal for my purposes, as I need to include pre-produced PDFs from
desktop publishing software inside an XSL-FO document that's output to PDF.
I'm curious: Is
Hi Jonathan,
With recent Windows (Vista), IIUC there is no difference between .cmd
and .bat; the engine remains the same in both cases: cmd.exe
In the past, Win 9x family (and before) used only .bat, witch was
threated with command.com
The engine cmd.exe was introduced with NT family.
On XP
Hi Vincent,
when you ask on this list, you should provide a shrinked XSL-FO that
demonstrates the problem (the one on Debian buglist is about 2MB, witch
is quite big).
That said, I've found that using fo:inline within a fo:block with
hyphenate=true linefeed-treatment=preserve throws an NPE.
Hi Theresa,
unless you want to play with whole system fonts, you should configure
only a limited set, either registring each font namely, or grouping them
in a directory that you can register with a single command.
See [1] for further details
Note that there are many other reasons that can
Theresa,
file:/// means the root of your local system.
You should check if the file is in the right place, and if FOP has read
permission on it.
Le 05/12/2011 16:10, Theresa Jayne Forster a écrit :
Ok, I tried setting up a font definition but I am getting an error no
matter what font I try
Hi Pedro,
We (Luis and I) tried successfully your XSL-FO with suggested changes
(inserting ZWSP by hand).
So, you should inspect closely your XML+XSLT transformation, there is
something wrong there.
I don't remember what XSLT engine do you use (FOP comes with Xalan 1.7.0
as a convenience, but you
ZWSP.
Le 23/11/2011 09:09, pedro a écrit :
Hi i can add a file, is not very short because this bug is visible if there
is two pages document! http://old.nabble.com/file/p32873641/fo.xml fo.xml
Pascal Sancho wrote:
Can you post a [short] XSL-FO (not XSL-T) that demonstrates the issue?
I
another thread.
Thanks!
Pascal Sancho wrote:
Hehe,
This seems to be related to bug #50806 [1].
(I didn't remembered it)
Fortunately, there is a workaround: insert a ZWSP (#x200b;) before each
fo:retrieve-marker, this should do the trick.
[1] https://issues.apache.org/bugzilla
Pedro,
what is the output? PDF, XSL-FO, other?
whitch tool (and version) do you use to see it?
I suspect this is a viewer issue, FOP works fine with such character.
Note that [disable-output-escaping=yes] is only for lt; or amp;, and
its use is discourged by good practices.
Le 22/11/2011
Can you post a [short] XSL-FO (not XSL-T) that demonstrates the issue?
I cannot reproduce what you describe.
Le 22/11/2011 14:16, pedro a écrit :
I use fop 0,95 and the output is a pdf that i open with Acrobat X or Foxit
Redaer.
Pascal Sancho wrote:
Pedro,
what is the output? PDF, XSL
/fo.xml
fo.xml http://old.nabble.com/file/p32870816/1321885821859 1321885821859
Pascal Sancho wrote:
Hi Pedro
Regarding your 1st question: alternative to marker (content on last page):
you can use page-position=last on an
fo:conditional-page-master-reference
Regarding your 2nd
on result (see inline coments)
Le 11/11/2011 15:55, gkasper a écrit :
Pascal Sancho wrote:
That should be fixed with things mentionned in other response I made a
few seconds before:
- b-p-d.optimum set with absolute size
- correct typo for scale-to-fit
Hi Pascal,
Could you please try
FOP 1.0 or FOP TRUNK give both same result: image is not truncated at
bottom.
I suspect you are using an older version, can you confirm that point?
Le 14/11/2011 12:37, gkasper a écrit :
Pascal Sancho wrote:
- data (XXX...) is rendered over the image
- there is no extra page
From
Hi,
Le 10/11/2011 01:42, gkasper a écrit :
Pascal Sancho wrote:
Your snippet should be like that:
fo:block font-size=0
fo:external-graphic src=url(Images/MASTER_CMS-1500-v4.gif)
block-progression-dimension.maximum=269.4mm
block-progression-dimension.optimum=100mm
That should be fixed with things mentionned in other response I made a
few seconds before:
- b-p-d.optimum set with absolute size
- correct typo for scale-to-fit
Le 10/11/2011 02:22, gkasper a écrit :
Sorry Pascal, I just noticed...
If I do it this way, it solves the second problem (extra
Hi,
Le 08/11/2011 20:35, gkasper a écrit :
Pascal Sancho wrote:
Hi,
You should apply them on fo:external-graphic: i-p-d and b-p-d replacing
respectively width and height.
fo:block b-p-d depends on its content if defaulting to 'auto'.
content-* should have 'scale-to-fit' or equivalent
08/11/2011 15:26, gkasper a écrit :
Pascal Sancho wrote:
This because the available inline-progression-dimension (i-p-d) is
reduced by the margin-left (or right), then your image size is reduced
both in width and height (since you set scaling=uniform, IIRC).
What FOP handles very well
Hi,
In XSL-FO, in default context, height specifies the
block-progression-dimension
reading the XSL-FO spec (see §7.15.3 at [1]):
b-p-d expressed in % is calculated with respect to the corresponding
dimension of the closest area ancestor that was generated by a
block-level formatting object,
Hi Pete,
I get expected behaviour when I transform your FO against either FOP 1.0
or FOP trunk.
But your PDF doesn't bahave as mine does.
- did you build your FOP against recent SVN export?
There is something wrong in your FOP env, FOP conf, ...
Le 03/11/2011 08:48, Peder a écrit :
Hi
Le 01/11/2011 03:29, Todd Hivnor a écrit :
I'm upgrading from FOP v0.20 to v1.0. My fixed sized tables are coming out a
different sized than before. I'm confused about why.
In the code below, I have a table-row with height=100px. The table-cells have
20px of padding. I end up using
Hi,
Please, do not mix 2 topics in one thread, that help users to retrieve
relevant info in archives.
That said:
assuming your rarr; is declared in a DTD, you have to set a
font-family that contains such glyph, even when in one of Base-14 fonts.
Le 28/10/2011 11:17, Jeffrey Walton a écrit :
Can you check if you have downloaded FOP sources?
this file comes with sources, but not with binary release.
Le 28/10/2011 11:17, Jeffrey Walton a écrit :
Hi All,
My XML source is using rarr; for a right arrow. FOP renders # instead
of the symbol in a PDF using the Apache FO stylesheet. I
Jeff,
Le 28/10/2011 12:57, Jeffrey Walton a écrit :
On Fri, Oct 28, 2011 at 5:59 AM, Pascal Sancho pascal.san...@takoma.fr
wrote:
Hi,
Please, do not mix 2 topics in one thread, that help users to retrieve
relevant info in archives.
Sorry, I don't understand what you meant. Rendering rarr
AM, Pascal Sancho pascal.san...@takoma.fr
wrote:
Can you check if you have downloaded FOP sources?
this file comes with sources, but not with binary release.
Yes, I downloaded the sources from a mirror listed on the Apache
download mirror page:
http://apache.cs.utah.edu/xmlgraphics/fop/source
Hi,
see below...
Le 26/10/2011 15:16, Heiko a écrit :
Hi,
I use FOP 1.0 inside an Eclipse RCP client to generate different pdf
reports.
Inside my xslt file, I have lines like:
fo:block font-family=Arial Narrow font-size=14pt
font-style=normal font-weight=bolder padding-bottom=18pt
Hi,
AFAIK, those lib are not required to build FOP. Typically, they are for
FOP dev usage.
using ant, you can avoid to launch the test suite, by typing in:
ant package
(or ant clean package if needed.
for further FOP ant options, type in: ant -p.
see [1] for further details
[1]
Hi Mark,
font metrics purpose is only when you don't want to embed a font in PDF.
this makes sense with widely distributed fonts, that usually carry a
little set of glyphes.
For embedded fonts, as said Mehdi, this feature is deprecated.
See [1].
That said, it remains possible that you are
Hi Christian,
Le 05/10/2011 20:11, Christian Grobmeier a écrit :
Hello Pascal,
On Wed, Oct 5, 2011 at 9:16 AM, Pascal Sancho pascal.san...@takoma.fr wrote:
Hi Sergiu,
it was me (Christian) who asked, Sergiu helped me :-)
Oups, sorry for that misreading.
can you provide a (short) XSL-FO
Hi,
FOP 0.20.x was known to have block-progression-dimension issues, and
sometimes the body content could overlap (below) the after-region.
A workaround consists in increasing the body margin-bottom until the
overlap disappears.
That said, the best action should to upgrade FOP to a recent
Hi Jing,
this depends on what quality you expect and on image subject.
for photography scene, jpeg or png-24 (= png true colors) is a good
choice, you can adjust the compression as you want (better compression
gives lower quality)
for schema, or large pictures with uniform color areas, svg can
Hi Thiago,
what you need is scale-down-to-fit (that exists and FOP implements it,
see [1] ;) ).
[1] http://www.w3.org/TR/xsl/#content-width
Le 22/09/2011 06:41, Sergiu Dumitriu a écrit :
On 09/21/2011 10:45 PM, ThiagoHP wrote:
Hi!
FO and Apache FOP newbie here. :)
I need to include
Hi Mike,
body.font.family and symbol.font.family are docbook specific parameters.
FOP does only handle XSL-FO, i.e. what is output by docbook XSLT.
That said, FOP 0.93 is quite old today, and font handling had been
strongly improved since that version: FOP 1.0 implements a basic
Hi Theresa,
one way to crop an image is to carry it within a svg snippet:
fo:instream-foreign-object width=100% height=100%
content-width=scale-to-fit content-height=scale-to-fit
svg xmlns=http://www.w3.org/2000/svg;
xmlns:xlink=http://www.w3.org/1999/xlink;
width=50mm
Hi,
fop1.extensions is a param for docbook XSLT, and this should be
documented in docbook matereial, not FOP material.
Le 13/09/2011 10:33, mike 675 a écrit :
Thanks, Pascal.
I asked on docbook-apps and they sent me here!
Pascal Sancho wrote:
Hi,
this is a docbook feature: see [1
Hi,
this is a docbook feature: see [1];
so, you should ask on docbook list [2] if this FOP extension is
supported by docbook XSLT.
[1]
http://docbook.sourceforge.net/release/xsl/1.75.1/doc/fo/fop1.extensions.html
[2] http://www.docbook.org/guidelines
Le 12/09/2011 12:30, mike 675 a écrit :
Hi theresa,
#195;#169; is an UTF-8 sequence (0xC3 0xA9) that encode EACUTE as UTF-8;
#239;#187;#191; is an UTF-8 sequence (0xEF 0xBB 0xBB) that encode The
BOM as UTF-8 (this is the UTF-8 signature);
You should have a look on how char encoding is handled in your app, it
that seems to be an issue
Hi Everson,
FOP 0.2x is an old design, and getting info about it is quite difficult
today, because it is no longer maintained, and FOP Web site doesn't
carry such info for a long time.
If you get no answer on this list, you can dive into the old source or
documentation at [1].
Note that the
Hi Eric,
Le 31/08/2011 14:36, Eric Douglas a écrit :
XSLFO is what you get when you combine XSLT with XML.
This is incomplete:
XML+XSLT can give (via xsl:output/@method attribute):
- XML (among what XSL-FO is, but not only)
- HTML (a SGML DTD)
- TEXT
XSLFO is an extension of XSLT and
Hi,
as you said, XSL is separated in 2 things:
- XML transformation (namespace http://www.w3.org/1999/XSL/Transform)
- Formating objects (namespace http://www.w3.org/1999/XSL/Format)
using the same name for this 2 separate things is quite unclear, so in
FOP lists we speak about either XSLT
Hi Louisa,
You need to insert ZWSP char (#x200b;) where you expect a line break.
This will add a break opportunity in your text line.
Le 02/08/2011 17:36, Louisa M a écrit :
Hi All, and sorry for my english,
I generate PDF with XML, XSLT and Apache-FOP. The text-content for this PDF,
is
Hi,
FOP-core input is XSL-FO and XSL-FO needs URI to carry images.
you have many options to feed XSL-FO:
- URL to a temp file that contains image data;
- URL to a script that carries image data;
- URI that encodes image data as base64 encoding.
- etc.
How image data is retrieved from DB is
Louis,
you can add the ZWSP at XSLT stage, before and/or after each Japanese glyph.
You can do that in a pure XSLT recursive loop, or using an embedded
script (technology will depend on what XSLT engine you use).
Le 03/08/2011 11:54, Louisa M a écrit :
thanks Pascal,
but how I insert this
Hi Bogusław,
#133; is the [next line] control character. It should not be used as
this in FO to PDF.
Rather, you should try Barcode4J, wich is designed to extend FOP in
barcode generation:
http://barcode4j.sourceforge.net/index.html
Le 18/07/2011 14:38, Bogusław Fries a écrit :
Sorry, once
Hi Swetha,
FOP 1.0 is more strict than FOP 0.2x regarding the XSL-FO REC 1.1.
Probably you will experiment further ValidationExceptions against FO
elements or attributes (missing %block% in fo:table-cell is the most
popular).
The best way is to rewrite your XSL-T to produce strict XSL-FO.
But
Hi,
Usually, the blank before and after an image are because of half-leading.
You can set them to 0 by explicitly setting font-height to 0 (and
line-height also, but since it defaults to 1.2, you don't need to change
it unless you have explicitely set it to a value other than a ratio,
i.e. unit
Hi Rob Oscar,
I'm not sure that the initial topic of this thread is still on
discussion (see Subject).
Please, if it is the case, don't hack an existing one, but open a new
thread with the right Subject, to avoid confusion for other users.
Le 22/06/2011 18:49, Rob Sargent a écrit :
It's a
Hi Gaetan,
I've successful tried the Ssarp letter.
IMO, this is not the initial cause: see the previous error message in
your log:
(...) at org.apache.xalan.transformer.TransformerImpl.executeChildTemplates
(...)
You should have a look in the XSLT processing, Xalan throwing an
Exception there.
Hmm,
Sorry, I didn't read the bottom of your message: fop version 0.95
Reproduced with that FOP version (0.95),
But works fine with FOP 1.0
Le 22/06/2011 09:38, Pascal Sancho a écrit :
Hi Gaetan,
I've successful tried the Ssarp letter.
IMO, this is not the initial cause: see the previous
Theresa,
as I said before, you can simplify your FO code with a single
fo:block-container:
fo:block-container
absolute-position=absolute
height=151.581mm
display-align=after
fo:block*Small print to be added here/fo:block
/fo:block-container
IIRC, you are upgrading from FOP 0.2x to
Theresa,
With FOP 1.0, you can use either fo:table construction or
fo:block-container, both gives normal behavior and text is displayed at
bottom of the surrounding fo:block-container.
Note that (as Andreas aid) the height attribute have no effect on
fo:table; you have to set it on fo:table-row.
Hi,
2 options for the absolute-position property can be usefull to place an
area:
- absolute: offsets with respect to nearest ancestor reference area
(block-container is one)
- fixed: fixes with respect to the page (in case of pagined medium).
Try this:
?xml version=1.0 encoding=UTF-8?
Hi Theresa,
FOP 0.2x TTFReader was buggy.
You can try to generate metrics files using a TTFReader that comes with
a recent FOP version. Such metrics files should work with older FOP
versions.
I don't remember if FOP 0.2x metrics generation proceeded in the same
way as current FOP version. See
Hi Eric,
#151; (AKA #x97;) is the control code for [EPA] (END OF GUARDED AREA).
(While in Windows Codepage 1252 this is the code for Dash).
With unicode encoding (like UTF-8), you should use the code #x2014; (EM
dash) or #x2014; (EN dash).
I don't remember if this character is handled with ISO
Hi Eric,
After a page-break, there is a new reference-area. For a block at the
beginning of the reference-area, the space-before is taken into account
if the space-before.conditionality property is set to 'retain' (see XSL
REC 1.1, $4.3 at [1]).
And this property default to 'discard' (see $7.11.5
Hi Theresa,
perhaps this link can help you:
http://xmlgraphics.apache.org/fop/1.0/fonts.html#font-list
Le 11/05/2011 10:16, Theresa Jayne Forster a écrit :
I am slowly getting through this minefield,
For the AutoReg fonts, how do we determine the names to use in the XML
I have been
Hi,
If your '' data don't contain any spaces, you can imagine a XSLT
that replace your string with a fo:table, since you have both line
separator(#xa;) and cell separator (last space before ''). XSLT
gurus will help you for that.
If not, uou have to ensure that the used font is a
Hi Alessio,
I realize that you didn't get any answer...
You should get the image height.
From this, you can easisly calculate a ceiling value, multiple of
line-height, to set the fo:external-graphic height property.
In addition, you should ensure that your half leading (space before and
after
Hi Kristina,
unlike FOP 1.x, FOP 0.2x was buggy on this topic, so it cannot be used
as reference.
You can check this: write 10 lines with known line-height and measure
the result: you don' get a 10x value with FOP 0.2x.
This result is not predictible, so you cannot mimic exactly the v0.2x
Hi Bas,
FOP currently doesn't support non-latin scripts.
Fortunately, Glenn Adams is working on this topic and has made a great job.
You can download sources from various locations (you'll have to build
FOP yourself):
- complex scripts FOP branch:
of?
Kind regards,
Bas van den Broek
-Original Message-
From: Pascal Sancho [mailto:pascal.san...@takoma.fr]
Sent: Thursday, May 05, 2011 11:30
To: fop-users@xmlgraphics.apache.org
Subject: Re: Arabic text being 'transformed' into something that looks Arabic
but is not exactly
Hi Marcos,
As you read the trace, this is not directly related to FOP (FOP
delegates the XSLT stage to Xalan).
You should have a look into your XSLT, probably an infinite loop nested
somewhere.
Note that better list for XSLT related questions can be found (see [1])
That said, you should
Hi Bruce,
Le 04/05/2011 12:12, Bruce Wen a écrit :
Hi Friends,
Could you please share the experience to generate bookmarks in PDF file?
Just like the attached snapshot.
This is what [Formatting Objects for Bookmarks] do (see XSL-FO $6.11 at
[1]).
See also FOP compliance page (at [2]), there
Hi,
There is no mechanism to reduce graphic size in FOP.
You have to optimize it before running FOP.
You should find tools that can resample bitmap images in a batch process.
Le 02/05/2011 17:12, Roberto Cahanap a écrit :
Hello fop users!
Is there a way in FOP to reduce the size of the PDF?
What FOP version do you use?
until FOP 0.94 (IIRC), color profile was systematically included in PDF.
Now, when sRGB profile is used, it is not embedded in PDF. Removing
color profile will reduce PDF size.
Le 03/05/2011 09:09, Pascal Sancho a écrit :
Hi,
There is no mechanism to reduce
Hi,
SVG uses sytem font (because rendered via AWT), while FOP uses
explicitely specified fonts (in conf file) for PDF rendering.
To ensure that text in SVG uses a specific font, this font must be
declared both in system font system and in FOP conf file (with the same
name, of course).
Le
Hi,
in short, there is leading space between 2 lines, half leading before
and half leading after.
This leading is based on both font-size and line-height.
You have to ensure that both properties are set to 0 to have a null leading.
Since line-height defaults to 1.2 (IOW: 1.2*font-size), you
Hi,
Relative font path works for me on embed-url attribute (Windows + JDK
6.0.20), whatever FOP version (0.95, 1.0, or TRUNK):
Either on my dev machine (invoking FOP via CLI):
snip
font-basefile:///D:/fonts/font-base
font kerning=yes embed-url=dejavu/DejaVuSans.ttf.../font
/snip
Or in
Hi Ulrich,
I have no solution, only questions:
- Are the 2 FOP versions run on the same host?
- What OS do you experiment?
- Have you tried direct access to /path/to/fonts + / + myfont.ttf
(either with ls or dir) ?
- Does FOP 1.0 load the right fop.xconf file, if any?
Le 13/04/2011 16:29,
Hi Mario,
You have to change your fox:crop-box to 'media-box' (see [1]).
FYI fox:crop-box possible values are:
- media-box (area containing cropmarks)
- bleed-box (area containing bleeds)
- trim-box (default, area remaining after crop)
[1]
Oops, I've don't read that...
You have to draw it yourself...
I've attached an XSLT file to make it.
You can use it as is, or tune it as you want.
Le 31/03/2011 17:00, Mario Madunic a écrit :
I've played with various values and when cop-box is set to trim-box the page
displayed is the actual
Hi,
This is a pure XSL-FO question, not a FOP related one.
That said,
IIUC, you want to have lateral margins on your fo:region-body.
Therefore, you need to specify margin-left and margin-right on your
fo:region-body.
extend properties do not affect the body region.
Le 17/02/2011 11:36, Jens
Hi,
FOP seems to be wrong here when a marker is used twice.
As a workaround, you can insert an ZWNJ (#x200b;) before the
fo:retreive-marker, that should do the trick (see attached FO snippet).
Can you fill in a new bug entry, with snippet as attachment, please?
(see [1]).
[1]
Hi,
What you need here is the relative-align property, witch is
unfortunately not yet supported by FOP (see [1] [2]).
As a work-around, you can add a space-before property on the 1st element
of the list-item-body, with the .conditionality set to 'retain'
[1]
Hi,
You should check your printer settings:
did you uncheck the [scale to print] option?
Le 06/12/2010 22:13, joe armstrong a écrit :
I'm trying to understand page layouts in apache fop. I have set a page width
of 21 cm and margin-left + margin-right to 5 cm, so I should get 16 cm of
content.
Hi,
you can insert a ZWSP (zero width space, #x200b;) between characters
you want a possible break.
Le 23/11/2010 08:30, Alexander Uvarov a écrit :
How to hyphenate nonwords? For example i have serial number ZZ10-SX70-BBQZA
in a table cell. Serial might be in any language. Table cell is small
Hi,
I see 2 distinct issues:
- spaces between pictures:
spaces between XSL elements are kept in rendered PDF.
you can easily avoid them by removing from XSL-FO code.
This is a normal behavior.
- breaks at space between 2 pictures:
That should not occur since there is a
Hi,
you have such warning because:
- both Symbol and ZapfDingbats fonts are only provided in regular form;
- Since FOP 1.0 implement font-selection, all 14 base fonts are set by
default, comprising Symbol and ZapfDingbats fonts
- you use elsewhere a font-weight property with 'bold'
To avoid
Hi,
I guess you describe what you see in (probably Adobe) PDF viewer.
FOP resolution is 1 milipoint (1/72000), so, appearance can depend on
actual border geometrics (location, width and height) on screen pixel
grid (usual resolution: 1/96, 750x less precise than FOP's one), and
depends on PDF
201 - 300 of 673 matches
Mail list logo
