Hello,
Hello Karen,
I tried it with the snapshot of the night before yesterday (due to the firewall I
cannot get into CVS directly). It was not rendered correctly.
I have included the document (doc.xml) and the stylesheet (doc2pdf.xsl) that lead to
docxalan.fo
If rendered to awt few
This would require the element mappings to handle things a bit better,
fairly easy.
The other part is to setup some sort of render factory for foreign data
handling (in fo:instream-foreign-object and external graphics). This would
need a bit of work and time.
Another issue might be the size of
Hi,
I designed an xsl-fo at work with win2k. It works nice and smooth, the
result is exactly what I want.
I wanted to do some work at home (on a win 98 PC) and the result is
different.
My xml file is someting like this:
school name = Don Bosco
class
class_nameMath/class_name
Total agreement to everything Keiron just said.
However, that's not to say that we can't work up something that meets your
needs for 'keep-together' on fo:list-item. It's usually possible to take
care of a specific; as Keiron says it's the general case (making keeps work
everywhere that they
hi all,
I have used FOP 0-19-0.CVS in generating of pdf file from xml. And, I have
a problem here, that is how can I put different header content in
bibliography page and the rest pages of a document?
The attactment is the xsl that I have generated, any problems?
Thanks for any help you can
Hello Koen
I may be able to help with ~part~ of this.
The latest version of AWTRender fails to draw a border at all
for your .fo file. However, the border re-appears if you increase
the border-size to 1.0pt. This may be a (bad) side effect of
changes we recently made to the awt render to
Dear Listners,
I have attached the latest iteration of Tree.java. I saw that Mark was
bypassing part of the FO tree, I think it was. At any rate, with
dynamic rendering, there was a need to be able to delete a subtree. The
methods are deleteSubTree and delete.
Looking at applying Tree to
PLEASE DO NOT REPLY TO THIS MESSAGE. TO FURTHER COMMENT
ON THE STATUS OF THIS BUG PLEASE FOLLOW THE LINK BELOW
AND USE THE ON-LINE APPLICATION. REPLYING TO THIS MESSAGE
DOES NOT UPDATE THE DATABASE, AND SO YOUR COMMENT WILL
BE LOST SOMEWHERE.
PLEASE DO NOT REPLY TO THIS MESSAGE. TO FURTHER COMMENT
ON THE STATUS OF THIS BUG PLEASE FOLLOW THE LINK BELOW
AND USE THE ON-LINE APPLICATION. REPLYING TO THIS MESSAGE
DOES NOT UPDATE THE DATABASE, AND SO YOUR COMMENT WILL
BE LOST SOMEWHERE.
I am using FOP 0-19-0.CVS and having problems nesting tables. Just as
a simple test I am trying to place one table inside a block, within a
single outer table cell. The PDF output does display the values, but
entirely ignores the inner table structure by placing the values on a
single row.
Hi,
I cannot access the FOP-FAQ on the xml.apache.org web
site, concerning the use of FOP, so I write directly
to this list.
I would like to apologise in advance because I am a
real beginner in this field and I might not be using
the right channel to ask my questions (let me know if
this is the
Hi,
Below is a patch to prevent AWTRender from drawing an invisible
border when the value for border-width is too small. The patch
basically says that no matter how small the border-width is, it will
always render at least 1 pixel on the target graphics context.
I leave it to others to rule on
Curious:
I'm using the docbook-xsl-1.14 tools from docbook.sourceforge.net to
convert a DocDook XML file into xsl:fo and then using FOP to convert
that into PDF. I've noticed FOP printing messages like this:
warning: property - linefeed-treatment is not implemented yet.
it turns out that
Hi Arnaud,
That's about right, but try putting the -d argument before the doc.fo
and doc.pdf. Hopefully you will get a better debugging message. It
sounds like your .fo file has an unknown object in it, although the
message isn't very helpful. You might want to include your .fo file with
your
Hi Emmanuel,
As you say, the problem seems to be in processing the XSL. That isn't
really done by FOP, except by calling Xalan (or some other kind of Trax
compliant transformer.)
Sounds like one of two things: obscure classpath problem or problem with
the Sun JDK 1.3.1 itself on Win98. Do you
Koen (and Ralph and others),
There is a problem, but it's not a border-drawing problem.
You have a left-margin specified as 2cm on a block which is containing
the paragraphs before the table and the table itself. This property is
inherited and is therefore used on both the fo:table and the
At 06:53 PM 8/7/01 +0200, you wrote:
Koen (and Ralph and others),
There is a problem, but it's not a border-drawing problem.
Karen,
Sorry, I wasn't clear -- I'm suggesting there are ~two~ separate problems
here. The first is what you describe below. The second is: given
the fo such as it is,
Hi Arved (and other interested parties),
Lots of other bugs (like the inline-area height) show up well in tables
because the grid makes things visible. That's the case with the trailing
white-space bug I saw the other day, resulting in an empty table row.
Some of these can also be shown by using
I had a similiar problem to this when running an FO file output from MSXML
through FOP. If my memory serves correctly, it was caused by the encoding,
which is UTF-16 by default. You need to set it to UTF-8. This may be because
MSXML by default places some binary data in the first byte or two of
19 matches
Mail list logo
