[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[groff] html output of Op vs Oo Oc
|
From: |
Jan Stary |
|
Subject: |
[groff] html output of Op vs Oo Oc |
|
Date: |
Thu, 7 Dec 2017 16:41:01 +0100 |
|
User-agent: |
Mutt/1.7.1 (2016-10-04) |
This is groff 1.22.3 as installed by the OpenBSD port.
Below please find a short manpage written in mdoc(7),
which I am trying to process into html with
groff -Thtml -mdoc rtpdump.1 > rtpdump.html
One point where it seems to fail is
.Oo Ar address Oc Ns / Ns Ar port
- the html output contains a paragraph break
... [</p>
after the opening [ of the .Oo, which I believe is an error.
The same happens later with another .Oo ... Oc
Is this known? A plain .Op renders fine,
but Oo ... Oc seems to have this bug.
Jan
.Dd December 7, 2017
.Dt RTPDUMP 1
.Os
.Sh NAME
.Nm rtpdump
.Nd parse and print RTP packets
.Sh SYNOPSIS
.Nm
.Op Fl F Ar format
.Oo Ar address Oc Ns / Ns Ar port
.\" FIXME html output
.\".Op Ar address Ns / Ns Ar port
.Sh DESCRIPTION
.Nm
reads RTP and RTCP packets on the given
.Ar address Ns / Ns Ar port ,
or from standard input by default,
and dumps a processed version to standard output.
.Pp
The options are as follows:
.Bl -tag -width Ds
.It Fl F Ar format
Write the output in the given
.Ar format ,
which is one of the following:
.Cm dump ,
.Cm header ,
.Cm payload ,
.Cm ascii ,
.Cm hex ,
.Cm rtcp ,
.Cm short .
.Pp
The
.Cm short
format dumps RTP or VAT data in lines such as
.Pp
.D1 Oo Cm - Oc Ns Ar time timestamp Op Ar seq
.\" FIXME html output
.Pp
where
.Sq Cm -
indicates a set marker bit,
.Ar time
is the arrival time,
.Ar timestamp
is the RTP timestamp, and
.Ar seq
is the RTP sequence number (only used for RTP packets).
.El
<!-- Creator : groff version 1.22.3 -->
<!-- CreationDate: Thu Dec 7 16:29:38 2017 -->
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd";>
<html>
<head>
<meta name="generator" content="groff -Thtml, see www.gnu.org">
<meta http-equiv="Content-Type" content="text/html; charset=US-ASCII">
<meta name="Content-Style" content="text/css">
<style type="text/css">
p { margin-top: 0; margin-bottom: 0; vertical-align: top }
pre { margin-top: 0; margin-bottom: 0; vertical-align: top }
table { margin-top: 0; margin-bottom: 0; vertical-align: top }
h1 { text-align: center }
</style>
<title></title>
</head>
<body>
<hr>
<p>RTPDUMP(1) General Commands Manual RTPDUMP(1)</p>
<p style="margin-top: 1em"><b>NAME</b></p>
<p style="margin-left:6%;"><b>rtpdump</b> – parse and
print RTP packets</p>
<p style="margin-top: 1em"><b>SYNOPSIS</b></p>
<p style="margin-left:17%;"><b>rtpdump</b>
[<b>−F </b><i>format</i>] [</p>
<p><i>address</i> ]/<i>port</i></p>
<p style="margin-top: 1em"><b>DESCRIPTION</b></p>
<p style="margin-left:6%;"><b>rtpdump</b> reads RTP and
RTCP packets on the given <i>address</i>/<i>port</i>, or
from standard input by default, and dumps a processed
version to standard output.</p>
<p style="margin-left:6%; margin-top: 1em">The options are
as follows:</p>
<p style="margin-top: 1em"><b>−F</b>
<i>format</i></p>
<p style="margin-left:17%;">Write the output in the given
<i>format</i>, which is one of the following: <b>dump</b>,
<b>header</b>, <b>payload</b>, <b>ascii</b>, <b>hex</b>,
<b>rtcp</b>, <b>short</b>.</p>
<p style="margin-left:17%; margin-top: 1em">The
<b>short</b> format dumps RTP or VAT data in lines such
as</p>
<p style="margin-left:24%; margin-top: 1em">[</p>
<p><b>-</b> ]<i>time timestamp</i> [<i>seq</i>]</p>
<p style="margin-left:17%; margin-top: 1em">where
‘<b>-</b>’ indicates a set marker bit,
<i>time</i> is the arrival time, <i>timestamp</i> is the RTP
timestamp, and <i>seq</i> is the RTP sequence number (only
used for RTP packets).</p>
<p style="margin-left:6%; margin-top: 1em">OpenBSD
November 23, 2017 OpenBSD</p>
<hr>
</body>
</html>
- [groff] html output of Op vs Oo Oc,
Jan Stary <=