Re: Maintenance release: improvements to basic-link

[Karen Lease]

Hi all,

I haven't seen anything about the next maintenance release for about a 
week now, but I noticed that there had been some discussion about 
basic-link problems.
In the meantime, I have improved the basic-link positioning and also 
made it work for external-graphic and foreign-inline-object, since I 
needed it for a project at work. It now works correctly when links are 
inside blocks and tables with before and/or after padding and borders; 
it also works inside list items in tables. The X positioning is corrected.
Nothing else seems to be broken. :-)

I've also changed the default behavior to make all the words into a 
single link rectangle; the current behavior can be forced by defining 
the system property links.merge to no.

If there are no objections, I will commit this to the maintenance branch.

-Karen

J.Pietschmann wrote:

 Hi all,
 we should think about getting 0.20.5 out of the door.
 Yes, I know I'm behind with the doc, I really promise to
 get it ready this weekend...
 
 As for the Bugs to be fixed, what should get in?
 Choices:
SNIP/
 3. Harder stuff
 - Links for non-text inlines(tried and failed: the
   link was misplaced, I think I know why but may still
   need some time)
 - Links in static content (no idea)
SNIP/
 J.Pietschmann
 
 
 -
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, email: [EMAIL PROTECTED]
 
 



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]

[Fwd: Regarding your comment about inline building on xsl-editors]

[Peter B. West]

  Fopdevs,

For those of you who are not subscribed to the xsl-editors list.

Comments please.  I've been trying to track down the original discussion 
that triggered my request ot the editors, in hopes of being able to 
enter into the mind-set of inline-building again, but at the moment I'm 
just confused.

Peter

 Original Message 
Subject: Regarding your comment about inline building on xsl-editors
Date: Wed, 18 Sep 2002 18:37:10 -0500
From: Paul Grosso [EMAIL PROTECTED]
To: Peter B. West [EMAIL PROTECTED]
CC: [EMAIL PROTECTED]



Peter,

Thank you for your comment to [EMAIL PROTECTED] archived at
http://lists.w3.org/Archives/Public/xsl-editors/2002AprJun/0031

We determined that the spec required some corrections to address
your question.  We would appreciate it if you could let us know
if you feel that our proposed changes sufficiently address your
questions.

The following is our proposed disposition of your above comment:

---

We propose the following corrections to the spec:

1. the Areas portion of 6.9.2 [fo:basic-link] be changed from:


  The fo:basic-link formatting object generates one or more normal
  inline-areas.  The fo:basic-link returns these areas, any
  page-level-out-of-line areas, and any reference-level-out-of-line
  areas returned by the children of the fo:basic-link.

to:

  The fo:basic-link formatting object generates one or more normal
  inline-areas.  The fo:basic-link returns these areas,
  together with any normal block-areas,
  page-level-out-of-line areas, and reference-level-out-of-line
  areas returned by the children of the fo:basic-link.


2. The same changes should be made to 6.6.2 [fo:bidi-override] and 6.6.7
  [fo:inline], which have the same difficulty.


3. In section 4.7.3 [Inline-building] the following phrase
   (that describes the subject of the ordering constraints):

  the normal and/or anchor inline-areas
  returned by the child formatting objects,

should be changed to:

  the normal and/or anchor inline-areas
  and normal block-areas
  returned by the child formatting objects,

---

Please Reply (cc-ing [EMAIL PROTECTED]) if you wish to make
an objection to our resolution.

Thank you for your interest in XSL.

Paul Grosso for the XSL FO Subgroup of the XSL WG 




-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]