From: Ingo Schwarze <schwarze@usta.de>
To: Jan Stary <hans@stare.cz>
Cc: discuss@mandoc.bsd.lv
Subject: Re: Mandoc for oil
Date: Fri, 14 Jun 2019 16:54:15 +0200 [thread overview]
Message-ID: <20190614145415.GE25099@athene.usta.de> (raw)
In-Reply-To: <20190614142714.GA34987@www.stare.cz>
Hi Jan,
Jan Stary wrote on Fri, Jun 14, 2019 at 04:27:14PM +0200:
> On Jun 14 14:29:41, schwarze@usta.de wrote:
>> The following may or may not work, not sure though:
>> - SUN Solaris 10 and older
> I can atest to Solaris 11.3 (SunOS 5.11)
> happily runing all recent releases of mandoc.
While certainly true, that wasn't the question, though;
building and running mandoc works even on Solaris 9 (= SunOS 5.9)
and on AIX; not sure whether HP-UX was ever tested.
The question was on which systems the native man(1) utility
might be unable to cope with manual pages in mdoc(7) format.
According to my testing on the OpenCSW cluster, the native man(1)
does handle mdoc(7) input on Solaris 11.3, which is no surprise
because the manual page of Solaris 11.3 man(1) says:
Source Format
Reference Manual pages are marked up with either nroff (see groff(1))
or SGML (Standard Generalized Markup Language) tags (see sgml(5)). The
man command recognizes the type of markup and processes the file
accordingly.
In contrast, it appears that Solaris 10 did not yet use groff by
default for manual page display. That's why is said that Solaris 10
might still need versions of manual pages converted from mdoc(7)
to man(7).
Yours,
Ingo
--
To unsubscribe send an email to discuss+unsubscribe@mandoc.bsd.lv
next prev parent reply other threads:[~2019-06-14 14:54 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-14 8:16 Matthew Singletary
2019-06-14 8:43 ` Jan Stary
2019-06-14 8:54 ` Jan Stary
2019-06-14 9:24 ` Matthew Singletary
2019-06-14 11:40 ` Jan Stary
2019-06-14 12:29 ` Ingo Schwarze
2019-06-14 13:08 ` Jan Stary
2019-06-14 14:27 ` Jan Stary
2019-06-14 14:54 ` Ingo Schwarze [this message]
2019-06-16 2:39 ` Matthew Singletary
2019-06-16 17:08 ` Ingo Schwarze
2019-06-14 9:54 ` Stephen Gregoratto
2019-06-14 12:03 ` Jan Stary
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=20190614145415.GE25099@athene.usta.de \
--to=schwarze@usta.de \
--cc=discuss@mandoc.bsd.lv \
--cc=hans@stare.cz \
/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).