David
Have you a particular reason to put your text alignment in your XML rather than
letting FO do your formatting? In a similar situation I had something like:
(XML)
address282 Quarry Road/address
addressMilford/address
zipCT 06460/zip
(XSL)
xsl:for-each select=address[position()!=last()]
Hi,
I was wondering if it is possible to let a block-container take the width of
it's containing block.
So in the following example, it would take the actual width of the external
graphic.
fo:block-container top=230mm left=40mm height=30mm
position=absolute
fo:block
From: Wouter de Vaal [EMAIL PROTECTED]
Hi,
I was wondering if it is possible to let a block-container take the width
of
it's containing block.
So in the following example, it would take the actual width of the external
graphic.
No, this isnt possible in FOP. In general, XSL-FO will let you do
No, this isnt possible in FOP. In general, XSL-FO will let you do this,
its
just that FOP only has limited support for block-container. Why do you
think
you need this feature? Perhaps there is a different way to achieve the
same
effect?
I'm creating an editor in which one can upload images
I could theoretically split the address up into multiple fields the way you
have suggested, but I am only using the address as an example. In other
places I need to put user observations that they have typed into a text box
in my report. These observations and other user entered fields exhibit
-Original Message-
From: J.Pietschmann [mailto:[EMAIL PROTECTED]
Andreas L. Delmelle wrote:
and so logically, would include the tab character placed before
the value of
the element in the source XML.
Thiss is wrong. You are in the XSLT source here (hopefully), and
text nodes
Andreas L. Delmelle wrote:
just white-space-treatment=preserve alone it has no effect and
The FOP compliance page (http://xml.apache.org/fop/compliance.html)
indicates only basic conformance for this property...
No -- the FOP compliance page indicates *no* conformance for this property.
The
Victor Mote wrote:
Hmmm. This is now the second time in mere days that this has confused even
our most able users. I find the color-coding extremely useful, but if it is
confusing everyone, perhaps we should remove it.
Victor Mote
IIRC, there was a discussion about color-coding before. It was
-Original Message-
From: Victor Mote [mailto:[EMAIL PROTECTED]
No -- the FOP compliance page indicates *no* conformance for this
property.
The blue in the basic column means that, because this property is not
required for basic XSL-FO conformance, FOP is conformant with the XSL-FO
-Original Message-
From: David Rosenstein [mailto:[EMAIL PROTECTED]
The transformation appears to be correct when i run it manually,
but when I
run the entire transformation manually it turns out correct
anyway (hence my
real confusion):
Next logical step would be to make a
You're character is probably outside the encoding of your XML file. What's the
encoding of your file (it's set in the header : ?xml encoding='...'
Hello:
I'm trying to print a special character for bullets, but everytime FOP
encounters this statement, it halts with the message: An
If i insert an image, the image will display like a character.
See:
*
* ~~~ text text *
* ~image~ *
* ~~~ *
* text text text*
* text text text*
*
But i need a text wrap around the image.
See:
*
*
Hi,
Here we are generating a .PDF file using FOP for french language using
XSLT. Most of the characters are coming out properly in transformations except
few.
if my input text contains lA'ACIC dA'adherence dans the transform output shows
l#ACIC d#adherence dans. The encoding type
[EMAIL PROTECTED] wrote:
...
But i need a text wrap around the image.
...
is this possible ?
The spec has fo:float for this purpose. Unfortunately, FOP doesn't
implement it.
J.Pietschmann
-
To unsubscribe, e-mail: [EMAIL
Jignesh-NX01880 Kapadia wrote:
if my input text contains lA'ACIC dA'adherence dans the transform output shows
l#ACIC d#adherence dans. The encoding type which we are using is ISO-8859-1.
See
http://xml.apache.org/fop/faq.html#pdf-characters
J.Pietschmann
--- Victor Mote [EMAIL PROTECTED] wrote:
Hmmm. This is now the second time in mere days that
this has confused even
our most able users. I find the color-coding
extremely useful, but if it is
confusing everyone, perhaps we should remove it.
Victor Mote
Don't worry about it--it's fine
16 matches
Mail list logo
