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,
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(
) 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 monospace o
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
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
behavio
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 i
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 provide
you know 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 '
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:
https://svn.apache.org/repos/asf/xmlgraphics/fop
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]), th
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
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 PD
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 20/04/20
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 jus
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):
file:///D:/fonts
...
Or in production env (WinServer + JRE5 + Jboss):
- same font element in fop.xconf,
- but font-b
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 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 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] http://xmlgraphics.apache.org/fop/1.0/extensions.html
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 Jahnk
Hi,
FOP seems to be wrong here when a marker is used twice.
As a workaround, you can insert an ZWNJ () 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] http://xmlgraphics.apache
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]
http://xmlgraphics.apache.org/fop/com
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
> conten
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 keep-together
Hi,
you can insert a ZWSP (zero width space, ) 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 and
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 suc
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 vi
Hi,
There is a Patch for that topic.
See: https://issues.apache.org/bugzilla/show_bug.cgi?id=48548
--
Pascal
Le 04/10/2010 10:09, Georg Datterl a écrit :
> Hi Fredrik,
>
> I know somebody (Alex?) was working on that some time ago, but I haven’t
> heard about it lately. Check the list archive fo
Hi Daniel,
for such need, the only required thing is fonts containing scripts and
diacritics.
Either you find 1 font that contains *all* glyphes,
Or you use a set of fonts to cover all your need.
in the latter case, you should use FOP 1.0 rather than previous version
(multiple font selection).
A
Hi,
you can add an empty table-foot with a border-top on each cell, that
should do the trick.
Pascal
Le 28/09/2010 21:11, Anil Pinto a écrit :
> Hello,
>
> We have been using FOP in our solution for quite a few years now and are
> very pleased with the product!
>
> I have a question pertaini
Hi,
I vaguely remember such issue, but I'm not sure at all;
try a blank border, sometimes that gave good results.
Pascal
Le 18/09/2010 07:27, Craig Ringer a écrit :
> On 17/09/2010 6:43 PM, Ancient wrote:
>> Hi!
>>
>> I have a huge problem right-aligning text. We have a server with fop 0.20.5.
>
t;
> On Wednesday, September 15, 2010 10:08:29 am Alexey Neyman wrote:
>> Hi Pascal,
>>
>> Just tried. While there is no exception,
>> still does not work in FOP 1.0 (still no effect whatsoever). See quoted
>> email as to why is not sufficient to solve
>> th
t; org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown
>
> Source)
> at
> org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown
> Source)
> at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
> at org.apache.xe
Hi,
I think the behaviour is correct here:
Cells height is not sufficient to see the effect you want.
try to increase the height of vertically spanned cells (by setting the
height property to 2em) and you will see what I mean.
Pascal
Le 13/09/2010 22:39, Alexey Neyman a écrit :
>bord
Hi,
I tried both OFFO 1.2 and utf-8 0.1 with a copy of the text nested in
the Matthias"s PNG, and I get the same output as described. So, I guess
there is no change for the Polish between the 2 versions
--
Pascal
Le 10/09/2010 14:42, Simon Pepping a écrit :
> On Thu, Sep 09, 2010 at 07:08:45PM -0
Le 08/09/2010 07:56, Antti Karanta a écrit :
> On Mon, 30 Aug 2010 18:31:18 +0300, Pascal Sancho
> wrote:
>> '#' indicates that the glyph is not available in any font used by FOP.
>> Note that SVG uses the fonts installed in the system, while FOP needs
>?? I
irst item there is space between ō and comma (,).
> please note that there is no space in XML and HTML for this still the issues
> is generating in PDF.
>
> Please let me know where i am going wrong with the xsl part.
>
> Regards
> Anand
>
>
> Pascal Sancho wrote:
>>
ound.
> I changed it to a unicode character which is in the font and I get that
> character with 0.95. That same code in 1.0 is producing a # and not getting
> the glyph not found message.
>
>
> -Original Message-
> From: Pascal Sancho [mailto:pascal.san...@takoma.fr]
&
e message in
> the console about not finding the glyph?
>
> ----
> *From:* Pascal Sancho [mailto:pascal.san...@takoma.fr]
> *Sent:* Monday, August 30, 2010 11:37 AM
> *To:* fop-users@xmlgraphics.apache.org
> *Su
Hi,
On my WinXP, the LTYPE.TTF (AKA "Lucida Sans Typewriter") doesn't
contain the glyph for \u25A1.
You should try another font.
--
Pascal
Le 18/08/2010 21:04, Eric Douglas a écrit :
>
> I'm trying to print a character to a PDF as □ which is supposed
> to be a square and it's printing a # characte
Hi,
'#' indicates that the glyph is not available in any font used by FOP.
Note that SVG uses the fonts installed in the system, while FOP needs
that used fonts are set in config file (if you use a non standard font).
So, you have to ensure that the fonts used in SVG are both declared in
your syst
Hi Spyros,
"auto" is the initial value for the table-layout property.
While it is not supported by FOP, you'll get this warning if you don't
explicitly set the property table-layout to "fixed"
--
Pascal
Le 02/08/2010 17:13, Spyros Papantoniou a écrit :
> Any ideas why table-layout="auto" [that is
Spyros,
we cannot verify the font your are using (due to licence protection).
Can you check your job with a well known and widely available font that
contains greek glyphes (one cited by Jeremias, or one of DejaVu collection).
If OK, dthe DINRg is probably faulty.
If not OK, can you provide a short
Hi Alexey,
some issues have been reported about area tree when fo:inline is used.
That can interact with keeps management.
You should rise a bug and attach your test case (see [1]).
[1] http://xmlgraphics.apache.org/fop/bugs.html#issues_new
--
Pascal
Le 24/07/2010 09:41, Alexey Neyman a écrit
Hi Akagi,
You should ask Docbook related question on Docbook list (see [1]).
Ideally, on FOP user list you should ask questions that come *after* the
XSLT transformation, and you should provide short XSL-FO snippet to arg
your question.
[1] http://www.docbook.org/guidelines
Pascal
Le 20/07/2010
>
>
>
>
>
>
>
>
>font-size="10pt"> select="."/>
>
>
>
>
>
>
>
No, it's a FOP bug;
I just gave a workaround solution, if applicable.
Pascal
Le 19/07/2010 14:24, Tom Browder a écrit :
> On Mon, Jul 19, 2010 at 03:12, Pascal Sancho wrote:
>
>> Hi Tom,
>>
>> I dove into your XSLFO, and found that the issue is related to
>&g
Hi Adam,
the solution can follow the 2 steps:
1- In your 2nd page master, the fo:flow should be to small to contain
anything and make the content to shift to 3rd page
2- your fo:page-sequence-master should content something like that:
Pascal
Le 16/07/2010 15:09, Adam
Hi Tom,
I dove into your XSLFO, and found that the issue is related to
space-before.maximum within list-block.
I rewrote (and shortened) your testcase (see your bug entry [1]).
Removing space-before.maximum properties within block-list makes the
issue desappear.
[1] https://issues.apache.org/bugz
Hi Anand,
can you provide a *short* XSLFO snippet that shows what you describe,
please?
Pascal
Le 14/07/2010 13:34, Anand Gade a écrit :
> i ama generating PDF output using Apache FOP. There are Japanese characters
> present. I am able to render these character in PDF by using MS Mincho font
> an
Hi Asitha,
following snippet should give you wished result:
Pascal
Le 16/07/2010 08:11, asitha w a écrit :
> Hi Everyone,
>
> Is There any way to achieve Soft page-breaks in fop 0.20.5, some thing
> similar to " " in
> the later fop version. any workarounds any one attempted.
>
> Than
Hi,
line-height-stretch is not a valid XSL-FO property, but seems to be a
RTF2FO configuration property.
You should visit RTF2FO site or googlize for line-height-stretch, this
list is only for FOP usage.
Note that XSL-FO line-height defaults to 1.2, but you can change this by
specifying line-heig
Hi,
what you need is xsl:param instead of xsl:variable. the syntax is the
same for both elements.
Note that this list is for FOP usage; to ask XSLT questions, the list
cited in [1] is more relevant.
[1] http://mulberrytech.com/xsl/xsl-list/
Pascal
Le 12/07/2010 11:47, Red Light a écrit :
> Hi,
>
Sushanth,
without a clean XSL-FO snippet, we only can provide you 'hypothetic'
solutions.
a possible solution should be using the 2 Fop extensions
fox:orphan-content-limit and fox:widow-content-limit.
Read [1] for further details.
[1]
http://xmlgraphics.apache.org/fop/0.95/extensions.html#widow-or
Hi Julian,
You are right, Fop 0.95 does a more precise job, while Fop 0.2x was
buggy in computing block-progression-dimensions.
You can easily check that by measuring 10 text lines on a Pdf print
(with a 1:1 print ratio and using an easy-to-use font-size/line-height
couple).
Pascal
Le 02/07/2010
Hi Eric,
Fop changes details is here:
http://xmlgraphics.apache.org/fop/changes.html#version_FOP%20Trunk
--
Pascal
Le 30/06/2010 15:52, Eric Douglas a écrit :
> What sort of features are in the Trunk which are not in 0.95? I didn't see
> anything like a What's New document.
>
-
Hi Craig,
With the Fop trunk version, you can produce either the new IF file (the
default), or the old AT file. The IF page [1] should give you further
information.
[1] http://xmlgraphics.apache.org/fop/trunk/intermediate.html
--
Pascal
Le 28/06/2010 02:51, Craig Ringer a écrit :
> Hi
>
> I'm l
Hi Tom,
Fop doesn't provide any default bullet by itself. I guess you are using
an XML + XSLT couple to feed Fop, in this case this is the XSLT job. You
have to thake a look closer in your XSLT.
--
Pascal
Le 26/06/2010 19:08, Tom Browder a écrit :
> On Sat, Jun 26, 2010 at 12:05, Tom Browder wr
Hi Craig,
reproduced with this shrinked XSL-FO snippet:
http://www.w3.org/1999/XSL/Format";>
This seems to be related to double wrapper nested in another wrapper.
As a workaround, you c
Hi,
This is related to empty inline with ID (see bug [1]).
your XS-FO can be shrinked to this and shows always the issue:
Definition: This is def #1
(note the space immediately after the inline with ID).
When removing the space (xml-space: ( lf | space | cr | tab ) ) between
inline and text-nod
Hi Giuseppe,
that is a good new! and you are welcome.
You can contribute initially by writing patches (see [1]), that is the
most common way for an initial contribution.
IIUC, you are ready to help on index implementation ([2]: REC 1.1 § 6.10).
I don't know if somebody in the dev team have some t
Hi Giuseppe,
1. no;
2. no, but any help is welcome to help in implementation of such
feature; FOP is open source!
3 yes: using a 2 pass XSLT (no format here, but you can apply your own):
my text with an indexed word.
:
Hi,
you can draw a solid rectangle on many ways:
empty b-c:
resized e-g:
using svg:
http://www.w3.org/2000/svg";
width="6in" height="0.7in" viewBox="0 0 1 1">
HTH,
Pascal
Le 15/06/2010 21:06, Steffanina, Jeff a écrit :
>
> I have a fo
Hi,
That seems to be related to anti aliasing.
When zooming, the thickness variation disappears.
In Adobe reader, anti-aliasing can be disabled by unchecking the 2D
acceleration.
--
Pascal
Le 10/06/2010 16:31, aemitic a écrit :
> Hi all,
>
> I found that using the attribute number-column-spanned
stination) was
> fine, but a second would crash fop with an NPE. (I'm using 0.95).
> Experimenting I found that if I put something, anything, in the fo:block
> then the NPE went away - but then I had the alignment issue to deal with.
>
> Cheers
> T
>
> -
Hi Trevor,
you can use a simpler construction:
That should not generate any area (since empty blocks), so that should
do the trick.
Note that 'px' is not a recommended unit as it is relative to ... screen.
--
Pascal
Le 07/06/2010 19:46, Trevor Nicholls a écrit :
> Hi Georg
>
> Here is the fo f
Unfortunately, rounded borders are not yet implemented (or even
specified in a recommendation).
You can use table structure to decompose your surrounding rectangle.
Pascal
Le 04/06/2010 14:47, Brad Smith a écrit :
> Hello,
>
> I am experimenting with using rounded edges around boxes of text in my
Hi,
As said in FAQ (see [1]), '#' means that a character is not found in the
used font.
This can have multiple causes:
- FOP is not correctly configured to use the provided font and falls
back to default;
- the provided font doesn't contain any glyph corresponding to the
character;
- the provide
Hi,
what you describe here is not related to any FOP limitation.
FOP job begins *after* XML transformation, the latter being delegated to
Xalan in FOP releases.
You will probably get more help on XSLT forum (see[1]).
That said, you can get some help on this list if you provide the
resulting XSL-F
According to [1]:
uni0F620F90 is a mix of uni0F62 plus uni0F90, IOW:
RA plus SUBJOINED KA
and the other uni0F6A0F90 is a mix of uni0F6A plus uni0F90, IOW:
FIXED-FORM RA plus SUBJOINED KA
The latter shows no character shaping and should only be used for
transliteration or transcription.
Since cu
Reading back your initial message:
Character stacking seems to be correct in your PDF, the problem is
definitively the lake of character shaping.
--
Pascal
Le 02/06/2010 09:59, Pascal Sancho a écrit :
> Hi,
> After some googlezing:
> reading [1]
> ཀ is the consonant KA.
> IIUC, co
Hi,
After some googlezing:
reading [1]
ཀ is the consonant KA.
IIUC, consonants can be stacked; in this case, KA becomes the sujoined
consonant ྐ (AKA ྐ).
reading [2]
in addition, there can be a character shaping mechanism, probably as Arabic.
Unfortunately, FOP supports neither character stacking
Hi Brad,
what you need is an integer value for the keep-together.* property.
integer value is not supported by FOP 0.95, but FOP TRUNK has a minimal
support on it.
try it, it can give you expected result.
--
Pascal
Le 25/05/2010 21:02, Brad Smith a écrit :
> Hello,
>
> I have certain elements in
Hi,
For FOP usage related questions, please ask to FOP-users list, witch is
more appropriate.
That said, you are facing to 2 separate topics:
1/ XML to XST-FO transformation stage: produced XML contains XML
entities rather than characters, witch gives a hard to read file for a
human being.
This qu
FOP behaves correctly on both 32 and 64bits JVM.
You should check if the application embedding FOP is x64 compatible (we
run FOP under Jboss, and there are 2 versions of Jboss: 32 bits Vs 64bits).
Pascal
bonekrusher a écrit :
> Thanks for the help. I have verified that the machine which is having
Hi,
IIUC, there is some complex shaping mechanism to render Devanagari
script (see [1]).
Unfortunately, FOP only supports simple character shaping (like latin
script).
I don't know if somebody has sufficient knowledge in FOP team, so help
is welcome.
Note that there is similar issue for Arabic, and
Hi Mario,
can you fill in a bug related to FOP documentation, please, in order to
keep track of that?
Thx,
Pascal
Mario Madunic a écrit :
> Thanks Venkat for looking into this for me.
>
> Maybe the compliance page needs a bit of updating (when someone has a moment)
> to state that @external-des
Hi,
Like other processors, FOP behaves correctly here, and produces similar PDF.
Non blank characters are drown at the right place on the sheet while
consecutive white-spaces are replaced with 1 white-space in copy-paste
operations.
IMHO, this is either a PDF 1.4 feature, or an Adobe-viewer speci
Hi,
This list is for FOP usage. You should ask XSLT questions on the right
list (see [1]).
That said, you cannot use a variable for such call.
Instead, you should try a xls:choose strucure:
[1] http://www.mulberrytech.com/xsl/xsl-list
Pascal
Red Light a écrit :
> Hi ,
>
> I wa
.95 with XML files and an XSL file. As far as I know it never
> generates a physical XSLFO file.
> How do you get an XSLFO file?
>
>
> -Original Message-
> From: Pascal Sancho [mailto:pascal.san...@takoma.fr]
> Hi,
> IIUC, the error occurs at the XSLT sta
Hi,
FOP 0.9x is very strict regarding the XSL-FO rec 1.1, while FOP 0.20.x
was lax.
So, you have to fight all validations issues to get a clean, strict XSL-FO.
Typically, you have to rewrite a consistent part of your XSLT when
upgrading from FOP0.20.x to FOP 0.9x.
In the case you reported, the er
Hi,
IIUC, the error occurs at the XSLT stage.
- you should give further information on the context (XSLT engine and
version, JRE, sources files, etc.), not only the error message.
- note that on this list, the best material is the XSL-FO source, not
the XML+XLST.
Pascal
GangadharAthi a écrit :
Hi,
This is a pure XSLT question.
you should ask it directly on the XSLT list:
http://www.mulberrytech.com/xsl/xsl-list
Pascal
maxmus a écrit :
> Hi,
> I have the following situation:
> I translate an XML datasource to PDF using an XSL stylesheet and FOP 0.95 .
> I can not pause the process, e.g
Hi,
reading back the 0.20.5 doc (graphic page at [1]), the FOP resolution
(1/72") cannot be changed by conf.
You have to explicitly give the actual size of the image within the
fo:external-graphic tag.
Note: IIRC, for background-image property, there is no way to set
another resolution.
[1]
http
Hi,
did you try a solution mixing page-sequence-master odd/even with a
fo:marker that comes at the end of the fo:flow?
that should do the trick, but I didn't tried it.
--
Pascal
bonekrusher a écrit :
> Hi,
>
> How can I set up my repeatable-page-master-alternatives to detect a page
> sequence tha
Mario,
can you provide a (short) XSL-FO snippet, including the SVG file, that
reproduce the issue?
Pascal
Mario Madunic a écrit :
> Pascal,
>
> Here is a copy of the various paths tried and the fo produced
>
> (...)
>
> And without the url() in the instances without a single quote.
>
> If this i
raphics/numericIndexPage.svg failed 0.94 as expected
> ../../../graphics/numericIndexPage.svg failed 0.94 as expected
>
> Marijan (Mario) Madunic
> Publishing Specialist
> New Flyer Industries
>
> -Original Message-
> From: Pascal Sancho [mailto:pascal.san...@takoma.fr
Hi Ismail,
FOP 0.20.x is very old now, but IIRC, the metrics tool provided with
this version could give buggy metrics files with some fonts. You should
try to generate metrics files using a recent FOP release (in this way,
you don't need to upgrade FOP 0.2x to 0.9x, just run it side by side).
See
Hi Alessandro,
You can get further information reading these pages:
http://xmlgraphics.apache.org/fop/dev/extensions.html
http://wiki.apache.org/xmlgraphics-fop/ExtensionsForPdf
Pascal
Alessandro Marino a écrit :
> I would like to extend FOP to provide custom xsl tags to insert annots
> fields i
Hi Arian,
Batik uses the system fonts, therefore, to use custom fonts in an
embedded SVG, you have to get your custom font available both on your
system AND in FOP configuration.
Pascal
Arian a écrit :
> Im curious Can this apply to fonts that are custom to fop? Like
> will your svg:text code
Hi Mario,
This should work. I suspect that the relative URL is the cause of your
trouble. Can you check it with an absolute path?
Pascal
Mario Madunic a écrit :
> I was doing the following with FOP 0.94 while testing
>
> background-repeat="no-repeat" ../>
> And it would appear as a bg on the pa
As said in another thread of this list, FOP resolution is 1/72000 in.
So, no screen can offer such resolution, and human eyes can view
difference between 2 identical lines that are are not on the same
position on the screen grid.
however, in Adobe Viewer, there are some options to get better rende
Hi Jeandur,
like the Red Light's thread [table border-collapse="collapse" and
borders] in this list, the display is affected by the different
resolution between FOP (1/72000 in) and the screen (often 1/96 in).
Rigorously, you should zoom in with a 72000/96 factor to get exactly
what FOP produce (I
Hi,
FOP atomic measurement is the millipoint (1/72000 in), witch give a
precision highly beyond the screen one (often 1/96 in):
the line can be drawn riding 2 pixels width, while its actual width is
about 1 pixel, so its screen rendering can depend on its position on the
screen grid.
If you zoom i
adding a step in my ANT task to validate my FO output so
> I can see where I have made an error as to its structure, especially
> placement of attributes.
>
> Once again thanks Pascal. Your help is greatly appreciated.
>
> Marijan (Mario) Madunic
>
>
> -Original Me
Hi Mario,
The force-page-count property applies only to fo:page-sequence.
You can get whant you want by using the property initial-page-number on
your fo:page-sequence objects.
Note you may need a blank page in your alternative sets id FOP has to
insert some extra blank pages, I.E. between TOP and
Hi Matthias,
If the exception occurs only when the patch is applied, you should add
any comment and/or testcase (as attachment) directly to the bug entry.
Pascal
Matthias Reischenbacher a écrit :
> Hi,
>
> I think the changes introduced in FOP trunk by the patch of bugzilla
> entry #48071 are
n-null Positions
> with an index can be checked
>
>
> Are you able to produce a PDF from the FO that I sent without error?
> If so, what revision are you using?
>
> Thank you all for your help.
>
> Kind Regards,
>
> Gregory Buchenberger, CDIA+, ECMs
>
>
>
Hi Gregory,
I cannot reproduce the exception with that material.
Can you describe your environment (comprising jar coming with FOP) ?
What FOP SVN revision do you use?
When invoking FOP feeded with an XSL-FO, is there a file location in the
log:
if yes, that should help to retreive the faulty fo
/show_bug.cgi?id=47430
Pascal
Lalithc a écrit :
> Check the files in the the following URL's:
> http://old.nabble.com/file/p27854500/BILL.jpg BILL.jpg
> http://old.nabble.com/file/p27854500/test.fo test.fo
> http://old.nabble.com/file/p27854500/xyz.pdf xyz.pdf
>
>
> Pasca
Hi Arian,
reading the source code, fopFactory.setFontBaseURL() is actually
deprecated, and should be replaced in FOP TRUNK with:
fopFactory.getFontManager().setFontBaseURL().
Note that the font subsystem has been widely rewritten since FOP 0.94.
Pascal
Arian a écrit :
> I saw the page
> http:/
Hi Brad,
perhaps you can insert such symbol in a 2-steps approach, by editing the
Intermediate Format.
I never tried this however.
Pascal
Brad Smith a écrit :
> Is it possible to make it so lines that are broken within a block have
> some sort of graphic or character denoting the fact? For exam
301 - 400 of 787 matches
Mail list logo
