Bug#944331: debian-policy: Spurious space after dash in plain text output
Control: reassign -1 python3-sphinx
Control: retitle -1 Spurious space after dash in plain text output
Control: affects -1 debian-policy
Guillem Jover <guillem@debian.org> writes:
> Noticed the following instances of spurious spaces after a dash, while
> skimming over the plain text policy document:
This seems to be some sort of bug in Sphinx, possibly in its override of
textwrap.TextWrapper. I can't reproduce this problem with TextWrapper
directly. Reassigning to Sphinx.
In the original RST source, there are no spaces after the hyphens in these
examples.
> - index, rendered as:
> ,---
> * 7.8. Additional source packages used to build the binary -
> "Built- Using"
> `---
> - chapter 4, footnote [11], rendered as:
> ,---
> Another common way to do this is for "build" to depend on
> "build- stamp" and to do nothing else, and for the "build-stamp"
> `---
> - chapter 6, footnote [2], rendered as:
> ,---
> This can happen if the new version of the package no longer
> pre- depends on a package that had been partially upgraded.
> `---
> - chapter 7, footnote [1], rendered as:
> ,---
> While "Build-Depends", "Build-Depends-Indep" and "Build-
> Depends- Arch" permit the use of alternative dependencies, these
> `---
> - chapter 8, footnote [7], rendered as:
> ,---
> This wording allows the development files to be split into
> several packages, such as a separate architecture-independent
> libraryname- headers, provided that the development package
> `---
> - chapter 8, footnote [13], rendered as:
> ,---
> separate "substvars" files for each binary package and calling
> "dpkg- gencontrol" with the appropriate flags.
> `---
--
Russ Allbery (rra@debian.org) <https://www.eyrie.org/~eagle/>
Reply to: