The mandatory .Os macro of an mdoc(7) manpage
makes the rendered manpage have "OpenBSD Reference Manual"
at the top center, and "OpenBSD X.Y" at the bottom.
As the mdoc(7) manual says,
Left unspecified, it defaults to the local
operating system version. This is the suggested form.
Viewing the same page on Linux with mandoc,
it renders "General Commands Manual" and "Linux 3.2.0-4-amd64".
Now, vieweing the same manpage on Linux with groff -mdoc,
it renders "BSD General Commands Manual" at the top center
and "BSD" at the bottom.
I suppose there is a difference between how mandoc and groff
figure out the OS information to use for .Os; groff_mdoc(7) says
.Os [<operating system>] [<release>]
If the first parameter is empty, the default `' is used.
This may be overridden in the local configuration file, mdoc.local.
Could someone please eleborate on this difference between
mandoc and groff regarding how they get the OS information?
Of course my Linux users wonder why the manpage says "BSD".
See an example page below.
Thank you.
Jan
.Dd "June 19, 2014"
.Dt SNDFILE-CMP 1
.Os
.Sh NAME
.Nm sndfile-cmp
.Nd compare two audio files
.Sh SYNOPSIS
.Nm sndfile-cmp
.Ar file1
.Ar file2
.Sh DESCRIPTION
.Nm
compares the audio data of two sound files.
For two files to compare as being the same, their channel counts, sample rate,
audio data lengths and actual audio data must match.
Other differences such as string metadata like song title, artist etc and their
presence or absence are ignored.
.Sh EXIT STATUS
.Bl -tag -width 0 -compact
.It 0
The audio data is the same
.It 1
The audio data differs
.El
.Sh SEE ALSO
.Lk http://www.mega-nerd.com/libsndfile
.Sh AUTHORS
.An Conrad Parker Aq Mt con...@metadecks.org
.An Erik de Castro Lopo Aq Mt er...@mega-nerd.com
