Re: [PATCH] posix.py: ffix: Correctly format URIs

2021-01-13 Thread G. Branden Robinson
[redirecting to groff@gnu.org; Reply-To set] Hi Jakub! At 2021-01-12T21:51:15+0100, Jakub Wilk wrote: > > On 1/10/21 7:50 AM, G. Branden Robinson wrote: [regarding groff's an-ext.tmac's .UR/.UE macros] > > > They use left and right angle bracket special character escapes > > > (Unicode U+2039 and

Re: [ms] Add a standard glyph name for hooked o instead of relying on .AM?

2021-01-13 Thread G. Branden Robinson
Hi Dorai, I'm replying to both you and the list because what I have to ask you is important. I used to work in software licensing compliance professionally, so perhaps I am extra paranoid. At 2021-01-14T06:05:41+, Dorai Sitaram via wrote: > Absolutely, do add whatever license is needed; and

Re: [PATCH] improve internationalization at startup

2021-01-13 Thread G. Branden Robinson
At 2021-01-13T02:43:46-0600, Dave Kemper wrote: > On 1/4/21, G. Branden Robinson wrote: > > For one thing, it annoys me that the hyphenation language code for > > English is wrong. > > I have no objection to changing this. But I observe that the file we > call(ed) tmac/hyphenex.us comes from TeX

PostScript fonts and the groff build process (was: [ms] Add a standard glyph name for hooked o instead of relying on .AM?)

2021-01-13 Thread G. Branden Robinson
At 2021-01-13T04:34:50-0600, Dave Kemper wrote: > On 1/4/21, Denis M. Wilson wrote: > > rfc1345 does not have a base-line ellipsis, a character frequently > > used in English writing. > > > It is available as \N'188' in the symbol font or as \[u2026]. > > Since commit aac5fd24 (2003), it has bee

Re: [ms] Add a standard glyph name for hooked o instead of relying on .AM?

2021-01-13 Thread Dorai Sitaram via
Absolutely, do add whatever license is needed; and modify what I have (both code and documentation) to suit groff's standards. My repo is purely temporary and meant to ferry the code to you better than email can. --d On Thursday, January 14, 2021, 12:32:19 AM EST, G. Branden Robinson wro

Re: End-of-sentence spacing, for our German readers

2021-01-13 Thread Dorai Sitaram via
I'm used to single-spacing by now, given its ubiquity, but surely the Germans carry their disdain for typographic breathing space a little too far? As in the posted article, paragraphs are difficult to visually separate, lacking as they do both leading horizontal indentation and vertical separa

Re: [ms] Add a standard glyph name for hooked o instead of relying on .AM?

2021-01-13 Thread G. Branden Robinson
First of all, let me say thanks to Dorai for quickly coming up with rfc1345.tmac! It needs a Free Software license put on it. I can write a unit test for it and fix up the man page, those aren't big problems. It would be nice to get it into groff 1.23.0, about which I am now getting anxious beca

Re: [ms] Add a standard glyph name for hooked o instead of relying on .AM?

2021-01-13 Thread Dave Kemper
On 1/4/21, Denis M. Wilson wrote: > rfc1345 does not have a base-line ellipsis, a character frequently used > in English writing. > It is available as \N'188' in the symbol font or as \[u2026]. Since commit aac5fd24 (2003), it has been available in the Symbol font as \[u2026] as well, no longer

Re: [ms] Add a standard glyph name for hooked o instead of relying on .AM?

2021-01-13 Thread Dave Kemper
On 1/3/21, G. Branden Robinson wrote: > Probably the best thing is for document authors (except of man(7) and > mdoc(7) documents) to come up with mnemonics that make sense to them for > the subset of Unicode characters of use and to define special characters > or strings to interpolate them. > >

Re: [PATCH] improve internationalization at startup

2021-01-13 Thread Dave Kemper
On 1/4/21, G. Branden Robinson wrote: > For one thing, it annoys me that the hyphenation language code for > English is wrong. I have no objection to changing this. But I observe that the file we call(ed) tmac/hyphenex.us comes from TeX (http://ctan.org/pkg/hyphenex), where it's billed explicitl