On Thu, Mar 29, 2012 at 10:53 PM, Bob Stayton <[email protected]> wrote:
> It is also the case that the 'generate.id.attributes' feature is not yet
> fully implemented in the stylesheets. Some elements generate an id, but
> others still generate a named anchor instead. I'd like to finish that
> feature before the next release.
>
> Bob Stayton
> Sagehill Enterprises
> [email protected]
>
>
> ----- Original Message ----- From: "Kirill Churin" <[email protected]>
> To: <[email protected]>
> Sent: Thursday, March 29, 2012 6:53 AM
> Subject: Re: [docbook-apps] xml:id on certain DocBook elements doesn't
> produce id's in HTML output
>
>
>
> On Thu, Mar 29, 2012 at 7:23 PM, Jirka Kosek <[email protected]> wrote:
>>
>> On 29.3.2012 14:31, Kirill Churin wrote:
>>>
>>> Hello list, why doesn't xml:id on such elements as <td> or
>>> <screenshot> produce id's on corresponding elements in HTML output?
>>
>>
>> There is no 1:1 mapping between DocBook and HTML elements. IDs in HTML
>> output are created only when there is reference to element. If natural
>> ID is missing in DocBook source then it is automatically created in HTML.
>>
>> Why do you need IDs on your HTML elements?
>>
>> Jirka
>>
>> --
>> ------------------------------------------------------------------
>> Jirka Kosek e-mail: [email protected] http://xmlguru.cz
>> ------------------------------------------------------------------
>> Professional XML consulting and training services
>> DocBook customization, custom XSLT/XSL-FO document processing
>> ------------------------------------------------------------------
>> OASIS DocBook TC member, W3C Invited Expert, ISO JTC1/SC34 member
>> ------------------------------------------------------------------
>>
>
> Exactly for that reason, I need to make a link to them, i.e.:
>
> <screenshot xml:id="some-screen" xreflabel="Nice screen">
> <mediaobject>
> <imageobject>
> <imagedata fileref="screen.png" />
> </imageobject>
> </mediaobject>
> </screenshot>
>
> <para>Look at the <xref linkend="some-screen" /> to see it's
> awesomeness.</para>
>
> --
> Kirill Churin
> Jabber: [email protected]
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
Could you suggest any workarounds I can use now, please?
--
Kirill Churin
Jabber: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
