Re: basic-link internal-destination - problem
Looks like you hit a bug in FOP Trunk. I'll need to investigate this a bit more closely. I will get back to you. For the fop-devs: The internal-destination is properly set on the area tree but the PDFRenderer doesn't find the right pageReference in renderInlineParent() and thus skips generating the PDFLink object. Maybe there's a general problem with forward references there. On 18.10.2005 12:33:34 Sven wrote: Hi there, i read about FOP's problem, not being able to display leaders co as links. In my case i have just simple text that is used as an internal hyperlink. FOP renders the page successfully without any warning about missing referenced IDs, so i have to assume everything works fine. But indeed none of the links is clickable. I am using the latest trunk from repository (revision 325900). Am i missing something important? Thanks for help :) ?xml version=1.0 encoding=utf-8? fo:root xmlns:fo=http://www.w3.org/1999/XSL/Format; fo:layout-master-set fo:simple-page-master margin=4.5cm page-width=21cm page-height=29.7cm master-name=titlepage fo:region-body / /fo:simple-page-master fo:simple-page-master margin=2.5cm page-width=21cm page-height=29.7cm master-name=default fo:region-body margin-bottom=1cm margin-top=1cm / /fo:simple-page-master /fo:layout-master-set fo:page-sequence master-reference=titlepage fo:flow flow-name=xsl-region-body fo:block space-after=12pt space-before=4em font-weight=bold font-size=14pt font-family=Helvetica fo:basic-link internal-destination=Einleitung Inhaltsverzeichnis /fo:basic-link /fo:block fo:list-block line-height=1.5em font-size=12pt font-family=Times fo:list-item fo:list-item-label end-indent=label-end() fo:block1./fo:block /fo:list-item-label fo:list-item-body start-indent=body-start() fo:block fo:basic-link internal-destination=Einleitung Einleitung /fo:basic-link fo:leader leader-length.optimum=100% leader-pattern=dots / fo:page-number-citation ref-id=Einleitung / /fo:block /fo:list-item-body /fo:list-item fo:list-item fo:list-item-label end-indent=label-end() fo:block2./fo:block /fo:list-item-label fo:list-item-body start-indent=body-start() fo:block fo:basic-link internal-destination=Zusammenfassung und Ausblick Zusammenfassung und Ausblick /fo:basic-link fo:leader leader-length.optimum=100% leader-pattern=dots / fo:page-number-citation ref-id=Zusammenfassung und Ausblick / /fo:block /fo:list-item-body /fo:list-item /fo:list-block /fo:flow /fo:page-sequence fo:page-sequence master-reference=default fo:flow flow-name=xsl-region-body fo:block space-after=0.5em space-before=1em id=Einleitung font-weight=bold font-size=14pt font-family=Helvetica 1. Einleitung /fo:block fo:block text-align=justify font-size=12pt font-family=Times Obwohl die agentenorientierte Softwareentwicklung im vergangenen /fo:block /fo:flow /fo:page-sequence fo:page-sequence master-reference=default fo:flow flow-name=xsl-region-body fo:block space-after=0.5em space-before=1em id=Zusammenfassung und Ausblick font-weight=bold font-size=14pt font-family=Helvetica 2. Zusammenfassung und Ausblick /fo:block fo:block text-align=justify font-size=12pt font-family=Times Darüber hinaus soll ein Ausblick auf weitere Integrationsmöglichkeiten gemacht werden. /fo:block /fo:flow /fo:page-sequence /fo:root Jeremias Maerki - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: height of instream-foreign-object
On 10/17/05, Andreas L Delmelle [EMAIL PROTECTED] wrote: I'm not sure I'm getting the point completely. Why do you insist on creating separate instream-foreign-objects for the different characters in the first place? IMO, the problem would practically solve itself if you could put all the text inside one i-f-o, no? The effect you get right now is that of a different block being created for each i-f-o, the default height of which is always the line-height (1.2em IIC). AFAICT, the only way to manipulate the height would be to specify a different font-size/line-height for each created block --but then again, this seems somewhat suboptimal. I think you'll fare far better with putting all of the characters inside one single instream-foreign-object. I can't use a single instream-foreign-object because I have no idea how many letters there are, so I have no idea what the height should be. Using line-height=0.8em is giving me good results though. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: basic-link internal-destination - problem
I've done a change that should fix the bug for you. Would you please update your working copy and retry? Please let me know if it works. Thanks for preparing the example FO file in the first place! That helped a lot. This is the fix: http://svn.apache.org/viewcvs?rev=326133view=rev On 18.10.2005 13:00:25 Jeremias Maerki wrote: Looks like you hit a bug in FOP Trunk. I'll need to investigate this a bit more closely. I will get back to you. For the fop-devs: The internal-destination is properly set on the area tree but the PDFRenderer doesn't find the right pageReference in renderInlineParent() and thus skips generating the PDFLink object. Maybe there's a general problem with forward references there. On 18.10.2005 12:33:34 Sven wrote: Hi there, i read about FOP's problem, not being able to display leaders co as links. In my case i have just simple text that is used as an internal hyperlink. FOP renders the page successfully without any warning about missing referenced IDs, so i have to assume everything works fine. But indeed none of the links is clickable. I am using the latest trunk from repository (revision 325900). Am i missing something important? Thanks for help :) snip/ Jeremias Maerki - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: height of instream-foreign-object
On Oct 18, 2005, at 14:08, robert frapples wrote: On 10/17/05, Andreas L Delmelle [EMAIL PROTECTED] wrote: The effect you get right now is that of a different block being created for each i-f-o, the default height of which is always the line-height (1.2em IIC). AFAICT, the only way to manipulate the height would be to specify a different font-size/line-height for each created block --but then again, this seems somewhat suboptimal. I think you'll fare far better with putting all of the characters inside one single instream-foreign-object. I can't use a single instream-foreign-object because I have no idea how many letters there are, so I have no idea what the height should be. Using line-height=0.8em is giving me good results though. I see. Still, even if you don't know how many letters there will be, you can still use one instream-foreign-object. I'd even say that you *do* now the number of characters, since you start from a full string which you split into separate chars. All you'd need to do is determine the string-length and set content-height/block-progression- dimension accordingly. FWIW... HTH! Cheers, Andreas - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: height of instream-foreign-object
This sounds much like a problem I had some time back, wherein I needed to make a small-caps font without using an actual small-caps font. Recalling that a typographer friend once told me that the small caps is really an all caps font with the lower-case letters set to 5/8 the size of the upper-case letters, I wrote a recursive template in XSLT 1.0 to produce the desired effect. For that project, I was working in HTML, so I used span elements. I didn't want to use a span element for each character, so I grouped them by case (upper or lower). I suspect you have an application that would benefit from something similar, with the i-f-o elements replacing the span elements. Jay Bryant Bryant Communication Services (presently consulting at Synergistic Solution Technologies) Andreas L Delmelle [EMAIL PROTECTED] 10/18/2005 11:15 AM Please respond to fop-users@xmlgraphics.apache.org To fop-users@xmlgraphics.apache.org cc Subject Re: height of instream-foreign-object On Oct 18, 2005, at 14:08, robert frapples wrote: On 10/17/05, Andreas L Delmelle [EMAIL PROTECTED] wrote: The effect you get right now is that of a different block being created for each i-f-o, the default height of which is always the line-height (1.2em IIC). AFAICT, the only way to manipulate the height would be to specify a different font-size/line-height for each created block --but then again, this seems somewhat suboptimal. I think you'll fare far better with putting all of the characters inside one single instream-foreign-object. I can't use a single instream-foreign-object because I have no idea how many letters there are, so I have no idea what the height should be. Using line-height=0.8em is giving me good results though. I see. Still, even if you don't know how many letters there will be, you can still use one instream-foreign-object. I'd even say that you *do* now the number of characters, since you start from a full string which you split into separate chars. All you'd need to do is determine the string-length and set content-height/block-progression- dimension accordingly. FWIW... HTH! Cheers, Andreas - 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]
