Skip to content

Added support for processing the 'xref' elements #60

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
Mar 2, 2017
Merged

Added support for processing the 'xref' elements #60

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
bccc3a1
Added support for processing DocBook 'xref' elements.
claudius108 Mar 27, 2015
1f42d24
Replaced some 'ulink' elements pointing within the document with 'xref'
claudius108 Mar 27, 2015
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
20 changes: 10 additions & 10 deletions data/lucene.xml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -405,9 +405,9 @@ order by ft:score($sect) descending return $sect</synopsis>
<para>Sometimes you may want to define different Lucene indexes on the same set of elements, e.g.
to use a different analyzer. eXist-db allows to name a certain index using the <option>field</option>
attribute:</para>
<synopsis language="xquery"><![CDATA[<text field="title" qname="title" analyzer="en"/>]]></synopsis>
<para>Such an index is called <option>named index</option>. See <ulink url="#query-a-named-index">Query a Named Index</ulink> on how to query the
<option>named indexes</option>.</para>
<synopsis language="xquery">&lt;text field="title" qname="title" analyzer="en"/&gt;</synopsis>
<para>Such an index is called <option>named index</option>. See <xref linkend="query-a-named-index"/> on how to query the
<option>named indexes</option>.</para>
</section>
</section>
<section>
Expand Down Expand Up @@ -438,7 +438,7 @@ return $m</programlisting>
module.</para>
<section id="query-a-named-index">
<title>Query a Named Index</title>
<para>To query a named index (see <ulink url="#named-indexes">Defining Fields</ulink>), use the <function>ft:query-field($fieldName, $query)</function> instead of
<para>To query a named index (see <xref linkend="named-indexes"/>), use the <function>ft:query-field($fieldName, $query)</function> instead of
<function>ft:query</function>:</para>
<synopsis language="xquery">ft:query-field("title", "xml")</synopsis>
<para>
Expand Down Expand Up @@ -704,11 +704,11 @@ return
a document, containing information which does not exist in the XML as such.</para>
<para>The field indexes are not configured via <filename>collection.xconf</filename>. Instead we add
fields programmatically from an XQuery (which could be run via a trigger):</para>
<programlisting language="xquery"><![CDATA[ft:index("/db/demo/test.xml", <doc>
<field name="title" store="yes">Indexing</field>
<field name="author" store="yes">Me</field>
<field name="date" store="yes">2013</field>
</doc>)]]></programlisting>
<programlisting language="xquery">ft:index("/db/demo/test.xml", &lt;doc&gt;
&lt;field name="title" store="yes"&gt;Indexing&lt;/field&gt;
&lt;field name="author" store="yes"&gt;Me&lt;/field&gt;
&lt;field name="date" store="yes"&gt;2013&lt;/field&gt;
&lt;/doc&gt;)</programlisting>
<para>The <option>store</option> attribute indicates that the fields content should be stored as a string.
Without this attribute, the content will be indexed for search, but you won't be able to retrieve the contents.
</para>
Expand All @@ -722,4 +722,4 @@ return
<synopsis language="xquery">ft:remove-index("/db/demo/test.xml")</synopsis>
</section>
</chapter>
</book>
</book>
2 changes: 2 additions & 0 deletions modules/docbook.xql
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -172,6 +172,8 @@ declare %private function docbook:to-html($nodes as node()*) {
<a href="{$node/@url}" target="_blank">{docbook:process-children($node)}</a>
else
<a href="{$node/@url}">{docbook:process-children($node)}</a>
case element(xref) return
<a href="#{$node/@linkend}">{root($node)/*//*[@id = $node/@linkend]/title/text()}</a>
case element(note) return
<div class="alert alert-success">
{
Expand Down