Helge,
I looked at this bug report because I was looking into other things
related to DocBook and man pages. I think this is not a bug.
If you look at the file you attached with "less", you will see
characters such as "<FC>" and "<F6>". Those are the hexadecimal
values of Latin1 characters, not parts of UTF-8 characters. Maybe you
accidentally attached the wrong file; I don't know. That would
explain why there are no complaints when you try to convert this as a
Latin1 document though.
I am attaching a version of your document re-encoded as UTF-8 for you
to experiment with. I did not try to process it.
I also changed the "doctype" word on the first line to "DOCTYPE"; I
think it is always supposed to be upper-case even if some tools don't
complain.
Because this is a DocBook file, you could try giving the filename the
suffix ".xml" and insert this as a first line in the file to declare
its encoding as UTF-8:
<?xml version="1.0" encoding="UTF-8"?>
You might also need to modify the system identifier in the DOCTYPE line.
In summary, I think the problem is that the document you attached is
not a valid UTF-8 document. There might be other reasons why it is
also not a valid SGML document.
The "emacs" editor will recognize SGML documents as such if the
filename ends in ".sgml". I do not know how well it validates general
SGML files though. If you end the filename in ".xml", you can enable
Nxml mode in emacs. See
https://www.emacswiki.org/emacs/UsingNxmlModeWithDocBook for more
information. Note that some older emacs instructions might say you
need to download the Nxml package and install it for emacs, but recent
versions of emacs include it.
I do not know what other validation tools are available for general
SGML files on Debian, apart from xsltproc.
I am not the maintainer of this package, and DocBook 4.1 is very, very
old at this point, but I am posting this in case it helps you resolve
this bug. Hopefully, this is also enough information for you to
decide to close the bug.
Good luck,
Paul Hardy
<!DOCTYPE refentry PUBLIC "-//OASIS//DTD DocBook V4.1//EN" [
<!ENTITY dhfirstname "<firstname>FIXME</firstname>">
<!ENTITY dhsurname "<surname>Niedermeyer</surname>">
<!ENTITY dhdate "<date>FIXME 2009</date>">
<!ENTITY dhsection "<manvolnum>1</manvolnum>">
<!ENTITY dhemail "<email>[email protected]</email>">
<!ENTITY dhusername "Max Mustermann">
<!ENTITY dhucpackage "<refentrytitle>CHIASMUS</refentrytitle>">
<!ENTITY dhpackage "demo">
<!ENTITY debian "<productname>Debian</productname>">
<!ENTITY gnu "<acronym>GNU</acronym>">
<!ENTITY gpl "&gnu; <acronym>GPL</acronym>">
<!ENTITY demo "<command>&dhpackage;</command>">
]>
<refentry>
<refentryinfo>
<address>
&dhemail;
</address>
<author>
&dhfirstname; &dhsurname;
</author>
<copyright>
<year>FIXME 2009</year>
<holder>&dhusername;</holder>
</copyright>
&dhdate;
</refentryinfo>
<refmeta>
&dhucpackage;
&dhsection;
</refmeta>
<refnamediv>
<refname>&dhpackage;</refname>
<refpurpose>Demo for docbook-to-man problems</refpurpose>
</refnamediv>
<refsynopsisdiv>
<cmdsynopsis sepchar=" ">
&demo;
<arg choice="plain"> -hilfe</arg>
</cmdsynopsis>
<cmdsynopsis>
&demo;
<arg choice="plain"> -beispiel</arg>
</cmdsynopsis>
</refsynopsisdiv>
<refsect1>
<title>BESCHREIBUNG</title>
<para>
&demo; is some programme </para>
<para>
Für Hinweise zur Sicherheit siehe "HINWEISE", für erste Schritte siehe
"EINFÜHRUNG" und für weiter Anwendungsbeispiele "BEISPIELE".
Testing ß.
</para>
</refsect1>
<refsect1>
<title>OPTIONEN</title>
<para>
Zwischen einer Option und dem zugehörigen Parameter können, müssen aber keine
Leerzeichen stehen. Die Optionen können in beliebiger Reihenfolge angegeben
werden. Wird eine Option mehrfach angegeben, so wird nur das letzte Auftreten
der Option (bzw. der zugehörige Parameter) ausgewertet. Wildcards werden von
chiasmus nicht unterstützt.
</para>
<variablelist>
<varlistentry>
<term><option>-hilfe</option></term>
<listitem>
<para>
Gibt eine kurze Hilfe aus.
</para>
</listitem>
</varlistentry>
<varlistentry>
<term><option>-beispiel</option></term>
<listitem>
<para>
Gibt Beispiele zur Verwendung von Chiasmus aus.
</para>
</listitem>
</varlistentry>
<varlistentry>
<term><option>-m</option> <option>something</option></term>
<listitem>
<para>
some text
</para>
<para>
Beispiele:
</para>
<orderedlist numeration="loweralpha" continuation='restarts'>
<listitem>
<para>
a. This is something
</para>
</listitem>
<listitem>
<para>
b. Something else
</para>
</listitem>
<listitem>
<para>
c. Even more so
</para>
</listitem>
<listitem>
<para>
d. A fourth item
</para>
</listitem>
<listitem>
<para>
e. A fifth item
</para>
</listitem>
</orderedlist>
</listitem>
</varlistentry>
<varlistentry>
<term><option>-q</option> <option>something</option></term>
<listitem>
<para>
Does somthing more
</para>
<para>
Beispiele:
</para>
<orderedlist numeration="loweralpha" continuation='restarts'>
<listitem>
<para>
a. Should be a) (restarted)
</para>
</listitem>
<listitem>
<para>
b. Should be b)
<screen><prompt>%</prompt> demo something ...</screen>
</para>
</listitem>
</orderedlist>
<para>
Hinweis: Die Option -q braucht nicht mit angegeben zu werden. Das Kommando
<screen><prompt>%</prompt> demo something else </screen>
leistet dasselbe wie das Kommando in Beispiel a.
</para>
</listitem>
</varlistentry>
<varlistentry>
<term><option>-z</option> <option>Options</option></term>
<listitem>
<para>
FIXME
</para>
<para>
some text
</para>
<para>
Beispiele:
</para>
<orderedlist numeration='loweralpha' continuation='restarts'>
<listitem>
<para>
a. Should be again a) </para>
</listitem>
<listitem>
<para>
b. Should be again b) </para>
</listitem>
</orderedlist>
</listitem>
</varlistentry>
</variablelist>
</refsect1>
</refentry>
