[Bug 235456] [maintainer update] japanese/mh: Fix man pages breakage on FreeBSD 11.x and later
bugzilla-noreply at freebsd.org
bugzilla-noreply at freebsd.org
Sun Feb 3 08:56:25 UTC 2019
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=235456
Bug ID: 235456
Summary: [maintainer update] japanese/mh: Fix man pages
breakage on FreeBSD 11.x and later
Product: Ports & Packages
Version: Latest
Hardware: Any
OS: Any
Status: New
Severity: Affects Some People
Priority: ---
Component: Individual Port(s)
Assignee: ports-bugs at FreeBSD.org
Reporter: CQG00620 at nifty.ne.jp
On recent FreeBSD, japanese/mh's man pages has been broken with mandoc,
the default man page formatter since 11.0-RELEASE.
Because the man pages uses some features that is not supported by mandoc.
(1) The man pages uses .fc macro which is not supported by mandoc.
(2) Some man pages uses .so macro with an absolute file path.
Mandoc's .so macro only supports a file in the current directory.
(3) Local macro definitions has a trailing whitespace and comment.
For example:
.de De \" Defaults section
Mandoc ignores these definitions unless the trailing component has
been removed. Mandoc's '.de' only accepts a macro name.
(4) The man pages uses \*(lq and \*(rq macros which is not displayed anything
with mandoc on a tty terminal other than UTF-8 locale.
(5) Many of whitespace in a quoted strings is escaped by backslash.
The escaped character is not displayed with mandoc.
For example, "PROFILE\ COMPONENTS" is displayed 'PROFILECOMPONENTS'
How to fix:
(1) Remove the .fc macro and delimiter character.
Replace the padding character to TAB character.
(patch-conf_doc_tmac.h and patch-conf_doc_me2man.sed)
(2) Replace the .so macro to the specified file contents.
(patch-conf_makefiles_doc and an AWK script in Makefile)
(3) Remove the trailing components from the macro name (patch-conf_doc_tmac.h).
(4) Define local macros such as '.ds lq \&"'. This idea is taken from
the top(1) man page. (patch-conf_doc_tmac.h)
(5) 's/\\[ 0]/ /g' (patch-conf_doc_me2man.sed)
--
You are receiving this mail because:
You are the assignee for the bug.
More information about the freebsd-ports-bugs
mailing list