diff options
author | jfbu <2589111+jfbu@users.noreply.github.com> | 2021-12-07 08:49:06 +0100 |
---|---|---|
committer | jfbu <2589111+jfbu@users.noreply.github.com> | 2021-12-09 18:12:29 +0100 |
commit | ccd2c83f2f4c133856b488c982ece198b6bd96ae (patch) | |
tree | c5119aca3c2dee7a32f2f1a0111576efac9234a9 /doc/development/tutorials/examples/autodoc_intenum.py | |
parent | 8ad49613a89264a9c60840a05f40709f47b324c8 (diff) | |
download | sphinx-git-ccd2c83f2f4c133856b488c982ece198b6bd96ae.tar.gz |
Add \sphinxhyphenin{inline,parsed}literal for customizability
Whether or not to allow linebreaks is matter of debate because user of
pdf can not reflow the displayed text, and overfull lines may lead to
loss of data beyond page border.
Since Sphinx 1.5, inline literals allow linebreaks after the characters
".", ",", ";", "?", "!", "/" and "\" (cf the inlineliteralwraps key of
latex_elements['sphinxsetup']).
With pdflatex the dash "-" does not allow a linebreak when used with a
monospace font (btw the dash is escaped to \sphinxhyphen{} which expands
back to a dash). But this failed with xelatex, so previous commits
ensured nobreak behaviour by redefining \sphinxhyphen to be
\sphinxhyphennobreak when encountered in inline and parsed literals.
This commit adds \sphinxhyphenin{inline,parsed}literal macros which
default to \sphinxhyphennobreak and thus allow to customize how the
dashes from sources will behave in such contexts in pdf output.
Diffstat (limited to 'doc/development/tutorials/examples/autodoc_intenum.py')
0 files changed, 0 insertions, 0 deletions