File: refentry.xml

package info (click to toggle)
docbook-defguide 2.0.17%2Bsvn9912-2
  • links: PTS, VCS
  • area: main
  • in suites: bullseye, buster
  • size: 93,432 kB
  • ctags: 299
  • sloc: xml: 396,482; perl: 4,471; python: 879; makefile: 150; sh: 80
file content (57 lines) | stat: -rw-r--r-- 1,401 bytes parent folder | download | duplicates (8)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
<refentry id="glossentry.element">
<?dbhtml filename="glossentry.html"?>
<refentryinfo>
<pubdate>$Date$</pubdate>
<releaseinfo>$Revision$</releaseinfo>
</refentryinfo>

<refmeta>
<indexterm><primary>elements</primary>
<secondary>glossentry</secondary></indexterm>
<refentrytitle>glossentry</refentrytitle>
<refmiscinfo>Element</refmiscinfo>
</refmeta>
<refnamediv>
<refname>glossentry</refname>
<refpurpose>&glossentry.purpose;</refpurpose>
</refnamediv>

&glossentry.synopsis.gen;
<refsect1 condition='ref.description'><title>Description</title>

<para>
<sgmltag>GlossEntry</sgmltag> is a wrapper around a glossary term and its
definition.
</para>

<refsect2><title>Processing expectations</title>
<para>
&format.block; Glossary entries are usually formatted to highlight the
terms and definitions, frequently in a style similar to 
<sgmltag>VarListEntry</sgmltag>s.
</para>
</refsect2>


&glossentry.parents.gen;
&glossentry.children.gen;
</refsect1>
<refsect1 condition='ref.elem.attrdesc'><title>Attributes</title>
<variablelist>
<varlistentry><term>sortas</term>
<listitem>
<para>
<sgmltag class='attribute'>SortAs</sgmltag> specifies the string by which the 
element's content is to be sorted. If unspecified, the proper content
is used.
</para>
</listitem>
</varlistentry>
</variablelist>
</refsect1>
<refsect1><title>Examples</title>

&glossentry.example.seealso.gen;
</refsect1>
</refentry>