[docutils:patches] #205 [manpage] Change macros for literal block to avoid warnings from groff 1.23

engelbert gruber via Docutils-develop <[email protected]>
Newsgroups gmane.text.docutils.devel
Message-ID </p/docutils/patches/205/bea1711b028ab36347830cceb6cb85691a163dd8.patches@docutils.p.sourceforge.net>
- **status**: open --> closed-fixed
- **Comment**:

already applied in prior version 



---

**[patches:#205] [manpage] Change macros for literal block to avoid warnings from groff 1.23**

**Status:** closed-fixed
**Group:** None
**Labels:** manpage 
**Created:** Sat Jul 29, 2023 05:05 PM UTC by Dmitry Shachnev
**Last Updated:** Wed Aug 09, 2023 10:25 AM UTC
**Owner:** nobody
**Attachments:**

- [manpage_literal_block.patch](https://sourceforge.net/p/docutils/patches/205/attachment/manpage_literal_block.patch) (627 Bytes; text/x-patch)


Docutils manpage writer currently uses `.ft C`, but this causes warnings from groff ≥ 1.23.0.

Please see the downstream bug https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1041809 for a discussion about this issue with many references.

The attached patch, based on the original patch from G. Branden Robinson, fixes the warnings and makes the manpage writer use `.EX` and `.EE` instead, which are documented [here](https://manpages.debian.org/unstable/groff/groff_man.7.en.html#Document_structure_macros):

> Begin and end example. After .EX, filling is disabled and a constant-width (monospaced) font is selected. Calling .EE enables filling and restores the previous font.

So this should be equivalent to the previous code (`.nf`/`.fi` was for the filling, `.ft C`/`.ft P` was for the font).


---

Sent from sourceforge.net because [email protected] is subscribed to https://sourceforge.net/p/docutils/patches/

To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/docutils/admin/patches/options.  Or, if this is a mailing list, you can unsubscribe from the mailing list.
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.