Hi,
I get a vertical text with your a fo file undezr FOP 0.93 (I suppose that is
what you want to get).
There is only 1 minor mistake in it:
Use "Sans-serif" instead of "SansSerif" in your font-family property.
Pascal
> -Message d'origine-
> De : Gregan, Miroslav [mailto:[EMAIL PROTECT
Not fair, I still get nothing correct!!
Even when I put no font-family property.
Could it be a library problem?
Miroslav
Hi,
I get a vertical text with your a fo file undezr FOP 0.93 (I suppose that is
what you want to get).
There is only 1 minor mistake in it:
Use "Sans-serif" instead of
That's strange. My Java version (java -version) reads 1.4.2, and I installed
Java on this machine from the latest SDK last year.
But in any case, it worked. Thanks.
That means you're probably still on old JDK 1.3 which doesn't contain
JAXP. Please add Xerces and Xalan to the classpath.
--
Vie
Hi Jeremias,
thanks a lot for your answers :-)
Update form Trunk works very fine now after setting the needed proxy in the
TortoiseSVN. The First Download and Update from Trunk works without the
Proxy-Settings. Maybe strange but never mind now.
My PDF-Output looks good at this moment. But may
Thank you very much Jeremias.
I'll try it.
Best regards
Xavier
Jeremias Maerki a écrit :
Well, just put fop.jar and all JAR files from FOP's lib directory in the
WEB-INF/lib directory of your web application. You can omit the JAXP
stuff, i.e. the following JARs if you use JDK 1.4 or later:
-
AFAIK, with FOP 0.93, related SVG libraries are:
- batik-all-1.6.jar
- xmlgraphics-commons-1.1.jar
Pascal
> -Message d'origine-
> De : Gregan, Miroslav [mailto:[EMAIL PROTECTED]
> Envoyé : mercredi 10 janvier 2007 11:40
>
> Not fair, I still get nothing correct!!
>
> Even when I
Hello List,
after the update of FOP from TRUNK today, I've got a "WARNING" while generating
a PDF-Output.
org.apache.fop.layoutmgr.inline.LineLayoutManager$LineBreakingAlgorithm
updateData2
WARNUNG: Line 1 of a paragraph overflows the available area. (fo:block,
"Aggregierte Ausfallzeit IT-Syste
[EMAIL PROTECTED] wrote:
Hello List,
after the update of FOP from TRUNK today, I've got a "WARNING" while
generating a PDF-Output.
org.apache.fop.layoutmgr.inline.LineLayoutManager$LineBreakingAlgorithm
updateData2
WARNUNG: Line 1 of a paragraph overflows the available area. (fo:block,
"Aggre
Hello Chris,
I do not defined a width for each column, so each column has the same width.
But the table looks like this in fo:
IT-SystemAggregierte Ausfallzeit
IT-SystemIT-KomponenteAggregierte Ausfallzeit
IT-KomponenteIT-Anwendung, die IT-System
benutzttolerierbare Ausfallzeit für
Systemarbe
I ran the transformation from both computers on the command line, the FO file
was identical and did not contain a fo:simple-page-master element with more
then one fo:region-body. I'm using Xalan 2.7.0 on both machines for XSLT
processing. Not sure if this is relevant but the machine I'm having
p
Hi all,
i searched the list a few hours by now, trying to get help on my tif
problem and i can now import a tif saved in rgb color.
But for print i need a cmyk tiff.
The Problem is, that the cmyk is renderd with batik, why? for rgb fop
takes teh right jimi...
The result from the cmyk is jus
On Jan 10, 2007, at 18:48, pwillsey wrote:
I ran the transformation from both computers on the command line,
the FO file
was identical and did not contain a fo:simple-page-master element
with more
then one fo:region-body.
Did you do a visual check, or a more reliable XPath check?
Someth
CMYK TIFF is currently only supported if the image itself is encoded as
a DCT image (with is the same compression JPEG uses). Otherwise, FOP
will process the image data wrongly, thinking it is RGB data. I suggest
you convert your images into a CMYK JPEG images. That is probably the
easiest work-aro
Ok, in this case I'd modify the application so you can write out the
generated FO within your application. Maybe there's something special
about that environment.
I'm sure you did it right, but are you certain that you properly
override the default XSLT implementation with Xalan 2.7.0 using the
en
Hi Jeremias,
now i am running into an error, that terminates the rendering:
javax.xml.transform.TransformerException: java.lang.RuntimeException:
TIFFImage16
at org.apache.xalan.templates.ElemLiteralResult.execute
(ElemLiteralResult.java:725)
at
org.apache.xalan.transformer.T
Without either the original exception (this is a nested one) or the
image file, I have no idea what this is about. Sorry. But why don't you
try JPEG directly. There's a higher chance that this will work.
On 10.01.2007 22:33:57 Kris Wolff wrote:
> Hi Jeremias,
>
> now i am running into an error, t
Hmm, "TIFFImage16" is one of those error messages that should actually
be resolved into an understandable error message. Looking at the source
code, it means as much as: "I don't support CMYK images with DCT
compression". "I" that is the TIFF codec in XML Graphics Commons.
Unfortunately, the image
Hi Jeremias,
i try to follow you in the code... hm, lost at some point. I
definetly need cmyk, so i start to begin looking for some jai
examples rendering tiff2jpeg without loosing the color theme. All i
get by now is some ugly image in compleate diferent colors
so i think other api,
Jeremias Maerki-2 wrote:
>
> Ok, in this case I'd modify the application so you can write out the
> generated FO within your application. Maybe there's something special
> about that environment.
>
I modified the application to do this and then I ran the fo file that was
created through one of
leeloo5e79-docbook wrote:
>
>
> It could be that the new UAX#14 line breaking introduced after 0.93 in
> late December is causing this. Can you please provide a full working
> testcase fo exhibiting the problem (if possible attached please not
> inlined with the message).
>
> Thanks
>
> Manue
I don't have much time right now to explain the current plans but take a
look at:
org.apache.fop.render.pdf.FopPDFImage
org.apache.fop.render.image.TIFFImage
org.apache.fop.render.image.XmlGraphicsCommonsImage (parent of TIFFImage)
Some notes for the upcoming redesign of the image package:
http://
21 matches
Mail list logo