atom feed8 messages in org.oasis-open.lists.docbook-appsRe: [docbook-apps] print output, id v...
FromSent OnAttachments
Dave PawsonOct 18, 2003 11:52 am 
Bob StaytonOct 18, 2003 1:24 pm 
Dave PawsonOct 19, 2003 2:28 am 
Bob StaytonOct 20, 2003 5:14 am 
Dave PawsonOct 20, 2003 9:04 am 
Bob StaytonOct 20, 2003 10:36 am 
David TolpinOct 21, 2003 1:53 am 
Bob StaytonOct 21, 2003 10:07 am 
Subject:Re: [docbook-apps] print output, id values
From:Bob Stayton (bo@sco.com)
Date:Oct 20, 2003 5:14:18 am
List:org.oasis-open.lists.docbook-apps

On Sun, Oct 19, 2003 at 10:32:13AM +0100, Dave Pawson wrote:

At 12:39 18/10/2003 -0700, Bob Stayton wrote:

On Sat, Oct 18, 2003 at 07:53:48PM +0100, Dave Pawson wrote:

From 'the sage'

http://www.sagehill.net/docbookxsl/XrefPageNums.html

I note that my use of <link isn't being translated into page numbers.

As that section says, link elements don't generate page numbers. I suspect it because link text is arbitrary and page number references may not fit in. Seems like it could be an option, however.

Since the id of the target is available, it wouldn't be hard to get the page number Bob, but I don't think it would be much use, since I've provided the text for the link. I found that moving the id value to the parent resolved the links.

Is there any guidance (tdg perhaps?) as to what makes good / bad endpoints for links?

Hmm, not that I know of. According to the DTD, any element with an ID can logically be the end point of a cross reference. So it comes down to what the stylesheets actually support.

Less bothered about that, since I'm using xep with hot links (how to make them visible?)

Color?

yes. I'm hoping its a param.

There is an attribute set named 'xref.properties' that you can use. It is applied to link, olink, ulink, and xref text in FO output.