RE: fo:leader weird output (again) ;o)
I do apologise. I've unfirewalled port 8080. I hadn't realised that it was set up like that. -Original Message- From: laurent marot [mailto:[EMAIL PROTECTED] Sent: 09 March 2003 17:43 To: [EMAIL PROTECTED] Subject: Re: fo:leader weird output (again) ;o) sorry but url doesn't work when i click submit button - Original Message - From: Rob Staveley (Tom) [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Sunday, March 09, 2003 6:34 PM Subject: RE: fo:leader weird output (again) ;o) Thank you so much! I followed your recommendations and http://coolbox.seseit.com/~rob/fop.0.20.5rc2.using-index.3.html looks good to me with 0.20.5rc2 -Original Message- From: J.Pietschmann [mailto:[EMAIL PROTECTED] Sent: 09 March 2003 11:29 To: [EMAIL PROTECTED] Subject: Re: fo:leader weird output (again) ;o) Rob Staveley (Tom) wrote: In the same vein... I'm trying to put together a catalogue index, which is dependent on fo:leader. I'm also getting a ragged right-hand margin from 0.20.5rc2 (see to GET from http://coolbox.seseit.com/~rob/fop.0.20.5rc2.html), but when I used the last of yesterday's snapshot from the CVS repository (xml-fop_20030309052748.tar.gz) the output looks worse rather than better (sorry I've not got a link for this). The problem is, the lines are correctly aligned during layout, in the PDF renderer the (912) strings have exactly the same x-position and area width. I can only guess something weird happens with the space calculation between the leader and the word on the line end. Also , the space at the block end is occasionally a problem. As a workaround: - Use leader-alignment=reference-area. This guarantees the leaders end at the same x-position if the followig word has the same length as on the line before. It also looks better. - Write your XSLT so that no extra space occurs at the end of the line, i.e. ...080)/fo:inline/fo:block instead of ...080)/fo:inline /fo:block This looks already much better. J.Pietschmann - 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] - 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]
RE: fo:leader weird output (again) ;o)
In the same vein... I'm trying to put together a catalogue index, which is dependent on fo:leader. I'm also getting a ragged right-hand margin from 0.20.5rc2 (see to GET from http://coolbox.seseit.com/~rob/fop.0.20.5rc2.html), but when I used the last of yesterday's snapshot from the CVS repository (xml-fop_20030309052748.tar.gz) the output looks worse rather than better (sorry I've not got a link for this). I therefore wonder if I'm doing something stupid. My link has got my XML source and XSL... I was wondering if some kind soul could eye-ball the XSL to see if there is something I can do to improve matters, or if I should hang back and wait for fo:leader to be sorted out by the maestros? -Original Message- From: J.Pietschmann [mailto:[EMAIL PROTECTED] Sent: 04 March 2003 22:02 To: [EMAIL PROTECTED] Subject: Re: fo:leader weird output (again) ;o) Clay Leeds wrote: When you say this bug is fixed in CVS do you mean that it's fixed in the maintenance branch (i.e., the soon-to-be-released 0.20.5/0.20.5rc3 version) Yes. There is a CHANGES and an archive for the commit messages at http://marc.theaimsgroup.com/?l=fop-cvs J.Pietschmann - 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]
Re: fo:leader weird output (again) ;o)
Rob Staveley (Tom) wrote: In the same vein... I'm trying to put together a catalogue index, which is dependent on fo:leader. I'm also getting a ragged right-hand margin from 0.20.5rc2 (see to GET from http://coolbox.seseit.com/~rob/fop.0.20.5rc2.html), but when I used the last of yesterday's snapshot from the CVS repository (xml-fop_20030309052748.tar.gz) the output looks worse rather than better (sorry I've not got a link for this). The problem is, the lines are correctly aligned during layout, in the PDF renderer the (912) strings have exactly the same x-position and area width. I can only guess something weird happens with the space calculation between the leader and the word on the line end. Also , the space at the block end is occasionally a problem. As a workaround: - Use leader-alignment=reference-area. This guarantees the leaders end at the same x-position if the followig word has the same length as on the line before. It also looks better. - Write your XSLT so that no extra space occurs at the end of the line, i.e. ...080)/fo:inline/fo:block instead of ...080)/fo:inline /fo:block This looks already much better. J.Pietschmann - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: fo:leader weird output (again) ;o)
J.Pietschmann wrote: something weird happens with the space calculation between the leader and the word on the line end. Ouch, stipid thinko: the area with the dots from the leader was assigned the leader length, rather than it's real word length. Also, some smace for the difference had to be inserted. This is corrected now. J.Pietschmann - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: fo:leader weird output (again) ;o)
Thank you so much! I followed your recommendations and http://coolbox.seseit.com/~rob/fop.0.20.5rc2.using-index.3.html looks good to me with 0.20.5rc2 -Original Message- From: J.Pietschmann [mailto:[EMAIL PROTECTED] Sent: 09 March 2003 11:29 To: [EMAIL PROTECTED] Subject: Re: fo:leader weird output (again) ;o) Rob Staveley (Tom) wrote: In the same vein... I'm trying to put together a catalogue index, which is dependent on fo:leader. I'm also getting a ragged right-hand margin from 0.20.5rc2 (see to GET from http://coolbox.seseit.com/~rob/fop.0.20.5rc2.html), but when I used the last of yesterday's snapshot from the CVS repository (xml-fop_20030309052748.tar.gz) the output looks worse rather than better (sorry I've not got a link for this). The problem is, the lines are correctly aligned during layout, in the PDF renderer the (912) strings have exactly the same x-position and area width. I can only guess something weird happens with the space calculation between the leader and the word on the line end. Also , the space at the block end is occasionally a problem. As a workaround: - Use leader-alignment=reference-area. This guarantees the leaders end at the same x-position if the followig word has the same length as on the line before. It also looks better. - Write your XSLT so that no extra space occurs at the end of the line, i.e. ...080)/fo:inline/fo:block instead of ...080)/fo:inline /fo:block This looks already much better. J.Pietschmann - 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]
Re: fo:leader weird output (again) ;o)
sorry but url doesn't work when i click submit button - Original Message - From: Rob Staveley (Tom) [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Sunday, March 09, 2003 6:34 PM Subject: RE: fo:leader weird output (again) ;o) Thank you so much! I followed your recommendations and http://coolbox.seseit.com/~rob/fop.0.20.5rc2.using-index.3.html looks good to me with 0.20.5rc2 -Original Message- From: J.Pietschmann [mailto:[EMAIL PROTECTED] Sent: 09 March 2003 11:29 To: [EMAIL PROTECTED] Subject: Re: fo:leader weird output (again) ;o) Rob Staveley (Tom) wrote: In the same vein... I'm trying to put together a catalogue index, which is dependent on fo:leader. I'm also getting a ragged right-hand margin from 0.20.5rc2 (see to GET from http://coolbox.seseit.com/~rob/fop.0.20.5rc2.html), but when I used the last of yesterday's snapshot from the CVS repository (xml-fop_20030309052748.tar.gz) the output looks worse rather than better (sorry I've not got a link for this). The problem is, the lines are correctly aligned during layout, in the PDF renderer the (912) strings have exactly the same x-position and area width. I can only guess something weird happens with the space calculation between the leader and the word on the line end. Also , the space at the block end is occasionally a problem. As a workaround: - Use leader-alignment=reference-area. This guarantees the leaders end at the same x-position if the followig word has the same length as on the line before. It also looks better. - Write your XSLT so that no extra space occurs at the end of the line, i.e. ...080)/fo:inline/fo:block instead of ...080)/fo:inline /fo:block This looks already much better. J.Pietschmann - 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] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: fo:leader weird output (again) ;o)
Simon,
I have found good success with using a table for my XSL-FO table of contents
output. It makes lining up the leader lines and page numbers much easier. It
is not wholly elegant, but it works great.
Mark Dudley
Xerox Corporation
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: Tuesday, March 04, 2003 12:59 PM
To: [EMAIL PROTECTED]
Subject: Re: fo:leader weird output (again) ;o)
I come again on this problem.
J.Pietschmann's advices helped me to use fo:leader (and the
page-number-citation) well,
but there is still a problem on using a non-proportionnal-font (Helvetica
here) with the fo:leader tag.
Here's an example of the output :
http://www.tatouage.fr/temp/fop_user_example.gif
Again, any ideas on a way to resolve this problem would be greatly
appreciated.
Please note that I don't want to use a proportionnal (like Courier) font
in my Table of Content, cause I have some graphical obligation.
Many thanks,
Simon
Well.
1. Which FOP version are you using?
I'm using the 0.20.5rc2 version of FOP, since I had some problem with the
markers with the last official release 0.20.4, which ere corrected in this
candidate.
[white-space-collapse=false].
2. Don't use this.
Yep, you're right ! This tag was outputing some stranges spaces ... !
3. Use text-align=justify text-align-last=justify
Didn't know about the text-align-last attribute ! Thanks ! :)
[fo:leader attributes]
4. Don't use this this way. It's probably best to leave
the defaults (min=0, opt=6pt, max=100%)
You're right again, I'm now using it into a table with the default values,
it's working great !
5. What's wrong with fo:page-number-citation ref-id={SOUSTHEME}/?
Right right right ! ... I'm sometime so complicated.
Also, it is usually more informative to post FO snippets
rather than XSLT snippets. The best way is to post a small,
self-contained FO document.
I'll send the FO output next time. Thanks for your answers, they were very
effective, once again !
Simon
-
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]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: fo:leader weird output (again) ;o)
[EMAIL PROTECTED] wrote: Please note that I don't want to use a proportionnal (like Courier) font in my Table of Content, cause I have some graphical obligation. The problem is not caused by the font, it is caused by the problem that FOP has to reserve space for the page numbers at a time when the numbers are not yet known (Bug #1130). This is already fixed in CVS. J.Pietschmann - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: fo:leader weird output (again) ;o)
J.Pietschmann wrote: [EMAIL PROTECTED] wrote: Please note that I don't want to use a proportionnal (like Courier) font in my Table of Content, cause I have some graphical obligation. The problem is not caused by the font, it is caused by the problem that FOP has to reserve space for the page numbers at a time when the numbers are not yet known (Bug #1130). This is already fixed in CVS. J.Pietschmann When you say this bug is fixed in CVS do you mean that it's fixed in the maintenance branch (i.e., the soon-to-be-released 0.20.5/0.20.5rc3 version) or what I understand is the re-design version (i.e. the not-so-soon-to-be-released-but-depends-on-definition-of-soon 1.0 version)? Or am I missing something, and there's a-version-being-talked-about-and-I-just-don't-have-a-clue version? ;-) -- Clay Leeds - [EMAIL PROTECTED] Web Developer - Medata, Inc. - http://www.medata.com PGP Public Key: https://mail.medata.com/pgp/cleeds.asc - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: fo:leader weird output (again) ;o)
Clay Leeds wrote: When you say this bug is fixed in CVS do you mean that it's fixed in the maintenance branch (i.e., the soon-to-be-released 0.20.5/0.20.5rc3 version) Yes. There is a CHANGES and an archive for the commit messages at http://marc.theaimsgroup.com/?l=fop-cvs J.Pietschmann - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
