For one thing, it annoys me that the hyphenation language code for
English is wrong. For another, it annoys me that no effort is made to
determine groff's locale from the system.
Please see https://savannah.gnu.org/bugs/?59814 .
Attaching patch here as well for interest.
I don't intend to merge
Enclosed is my draft for rfc1345.tmac.
--d
On Sunday, January 3, 2021, 09:27:06 PM EST, Dorai Sitaram via
wrote:
I'll be happy to write up an rfc1345.tmac and send it to you. I don't think
it requires a tremendous amount of maintenance, as the list of mnemonics
appears not to hav
Hi, Doug!
At 2020-12-22T09:33:20-0500, M Douglas McIlroy wrote:
> The words about double spacing quoted below can be misread as
> unconditional advice. I suggest replacing "In" with "In this case".
>
> Also so much mention of AT&T strikes me as clutter. At least the first
> instance would better
I'll be happy to write up an rfc1345.tmac and send it to you. I don't think it
requires a tremendous amount of maintenance, as the list of mnemonics appears
not to have changed since June 1992.
--d
On Sunday, January 3, 2021, 08:16:12 AM EST, G. Branden Robinson
wrote:
At 2020-12-
Dear All,
thank you for your kind support in 2020! Please accept my best wishes
for 2021!
Though I do understand that groff and friends do not officially support
CJK languages, I came across a Japanese adaptation which was deeply
buried in a debian archive. Unfortunately the binaries do not run
Hi Kurt,
At 2020-12-04T13:03:20-0500, T. Kurt Bond wrote:
> I downloaded groff-1.22.4.tar.gz to check if that compiled, and I didn't
> even get that far, since that tar file contains a INSTALL.REPO but not an
> INSTALL, and no configure script, and trying the bootstrap script fails, of
> course, s
I like the idea of an rfc1345.tmac file, and would be happy to operate
under the false assumption that it exists. I think it would be reasonable
to abandon the old AT&T accent strings while we're at it, even though I
have plenty of groff source that uses them.
Corollary 1: So that calls for abando
At 2020-12-14T19:07:06+, Dorai Sitaram via wrote:
> s.tmac defines a bunch of strings to display extra glyphs if the user
> calls the .AM macro. Most of these glyphs are already available with
> standard glyph names, and, as far as I can tell, the only new glyph
> defined is the hooked o, (equ