aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorMark Loeser <halcy0n@gentoo.org>2006-03-09 18:18:30 +0000
committerMark Loeser <halcy0n@gentoo.org>2006-03-09 18:18:30 +0000
commitbd0c29664f835fef571ca7abf27bd68e236cf8d2 (patch)
treed8eda2c70ab537cd18349ba81298c4c9156344e0
parentAdd some more uri's (diff)
downloaddevmanual-bd0c29664f835fef571ca7abf27bd68e236cf8d2.tar.gz
devmanual-bd0c29664f835fef571ca7abf27bd68e236cf8d2.tar.bz2
devmanual-bd0c29664f835fef571ca7abf27bd68e236cf8d2.zip
Use a definition list instead of a table
git-svn-id: svn+ssh://svn.gentoo.org/var/svnroot/devmanual/trunk@19 176d3534-300d-0410-8db8-84e73ed771c3
-rw-r--r--keywording/text.xml88
1 files changed, 42 insertions, 46 deletions
diff --git a/keywording/text.xml b/keywording/text.xml
index a7effc3..b583568 100644
--- a/keywording/text.xml
+++ b/keywording/text.xml
@@ -36,52 +36,48 @@ KEYWORDS="x86 sparc mips ~ppc ~ppc-macos -ia64"
The different levels of keyword are:
</p>
-<table>
- <tr>
- <th>Keyword</th>
- <th>Meaning</th>
- </tr>
- <tr>
- <ti>
- <c>arch</c> (<c>x86</c>, <c>ppc-macos</c>)
- </ti>
- <ti>
- Both the package version <e>and</e> the ebuild are widely tested, known to work
- and not have any serious issues on the indicated platform.
- </ti>
- </tr>
- <tr>
- <ti>
- <c>~arch</c> (<c>~x86</c>, <c>~ppc-macos</c>)
- </ti>
- <ti>
- The package version and the ebuild are believed to work and do not have any
- known serious bugs, but more testing is required before the package version
- is considered suitable for <c>arch</c>.
- </ti>
- </tr>
- <tr>
- <ti>
- No keyword
- </ti>
- <ti>
- If a package has no keyword for a given arch, it means it is not known
- whether the package will work, or that insufficient testing has occurred for
- <c>~arch</c>.
- </ti>
- </tr>
- <tr>
- <ti>
- <c>-arch</c> (<c>-x86</c>, <c>-ppc-macos</c>)
- </ti>
- <ti>
- The package version will not work on the arch. This could be caused by badly
- written code (for example, non-64-bit or endian clean code), relying upon
- particular hardware (for example, a BIOS querying tool would not work on
- non-BIOS architectures) or binary only packages.
- </ti>
- </tr>
-</table>
+<dl>
+ <dt>
+ <c>arch</c> (<c>x86</c>, <c>ppc-macos</c>)
+ </dt>
+ <dd>
+ <p>
+ Both the package version <e>and</e> the ebuild are widely tested, known to work
+ and not have any serious issues on the indicated platform.
+ </p>
+ </dd>
+ <dt>
+ <c>~arch</c> (<c>~x86</c>, <c>~ppc-macos</c>)
+ </dt>
+ <dd>
+ <p>
+ The package version and the ebuild are believed to work and do not have any
+ known serious bugs, but more testing is required before the package version
+ is considered suitable for <c>arch</c>.
+ </p>
+ </dd>
+ <dt>
+ No keyword
+ </dt>
+ <dd>
+ <p>
+ If a package has no keyword for a given arch, it means it is not known
+ whether the package will work, or that insufficient testing has occurred for
+ <c>~arch</c>.
+ </p>
+ </dd>
+ <dt>
+ <c>-arch</c> (<c>-x86</c>, <c>-ppc-macos</c>)
+ </dt>
+ <dd>
+ <p>
+ The package version will not work on the arch. This could be caused by badly
+ written code (for example, non-64-bit or endian clean code), relying upon
+ particular hardware (for example, a BIOS querying tool would not work on
+ non-BIOS architectures) or binary only packages.
+ </p>
+ </dd>
+</dl>
<p>
The <c>-*</c> keyword is special. It is used to indicate package versions which are