From: Richard Salz <rich.salz@gmail.com>
To: Clem Cole <clemc@ccc.com>
Cc: TUHS main list <tuhs@minnie.tuhs.org>
Subject: Re: [TUHS] Style and diction commands available?
Date: Wed, 23 Dec 2020 16:35:08 -0500 [thread overview]
Message-ID: <CAFH29tqkQsk701RQniW3kFp0oHH67_SwSVV91j-2P+2j2=yS9A@mail.gmail.com> (raw)
In-Reply-To: <CAC20D2NiWcL3Tbf9ecx78fB97gCnaGHbELEjnOjhaUEPaEtYjw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1088 bytes --]
My goal was to find something to catch simple errors in IETF RFC's. And
yeah, a typo on 13 vs 3 :)
I've run it over a few documents, not sure if it's worth adding an
xml/markdown filter to handle input "better" or not.
On Wed, Dec 23, 2020 at 3:25 PM Clem Cole <clemc@ccc.com> wrote:
> Sorry, I should have mentioned those too. I thought you were interested
> in something closer to the historical version. Truth be known, I have
> Gnu's version 1.11 installed on my Mac (as part of brew), however but I
> think they are 13 years old not 3 :-)
>
> On Wed, Dec 23, 2020 at 2:33 PM Richard Salz <rich.salz@gmail.com> wrote:
>
>> I pulled copies from Clem's recommendation,
>>
>> > The DWB distribution from the Toolkit is not around to my knowledge,
>> but: https://minnie.tuhs.org/cgi-bin/utree.pl?file=V8/usr/src/cmd look
>> for the diction and style directories, which should be close.
>>
>> I got them to compile with modern C. Then I found that FSF has their own
>> rewrites.https://www.gnu.org/software/diction/ It's only three years
>> old, not 30. :)
>>
>> Just FYI.
>>
>
[-- Attachment #2: Type: text/html, Size: 2047 bytes --]
prev parent reply other threads:[~2020-12-23 21:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-23 19:32 Richard Salz
2020-12-23 20:25 ` Clem Cole
2020-12-23 21:35 ` Richard Salz [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='CAFH29tqkQsk701RQniW3kFp0oHH67_SwSVV91j-2P+2j2=yS9A@mail.gmail.com' \
--to=rich.salz@gmail.com \
--cc=clemc@ccc.com \
--cc=tuhs@minnie.tuhs.org \
/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).