discuss@mandoc.bsd.lv
 help / color / mirror / Atom feed
From: Ingo Schwarze <schwarze@usta.de>
To: discuss@mdocml.bsd.lv
Subject: Re: double space after `.' issue
Date: Thu, 23 Sep 2010 21:51:45 +0200	[thread overview]
Message-ID: <20100923195145.GC11894@iris.usta.de> (raw)
In-Reply-To: <20100923171403.GM13645@bramka.kerhand.co.uk>

Hi Jason,

Jason McIntyre wrote on Thu, Sep 23, 2010 at 06:13:39PM +0059:

> hi. source from disklabel(8):
> 
> 	The disk label contains information about disk characteristics
> 	.Pq size, type, etc.
> 	and the partition layout, stored on the disk itself.
> 
> groff:
> 	The disk label contains information about disk characteristics
> 	(size, type, etc.) and the partition layout, stored on the disk
> 	itself.
> 
> mandoc:
> 	The disk label contains information about disk characteristics
> 	(size, type, etc.)  and the partition layout, stored on the disk
> 	itself.
> 
> i.e. mandoc produces a double space before "and".

Yes, it imagines the dot were a full stop, which it isn't.

> groff and mandoc are handling that .Pq line differently.
> is this on a TODO list,

I am aware of the fact that end-of-sentence detection is still not
perfect, and have now added an entry to the TODO list:

 - in enclosures, mandoc sometimes fancies a bogus end of sentence
   reminded by jmc@  Thu, 23 Sep 2010 18:13:39 +0059

> or do i need to change the source?

No, please don't!
That mdoc source code is 100% correct.

Yours,
  Ingo
--
 To unsubscribe send an email to discuss+unsubscribe@mdocml.bsd.lv

      reply	other threads:[~2010-09-23 19:51 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-23 17:14 Jason McIntyre
2010-09-23 19:51 ` Ingo Schwarze [this message]

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=20100923195145.GC11894@iris.usta.de \
    --to=schwarze@usta.de \
    --cc=discuss@mdocml.bsd.lv \
    /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).