Hmm, I cannot reproduce the error with your example file. I get an error,
though: you specified a border on region-body which is not allowed by
the spec. But if I remove the border, everything is fine. Shrug.
Are you using a peculiar XML parsing setup? Maybe the generated FO looks
ok (if it is ser
Steve,
The XSL-FO line building rules are fairly complex (see section 4.5 in the
spec). However, the default case is roughly: Line height, including the
half-leading values, is determined by the font set on the enclosing block.
Any inline areas that are smaller in height will not cause the line he
Thanks Jay and Andreas.
What if I keep getting errors even though I have the minimalistic of FO?
fo:root is missing child elements.
Required Content Model: (layout-master-set, declarations?,
bookmark-tree?, page-sequence+)
http://www.w3.org/1999/XSL/Format";>
? means 0 or 1 (so optional, yes)
+ means 1 or more (required and may repeat)
* means 0 or more (optional and may repeat)
(no mark) means just 1 (required and may not repeat)
Jay Bryant
Bryant Communication Services
http://www.bryantcs.com/
- Original Message -
From: "Fournier,Danny [N
On Mar 3, 2008, at 19:08, Fournier,Danny [NCR] wrote:
Thanks Andreas. Everything worked in 0.20.5 so I assumed that it would
still work in 0.94.
What is the suffix appended to the order of the fields? I've seend
"?",
which I assume mean optional. What about "+" ?
Basically the same as with
Thanks Andreas. Everything worked in 0.20.5 so I assumed that it would
still work in 0.94.
What is the suffix appended to the order of the fields? I've seend "?",
which I assume mean optional. What about "+" ?
DF
> -Original Message-
> From: Andreas Delmelle [mailto:[EMAIL PROTECTED]
>
On Mar 3, 2008, at 18:09, Fournier,Danny [NCR] wrote:
Hi
Here is the rendered XSL-FO:
I get the following message:
javax.xml.transform.TransformerException:
org.apache.fop.fo.ValidationException: Error(Unknown location):
fo:simple-page-master is missing child elements.
Required Content M
Here is the rendered XSL-FO:
I get the following message:
javax.xml.transform.TransformerException:
org.apache.fop.fo.ValidationException: Error(Unknown location):
fo:simple-page-master is missing child elements.
Required Content Model: (region-body, region-bef
> On Feb 26, 2008, at 16:42, Johannes Caspary wrote:
>
> Hi
>
>> My problem concerns the functionality to retain formatting
>> information such as line feeds or white spaces that have been
>> stored like that in the XML document. There is the attribute white-
>> space-collapse of fo:block, which, w
Thanks. I needed to know that I wasn't completely off the mark on this
one.
-Lou
Andreas Delmelle <[EMAIL PROTECTED]> wrote on 02/29/2008
03:13:39 PM:
> On Feb 29, 2008, at 16:58, [EMAIL PROTECTED] wrote:
>
> Hi Lou
>
> It should definitely work. That is: it is a perfectly legitimate
> va
I am using uming, however, the font is called ARPLShanHeiSunUni. All I
do is
font-family="ARPLShanHeiSunUni" font-weight="normal" text-align="left">
and everything works fine
Peter
element is indeed embedded inside element.
Not sure why it is getting stripped off my message while posting
element is indeed embedded inside element.
Not sure why it is getting stripped off my message while posting reply.
xsltuser wrote:
>
> FOP version I'm using is 0.94
>
> Entry in the FOP configuration file is as per the specification:
>
>
>weight="normal"/>
FOP version I'm using is 0.94
Entry in the FOP configuration file is as per the specification:
When I run xslt through the FOP processor, everything goes on smoothly with
no errors thrown but the generated pdf does not display any chinese text as
expected.
xslt
13 matches
Mail list logo
