From: "Sören Tempel" <soeren@soeren-tempel.net>
To: discuss@mandoc.bsd.lv
Subject: Compatibility with xsltproc?
Date: Thu, 25 Jun 2020 12:17:04 +0200 [thread overview]
Message-ID: <3BSFGLBLAOYGW.242OQJ5FBW8XR@8pit.net> (raw)
Hello there,
I am a contributor to the Alpine Linux distribution which uses
mandoc-1.14.5 by default. Recently some man page rendering issues were
reported in our bug tracker [0]. Upon further investigation I found
these incorrectly rendered man pages to be generated using xsltproc(1)
and xmlto(1). I searched the mailing list archives as well as the
documentation and TODO list for specific entries regarding xsltproc(1)
and didn't manage to find any specific mentions.
I also checked the xsltproc(1) man page on OpenBSD to make sure that
this problem isn't Alpine specific and the xsltproc(1) man page itself
seems to be rendered incorrectly on OpenBSD as well.
Are rendering issues related to man pages generated using xsltproc(1) a
known issue? Is there any know workaround, e.g. specific flags which can be
passed to xsltproc(1) to make the generated man pages compatible with
mandoc?
Greetings,
Sören
[0]: https://gitlab.alpinelinux.org/alpine/aports/-/issues/11674
--
To unsubscribe send an email to discuss+unsubscribe@mandoc.bsd.lv
reply other threads:[~2020-06-25 15:28 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3BSFGLBLAOYGW.242OQJ5FBW8XR@8pit.net \
--to=soeren@soeren-tempel.net \
--cc=discuss@mandoc.bsd.lv \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).