Re: basic-link internal-destination - problem

2005-10-18 Thread Jeremias Maerki
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

Re: height of instream-foreign-object

2005-10-18 Thread robert frapples
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

Re: basic-link internal-destination - problem

2005-10-18 Thread Jeremias Maerki
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

Re: height of instream-foreign-object

2005-10-18 Thread Andreas L Delmelle
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

Re: height of instream-foreign-object

2005-10-18 Thread JBryant
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