From: Kristaps Dzonsons <kristaps@bsd.lv>
To: "discuss@mdocml.bsd.lv" <discuss@mdocml.bsd.lv>
Subject: mandoc and EOS spacing.
Date: Wed, 12 May 2010 23:03:14 +0200 [thread overview]
Message-ID: <4BEB1792.1040102@bsd.lv> (raw)
Hello,
I just checked in a framework for EOS spacing in mandoc. It's a very
small, easily-auditable patch, but it works quite well and can expand to
handle lots of hard cases.
It works by the back-ends setting a flag for nodes are on a sentence
boundary. The front-end drivers catch this and (optionally) sets a flag
for the output engine, which adds an extra space to the inter-word spacing.
I've implemented it for non-literal free-form text contexts in both
-mdoc and -man for -Tascii. It's documented in mdoc.7 and man.7,
respectively, both of which have also been end-of-sentence-end-of-lined.
Thanks,
Kristaps
--
To unsubscribe send an email to discuss+unsubscribe@mdocml.bsd.lv
reply other threads:[~2010-05-12 17:14 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=4BEB1792.1040102@bsd.lv \
--to=kristaps@bsd.lv \
--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).