x27;s
> intrinsic size naturally gets smaller
Yes, that's interesting. Actually this is not my own issue, I
was helping a client and thought to report here what I thought
was a problem. But that makes sense. I'll forward this idea to
him.
Anyway, thanks for the help,
--
Florent G
not properly reporting the image resolution.
How can I give you more info about that?
Regards,
--
Florent Georges
http://www.fgeorges.org/
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additio
the image with
72 dpi for the documentation, but I thought that is maybe a bug of FOP.
Hope that helps,
--
Florent Georges
http://www.fgeorges.org/
<>-
To unsubscribe, e-mail: [EMAIL PROTECTED
Andreas L Delmelle wrote:
Hi
> The known workaround is to insert zero-width breaking spaces
> in the word at certain points.
Unfortunately, it is not really a possible solution. FO documents
are generated and in a lot of places we don't have any control on input
text (as the name of a suppl
Cheffe wrote:
> Since 0.93 on the attribute wrap-option='wrap' is
> supported i
> think. Give it a try
Thank you for the response. Unfortunately, that doesn't solve my
problem. Actually, it is not surprising, as 'wrap' is the default
value in one hane, and in the other hand the problem arise
Hi
I just saw a strange overflow in a table cell. The cell
contains two words, and the second word seems to being not
put on a new line if it is larger than the column width.
Here is a use case. The second cell is a little bit less
large, then both words are kept on a single line, while in
t
Simon Pepping wrote:
Hi
> Post refused. Regrettably, xsl-list does not accept non-subscriber
> contributions.
Actually, Gmane is an independant Mail-to-Usenet-then-back
gateway. XSL List is a plain mailing list. But I use Gmane to dig
in the archives as it has a better interface IMHO than
Simon Pepping wrote:
> Post refused.
I forward your post to XSL List.
Regards,
--drkm
___
Yahoo! Mail réinvente le mail ! Découvrez le nouveau Yahoo! Mail et s
Hi
Maybe you'll be interested to respond to the following email, asking
which version of FOP to use in an XSL-FO classroom:
http://article.gmane.org/gmane.text.xml.xsl.general.mulberrytech/55760
Regards,
--drkm
Jeremias Maerki wrote:
Hi
> Seems to be a problem in Saxon. When I last tested with Saxon
> 8.7.1, everything was fine. But I downloaded 8.8 and I can now
> reproduce your problem. So it's a regression in Saxon. The SAX
> startDocument() method is somehow called twice although it must
> not be.
Pascal Sancho wrote:
Hi
> Tested on both FOP 0.92 (works badly) and FOP_TRUNK (works
> fine), this has been corrected in latest code
Ok, thanks for the info. I'll wait for 0.93 to add this
functionality. And thanks to Stefan and Manuel: you're right, my
samples were not well-formed (my fau
Bart van Riel wrote:
> OK, so I need to:
> 1. Extract the element data from the html-holding element;
> 2. Convert the character escapes (should be do-able);
http://www.w3.org/1999/XSL/Transform";
version="1.0">
2a. Convert that HTML to well-formed XML.
Bart van Riel wrote:
Hi
> In short, I need to:
> 1. extract the data from the xml element;
> 2. convert the XML escapes to '<' and '>';
> 3. apply styles to the html.
You have a lexical representation of an XML tree. Because you want
to use it as an XML tree, you have to parse it. You can
"J.Pietschmann" wrote:
Hi
> Try a higher resolution printer (or printer setting)
> first, or even just another, modern printer. Small
> changes in the grey value may also have an effect. If you
> can get detailed information on your printer (resolution,
> dithering algorithm/matrix, or how ce
Hi
This question is maybe a little bit off-topic. I have a
problem with a grey background while faxing a printed PDF,
generated by FOP. The background looks like in the
following (in French, I think we say it is an "effet de
moiré"):
http://www.fgeorges.org/tmp/fax-bug.png
For a samp
Shamem Miah wrote:
> Sorry I didn't understand that. Is it possible you can provide a
> link with an example or explanation?
You can view the XSLT FAQ about the identity transformation:
http://www.dpawson.co.uk/xsl/sect2/identity.html
Basically, try something like that for the first tr
Shamem Miah wrote:
Hi
>font-size="12pt"
> font-family="sans-serif">
> /data/value
You can achive that with two transformations. The first to transform
the above in:
and the later as usual, to produce the FO to pass to FOP.
Regards,
--drkm
Jeremias Maerki wrote:
Hi
> Bug is filed against SAXON including patch:
>
http://sourceforge.net/tracker/index.php?func=detail&aid=1483350&group_id=29872&atid=397617
> Let's see what happens.
Michael seems to just have included your patch. See the full comment
on the issue page.
Thanks
Jeremias Maerki wrote:
> > So is the above result right or a bug?
> It's correct.
Ok, I misunderstood completly here, sorry. Thanks for your
comprehensive explanation.
Regards,
--drkm
__
Hi
Doesn't the following have to result in a table with a
border of 1pt, and two rules of 0.25pt?
Line 1
Line 2
Jeremias Maerki wrote:
> No, I did not, but I think the whole thing will be resolved
> more quickly if I write the necessary patch for SAXON and
> submit that with the error description. But first, I want
> to look at the PDF size problem.
Ok, thanks a lot.
Regards,
--drkm
Jeremias Maerki wrote:
Hi Jeremias
> As I suspected, it's a bug in SAXON 8.7.1.
> net.sf.saxon.dom.DOMWriter.attribute() does not convert
> empty Strings (for "no namespace") to null when it calls
> element.setAttributeNS().
> Of course, one could argue who exactly is at fault here,
> SAXON or
Hi
I just downloaded and installed the new beta release. First of all,
thanks to you all folks for your work!
My first test to see if everything seems to be installed right is to
run FOP without argument:
~> fop
USAGE
[... all help message snipped ...]
Apr 20, 20
Ian & Chris wrote:
> I am currently trying to format a large number (19v2) in a
> report, the format-number function seems to do incorrect
> formatting when it deals with large numbers, and an example
> follows:
>
This is not related to FOP, but to your XSLT processor. I suggest
you to post
Cinzia wrote:
> Then am I correct in assuming that by removing those lines
> feeds (i.e. all cityInstal elements on one line) would
> give position() 1,2,3... in fortest3b
For questions regarding XSLT and XPath, I strongly suggest you to use
XSL List at Mulberrytech.
Regards,
--drkm
Andreas L Delmelle wrote:
> On Mar 6, 2006, at 01:25, Florent Georges wrote:
> > Andreas L Delmelle wrote:
> >> The problem is an empty fo:instream-foreign-object.
> > Thanks for the solution (mmh, this file passed my
> > validator, I'll have to check that
Andreas L Delmelle wrote:
> The problem is an empty fo:instream-foreign-object.
Thanks for the solution (mmh, this file passed my validator, I'll
have to check that).
Regards,
--drkm
__
Hi
While running some tests, I found an NullPointerException with 0.91:
~> fop contract.fo contract.pdf
Exception
java.lang.NullPointerException
Attached the contract.fo file. I'm sorry I don't have time to locate
more precisely the error to reduce the size of this file (I hav
Jeremias Maerki wrote:
> Easily fixed when I know where to look. Thanks for tracking
> it down. It's fixed in FOP Trunk now:
Perfect. Thanks for the quick reply.
> http://svn.apache.org/viewcvs?rev=381978&view=rev
Even simplified ;-)
Regards,
--drkm
Florent Georges wrote:
> The reported unknown host is not the drive letter in the
> URI, but the drive letter of the base URI. I'm not sure if
> it's expected.
Ok, I think I found how to reproduce the bug, and
understand it, but I'm not sure exactly where belongs the
Florent Georges wrote:
> Manuel Mall wrote:
> > Try if file:///C:/test/logo.svg works. That should
> > remove any ambiguity about what is the path and what is
> > the hostname in the URL.
> I'll try tomorrow (as I can't reproduce the problem
> outside th
Manuel Mall wrote:
> On Wednesday 01 March 2006 08:10, Florent Georges wrote:
> > I'll try tomorrow (as I can't reproduce the problem
> > outside the server). But as I said, the URI is
> > generated by Saxon, by using the XPath 2.0
> > fn:resolve-uri().
mbiguity about what is the path and what is the
> hostname in the URL.
>
> Manuel
>
> On Wednesday 01 March 2006 00:49, Florent Georges wrote:
> > Jeremias Maerki wrote:
> > > Hmm, as I said in my other response, I tested locally with
> > > 0.91beta and FOP
Jeremias Maerki wrote:
> Hmm, as I said in my other response, I tested locally with
> 0.91beta and FOP Trunk and it works. I wonder what goes
> wrong. Are you sure that the URLs generated by Saxon really
> point to existing files?
> "Image not available" is only the second error message. Is
> the
Jeremias Maerki wrote:
> Both url(file:/C:/..) and url(file:///C:/..) work fine in FOP
> 0.91beta.
Mmh, yes, I just checked this on a local directory. Maybe related to
the file permissions, I don't know. I'll investigate further.
Thanks, and sorry for the noise,
--drkm
Florent Georges wrote:
> I'm using the following to access an SVG file on a Windows
> server:
>
Sorry, I forgot to specify the version I use: FOP 0.91beta.
Re
Hi
I'm using the following to access an SVG file on a Windows
server:
See the value of the URI (i.e. 'file:/C:/...'). If I use a
relative URI, starting for example by '../', no problem.
But with the above URI the file is not found, and I get the
following error message:
FONode.Ima
Jeremias Maerki wrote:
> I've fixed the problem in FOP Trunk:
> http://svn.apache.org/viewcvs?rev=376226&view=rev
> There was another bug that surfaced with your test file
> once I had fixed the above problem. That is fixed, too:
> http://svn.apache.org/viewcvs?rev=376235&view=rev
Very good ne
Jeremias Maerki wrote:
> I need to verify first but I think I know what's wrong. For those who
> know the technical details: I think the list layout managers ignore
> padding-top and padding-bottom when they produce the combined element
> list. I had to fix a similar problem for tables and it may
Florent Georges wrote:
> I post the real FO and PDF (with alphanumeric modified) resp.
> there:
Simplified:
http://cjoint.com/?ciuNyWQ2oV
http://cjoint.com/?ciuNYOUH7C
Regards,
Chris Bowditch wrote:
> The problem appears obvious to me, look at your
> simple-page-master:
> margin-bottom="75pt" margin-right="50pt" />
>
>
>
>
> The size allowed for the region-after is 100pt, but your
> region-body only has a bottom margin of 75pt.
Yes, indeed. Than
Hi
I have a problem with the 'xsl-region-body' that overlap
with the 'xsl-region-after'. I tried to reduce the problem,
but I was not able to identify precisely the problem.
Here are the FO source and the PDF output produced by FOP
0.91beta:
FO: http://cjoint.com/?cilOqguiGW
PDF:
Florent Georges wrote:
> Before: url('rsrc/logo.svg')
> After: url('../<...>/xsl/rsrc/logo.svg')
Oops. It seems that the problem is being debated on a sibling
thread. Sorry fo
Hi
Since I upgraded to FOP 0.91, the base URI to resolve url() seems to
be changed. Before (in FOP 0.20.5, but in 0.90 too, I think), I used a
URI relative to the FO file. Now, I have to use a URI relative to the
current directory.
Before: url('rsrc/logo.svg')
After: url('../<...>/
"J.Pietschmann" wrote:
> /[EMAIL PROTECTED] Temporary hack to compile, improve later */
> return new java.net.URL(uri).openStream();
> Don't expect a quick fix,Getting the necessary information
> for resolving relative URLs at this point will need some
> work.
Ok, thanks for pointing this out.
Hi
I have a little trouble to use a relative URI in the FOP config file.
Here is an excerpt:
I got the following:
pdf.Failed to embed fontfile: ../fonts/arial.ttf(URI could not be
resolved (no protocol: ../fonts/arial.ttf): ../font
find and correct it.
Thanks for the explanation, and best wishes to all,
--drkm
> On 24.12.2005 15:32:07 Florent Georges wrote:
> > Jeremias Maerki wrote:
> >
> > Hi
> >
> > > I'll see what I can do about it. Since the problem sits
> > > in
"J.Pietschmann" wrote:
> This is a FAQ:
> http://xmlgraphics.apache.org/fop/faq.html#fo-center-table-horizon
Oh, sorry for the noise. Thanks for pointing this out.
Regards,
--drkm
__
here an other way to center a table
on the page (on an 'fo:flow') with FOP 0.91?
Thanks for your help. Regards,
--drkm
drkm wrote:
> From Florent Georges Tue Dec 27 17:50:26 2005
> Date: Tue, 27 Dec 2005 17:50:26 +0100 (CET)
> From: Florent Georges <[EMAIL PROTECTED]>
Jeremias Maerki wrote:
Hi
> I'll see what I can do about it. Since the problem sits
> in the layout engine it's covered by the automated tests
> so no big danger to port the change. I'm not through
> testing for 0.91 anyway.
I just upgraded to 0.91 beta, and test my documents. All is workin
Jeremias Maerki wrote:
> I'll see what I can do about it. Since the problem sits
> in the layout engine it's covered by the automated tests
> so no big danger to port the change. I'm not through
> testing for 0.91 anyway.
Thanks all for your quick help. Anyway, I wait for the 0.91, and
I'll ke
Manuel Mall wrote:
> Thanks for the problem description and testcase which made
> it easy to reproduce and debug.
It's the minimum I can do when requesting help.
> As it turned out there was a problem with respect to lines
> who contained only a linefeed (no preceding text) and had
> a text-al
Andreas L Delmelle wrote:
> On Dec 22, 2005, at 14:25, Florent Georges wrote:
> > Is the newline expected?
> Yes. Writing (in a block with linefeed-treatment="preserve"):
> ...
> ...
> is the same as
> ...
...
Ok, thanks. Is it because the text nodes in bl
Hi
I have a strange behaviour with 'linefeed-treatment' set
to 'preserve' and 'text-align' set to 'center' with
FOP-0.90. Given the following FO:
http://www.w3.org/1999/XSL/Format";>
Leasing a ...
Hi
I didn't find trace of this bug in bugzilla, although I
guess it was already reported. It related to the treatment
of linefeeds. Given the following FO:
http://www.w3.org/1999/XSL/Format";>
Bla
bla
55 matches
Mail list logo
