<html>
<head>
<meta content="text/html; charset=utf-8" http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<div class="moz-cite-prefix">Hi Clément,<br>
<br>
Le 04/03/2016 12:48, Clément David a écrit :<br>
</div>
<blockquote
cite="mid:1457092104.2345.29.camel@scilab-enterprises.com"
type="cite">
<pre wrap="">Hi Samuel,
Le mardi 23 février 2016 à 21:19 +0100, Samuel Gougeon a écrit :
</pre>
<blockquote type="cite">
<pre wrap="">
So, just to remember: just use <xref> like the <link> tag, with providing a reference that is
internal to the page, instead of the reference to an external page :
<xref linkend="blabla">Option wb</xref>
...
<term id="blabla">"wb"</term>
will show a link Option wb that when ones click on it will go to the section of the page where the
term <term id="blabla">"wb"</term> appears.
That's all.
</pre>
</blockquote>
<pre wrap="">
Yep I confirm this behavior and posted [bug #14444]. This feature will alos let us improve
the current documentation by using this feature on all pages that cross-reference related features
(eg. almost every page through the "See also" section).
[bug #14444]: <a class="moz-txt-link-freetext" href="http://bugzilla.scilab.org/show_bug.cgi?id=14444">http://bugzilla.scilab.org/show_bug.cgi?id=14444</a></pre>
</blockquote>
<br>
Humm, i am not sure to understand what you mean about the expected
behavior / purpose of the <xref> tag.<br>
<br>
By the way, i am nor sure to clearly understand differences between
<xref> and <link>, and the initial answer<br>
from Calixte at the beginning of this thread does not clarifies
them. Even this is not clear in the Docbook user manual.<br>
<br>
The <link > tag may as well have an <i>endterm</i> attribute,
getting in the target the content to be displayed as the link,
turning the tag as an autoclosed one: <br>
<link linkend="id_of_target"
endterm="id_of_target_having_the_content_to_be_displayed_in_the_link"/><br>
<br>
So, the only difference that i can see -- according to Docbook -- is
that <xref> is <i>always</i> an autoclosed tag <br>
that can't be written <xref...>...</xref>. But in
Scilab, it is implemented exactly as a <link> needing a
</link>.<br>
<br>
So, <b>my first question is: Do you intend to make <link> and
<xref> different? And if yes, in which aspect?</b><br>
<br>
I was initially looking for a way to target a section of a page,
rather than the page (its top) itself.<br>
I tried the html syntax with an id in the target and #id in the
link, but this does not work. <br>
Then i found this <xref> tag, and its non-standard
implementation equal to the standard <link> one.<br>
<br>
Further tests show that, with the current implementation, if in a
"See also" section or wherever else <br>
one uses <link linkend="the_id">item</link> OR <xref
linkend="the_id">item</xref> AND<br>
<ul>
<li>a) "the_id" is an xml:id of a page, OR<br>
</li>
<li>b) "the_id" is the id of an element of the same page, OR<br>
</li>
<li>c) "the_id" is the id of an element of another page, <br>
</li>
</ul>
then the top of the page (a), or the element of the same or other
page (b) and c)) <br>
are already well targeted, in the helpbrowser as well as in HTML
files.<br>
<br>
Hence, i do not see anything specific to <xref> that should be
implemented about cross-referencing.<br>
<br>
The problems that i see are the following:<br>
<ul>
<li>the xml:id of a page and ids in pages are equally considered.
This may set some "unresolved" <br>
conflicts between ids. It would be better to have two distinct
levels of targeting, as in HTML, <br>
i.e. to be able to use a 2-level address id_page#id_element for
linkend/href values.<br>
<br>
</li>
<li>In the "See also" section or in any other part of a page of an
external module, <br>
<link> succeeds linking to a Scilab page<i> in the help
browser</i>, but fails to link to the <br>
online HTML Scilab page in its HTML version. This is already
reported, and should <br>
be quite easy to fix, since some Scilab online pages exist and
can be targeted.<br>
<br>
</li>
<li>In the "See also" section of an external module, <link>
pointing to Scilab pages are <br>
not followed by short descriptions of the related pages. This is
another reported bug.</li>
</ul>
<p>So, my last questions are :<br>
</p>
<ul>
<li><b>Do you intend to implement resolved addresses such as
page_id#item_id ?<br>
<br>
</b></li>
<li><b>Do you intend to implement the endterm attribute for
<link> ?<br>
</b><br>
</li>
<li>Don't you think that the <xref> tag is useless and
should be removed ?<br>
<br>
</li>
</ul>
<p>Best regards<br>
Samuel<br>
<br>
</p>
</body>
</html>