From owner-freebsd-doc@FreeBSD.ORG  Mon May 12 22:44:55 2003
Return-Path: <owner-freebsd-doc@FreeBSD.ORG>
Delivered-To: freebsd-doc@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP
	id AE3C837B401; Mon, 12 May 2003 22:44:55 -0700 (PDT)
Received: from rwcrmhc51.attbi.com (rwcrmhc51.attbi.com [204.127.198.38])
	by mx1.FreeBSD.org (Postfix) with ESMTP
	id DB8D143FAF; Mon, 12 May 2003 22:44:54 -0700 (PDT)
	(envelope-from horikawa@jp.freebsd.org)
Received: from localhost (12-252-35-167.client.attbi.com[12.252.35.167])
          by attbi.com (rwcrmhc51) with SMTP
          id <2003051305445405100bsdk2e>; Tue, 13 May 2003 05:44:54 +0000
Date: Mon, 12 May 2003 23:42:34 -0600 (MDT)
Message-Id: <20030512.234234.74754585.horikawa@attbi.com>
To: keramida@ceid.upatras.gr
From: horikawa@jp.FreeBSD.org
In-Reply-To: <20030512105048.GB711@gothmog.gr>
References: <20030512.010014.74754261.horikawa@attbi.com>
	<20030512105048.GB711@gothmog.gr>
X-Mailer: Mew version 3.1 on Emacs 21.2 / Mule 5.0 (SAKAKI)
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
cc: freebsd-doc@freebsd.org
cc: ru@freebsd.org
Subject: Re: ".It Xo" ... generates improper output on groff 1.18.1
X-BeenThere: freebsd-doc@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Documentation project <freebsd-doc.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-doc>,
	<mailto:freebsd-doc-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-doc>
List-Post: <mailto:freebsd-doc@freebsd.org>
List-Help: <mailto:freebsd-doc-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-doc>,
	<mailto:freebsd-doc-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 13 May 2003 05:44:56 -0000

Giorgos Keramidas <keramida@ceid.upatras.gr> wrote:
> On 2003-05-12 01:00, Kazuo Horikawa <horikawa@jp.FreeBSD.org> wrote:
> > Hi,
> >
> > Recently, using groff 1.18.1, I realized that sequences like below
> > produce improper output.
> >
> > .It Xo
> > .Em start
> > and
> > .Em size
> > .Xc
> > fields provide the start address
> > and size of a slice in sectors.
> >
> > Sequence above taken from src/sbin/fdisk/fdisk.8 rev 1.34 is formated
> > as follows:
> >
> >      andrsize'                      fields provide the start address and size
> >                            of a slice in sectors.
> >
> > I could see "warning: missing closing delimiter" on stderr, if -ww is
> > specified.
> >
> > Is this fixed by recent groff 1.19, or still existing problem?
> 
> This...
> 
>     .Bl -tag
>     The
>     .Nm
>     utility reads files sequentially, writing them to the standard output.
>     .It Xo
>     .Em start
>     and
>     .Em size
>     .Xc
>     fields provide the start address
>     and size of a slice in sectors.
>     .El
> 
> works fine using groff 1.19 with -z -ww -mandoc options here.

I see.  Interesting.  I also verified groff 1.18.1 with -z -ww
-mandoc works fine for the sequence above.

But, I am afraid you will see "warning: missing closing delimiter"
if you have:
	.Bl -tag -width ".Em cyl , sector No and Em head"
instead of:
	.Bl -tag

As I did not have a chance to reinstall a recent -current, I installed
groff 1.19 and got the same warning when I format fdisk(8).

Can you format fdisk(8) without warning using groff 1.19?
--
Kazuo Horikawa