[Pkg-db-devel] Bug#258831: db4.2-doc: incorrect html syntax in docs, makes docs partly unreadable [#10600]
Gunter Ohrner
Gunter Ohrner <G.Ohrner@post.rwth-aachen.de>, 258831@bugs.debian.org
Mon, 12 Jul 2004 18:43:31 +0200
--Boundary-00=_z+r8Aq6GPhzzf4v
Content-Type: Text/Plain;
charset="iso-8859-15"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
=2D----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Am Montag, 12. Juli 2004 16:31 schrieben Sie:
> > Several HTML files, eg. the files describing the command line
> > utilities, contain incorrectly nested and closed tags which
> Can you give me specific details, and what should change? (Does
> <dl> require a closing phrase? Can you give me a diff for the
> document that makes it display correctly?)
Yes, of course. As I don't know what html standard your docs should conform=
to=20
(if any) I justed changed so much that it displayed correctly. It's still n=
o=20
valid html in the later html (HTML 4 and up) standards I know, though.
<p></p> isn't allowed to contain the block level element <dl> but the cause=
of=20
the mis-display were <p>'s directly within <dl> which is not allowed either.
A patch for db_archive.html is attached.
Greetings,
Gunter
=2D --=20
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
+ http://aachen.uni-dsl.de/ - Der direkte Draht in's Hochschulnetz! +
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Verence would rather cut his own leg off than put a witch in prison,=20
since it'd save trouble in the long run and probably be less painful. =20
-- (Terry Pratchett, Lords and Ladies)
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
+ PGP-verschl=FCsselte Mails bevorzugt! +
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
=2D----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)
iD8DBQFA8r/B0ORHvREo8l8RAhFpAKCOhfl5/u9cKliIqfKjS7koqEww1wCfRASY
GyReUKiQHjImS+gcw2Vez1w=3D
=3D6bF2
=2D----END PGP SIGNATURE-----
--Boundary-00=_z+r8Aq6GPhzzf4v
Content-Type: text/x-diff;
charset="iso-8859-15";
name="partly_fix.diff"
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
filename="partly_fix.diff"
--- db_archive_buggy.html 2004-07-12 18:04:13.000000000 +0200
+++ db_archive.html 2004-07-12 18:12:11.000000000 +0200
@@ -1,3 +1,4 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<!--$Id: db_archive.so,v 10.28 2002/11/13 21:49:24 bostic Exp $-->
<!--Copyright 1997-2003 by Sleepycat Software, Inc.-->
<!--All rights reserved.-->
@@ -28,22 +29,22 @@
database files), but they may then be deleted from the system to reclaim
disk space.</p>
<p>The options are as follows:</p>
-<p><dl compact>
-<p><dt><b>-a</b><dd>Write all pathnames as absolute pathnames, instead of relative to the
+<dl compact>
+<dt><b>-a</b><dd>Write all pathnames as absolute pathnames, instead of relative to the
database home directories.
-<p><dt><b>-d</b><dd>Remove log files that are no longer needed; no filenames are written.
+<dt><b>-d</b><dd>Remove log files that are no longer needed; no filenames are written.
Automatic log file removal is likely to make catastrophic recovery
impossible.
-<p><dt><b>-h</b><dd>Specify a home directory for the database environment; by
+<dt><b>-h</b><dd>Specify a home directory for the database environment; by
default, the current working directory is used.
-<p><dt><b>-l</b><dd>Write out the pathnames of all the database log files, whether or not
+<dt><b>-l</b><dd>Write out the pathnames of all the database log files, whether or not
they are involved in active transactions.
-<p><dt><b>-P</b><dd>Specify an environment password. Although Berkeley DB utilities overwrite
+<dt><b>-P</b><dd>Specify an environment password. Although Berkeley DB utilities overwrite
password strings as soon as possible, be aware there may be a window of
vulnerability on systems where unprivileged users can see command-line
arguments or where utilities are not able to overwrite the memory
containing the command-line arguments.
-<p><dt><b>-s</b><dd>Write the pathnames of all the database files that need to be archived
+<dt><b>-s</b><dd>Write the pathnames of all the database files that need to be archived
in order to recover the database from catastrophic failure. If any of
the database files have not been accessed during the lifetime of the
current log files, db_archive will not include them in this
@@ -53,8 +54,8 @@
ignore them. When <a href="../utility/db_recover.html">db_recover</a> is run, any files to which the
log refers that are not present during recovery are assumed to have been
deleted and will not be recovered.</p>
-<p><dt><b>-V</b><dd>Write the library version number to the standard output, and exit.
-<p><dt><b>-v</b><dd>Run in verbose mode, listing the checkpoints in the log files as they
+<dt><b>-V</b><dd>Write the library version number to the standard output, and exit.
+<dt><b>-v</b><dd>Run in verbose mode, listing the checkpoints in the log files as they
are reviewed.
</dl>
<p>Log cursor handles (returned by the <a href="../api_c/log_cursor.html">DB_ENV->log_cursor</a> method) may have open
--Boundary-00=_z+r8Aq6GPhzzf4v--