"Jose' Matos" <[EMAIL PROTECTED]> schrieb am 17.05.04 16:29:31:
> 
> In 1.3.4:
> 
>  <para>
> <anchor id="first-par">blah blah...
>   </para>
> 
> In 1.4cvs:
>   <para  id = "first-par">
> <!-- anchor id="first-par" -->blah blah...
>   </para>
> 

I haven't ever used id's in para's, but might work, why not? This will have to be 
checked. If it works, it will enable setting xrefs not to anchors, but at least to a 
position "not far away" from a hypothetical, perfectly positioned anchor.

 
> For sections and any other paragraph that you can set from menu that is 
> correct, but for table and figures what we have now is:
> 
> <table>
> <title id="someid">...</title>
> ....
> </table>
> 
> Instead of
> <table id="someid">
> <title>...</title>
> ....
> </table>
> 
> Is that OK with you?
> 

No. I am not even sure if an id in the title is semantically correct for the DocBook 
SGML DTD - from the "feeling" of it, I would say no. Anyway, I need the id in the 
table element (or equation, inlineequation etc. element), because I want to use xrefs 
to a table (equation, inlineequation and so on), not to a title. Sematically, you 
never point to a title, rather to an element which might also have a title.

>   Now the anchor id is always transfered to its parent element. This only 
> happens for the first, all other are ignored.
>  

Good. Can't you determine which anchor comes from a "title" setting in the .lyx file 
and which not? Actually, only anchors that are due to titles need to be transfered 
into the element as id's. Other anchors are not relevant to our discussion here.

>   I forgot about equation and inline equation, but here it is easy as there 
> is only one id. :-)
> 
>   I will do it soon. If not I will beg for help to André. ;-)
> 

Fine. Tell me when you are ready, I have more stuff.  :-D

O.K., I just could not resist: while you are looking at equation and inlineequation, 
have a look at:

http://www.karakas-online.de/forum/viewtopic.php?t=860

and make some thoughts for a future discussion. This cost me the whole weekend and 
made me backstep to 1.2.0.  I will open a new thread about it when we are ready, but 
you can of course answer in that thread too. ;-)

Chris

-- 
Regards

Chris Karakas
http://www.karakas-online.de

Reply via email to