Re: PNG resolution not resolved?
Jeremias Maerki wrote: Maybe your expectations are wrong: If you generate an image at say 72x72 pixels and set the resolution to 72 dpi, you get an image with an intrinsic size of exactly 1 inch. If you save it with 300dpi (but the image is still 72x72 pixels), the image'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 Georges http://www.fgeorges.org/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: PNG resolution not resolved?
Jeremias Maerki wrote: A short test with your back.png shows no problems on my machine (WinXP, Sun JVM 1.6.0_03 and Sun JVM 1.4.2_16). Thanks for the response. I am on Win XP SP 2, Sun JVM 1.6.0_01. It could be that on your machine, a ImageIO PNG codec is running that is 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 additional commands, e-mail: [EMAIL PROTECTED]
PNG resolution not resolved?
Hi, It seems that FOP 0.95 does not resolve correctly the resolution of the enclosed image. The resolution of this file is 300 dpi, but it seems FOP uses its default 72 dpi. If I save the image with 72 dpi, the result is ok. I can just use content-width=400% for now, or save 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/ inline: back.png- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Cell overflow: word too large
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 the first cell the second word goes on a new line: fo:root xmlns:fo=http://www.w3.org/1999/XSL/Format; fo:layout-master-set fo:simple-page-master master-name=main fo:region-body margin=25pt/ /fo:simple-page-master /fo:layout-master-set fo:page-sequence master-reference=main fo:flow flow-name=xsl-region-body fo:table font-family=Helvetica font-size=8pt width=239.75pt table-layout=fixed fo:table-column column-width=121pt/ fo:table-column column-width=118.75pt/ fo:table-body fo:table-row fo:table-cell border-style=solid border-width=0.25pt fo:block start-indent=3pt end-indent=3pt NIEUWE AUTOMOBIELMAATSCHAPPIJ/fo:block /fo:table-cell fo:table-cell border-style=solid border-width=0.25pt fo:block start-indent=3pt end-indent=3pt NIEUWE AUTOMOBIELMAATSCHAPPIJ/fo:block /fo:table-cell /fo:table-row /fo:table-body /fo:table /fo:flow /fo:page-sequence /fo:root Is it the expected behaviour? Is there a way to force breaking line even if the word is too large for the cell? Regards, --drkm ___ Découvrez une nouvelle façon d'obtenir des réponses à toutes vos questions ! Profitez des connaissances, des opinions et des expériences des internautes sur Yahoo! Questions/Réponses http://fr.answers.yahoo.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Cell overflow: word too large
Cheffe wrote: Since 0.93 on fo:block 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 only in a specific case (one cell is well formated, but the other is not, where the word to wrap is longer than the cell width). Regards, --drkm ___ Découvrez une nouvelle façon d'obtenir des réponses à toutes vos questions ! Profitez des connaissances, des opinions et des expériences des internautes sur Yahoo! Questions/Réponses http://fr.answers.yahoo.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Cell overflow: word too large
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 supplier, for example). Detecting all places where it could be interesting to insert such spaces and actually insert them could be very expensive (in both development time and processing time). Activating hyphenation should also do the trick, IIC. I didn't think to hyphenation. I just downloaded fop-hyph.jar and did a few tests. The result is quite good, but it seems to have a strange interaction between hyphenation and linefeeds when linefeed-treatment = preserve. I need to investigate a little bit further. Thanks for the answer. I know at least what I can expect and where to look now. Regards, --drkm ___ Découvrez une nouvelle façon d'obtenir des réponses à toutes vos questions ! Profitez des connaissances, des opinions et des expériences des internautes sur Yahoo! Questions/Réponses http://fr.answers.yahoo.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: 0.20.5 vs/ 0.92beta thread on XSL List
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 son interface révolutionnaire. http://fr.mail.yahoo.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: 0.20.5 vs/ 0.92beta thread on XSL List
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 the XSL List official archives. Lists at Gmane can choose to be read-only or if posting is allowed via Gmane. XSL List is read-only. So the only way to post to XSL List is to send an email to [EMAIL PROTECTED] But you have to subscribe to recieve the emails, of course. I wasn't clear. Sorry, my fault. I just posted your response to the list. Regards, --drkm ___ Découvrez une nouvelle façon d'obtenir des réponses à toutes vos questions ! Demandez à ceux qui savent sur Yahoo! Questions/Réponses http://fr.answers.yahoo.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
0.20.5 vs/ 0.92beta thread on XSL List
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 ___ Découvrez une nouvelle façon d'obtenir des réponses à toutes vos questions ! Demandez à ceux qui savent sur Yahoo! Questions/Réponses http://fr.answers.yahoo.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Error when using FOP embedded using Saxon for transformation
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. BTW, Mike released a snapshot of the SVN repository on the 29th of September. Maybe this fix the problem? See: http://sourceforge.net/mailarchive/message.php?msg_id=36968233 Regards, --drkm ___ Découvrez un nouveau moyen de poser toutes vos questions quel que soit le sujet ! Yahoo! Questions/Réponses pour partager vos connaissances, vos opinions et vos expériences. http://fr.answers.yahoo.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Extra fo:inline introduces extra new lines
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 fault, while simplifying the code to post). BTW, thanks to all FOP developers and fop-users contributors for your time. Regards, --drkm ___ Découvrez un nouveau moyen de poser toutes vos questions quelque soit le sujet ! Yahoo! Questions/Réponses pour partager vos connaissances, vos opinions et vos expériences. http://fr.answers.yahoo.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE : Re: RE : directly converting 'lt;' to html in .fo file
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);
xsl:transform
xmlns:xsl=http://www.w3.org/1999/XSL/Transform;
version=1.0
xsl:template match=/
xsl:value-of disable-output-escaping=yes
select=path/to/html-holding/
/xsl:template
/xsl:transform
2a. Convert that HTML to well-formed XML.
For that, you can use a tool like HTMLTidy. See the W3C
web site, or Google.
3. Replace the original data with the coverterd.
Use a modified identity transformation to include the
well-formed document:
xsl:transform
xmlns:xsl=http://www.w3.org/1999/XSL/Transform;
version=1.0
xsl:template match=@*|node()
xsl:copy
xsl:apply-templates select=@*|node()/
/xsl:copy
/xsl:template
xsl:template match=html-holding
xsl:copy-of select=document('converted.xml')/
/xsl:template
/xsl:transform
Any thoughts on the XSL commands to do this?
Such XSLT questions (as well as XPath questions BTW) would
be better asked on XSL List.
Regards,
--drkm
__
Do You Yahoo!?
En finir avec le spam? Yahoo! Mail vous offre la meilleure protection possible
contre les messages non sollicités
http://mail.yahoo.fr Yahoo! Mail
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
PDF document (when printed) doesn't fax correctly
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 sample of original document: http://www.fgeorges.org/tmp/fax-bug-sample.png Does someone knows a trick we could use (a different color, or whatever)? Or have we to just drop the grey color, and use a plain white background? Thanks in advance. Regards, --drkm ___ Yahoo! Mail réinvente le mail ! Découvrez le nouveau Yahoo! Mail et son interface révolutionnaire. http://fr.mail.yahoo.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Seperating xml and tempalte but using one file
Shamem Miah wrote: Hi fo:block font-size=12pt font-family=sans-serif /data/value/fo:block You can achive that with two transformations. The first to transform the above in: fo:block font-size=12pt font-family=sans-serif xsl:value-of select=[...]/data/value/ /fo:block and the later as usual, to produce the FO to pass to FOP. Regards, --drkm ___ Faites de Yahoo! votre page d'accueil sur le web pour retrouver directement vos services préférés : vérifiez vos nouveaux mails, lancez vos recherches et suivez l'actualité en temps réel. Rendez-vous sur http://fr.yahoo.com/set - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Seperating xml and tempalte but using one file
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 transformation:
xsl:transform
xmlns:xsl=http://www.w3.org/1999/XSL/Transform;
xmlns:fo=http://www.w3.org/1999/XSL/Format;
xmlns:x_=http://www.fgeorges.org/Transform/Alias;
version=2.0
xsl:namespace-alias stylesheet-prefix=x_
result-prefix=xsl/
xsl:template match=@*|node()
xsl:copy
xsl:apply-templates select=@*|node()/
/xsl:copy
/xsl:template
xsl:template match=fo:*/text()
!-- Try to set a variable, instead. --
x_:value-of select=doc('')/to-datas/{.}/
/xsl:template
/xsl:transform
It will transform the fo:* elements by wrapping their text nodes into
xsl:value-of elements. So you'll give an XSLT script. Then use this
script as usual, to produce the FO.
You'll have maybe to customize the template rule matching /,
depending on what your document looks like (is it an FO or XSLT
document?, etcetera).
Regards,
--drkm
___
Faites de Yahoo! votre page d'accueil sur le web pour retrouver directement vos
services préférés : vérifiez vos nouveaux mails, lancez vos recherches et
suivez l'actualité en temps réel.
Rendez-vous sur http://fr.yahoo.com/set
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: REGRESSION: embedded SVG support in 0.92beta compared to 0.91beta
Jeremias Maerki wrote: Hi Bug is filed against SAXON including patch: http://sourceforge.net/tracker/index.php?func=detailaid=1483350group_id=29872atid=397617 Let's see what happens. Michael seems to just have included your patch. See the full comment on the issue page. Thanks for having reported the issue. Regards, --drkm ___ Faites de Yahoo! votre page d'accueil sur le web pour retrouver directement vos services préférés : vérifiez vos nouveaux mails, lancez vos recherches et suivez l'actualité en temps réel. Rendez-vous sur http://fr.yahoo.com/set - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
table-body, border-width, and inherit
Hi Doesn't the following have to result in a table with a border of 1pt, and two rules of 0.25pt? fo:table border-style=solid border-width=1pt fo:table-column column-width=100pt/ fo:table-body border-width=0.25pt fo:table-row fo:table-cell border-bottom-style=solid fo:block fo:inlineLine 1/fo:inline /fo:block /fo:table-cell /fo:table-row fo:table-row fo:table-cell border-bottom-style=solid fo:block fo:inlineLine 2/fo:inline /fo:block /fo:table-cell /fo:table-row fo:table-row fo:table-cell fo:block fo:inlineLine 3/fo:inline /fo:block /fo:table-cell /fo:table-row /fo:table-body /fo:table Actually, the two rules are of 1pt. Is it expected? I thought that by inherit, the value was the one of the nearest ancestor with that value (well, the value in the parent, itself maybe inherit). So is the above result right or a bug? PS: I use FOP 0.92beta. Regards, --drkm ___ Faites de Yahoo! votre page d'accueil sur le web pour retrouver directement vos services préférés : vérifiez vos nouveaux mails, lancez vos recherches et suivez l'actualité en temps réel. Rendez-vous sur http://fr.yahoo.com/set - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: table-body, border-width, and inherit
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 ___ Faites de Yahoo! votre page d'accueil sur le web pour retrouver directement vos services préférés : vérifiez vos nouveaux mails, lancez vos recherches et suivez l'actualité en temps réel. Rendez-vous sur http://fr.yahoo.com/set - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: REGRESSION: embedded SVG support in 0.92beta compared to 0.91beta
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 ___ Faites de Yahoo! votre page d'accueil sur le web pour retrouver directement vos services préférés : vérifiez vos nouveaux mails, lancez vos recherches et suivez l'actualité en temps réel. Rendez-vous sur http://fr.yahoo.com/set - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: format-number incorrectly formatting number (fop 0.91beta)
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: xsl:value-of select='format-number(-34567890123456787.00,###,###.00 ;###,###.00CR)'/ This is not related to FOP, but to your XSLT processor. I suggest you to post either to the XSL List (fron Mulberrytech) or to the list of your XSLT processor. Regards, --drkm ___ Faites de Yahoo! votre page d'accueil sur le web pour retrouver directement vos services préférés : vérifiez vos nouveaux mails, lancez vos recherches et suivez l'actualité en temps réel. Rendez-vous sur http://fr.yahoo.com/set - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: guide me
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 ___ Nouveau : téléphonez moins cher avec Yahoo! Messenger ! Découvez les tarifs exceptionnels pour appeler la France et l'international. Téléchargez sur http://fr.messenger.yahoo.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: NPE
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). Well, AFAICT, it's not really empty from a SAX parser's point of view. It does contain a text-node, but this is completely ignored by FOP. The SAX characters() events are only handled for FOs that can contain #PCDATA. Mmh, I'm not sure to understand. The document contains some: fo:instream-foreign-object/ as well as some: fo:instream-foreign-object.../fo:instream-foreign-object I guess you only saw the later. Furthemore, if I understand right §6.6.6 (mmh, ok, born to be a problematic paragraph :-p): Contents: The fo:instream-foreign-object flow object has a child from a non-XSL namespace. The permitted structure of this child is that defined for that namespace. So it is required to an IFO to have a child element, isn't it? And to don't have non-whitespace #PCDATA. Right? So an FO validator would have to report an error for both the above IFOs, isn't it? PS: I based my validator on the RNC grammar provided by RenderX at URL:http://www.renderx.com/tools/validators.html. Regards, --drkm ___ Nouveau : téléphonez moins cher avec Yahoo! Messenger ! Découvez les tarifs exceptionnels pour appeler la France et l'international. Téléchargez sur http://fr.messenger.yahoo.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
NPE
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 have to
continue some work now and its not an error I find in real files).
I'm sorry too I had to delete the text from this file (it's maybe
harder to read).
Hope that helps. Regards,
--drkm
___
Nouveau : téléphonez moins cher avec Yahoo! Messenger ! Découvez les tarifs
exceptionnels pour appeler la France et l'international.
Téléchargez sur http://fr.messenger.yahoo.com?xml version=1.0 encoding=UTF-8?fo:root xmlns:xsl=http://www.w3.org/1999/XSL/Transform; xmlns:saxon=http://saxon.sf.net/; xmlns:xs=http://www.w3.org/2001/XMLSchema; xmlns:xdt=http://www.w3.org/2005/xpath-datatypes; xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance; xmlns:fo=http://www.w3.org/1999/XSL/Format; xmlns:wel=http://wel.inglease.be/v1.00/xsltTools; white-space-collapse=truefo:layout-master-setfo:simple-page-master master-name=masterNamePageMain0 page-height=845pt page-width=598pt margin-top=11.5pt margin-left=11.5pt margin-bottom=10pt margin-right=10ptfo:region-body margin-left=50pt margin-top=75pt margin-bottom=65pt margin-right=50pt/fo:region-before extent=76pt precedence=true/fo:region-after extent=100pt precedence=true/fo:region-start extent=52pt/fo:region-end extent=39pt//fo:simple-page-masterfo:simple-page-master master-name=masterNamePageTitle1 page-height=845pt page-width=598pt margin
-top=11.5pt margin-left=11.5pt margin-bottom=10pt margin-right=10ptfo:region-body margin-left=25pt margin-top=25pt margin-bottom=65pt margin-right=75pt/fo:region-before extent=76pt precedence=true/fo:region-after extent=100pt precedence=true/fo:region-start extent=52pt/fo:region-end extent=39pt//fo:simple-page-master/fo:layout-master-setfo:page-sequence master-reference=masterNamePageTitle1fo:static-content flow-name=xsl-region-beforefo:block color=#00 font-family=Helvetica Condensed font-size=8pt text-align=rightfo:inline.../fo:inline/fo:blockfo:block color=#00 font-family=Arial font-size=8pt text-align=rightfo:instream-foreign-object.../fo:instream-foreign-object/fo:block/fo:static-contentfo:static-content flow-name=xsl-region-afterfo:block-container position=absolute absolute-position=absolute top=50pt left=65pt height=64pt width=475ptfo:block span=none font-f
amily=Helvetica Condensed font-size=6pt background-color=transparent line-height=7ptfo:table border-collapse=separate width=100% table-layout=fixedfo:table-column column-width=175pt/fo:table-column column-width=85pt/fo:table-column column-width=115pt/fo:table-column column-width=100pt/fo:table-bodyfo:table-rowfo:table-cell display-align=beforefo:block linefeed-treatment=preserve text-align=leftfo:inline white-space-collapse=false...
fo:inline font-style=italic font-size=from-parent(font-size) - 1pt.../fo:inline
...
.../fo:inline/fo:block/fo:table-cellfo:table-cell display-align=beforefo:block linefeed-treatment=preserve text-align=center font-size=9ptfo:inline- fo:page-number//fo:page-number-citation ref-id=ending.page/ -/fo:inlinefo:inline white-space-collapse=false
/fo:inline/fo:block/fo:table-cellfo:table-cell display-align=beforefo:block//fo:table-cellfo:table-cell display-align=beforefo:block linefeed-treatment=preserve text-align=leftfo:inline white-space-collapse=false...
...
.../fo:inline/fo:block/fo:table-cell/fo:table-row/fo:table-body/fo:table/fo:block/fo:block-container/fo:static-contentfo:flow flow-name=xsl-region-bodyfo:block-container position=absolute absolute-position=absolute top=60pt left=45pt height=350pt width=448ptfo:block span=nonefo:table border-collapse=separate width=100% table-layout=fixedfo:table-column column-width=436pt/fo:table-bodyfo:table-row height=150ptfo:table-cell display-align=beforefo:block span=all text-align=centerfo:external-graphic src=url('{$ING.logo}')//fo:block/fo:table-cell/fo:table-rowfo:table-row height=50ptfo:table-cellfo:block//fo:table-cell/fo:table-rowfo:table-rowfo:table-cell border-style=solid border-width=1pt border-color=#00 color=#00 background-color=#cc padding-top=10pt padding-bottom=5ptfo:block font-family=Helvetica Condensed font-size=16pt text-align=center linefeed-tr
eatment=preservefo:inline font-weight=bold/fo:inline white-space-collapse=false
/fo:inlinefo:inline font-weight=bold.../fo:inlinefo:inline white-space-collapse=false
/fo:inlinefo:inline white-space-collapse=false
/fo:inlinefo:inline white-space-collapse=false
/fo:inlinefo:inline white-space-collapse=false
/fo:inline/fo:block/fo:table-cell/fo:table-row/fo:table-body/fo:table/fo:block/fo:block-container/fo:flow/fo:page-sequencefo:page-sequence master-reference=masterNamePageMain0fo:static-content
Re: Absolute 'file:' URI scheme bug on Windows?
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=381978view=rev Even simplified ;-) Regards, --drkm ___ Nouveau : téléphonez moins cher avec Yahoo! Messenger ! Découvez les tarifs exceptionnels pour appeler la France et l'international. Téléchargez sur http://fr.messenger.yahoo.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Absolute 'file:' URI scheme bug on Windows?
Manuel Mall 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(). So I can't really change the format of the
URI.
If I remember well, I gave also:
java.net.UnknownHostException: C
when trying to use a file in the D: drive (file:/D:/...). Maybe the
base URI? I'll try to test some combinations of base URIs, drives and
URI formats.
Thanks for your help. Regards,
--drkm
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.
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 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 first an UnknownHostException: C or a
FileNotFoundException?
Sorry for the delay, but I can't reproduce the error on my local
station, and I can't make tests on the server as easy as I want.
Here is the stderr:
Error with opening URL '/C:/test/logo.svg': C
java.net.UnknownHostException: C
Image not available: url('file:/C:/test/logo.svg')
Here are the JARs in the classpath:
apache-xmlgraphics-fop-091-beta.jar
apache-avalon-framework-4.2.0.jar
apache-xmlgraphics-batik-all-1.6.jar
apache-commons-io-1.1.jar
apache-commons-logging-1.0.4.jar
apache-serializer-2.7.0.jar
apache-xerces-2.7.0-xalan.jar
apache-xerces-2.7.0-xercesImpl.jar
xml-apis-1.0.b2.jar
And the sample FO:
?xml version=1.0 encoding=utf-8?
fo:root xmlns:fo=http://www.w3.org/1999/XSL/Format;
white-space-collapse=true
fo:layout-master-set
fo:simple-page-master master-name=master
page-height=845pt
page-width=598pt
fo:region-body margin-left=50pt
margin-top=50pt
margin-bottom=50pt
margin-right=50pt/
/fo:simple-page-master
/fo:layout-master-set
fo:page-sequence master-reference=master
fo:flow flow-name=xsl-region-body
fo:block padding-top=10pt
fo:external-graphic src=url('logo.svg')/
/fo:block
fo:block padding-top=10pt
fo:external-graphic
src=url('file:/C:/test/logo.svg')/
/fo:block
/fo:flow
/fo:page-sequence
/fo:root
On my local station, here is the content of the classpath, it may
be of interest:
fop-0.91beta.jar
avalon-framework-4.2.0.jar
batik-all-1.6.jar
commons-io-1.1.jar
commons-logging-1.0.4.jar
serializer-2.7.0.jar
xalan-2.7.0.jar
xercesImpl-2.7.1.jar
xml-apis-1.3.02.jar
And finally the JRE version on the server, then the two I tested
on
my station (where both are ok):
$ java -version
java version 1.4.2_06
Java(TM) 2 Runtime Environment, Standard Edition (build
1.4.2_06-b03)
Java HotSpot(TM) Client VM (build 1.4.2_06-b03, mixed mode)
$ java -version
java version 1.4.2_08
Java(TM) 2 Runtime Environment, Standard Edition (build
1.4.2_08-b03)
Java HotSpot(TM) Client VM (build 1.4.2_08-b03, mixed mode)
$ java -version
java version 1.5.0_06
Java(TM) 2 Runtime Environment, Standard Edition (build
1.5.0_06-b05)
Java HotSpot(TM) Client VM (build 1.5.0_06-b05, mixed mode,
sharing)
Thanks for your help. Regards,
--drkm
_
__ Nouveau : téléphonez moins cher avec Yahoo! Messenger !
Découvez les tarifs exceptionnels pour appeler la France et
l'international. Téléchargez sur http://fr.messenger.yahoo.com
-
To unsubscribe, e-mail:
[EMAIL PROTECTED]
For additional commands, e-mail:
[EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail:
[EMAIL PROTECTED]
___
Nouveau : téléphonez moins cher avec Yahoo! Messenger ! Découvez les tarifs
exceptionnels pour appeler la France et l'international.
Téléchargez sur http://fr.messenger.yahoo.com
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Absolute 'file:' URI scheme bug on Windows?
Hi
I'm using the following to access an SVG file on a Windows
server:
fo:external-graphic src=url('file:/C:/...')/
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.Image not available: url('file:/C:/.../xx.svg')
The problem is that this URI is generated by the XPath 2.0
function 'fn:resolve-uri()' (Saxon 8.6.1, but I think this
behaviour is herited from a standard Java class).
Which is wrong, which is right? FOP or Saxon?
Thanks for your help. Regards,
--drkm
___
Nouveau : téléphonez moins cher avec Yahoo! Messenger ! Découvez les tarifs
exceptionnels pour appeler la France et l'international.
Téléchargez sur http://fr.messenger.yahoo.com
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
RE: Absolute 'file:' URI scheme bug on Windows?
Florent Georges wrote:
I'm using the following to access an SVG file on a Windows
server:
fo:external-graphic src=url('file:/C:/...')/
Sorry, I forgot to specify the version I use: FOP 0.91beta.
Regards,
--drkm
___
Nouveau : téléphonez moins cher avec Yahoo! Messenger ! Découvez les tarifs
exceptionnels pour appeler la France et l'international.
Téléchargez sur http://fr.messenger.yahoo.com
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: Absolute 'file:' URI scheme bug on Windows?
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 ___ Nouveau : téléphonez moins cher avec Yahoo! Messenger ! Découvez les tarifs exceptionnels pour appeler la France et l'international. Téléchargez sur http://fr.messenger.yahoo.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Body overlapping over the footnotes
Chris Bowditch wrote: The problem appears obvious to me, look at your simple-page-master: fo:region-body margin-left=50pt margin-top=75pt margin-bottom=75pt margin-right=50pt / fo:region-before extent=76pt precedence=true / fo:region-after extent=100pt precedence=true / fo:region-start extent=52pt / fo:region-end extent=39pt / The size allowed for the region-after is 100pt, but your region-body only has a bottom margin of 75pt. Yes, indeed. Thanks for pointed this out. Change the bottom margin to 100pt and they will not overlap. Unfortunately, this doesn't solve the problem. Actually, this solve the problem in the simple example I have shown you. But not in the real document, thanks to Murphy. I post the real FO and PDF (with alphanumeric modified) resp. there: http://cjoint.com/?cirmeCeuif http://cjoint.com/?cirmBb6ffr http://cjoint.com/?cirm61QAdJ The last one is the FO, indented (not really the original FO, but more readable). Thanks in advance. Regards, --drkm ___ Nouveau : téléphonez moins cher avec Yahoo! Messenger ! Découvez les tarifs exceptionnels pour appeler la France et l'international. Téléchargez sur http://fr.messenger.yahoo.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Body overlapping over the footnotes
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 be that I didn't also check lists back when I did that. I'll look into it tomorrow. I don't exactly know the technical details, but I can imagine the source of the problem. And the solution below tends to confirm your intuition, IMHO. The immediate work-around would be to replace padding-top and padding-bottom with space-before and space-after (conditionality=retain) on the child elements of the list items. But that's an ugly hack. I better fix this. Sure. But it works. Hopefully: I have a deadline soon (all deadlines are soon ;-p). Because I'm using XSLT 2.0, I still have a clear work aroud: xsl:template match=/ xsl:variable name=first.pass xsl:apply-templates/ /xsl:variable xsl:variable name=second.pass xsl:apply-templates select=$first.pass mode=post.process/ /xsl:variable fo:root xsl:apply-templates select=$second.pass mode=fop.0.91beta.bug/ /fo:root /xsl:template xsl:template match=node()|@* mode=post.process ... /xsl:template xsl:template match=@*|node() mode=fop.0.91beta.bug xsl:copy xsl:apply-templates select=@*|node() mode=fop.0.91beta.bug/ /xsl:copy /xsl:template xsl:template match=fo:list-item mode=fop.0.91beta.bug xsl:copy xsl:apply-templates select=node()|@*[not(name() eq 'padding-bottom' or name() eq 'padding-top')] mode=fop.0.91beta.bug/ /xsl:copy /xsl:template xsl:template match=fo:list-item-label/*|fo:list-item-body/* mode=fop.0.91beta.bug xsl:variable name=top select=../../@padding-top/ xsl:variable name=bottom select=../../@padding-bottom/ xsl:copy xsl:if test=$top xsl:attribute name=space-before select=$top/ /xsl:if xsl:if test=$bottom xsl:attribute name=space-after select=$bottom/ /xsl:if xsl:apply-templates select=@*|node() mode=fop.0.91beta.bug/ /xsl:copy /xsl:template Thanks for this rapid solution. Regards, --drkm ___ Nouveau : téléphonez moins cher avec Yahoo! Messenger ! Découvez les tarifs exceptionnels pour appeler la France et l'international. Téléchargez sur http://fr.messenger.yahoo.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Base URI for url() (in fo:external-graphic)
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('../.../xsl/rsrc/logo.svg')
What's the correct behaviour?
Thanks for your help. Regards,
--drkm
___
Nouveau : téléphonez moins cher avec Yahoo! Messenger ! Découvez les tarifs
exceptionnels pour appeler la France et l'international.
Téléchargez sur http://fr.messenger.yahoo.com
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
How to use a relative URI in the config file (in 'renderer/fonts/font/@embed-url')
Hi I have a little trouble to use a relative URI in the FOP config file. Here is an excerpt: renderer mime=application/pdf fonts font metrics-url=../fonts/arial.xml embed-url=../fonts/arial.ttf font-triplet name=Arial style=normal weight=normal/ /font /fonts /renderer I got the following: pdf.Failed to embed fontfile: ../fonts/arial.ttf(URI could not be resolved (no protocol: ../fonts/arial.ttf): ../fonts/arial.ttf) I tried to use file://../, file://.././, etc., but no one works. The only one that works is an absolute one, but I really can't use this. Any idea? PS: I use FOP-0.91. Regards, --drkm ___ Nouveau : téléphonez moins cher avec Yahoo! Messenger ! Découvez les tarifs exceptionnels pour appeler la France et l'international. Téléchargez sur http://fr.messenger.yahoo.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: linefeed-treatment='preserve' and text-align='center' interaction
Jeremias Maerki wrote: That warning was added between 0.90 and 0.91. It basically says that you have a block-container whose contents together add up to a height (=block-progression-dimension) that is bigger than the block-container's content height. Yes. I did 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 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 working fine. But the following warning I never seen before: Part/page 1 overflows the available area in block-progression dimension. (fo:block-container, location: 1/1547) I'll need a bit further investigation. Anyway, thanks for the quick response, merry christmas and happy new year, --drkm Jeremias Maerki - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] ___ Nouveau : téléphonez moins cher avec Yahoo! Messenger ! Découvez les tarifs exceptionnels pour appeler la France et l'international. Téléchargez sur http://fr.messenger.yahoo.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Fw: RE: [xsl] FO: center a table
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 ___ Nouveau : téléphonez moins cher avec Yahoo! Messenger ! Découvez les tarifs exceptionnels pour appeler la France et l'international. Téléchargez sur http://fr.messenger.yahoo.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: linefeed-treatment='preserve' and text-align='center' interaction
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 working fine. But the following warning I never seen before: Part/page 1 overflows the available area in block-progression dimension. (fo:block-container, location: 1/1547) I'll need a bit further investigation. Anyway, thanks for the quick response, merry christmas and happy new year, --drkm ___ Nouveau : téléphonez moins cher avec Yahoo! Messenger ! Découvez les tarifs exceptionnels pour appeler la France et l'international. Téléchargez sur http://fr.messenger.yahoo.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: linefeed-treatment='preserve' and text-align='center' interaction
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 keep you informed. Regards, --drkm ___ Nouveau : téléphonez moins cher avec Yahoo! Messenger ! Découvez les tarifs exceptionnels pour appeler la France et l'international. Téléchargez sur http://fr.messenger.yahoo.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: linefeed-treatment='preserve' and text-align='center' interaction
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): fo:inline.../fo:inline fo:inline.../fo:inline is the same as fo:inline.../fo:inline fo:inline.../fo:inline Ok, thanks. Is it because the text nodes in blocks (between inlines) are part of the block, or because newlines are treated in a special way? Can you please point me where this is stated in the REC.? Thanks, --drkm ___ Nouveau : téléphonez moins cher avec Yahoo! Messenger ! Découvez les tarifs exceptionnels pour appeler la France et l'international. Téléchargez sur http://fr.messenger.yahoo.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
