Re: DOCBOOK-APPS: [Fwd: Re: Proposal: Image Tag Conventions]

[Bob Stayton <bobs@caldera.com>]

> Subject: DOCBOOK-APPS: [Fwd: Re: Proposal: Image Tag Conventions]
> 
> Hi folks, does this look like a bug in the XSL sheets for screenshot? 
> If the explanation isn't clear enough, let me know and I'll provide some
> more details.
> 	Greg
> 
> 
> 
> There is one minor problem with this: you can not refer to <screenshot>
> using <xref>. If you try, you get error message 
> 
> No template named "screenshot" exists in the context named "title" in
> the "en" localization.
> Don't know what gentext to create for xref to: "screenshot", ("id")
> 
> and the HTML output will contain link to the screenshot looking like <a
> href="documenturl#id">???</a>
 
I don't think this is a bug in the XSL stylesheets.
The xref element is supposed to generate the text
for the link, typically the title or number of the target
element.  But what do you expect the generated text to
say in the case of a screenshot?  It has neither a title
nor a number.  It might have a <caption> but that
element can have complex structure and would be a bit
dangerous to insert as hot text.

Isn't this situation also the case with mediaobject (your second
option)?

 
> Thus, we either need to put <screenshot> inside <figure> wrapper (if we
> want it to be numbered as "Figure *.*") - which is becoming rather
> cumbersome - or use <ulink> to refer to it, e.g.  
> 
> ...shown in <ulink linkend="id">screenshot</ulink> below

I think you mean <link> here, not <ulink>.  
That would certainly work.

bobs
Bob Stayton                                 400 Encinal Street
Publications Architect                      Santa Cruz, CA  95060
Technical Publications                      voice: (831) 427-7796
Caldera International, Inc.                 fax:   (831) 429-1887
                                            email: bobs@caldera.com