[liblouis-liblouisxml] [liblouis commit] r46 - trunk/doc
- From: codesite-noreply@xxxxxxxxxx
- To: liblouis-liblouisxml@xxxxxxxxxxxxx
- Date: Mon, 22 Dec 2008 14:14:34 +0000
Author: christian.egli@xxxxxxxxxxxxxx
Date: Mon Dec 22 06:11:06 2008
New Revision: 46
Modified:
trunk/doc/liblouis-guide.texi
Log:
Remove '-' from opcode anchor names to generate nicer html output.
Modified: trunk/doc/liblouis-guide.texi
==============================================================================
--- trunk/doc/liblouis-guide.texi (original)
+++ trunk/doc/liblouis-guide.texi Mon Dec 22 06:11:06 2008
@@ -25,21 +25,21 @@
@c Opcode.
@macro opcode{name, args}
@opcodeindex \name\
-@anchor{\name\-opcode}
+@anchor{\name\ opcode}
@item \name\ \args\
@end macro
@macro doubleOpcode{name1, args1, name2, args2}
@opcodeindex \name1\
@opcodeindex \name2\
-@anchor{\name1\-opcode}
-@anchor{\name2\-opcode}
+@anchor{\name1\ opcode}
+@anchor{\name2\ opcode}
@item \name1\ \args1\
@itemx \name2\ \args2\
@end macro
@macro opcoderef{name}
-@code{\name\} opcode (@pxref{\name\-opcode,\name\,@code{\name\}})
+@code{\name\} opcode (@pxref{\name\ opcode,\name\,@code{\name\}})
@end macro
@copying
@@ -703,7 +703,7 @@
The order of the various types of opcodes or table entries is
important. Character-definition opcodes should come first. However, if
the optional @code{display} opcode is used
-(@pxref{display-opcode,display,@code{display}}) it should precede
+(@pxref{display opcode,display,@code{display}}) it should precede
character-definition opcodes. Braille-indicator opcodes should come
next. Translation opcodes should follow. The @code{context} opcode is
a translation opcode, even though it is considered along with the
@@ -911,8 +911,8 @@
More than one @code{noletsign} opcode can be used. This is equivalent
to a single entry containing all the letters. In addition, if a single
letter, such as @samp{a} in English, is defined as a @code{word}
-(@pxref{word-opcode,word,@code{word}}) or @code{largesign}
-(@pxref{largesign-opcode,largesign,@code{largesign}}), it will be
+(@pxref{word opcode,word,@code{word}}) or @code{largesign}
+(@pxref{largesign opcode,largesign,@code{largesign}}), it will be
treated as though it had also been specified in a @code{noletsign}
entry.
@@ -1496,7 +1496,7 @@
@section The Context and Multipass Opcodes
@table @code
-@anchor{context-opcode}
+@anchor{context opcode}
@opcodeindex context
@opcodeindex pass2
@opcodeindex pass3
For a description of the software and to download it go to
http://www.jjb-software.com
Other related posts:
- » [liblouis-liblouisxml] [liblouis commit] r46 - trunk/doc - codesite-noreply
