Hi,
That sounds like a bug.
Can you file in a new issue on Jira [1], please?
You should attach (not copy/paste) your test case as file.
[1] https://issues.apache.org/jira/browse/FOP
2013/8/28 Marc marc.li...@free.fr:
I discover a problem when the page layout is 2 columns, and an picture
Hi,
What you need is tu use a font that contains all glyphes you need.
Follow [1] to attach a new font to FOP.
The Dejavu font (opensource) [2] should be usefull.
[1] http://xmlgraphics.apache.org/fop/1.1/fonts.html#register
[2] http://dejavu-fonts.org/wiki/Main_Page
2013/8/28 Daniele Palladino
Hi,
you just need to set the property hyphenate to false.
http://www.w3.org/TR/xsl/#hyphenate
2013/8/5 Elena Fialkova efialk...@bioreference.com
How do you format a column so that it breaks ONLY on space. Currently,
it seems to have many rules to break a text in a column. For example, it
Hi,
I'm not sure there is a specific script for Vietnamese.
IIUC, this can be written either with latin script, or with a chinese
subset script.
Both Latin ans Chinese scripts are handled correctly with Fop, without
complex script feature. You should just feed FOP with an appropriate font.
Maybe
Hi,
ligature feature depends on font capabilities.
It comes with the complex script new feature added in FOP 1.1 (see [1]).
There is an (incomplete) list of fonts that support such feature (see [2]).
You can disable such behaviour in 2 ways:
- either disable the whole feature (see [3]),
- or
Hi,
Yes, FOP current supports border-collapse (separate|collapse values only,
see [1]),
while FOP v0.20.5 did not. The design of this old version was quite
different from the current one, regarding border painting.
The thread you cited is about the current (new) design, so it cannot apply
to FOP
Hi,
the 2nd image has following features:
dot size: 919x600 pixels
resolution: 44417x44417 DPI
true size: 0.0207x0.0135 IN²
and the content-height of the 2nd external-graphic is set to 100%,
witch means: 100% of the height of container,
the latter defaulting to 100% of the height of the content
Hi,
you should describe what do you feed to FOP, and, as a best practice,attach
some material, ideally an XSL-FO input file (rather than XML+XSLT), or
other input format handled by FOP (IF, AT, etc.)
2013/4/11 Bonekrusher djs...@yahoo.com
Running embedded code in trunk, I am getting the
Hi,
Behavior is related to xml blanks (white-space, line-feed, etc.) that are
before or after fo:inline tags.
You should avoid to use fo:inline when it is not required (replacing it
with fo:wrapper when it is just used as properties carrier), or avoid to
get extra blanks in your resulting
Hi,
Just for convenience, you should monitor the corresponding issue in Jira:
https://issues.apache.org/jira/browse/FOP-1760
Bugzilla Fop issues became read-only when we migrated them to Jira.
2013/3/10 Alexey Neyman sti...@att.net
Hi,
Are there any plans to implement change bars in FOP?
Hi,
You should file in a new JIRA entry, attaching your XSL-FO (do not
inclue it in comment) and both PDF outputs.
2013/3/1 Joseph Wright j...@otnb.com:
We currently use 0.95 for creating PDFs and are migrating to 1.1 as we
need some of the new features. We noticed one of our existing features
part.
Best regards
Markus
-Ursprüngliche Nachricht-
Von: Pascal Sancho [mailto:psancho@gmail.com]
Gesendet: Dienstag, 19. Februar 2013 16:53
Hi markus,
I'm not familiar with RTF, but I'm not sure that this format allows table to
be nested in list.
There are some limitation
Hi markus,
I'm not familiar with RTF, but I'm not sure that this format allows
table to be nested in list.
There are some limitation with such output.
2013/2/19 markus.sticker.e...@zf.com:
Sorry but it seems that the rtf is empty.
Von: Sticker Markus EXT FRD EPOS
Gesendet: Dienstag, 19.
Hi,
mixing elastic space-* with keep-with-next reveals a fop bug.
You should report this issue in Jira, attaching both test case (FO)
and result (PDF).
Notes:
- I get the same result with either keep-with-next or k-w-n.within-line
- k-w-n.within-line shouldn't be taken into account on
Hi Markus,
you can insert a ZWSP (#x200b;) everywhere you want a break opportunity.
This is a best practice when there is no matching hyphenation pattern.
2013/1/22 markus.sticker.e...@zf.com:
Hi,
I did some tests with different sources. The “_” is working very well. But
I’ve got an issue
Hi,
You should have a look to [1] fop output formats
there is a -tiff option on command line interface.
The TIFF section [2] gives further info about TIFF configuration.
[1] http://xmlgraphics.apache.org/fop/1.1/output.html
[2] http://xmlgraphics.apache.org/fop/1.1/output.html#bitmap
2013/1/18
Hi,
can you attach your file, rather than copy/paste it?
that will allow one to test it easily.
2013/1/18 nels nbhc...@gmail.com:
Glenn Adams-2 wrote
If you want to use strict mode using the command line interface, then you
need to use the FOP configuration file to specify strict validation
Hi,
tables are good for data grids, but you can use alternate solution in
many cases.
Example 1: Border can apply to many FOs, so you don't need to use table here.
Example 2: title starting with graphic symbol:
table solution needs a complete table structure:
Hi,
Yes:
FOP uses BATIK to render SVG, witch uses system fonts to render SVG text.
And
FOP uses fop.xconf to embed fonts in PDF.
So you need to declare fonts for SVG in both system and FOP config.
2012/12/21 Alexey Neyman sti...@att.net:
Are you saying that the font used in SVG needs to be
Hi,
simply using the font-family attribute on the fo:root element.
Note that all inherited properties can be set on fo:root element, so
you can set your own default properties there, including font-family.
2012/12/20 Stefan Hinz stefan.h...@oracle.com:
Hi Bernardo,
That's good advice,
Hi,
FOP doesn't provide such feature, whatever the version.
Just for curiosity: what do you aim to do with resulting fo?
2012/12/6 sareth gwen89pe...@hotmail.com:
hello, I currently use FOP 0.95 and I would like to know if it's possible to
convert RTF to FO with pictures ?
I found two tools
Hi,
there are some issues related to page-number-citation in right-to-left
mode in conjunction with align right.
See [1].
[1] https://issues.apache.org/bugzilla/show_bug.cgi?id=54139
2012/11/27 Ryan Fong ryan.f...@workday.com:
G'day, mates. This is a follow-up message to one I posted a couple
Hi,
all config material for text/plain had been removed from FOP in rev
829767 (oct 2009, 26th).
So, there is no documented option configuration for that MIME type.
Recommended settings (FOP website, @ [1]) should be applied directly
in XSL-FO, on fo:root.
[1]
Hi,
according to XSL-FO REC 1.1 (§7.27.3 at [1]), percentage is a legal
value for column-gap, regarding the i-p-d of the region (in your case:
20in*5% = 1in is expected, FOP giving 0).
So, you should file in a bug entry on bugzilla, attaching a shortened test case.
[1]
Hi,
border drawing design is quite different in FOP current Vs FOP 0.2x.
The former was quite imprecise, and could not easily support extended
border features.
I've tried your test case (from archive [1]) against Acrobat Reader X,
and at normal zoom the display depends on Enhance Thin Lines
Hi,
This should work.
Please, file in a new bug entry, attaching the material you gave here.
2012/10/29 franck FIMBEL ffim...@gmail.com:
Hi,
I am trying to use the attribute page-position=only in a
conditional-page-master-reference in order to produce a different page
header if the document
Hi,
FOP implements the Unicode Line Breaking Algorithm UAX #14 [see 1].
degree symbol is classified as Postfix Numeric, for witch break
before is not allowed if preceded with numeric or closing sign.
numéro sign is classified as Prefix Numeric, therefore constraints
are inverted.
In addition to
: Wednesday, October 24, 2012 5:59 PM
To: fop-users@xmlgraphics.apache.org
Subject: Re: Word secability on character #176
Thank you Pascal.
Is there a possibility to indicate in the config Fop to do not cut on this
character ?
-Message d'origine- From: Pascal Sancho
Sent: Wednesday
#x2060;°AA/fo:inline/fo:block
-Message d'origine- From: Pascal Sancho
Sent: Thursday, October 25, 2012 9:33 AM
Hi,
I'm not familiar with hyphenation patterns. As a starting point, you
can read [1].
That said, you can insert a WJ char (Word Joiner, ie: #x2060;) where
Hi,
You should use the keep-together property (see [1]):
fo:inline keep-together.within-line=always.../fo:inline
[1] http://www.w3.org/TR/2006/REC-xsl11-20061205/#keep-together
2012/10/24 Christian Pestel christian.pes...@orange.fr:
Hi,
Fop don’t cut a long word like
Hi,
Yes, FOP provides an extension that ca
2012/10/22 Fries Bogusław bfr...@dpd.com.pl:
Hello,
I have xml with the data to obtain one single PDF document. I need to
duplicate this document ( using a xsl-fo commands) and merge it into one
single PDF. It possible?
Bogusław Fries
--
re-Hi,
Sorry, fingers too big... I continue.
Yes, FOP provides an extension that can help you; follow this:
http://xmlgraphics.apache.org/fop/1.1/extensions.html#external-document
2012/10/23 Pascal Sancho psancho@gmail.com:
Hi,
Yes, FOP provides an extension that ca
2012/10/22 Fries
Hi,
TXT is not a primary target output for FOP, and this should be
considered as a piece of sugar.
There are some recommendation that could improve such output (see [1]).
That said, a better approach should be to write a dedicated XSLT that
output exactly what you expect.
[1]
No problem, Victor;
One can help you if you supply information and material witch can help
to reproduce issue.
As other projects, FOP website proposes a starter kit. See [1].
If you encounter some problem when running FOP, this list is the right
place where to ask.
FOP website gives an overview
Hi,
in addition to what Luis said:
SVG should support CMYK through icc-color property (see [1]), but I
don't know if Batik does handle this feature.
Note that fox:cmyk() is a FOP extension, and it is recommended to use
the standard FO function rgb-icc() (see [2]).
[1]
Hi,
I don't know what is syntex.
FOP features PDF accessibility (see [1]). That could help you.
[1] http://xmlgraphics.apache.org/fop/1.1rc1/accessibility.html
2012/10/16 Wilhelm wilhelm.me...@fh-kl.de:
Hi all,
is there anything like syntex in fop possible: that is, a possiblility to
Hi,
what JVM (vendor + version) do you use?
do you have some svg in your doc?
If yes, do you run a Xserver?
regarding confidentiality, you have 2 options:
- either submit material witch content is replaced with dummy one
- or send privately confidential material to 1 person (not in
users-list,
Hi,
1st, this discussion should move to fop-dev list now.
2nd, there is definitively some issues that are due to length handled
as integer (char width you pointed here, i-p-d changes from page to
page because length is rounded when it result in float value (metric
to imperial conversion,
with FOP's cavalier attitude towards rounding in AFP clear previously in a
bug report.
On 25 September 2012 08:11, Pascal Sancho psancho@gmail.com wrote:
Hi,
1st, this discussion should move to fop-dev list now.
2nd, there is definitively some issues that are due to length handled
Hi Rob,
sorry for the delay.
In your test case, ICC profiles are not taken into account in the
fo:layout-master-set (probably because fo:declarations comes after),
while in fo:page-sequence all works as expected.
So you may file in a bug entry.
Note that FOP behaves as this whatever the version
Hi,
This question is definitively off topic in FOP-users list.
You should ask such question to jcgm team. Perhaps you can open a ticket at [1].
[1] https://sourceforge.net/tracker/?group_id=283070atid=1200470
2012/9/11 froglander kristina.here...@trax.aero:
I have looked through the features
Hi Martin,
the pdf-image version that works with FOP 1.1RC1 is the 2.1.0.SNAPSHOT.
You have to build it by yourself, from pdf-image/trunk, using the
dist option with ant.
If you are facing to same (or other) issue using this trunk version,
please provide material to let someone to reproduce the
Hi,
By customizing a very old FOP version, you 'll take the risk to have
your own version of FOP, and getting help about it will become more
and more difficult for (at least) 2 reasons:
- old design knowledge is smaller each year,
- nobody else knows what changes you made in your customized FOP.
.
Probably I missed something, but this seems to me related to the
computed area for page number citation.
2012/8/28 Pascal Sancho psancho@gmail.com:
Hi Glen,
Not exactly:
FOP 0.95: table content is shrunk to fit in clip space (wrong)
FOP 1.0: table content is shifted to the wrong side
Hi,
cmyk() is not an XSLT function, it is a FOP extension for XSL-FO (see [1]).
In your snippet, you should use it as this:
xsl:param name=darkbackgroundcolorcmyk(0.0, 0.564, 0.529, 0.325)/xsl:param
[1] http://xmlgraphics.apache.org/fop/1.0/extensions.html#color-function-cmyk
2012/8/27 Rob
...@skynav.com:
On Mon, Aug 27, 2012 at 10:10 PM, Pascal Sancho psancho@gmail.com
wrote:
There is something wrong in your XSL-FO:
the table containing TOC is wider than available i-p-d, and the
corresponding region-body has its property overflow set to hidden.
So, the PDF shows what
Hi,
There is something wrong in your XSL-FO:
the table containing TOC is wider than available i-p-d, and the
corresponding region-body has its property overflow set to hidden.
So, the PDF shows what is expected visually.
But...
hidden text can be copied, and IMHO this is not the correct
Hi,
Unless I missed something, I cannot reproduce what you describe.
did you tried it without VH's patch?
I note that my FOP substitutes some fonts, that an have some effect there.
I attach the output (pdf from FOP trunk, without patch and without
your fonts), so you will see if there is
Hi,
You have to set it in config file with the hyphenation-base element (see [1]).
Then from the command line script, you should use the -c option (see [{2])
[1] http://xmlgraphics.apache.org/fop/1.0/configuration.html#general-elements
[2]
Hi,
Can you confirm that on both platforms you use the same FOP v0.95?
Also, you should examine or attach the 2 XSL-FO (i.e. XML+XSLT
result), there is certainly differences that explain different
outputs, and this is the minimal material that allows everybody to
help you more efficiently.
From
Hi,
NFOP seems to be a dead project, last commit occurred on may 2008, and
was based on FOP 0.20.5, witch is a *very* old FOP version, based on
an abandoned design.
On the other hand, FOP has now integrated the cited patch and either
current 1.1RC1 version or TRUNK version.
Giving you the list
Hi,
I think this is the same as another issue [1].
[1] https://issues.apache.org/bugzilla/show_bug.cgi?id=48765
2012/7/23 mehdi houshmand med1...@gmail.com:
Hi Wilhelm,
I've created a bug[1] to track this issue, I'll investigate and post any
findings.
Mehdi
[1]
Hi,
the given position is relative to FO file;
in your case: 304th line, 166th character.
2012/7/20 Rob Sargent rsarg...@xmission.com:
Running fop-1.0, I get messages such as
Content overflows the viewport of an fo:block-container in block-progression
direction by 7200 millipoints. (See
, grumpy :).
rjs
On 07/12/2012 02:35 AM, Pascal Sancho wrote:
Hi,
One needs to see what there is in the XSL-FO (XML + XSLT transfo
result) fed to FOP.
Can you have a look on it, or provide a minimal version of it, so one
can reproduce the described issue?
2012/7/11 Rob Sargent rsarg
Hi,
in XSL-FO REC2 Working Draft, I see no change regarding footnotes (see [1]).
AFAIK, there is no plan to implement such extension in FOP, but since
it is open source, everybody can contribute and submit a patch (see
[2]) to add such extension.
That said, there is probably an alternative:
Hi,
One needs to see what there is in the XSL-FO (XML + XSLT transfo
result) fed to FOP.
Can you have a look on it, or provide a minimal version of it, so one
can reproduce the described issue?
2012/7/11 Rob Sargent rsarg...@xmission.com:
In the middle of my document that page numbering goes
Hi,
no, fox:destination is still in use and it doesn't replace the syntax
you are speaking about.
With fox:destination, your destination can be in whatever page; if a
new version of your doc results in changing the page number of your
target, you don't need to change the url.
2012/7/9
Hi,
There is something wrong in FOP regarding the fo:character.
This is reproduced with FOP dev version.
You should fill in a bug report at [1], attacching your test case.
That said, this fo:character is not required in your snippet, you can
insert directly any character in your text node:
Un
Hi,
The span attribute should be set on the top-level fo:block-container:
fo:block-container span=all
fo:block
fo:external-graphic...
This will give you the expected output.
2012/7/2 Phillip B Oldham phillip.old...@gmail.com:
Hi all
I'd like to have a 2-col layout which flows over a
Hi,
Hmm,
IIUC, JCGM is an imageIO plugin that allows to use CGM with FOP.
So, you are probably facing to JCGM limitations. See [1].
[1] http://jcgm.sourceforge.net/features.html
2012/7/2 froglander kristina.here...@trax.aero:
Thank you for your reply!
This is something that someone else set
Hi,
If you get a space between # and 28, this is because it is added
during XSLT stage, probably because of linefeeds or spaces around text
nodes.
Strictly speaking, this is out of topic in this list.
That said, if you want to avoid such unexpected spaces in XSL-FO
output, you have to embed all
Hi
2012/6/22 Rita Greenberg rgreenb...@medata.com:
Oops - I thought it worked but no - it's not!
In my xsl:fo stylesheet I'm using wrap-option=wrap on a fo:cell level.
FOP has limited support for wrap-option: only for fo:block. See
Compliance page at [1].
That said, FOP breaking algorithm
Hi,
metric files are deprecated.
The only usage for these metric files is when you don't want to embed
font files, witch is not used today.
2012/6/22 Marc marc.li...@free.fr:
Youcan embedded fonts in the pdf file.
to do that you have to modify the fop configuration file and dispose of the
Hi Christian,
You should fill in a bug, attaching both files; the writing-mode is
not taken into account for table position.
2012/6/21 Christian Pestel christian.pes...@orange.fr:
It’s better with sample.
Christian Pestel
christian.pes...@orange.fr
From: Christian Pestel
Sent:
Hi Benson,
1st, on this list you have to describe what you expect and what you
get, and provide material that can make volunteers to understand what
you ask.
Please read [1] before submitting a question on this list.
That said, I understand from your link that you are using FOP 0.93,
witch is
Hi,
The '#' means that the character is not found in the used font.
You have here 2 alternatives:
- either use a font that contains such character (tried successfully
with DejaVu collection, follow [1])
- or (as said Eric) use keep-together.within-line on 1 fo:inline for
each first-second.
[1]
Hi Léa,
2012/6/11 Léa Massiot lmhe...@orange.fr:
Hello Pascal,
I'm sorry to come back on this but I do not understand your example... :/
My underlying question is the following: what is the proper method which can
be used to associate a set of traits with specific values to a given fo
Hi,
This is a pure XSLT related question.
That said, there are usually 2 ways to repeat attributes over a
collection of elements:
- either the one you described
- or using a xsl:call-template.
The latter is more appropriate if you need to pass parameters to your attributes
2012/6/8 Léa
Léa,
here is an example:
myElement
xsl:call-template name=myAttributeSet
xsl:with-param name=myParam
myParamValue
/xsl:with-param
/xsl:call-template
...
/myElement
xsl:template name=myAttributeSet
xsl:param name=myParam/
xsl:attribute name=myAttribute
xsl:value-of
= FOP don't
fail
but this workarround don't seem to work with SVG font.
-Message d'origine-
From: Pascal Sancho
Sent: Thursday, May 31, 2012 12:03 PM
Christian,
any is not a font per se, it just indicates that default font is used
(FOP uses Helvetica, and PDF viewer replace it with Arial
substitution.
Could you please try my sample in PDF-A ?
-Message d'origine-
From: Pascal Sancho
Sent: Thursday, June 07, 2012 9:28 AM
Hi,
If you explicitly substitute Helvetica with Arial in FOP config for PDF,
you have to ensure that no references to Helvetica remains in final PDF.
IMHO
be appropriate. Perhaps
Insufficient space for line break causes error on
zero-length region-body would be closer to the truth.
Thanks a ton for the work-around! Saved the day, to be sure.
rjs
On 06/04/2012 02:05 AM, Pascal Sancho wrote:
Hi
engine?
Pascal Sancho wrote:
Hi,
I see 2 options:
- either play with letter-spacing (this is what Xep does),
- or insert a ZWSP (#x200b;) where you want a break opportunity
(before each uppercase letter could be a good place for a method name).
Le 04/06/2012 11:14, SNawa a écrit :
Hi All I
Hi,
I see 2 options:
- either play with letter-spacing (this is what Xep does),
- or insert a ZWSP (#x200b;) where you want a break opportunity
(before each uppercase letter could be a good place for a method name).
Le 04/06/2012 11:14, SNawa a écrit :
Hi All I have table with some text.
Hi,
The characters map in Wingdings is not a standard thing:
#x28;#xFE;#xFD;#xFC; are Unicode for (þýü
Regarding what is output in the PDF produced with Word:
the sequence you expect is #xF028;#xF0FE;#xF0FD;#xF0FC;, witch is
located in [private use character] Unicode page: IOW, this is
Hi Rob,
sure you are facing a bug:
when there is no room on 1 page to insert a line-break, then, if IPD
change on next page, the described FOPException is thrown.
See the attached minimal XSL-FO: when you remove the expression
+ 0.001pt from the margin-top value, it works like charm.
Can
Pdf is ko : the font Helvetiva is referenced in pdf/A instead of Verdana.
Why ?
May be some pb with Batik ?
Christian Pestel
christian.pes...@orange.fr
-Message d'origine-
From: Pascal Sancho
Sent: Wednesday, May 30, 2012 5:13 PM
To: fop-users@xmlgraphics.apache.org
Subject: Re
font: /Helvetica
and the any font seems not to be used in this context.
Is there a solution ?
Thank.
Christian Pestel
christian.pes...@orange.fr
-Message d'origine-
From: Pascal Sancho
Sent: Thursday, May 31, 2012 9:39 AM
To: fop-users@xmlgraphics.apache.org
Subject: Re: Offending
Hi,
embedding fonts is required by the PDF/A-1b spec, even when you use some
of base 14 fonts.
Since there is license restriction with Helvetica (and other base 14)
font, it is not embedded by default. You have to get it by yourself (you
can purchase it on vendor's web site).
Or you can
Hi,
I found 2 issues related to IPD change between 2 pages that throw such
exception:
https://issues.apache.org/bugzilla/show_bug.cgi?id=50985
https://issues.apache.org/bugzilla/show_bug.cgi?id=51043
Perhaps the issue you are facing to is related to.
That said, one method to focus on the
, Christian Pestel a écrit :
Hi Pascal,
I don't understand why a simple fo file with texte fo:block
font-family=Helvetica work fine in PDF-A (no license problem)
and an fo file with SVG image don't work.
Christian Pestel
christian.pes...@orange.fr
-Message d'origine-
From: Pascal Sancho
Hi,
extra spaces before and after the image are half leading (above and
below text). They are due to font-size and line-height properties.
If your fo:block doesn't contain any text, you can set them to 0.
Since the line-height property is defaulting to 1.2 (IOW, computed value
is 1.2 *
Hi,
IIUC, what you need is the relative-align property (see [1]).
Unfortunately, this is not yet supported by FOP (see [2]).
The unique workaround I can imagine is to insert a transparent image to
adjust the height of the smallest inline area.
[1] http://www.w3.org/TR/xsl/#relative-align
[2]
Hi,
FOP Fonts do not need to be installed on your system.
You just need to pass fonts location to FOP.
1/ register all used font files in configuration file (see [1], more
precisely register a particular font)
2/ depending on how you use fop (either command line or embedded in your
app),
-Original Message-
From: Pascal Sancho [mailto:pascal.san...@takoma.fr]
Sent: Monday, April 16, 2012 5:05 PM
Oh sorry, I didn't read the Subject.
I confirm what Octavi said: FOP 1.0 crashes while FOP trunk successfully
run your test.
Le 16/04/2012 16:40, Pascal Sancho a écrit :
Hi,
what
Hi David,
sorry for late answer.
What you report is related to Bugzilla issue #44328 (see [1]).
orphans and widows properties are not taken into account when
LF-treatment=preserve.
You can try to apply the patch and feedback if success.
[1]
Hi,
what do you mean by it crash?
- how does FOP behave?
- is there an error message?
that said, your snippet appears to be regular. I don't see anything wrong.
Further info will be welcome.
Le 16/04/2012 15:53, Bogusław Fries a écrit :
We have the following stylesheet:
xsl:stylesheet
Oh sorry, I didn't read the Subject.
I confirm what Octavi said: FOP 1.0 crashes while FOP trunk successfully
run your test.
Le 16/04/2012 16:40, Pascal Sancho a écrit :
Hi,
what do you mean by it crash?
- how does FOP behave?
- is there an error message?
that said, your snippet
Hi,
also, you can use scale-down-to-fit, in this case the image will be
resized *only* if too large.
Le 30/03/2012 15:48, Klearchos Klearchou a écrit :
Hello Eric,
are you looking for something like this?
fo:external-graphic src=url('{$sourceImageLink}')
content-width=scale-to-fit
Hi,
like width or height, i-p-d and b-p-d usage don't resize images, but the
rectangle allocated to it.
Once you have defined your rectangle (using elastic dimensions or not,
depending on *.minimum, *.maximum and *.optimum values), you should use
content-* properties to rescale your image, if
Hi,
This thread is related to issue #52969 (see [1]).
Please, discussing this issue on both places is not a good practice;
doing-it first on this list is a good start, then if a bug is revealed,
you can ask on buglist.
That said, I guess you set the value @User directly in your XSLT.
If
Mohanty a écrit :
Pascal Sancho pascal.sancho at takoma.fr writes:
Thanks Pascal. Great suggestion.
The snippet I included earlier was formatted for better read. In real FO
there
is no LF. I use empty blocks to put line breaks. I am still struggling to
understand how the IS there any
was disbanded as a rapid succession of
sub-bullets could lead to overly-large keep-together blocks (causing
holes in the output) and left me wondering if I should undo the
construct (as perhaps bad practice). But lo - I'll leave it in.
On 02/17/2012 07:32 AM, Pascal Sancho wrote:
Hi,
The right
-
From: Lal Mohanty [mailto:lmohanty at yahoo.com]
Sent: Friday, February 17, 2012 4:09 PM
Pascal Sancho pascal.sancho at takoma.fr writes:
Hi,
XSLT snippet is not appropriate to figure what you describe.
You should a *short* XSL-FO to this thread, that demonstrates the
issue you
Hi,
sorry for this late response.
Your approach seems elegant.
However, I think there is a quicker workaround:
1st step, you generate your PDF.
2nd step, you insert each page in a 2nd PDF, using FOP again:
you can use the pdf-image plugin [1], in conjunction with free-form
transformation
Hi,
The right construction should be to insert a sub-level list within a
parent list-item:
fo:list-block
fo:list-item
fo:list-item-label.../fo:list-item-label
fo:list-item-body
fo:blockmy level 1 item/fo:block
fo:list-block
fo:list-item
Hi,
You can share this in the wiki/howTo section, I think this is the right
place for that:
http://wiki.apache.org/xmlgraphics-fop/FrontPage
Le 17/02/2012 10:12, Theresa Jayne Forster a écrit :
Ok, as you know I was asking how to do this and having so many problems.
I resolved the problem but
Hi,
XSLT snippet is not appropriate to figure what you describe.
You should a *short* XSL-FO to this thread, that demonstrates the issue
you are describing.
Le 17/02/2012 01:19, Lal Mohanty a écrit :
I am having a problem with keep-together.within-page=always in Fop
0.95/1.0.
It behaves
Hi,
If IIUC, what you need is the property 'relative-align' ([1] XSL-FO REC
1.1, §7.14.6).
Unfortunately, this is not implemented in FOP ([2] FOP compliance page).
AFAIK, the only workaround is the one you describe: playing with
margin-before (or padding|space -before).
[1]
Hi,
FOP 1.0 works as expected.
You should look at what is output from your XSLT.
Try to produce a short XSL-FO, look inside, and feed FOP with it.
If there is something wrong, please isolate the XSL-FO snippet that
produce unexpected output, and attach it on this thread.
At XSLT stage, many
101 - 200 of 673 matches
Mail list logo
