From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mail-bw0-f49.google.com (mail-bw0-f49.google.com [209.85.214.49]) by krisdoz.my.domain (8.14.3/8.14.3) with ESMTP id p4I6UWUI017221 for ; Wed, 18 May 2011 02:30:33 -0400 (EDT) Received: by bwz1 with SMTP id 1so1425184bwz.36 for ; Tue, 17 May 2011 23:30:27 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:x-authentication-warning:date:from:to:subject :message-id:references:mime-version:content-type:content-disposition :content-transfer-encoding:in-reply-to:user-agent; bh=2eQOE9fxfpmwNJRCCyPAJod6VEoOnceF6RfCeM8lObw=; b=tk/x4M+D8zHAzleoS6QyZ08xJpKNeszmOJaUJHQiLIIke2tbKnTQxxrP6EDbcEZVYC iXDHtLGbA8QT6FVu6kP8dZeH5AlUsmbkqQnGQKL4KMVVDR0pAcv+EXVScppPe1Dhd89K ffrukgsA2l84Tq3y0hUe3o6i6FrepfPviTkEI= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=x-authentication-warning:date:from:to:subject:message-id:references :mime-version:content-type:content-disposition :content-transfer-encoding:in-reply-to:user-agent; b=UqiY35VYnuVMHj2XMCxovarDa0k1SrC5oVy9C3qkxWCs4X2YsqhBzDh6KldxPz4iKj DhXJFKwC37UwQZ9bZAFgxJG5z9p61ZVrRGJsrYCgQlyIge6JhDzWi5fhvbYBcuPcMq+N 65pFHdUfGwUyEW+nF7D4TX+rAO2y0wODvc34c= Received: by 10.204.7.156 with SMTP id d28mr1472191bkd.28.1305700227118; Tue, 17 May 2011 23:30:27 -0700 (PDT) Received: from procyon.xvoid.org ([213.132.76.142]) by mx.google.com with ESMTPS id d25sm742911bkd.17.2011.05.17.23.30.25 (version=TLSv1/SSLv3 cipher=OTHER); Tue, 17 May 2011 23:30:25 -0700 (PDT) Received: from procyon.xvoid.org (yuri@procyon.xvoid.org [IPv6:::1]) by procyon.xvoid.org (8.14.4/8.14.4) with ESMTP id p4I6UNc4092963 for ; Wed, 18 May 2011 10:30:23 +0400 (MSD) (envelope-from yuri.pankov@gmail.com) Received: (from yuri@localhost) by procyon.xvoid.org (8.14.4/8.14.4/Submit) id p4I6UNLd092962 for discuss@mdocml.bsd.lv; Wed, 18 May 2011 10:30:23 +0400 (MSD) (envelope-from yuri.pankov@gmail.com) X-Authentication-Warning: procyon.xvoid.org: yuri set sender to yuri.pankov@gmail.com using -f Date: Wed, 18 May 2011 10:30:23 +0400 From: Yuri Pankov To: discuss@mdocml.bsd.lv Subject: Re: tbl example - what should be fixed? Message-ID: <20110518063023.GE1321@procyon.xvoid.org> References: <20110516111854.GA58664@procyon.xvoid.org> <4DD27469.5070505@bsd.lv> X-Mailinglist: mdocml-discuss Reply-To: discuss@mdocml.bsd.lv MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable In-Reply-To: <4DD27469.5070505@bsd.lv> User-Agent: Mutt/1.5.21 (2010-09-15) On Tue, May 17, 2011 at 03:13:13PM +0200, Kristaps Dzonsons wrote: > > We have a lot of manpages having the similar looking tables: > > .TS > > tab(=07) box; > > cw(2.75i) |cw(2.75i) > > lw(2.75i) |lw(2.75i) > > . > > TYPE=07VALUE > > _ > > Type1=07Value1 > > _ > > Type2=07Value2 > > .TE > > > > Output of -Tlint: > > tbl.example:2:5: ERROR: skipping bad character: ignoring byte > > tbl.example:2:6: ERROR: bad table syntax > > tbl.example:3:12: ERROR: bad table layout > > tbl.example:4:12: ERROR: bad table layout > > tbl.example:6:15: ERROR: skipping bad character: ignoring byte > > tbl.example:6:4: ERROR: bad table layout > > tbl.example:8:4: ERROR: skipping bad character: ignoring byte > > tbl.example:8:2: ERROR: bad table layout > > tbl.example:10:20: ERROR: skipping bad character: ignoring byte > > tbl.example:10:1: ERROR: bad table layout > > tbl.example:1:1: ERROR: no table data cells specified > > > > > > My questions is, is there anything that could/should be fixed/improved > > in tbl parser, or all of the errors are 100% correct and should be fixed > > in the manpages? >=20 > Yuri, >=20 > From mdoc.7: >=20 > LANGUAGE SYNTAX > mdoc documents may contain only graphable 7-bit ASCII > characters, the space character, and, in certain circumstances, > the tab character. >=20 > The tbl.7 manuals says the same. But you have non-ASCII characters in=20 > the input. groff is probably letting you get away with this by simply=20 > reading through the binary to the ')', but mandoc throws away the binary= =20 > characters before parsing. >=20 > Second, you did raise a bug! I was looking for modifiers for the=20 > vertical bar, i.e., a|b -> error. I just committed a fix for this. >=20 > The stand-alone period is another problem. groff *should* ignore it by= =20 > its own definition of a no-op macro. But as it occurs in a tbl context,= =20 > it's different? Blje... For now, just put the period on the same line= =20 > as the last macro. Thanks, Kristaps. I was just making sure what I should fix locally (a simple sed script took care of it..) Yuri -- To unsubscribe send an email to discuss+unsubscribe@mdocml.bsd.lv