keiron 2002/09/18 23:52:14
Modified:docs/examples/fo alignment.fo
Log:
looks more like the spec example
Revision ChangesPath
1.4 +4 -1 xml-fop/docs/examples/fo/alignment.fo
Index: alignment.fo
On Thu, 2002-09-19 at 02:48, Steve Cameron wrote:
Can anyone provide me with an example of a 'nice' looking PDF table
generated with Fop. I have tried a few border options and end up with
lines of different width along different sides of the table and rows.
Have you looked in the examples?
Hi,
i have a problem with the fop.
when I execute my Servlet , I become a list of errors!
i use tomcat 3.2.3, fop 0.20.4 and winnt 4
Here are the errors:
javax.xml.transform.TransformerFactoryConfigurationError: Provider for
javax.xml.transform.TransformerFactory cannot be found
at
The area tree now only contains the values used for rendering. The
min/opt/max values should only be handled by the layout managers and
when the areas are created and added then it can set the fixed size of
the areas. The area tree has also be cleaned up a bit to make better use
of the block
I look to source code, and IMHO you must modify
src/org/apache/fop/images and
src/org/apache/fop/images/analyzer
classes to suport DPI (extract dpi from file and compute
right
width/height)
Thanx for the info. I did modify these classes, and also
ExternalGraphic.java in
keiron 2002/09/19 02:20:06
Modified:src/org/apache/fop/area Area.java Block.java
BlockParent.java RegionReference.java
Log:
don't implement serializable twice
Revision ChangesPath
1.10 +3 -1 xml-fop/src/org/apache/fop/area/Area.java
On Thu, 2002-09-19 at 11:00, Ambar Roy wrote:
I look to source code, and IMHO you must modify
src/org/apache/fop/images and
src/org/apache/fop/images/analyzer
classes to suport DPI (extract dpi from file and compute
right
width/height)
Thanx for the info. I did modify these classes,
A table consists of a series of embeded elements; the hyerarchy goes
somewhat like this (assume fo namespace):
table
table-body
table-row
table-cell
blockhere is the actual content/block
/table-cell
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=12809.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
Sounds reasonable. Depending on certain things, though, the system classloader might
not be able to find the classes. I asked the guy in charge of deployment at my
workplace where we kept FOP under Apache 4.0.4, and he said we kept it in Apache's
common-lib folder, so perhaps the best way to
The newer version probably uses the Avalon logger. This will throw the ERROR message, but should not break the code. You'll have to search for that fix in the archives.
It sounds like your not getting the right data in your FO file. Try running your data through the stylesheet on the command
Kevin Yeung wrote:
I am having troubles with long strings and table cells.
The common approach is to put zero width spaces into
the product number in order to give FOP a chance to
break the line. Note that 0.20.4 appears to have a bug
in the width calculation, you'll probably have to get
the
Amin Schoeib wrote:
I tried the code of JohnPT.
...
java.lang.NullPointerException
at org.apache.fop.fo.flow.Flow.setFlowName(Unknown Source)
at org.apache.fop.fo.flow.Flow.init(Unknown Source)
This is the real problem. Ensure your fo:flow has a flow
name specified:
fo:flow
[EMAIL PROTECTED] wrote:
I suggest we write a special language hyphenation file for URLs -- it is
not a natural language, but it is one nevertheless, with its own lexical
rules.
interesstingly, I just had the same thought.
(Can someone provide me with a pointer to the pertinent spec?)
[EMAIL PROTECTED] wrote:
1) use border-collapse=collapse on the table element to make adjacent
borders overlap
Ahem. From the source:
// System.err.println(Collapse borders);
/*
* Hard case.
* Cell border is combination of other cell borders, or table
*
Raúl Carazo wrote:
I've got a problem with my fonts!!! I used FOP 0.20.1 with Verdana without
problems. but suddenly (I'm sure we have done something, but I can't find it!!!),
this message appears
WARNING: unknown font Verdana,normal,normal so defaulted font to any
and Verdana
Tobias,
One alternative is to do the XSLT transform outside of FOP - i.e. do it
directly with Xalan. You can provide a stream to Xalan, and output into a
ByteArrayOutputStream, and then provide the fop Driver with an input source
that wraps the byte[] in the ByteArrayOutputStream.
I find it
I will be out of the office starting 19/09/2002 and will not return until
22/09/2002.
I will be out of the office and will have very limited access to my email.
I will respond to your message when I return.
If you have technical questions or issues regarding Scriptura, please send
them to
18 matches
Mail list logo
