Bob Stayton <[EMAIL PROTECTED]>, 2007-08-17 13:39 -0700:

> The anchor is coming from the template named informal.object in 
> html/formal.xsl, which calls the template named "anchor".  Starting in 
> version 1.73.0, this was changed from:
>
> <xsl:call-template name="anchor"/>
>
> to:
>
> <xsl:call-template name="anchor">
>  <xsl:with-param name="conditional" select="0"/>
> </xsl:call-template>
>
> When the "conditional" parameter is set to 1 (the default), then an id is 
> output only when the element has one.  When set to 0, then an id is always 
> output (generated if necessary).
>
> I'm not sure why the parameter was changed in 1.73.0.

My fault. I changed it in r6952 to get the "dbfunclist" processing
instruction to work as expected. But I hadn't anticipated it would
have this effect, so I think I probably need to revert this change
for 1.73.1

  --Mike

> ----- Original Message ----- From: "Sam Steingold" <[EMAIL PROTECTED]>
> To: <[email protected]>
> Sent: Friday, August 17, 2007 6:10 AM
> Subject: [docbook-apps] gensym IDs for informal*
>
>> I noticed that recently informaltables and informalexamples started to
>> get gensym IDs:
>>
>> <div class="informaltable"><a id="id3042995"></a><table  .....
>>
>> why?
>> I don't like this because this creates spurious diffs.
>> I cannot always avoid this because some informaltables are in reused
>> entities:
>>
>> <!ENTITY foo '<informaltable>...</informaltable>'>
>> ....
>> &foo;
>> ...
>> &foo;
>>
>> and IDs must be unique.
>>
>> I was using informal* objects specifically to avoid them being mentioned
>> in any auto-generated list, so there seems to be no reason to assign
>> them gensym IDs.
>>
>> thanks.
>>
>> Sam.

-- 
Michael(tm) Smith
http://people.w3.org/mike/
http://sideshowbarker.net/

Attachment: smime.p7s
Description: S/MIME cryptographic signature

Reply via email to