Your message dated Wed, 11 Dec 2019 17:26:07 -0800
with message-id
<CAPQicOwc6vMjbPC=gfqmrp1edd_waqmcwpnjowzwmxkipa2...@mail.gmail.com>
and subject line a2x: closing old bug
has caused the Debian Bug report #787325,
regarding /usr/bin/a2x: asciidoc files with same subsection-titles results in
broken docbook-xml
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
787325: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=787325
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: asciidoc
Version: 8.6.9-3
Severity: normal
File: /usr/bin/a2x
Dear Maintainer,
if you create a simple asciidoc document in lang=de with multiple sections and
subsections, and the subsections uses the title "Zusammenfassung", than a2x
generates broken docbook xml with missed title of theses subsections,
because it interprets the title "Zusammenfassung" as "abstract" and
generates a <abstract />-node, which is wrong.
The problem is related to /etc/asciidoc/lang-de.conf and could occur in
other languages, too.
Example:
-- snip --
:doctype: article
:lang: de
:encoding: utf-8
testdocument
============
== section1 ==
=== Zusammenfassung ===
in subsection of section1
== section2 ==
=== Zusammenfassung ===
in subsection of section2
-- snap --
The resulting XML looks like:
-- snip --
<?xml version="1.0" encoding="utf-8"?>
<!DOCTYPE article PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN"
"http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd";>
<?asciidoc-toc?>
<?asciidoc-numbered?>
<article lang="de">
<articleinfo>
<title>testdocument</title>
</articleinfo>
<section id="_section1">
<title>section1</title>
<abstract id="_zusammenfassung">
<simpara>in subsection of section1</simpara>
</abstract>
</section>
<section id="_section2">
<title>section2</title>
<abstract id="_zusammenfassung_2">
<simpara>in subsection of section2</simpara>
</abstract>
</section>
</article>
-- snap --
-- System Information:
Debian Release: 8.0
APT prefers proposed-updates
APT policy: (500, 'proposed-updates'), (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 3.16.0-4-amd64 (SMP w/2 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) (ignored: LC_ALL
set to de_DE.UTF-8)
Shell: /bin/sh linked to /bin/bash
Init: systemd (via /run/systemd/system)
Versions of packages asciidoc depends on:
ii python 2.7.9-1
pn python:any <none>
Versions of packages asciidoc recommends:
ii dblatex 0.3.5-2
ii docbook-utils 0.6.14-3
ii libxml2-utils 2.9.1+dfsg1-5
ii xmlto 0.0.25-2
Versions of packages asciidoc suggests:
ii source-highlight 3.1.7-1+b1
ii vim-addon-manager 0.5.3
-- Configuration Files:
/etc/asciidoc/docbook-xsl/epub.xsl changed [not included]
/etc/asciidoc/wordpress.conf a71a56ba11aad0f6e080a91ca0de681a [Errno 2] Datei
oder Verzeichnis nicht gefunden: u'/etc/asciidoc/wordpress.conf
a71a56ba11aad0f6e080a91ca0de681a'
-- no debconf information
--- End Message ---
--- Begin Message ---
Hi,
As this is by design and given how few support asciidoc has, I'd
recommend just go ahead and use asciidoctor instead. It supports those
use case and has become the reference for the asciidoc language over
this python implementation.
Joseph
--- End Message ---
