doc: Don't use the HTML <ul> but the DocBook equivalent
Of course, this confused gtk-doc. (cherry picked from commit be512104784a9200a2e98a75d16a56e3897a8845)
This commit is contained in:
parent
f1f1e876f1
commit
5c12c36c58
1 changed files with 8 additions and 7 deletions
|
@ -66,13 +66,14 @@
|
|||
* Compared to using the #CoglMatrix api directly to track many
|
||||
* related transforms, these can be some advantages to using a
|
||||
* #CoglMatrixStack:
|
||||
* <ul>
|
||||
* <li>Faster equality comparisons of transformations</li>
|
||||
* <li>Efficient comparisons of the differences between arbitrary
|
||||
* transformations</li>
|
||||
* <li>Avoid redundant arithmetic related to common transforms</li>
|
||||
* <li>Can be more space efficient (not always though)</li>
|
||||
* </ul>
|
||||
* <itemizedlist>
|
||||
* <listitem>Faster equality comparisons of transformations</listitem>
|
||||
* <listitem>Efficient comparisons of the differences between arbitrary
|
||||
* transformations</listitem>
|
||||
* <listitem>Avoid redundant arithmetic related to common transforms
|
||||
* </listitem>
|
||||
* <listitem>Can be more space efficient (not always though)</listitem>
|
||||
* </itemizedlist>
|
||||
*
|
||||
* For reference (to give an idea of when a #CoglMatrixStack can
|
||||
* provide a space saving) a #CoglMatrix can be expected to take 72
|
||||
|
|
Loading…
Reference in a new issue