Hi Doug,
At 2021-01-05T16:19:12-0500, M Douglas McIlroy wrote:
> rfc1345.tmac is a great contribution. I hope to see
>
> 1. inclusion in the standard groff distribution.
It shipped, eventually, in groff 1.23.0 six months ago.
> 2. the gitlab comment
>"Added \[Eu], \[=R], \[=P] from Vim digr
Hi Doug,
Looks like today's my day to reply to years-old mails.
At 2021-01-03T17:26:35-0500, M Douglas McIlroy wrote:
> 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 acce
On 1/14/21, I wrote:
> I had sort of assumed this
> wasn't being done because no one had floated the idea before, so I
> brought it up for discussion. If there seems to be general buy-in,
> I'll open a savannah feature request for it.
Opened: http://savannah.gnu.org/bugs/?59932
(Repeating as public confirmation.) I have updated
https://gitlab.com/ds26gte/groff1345 with a COPYRIGHT file. Thanks for
suggesting the prose.
--d
Sent from Yahoo Mail on Android
On Thu, Jan 14, 2021 at 1:45 AM, G. Branden
Robinson wrote: Hi Dorai,
I'm replying to both you and the lis
On 1/13/21, G. Branden Robinson wrote:
> I have no argument against your reasoning. The main reason this isn't
> being done is because no one is working on it (to my knowledge).
I get the scarcity of groff developers, but I had sort of assumed this
wasn't being done because no one had floated th
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
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
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
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
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
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.
>
>
Thanks! Updated accordingly.
--d
On Wednesday, January 6, 2021, 02:40:55 PM EST, Richard Morse
wrote:
Sorry to jump in, but because of the recent thread around sentence spacing,
probably the man page should either have every sentence start on a new line, or
put two spaces after sent
Sorry to jump in, but because of the recent thread around sentence spacing,
probably the man page should either have every sentence start on a new line, or
put two spaces after sentence-final periods?
Ricky
> On Jan 6, 2021, at 11:44 AM, Dorai Sitaram via wrote:
>
> Thanks, Doug! I've updated
Thanks, Doug! I've updated https://gitlab.com/ds26gte/groff1345 to include
your suggestions 2 and 3.
I am not at all confident that the man page I've added hits the right notes or
even uses the correct terminology, but the community can easily correct it to
meet its standards.
--d
O
rfc1345.tmac is a great contribution. I hope to see
1. inclusion in the standard groff distribution.
2. the gitlab comment
"Added \[Eu], \[=R], \[=P] from Vim digraph table."
inserted in the file
3. A section groff_mrfc1245 in man7. It can be very short.
Tell what it is; and refer reade
Careful diff'ing reveals that in addition to the \[,.] for horizontal
ellipsis, the only digraphs that Vim has over and above RFC 1345 are those for
the currency symbols for euro and rouble. That RFC 1345 (written in 1992)
missed the euro is understandable, as the latter clinked into existence
To avoid emailing updated versions of rfc1345.tmac, I've created a temporary
Git repo
https://gitlab.com/ds26gte/groff1345
I've added \[,.] from Vim. If I find any more Vim digraphs that aren't already
covered by RFC 1345, I'll add them in due course.
--d
On Monday, January 4, 20
Indeed it doesn't. (TBH, I've never warmed to the single-character ellipsis as
it seems too narrow in most fonts.)
I notice Vim's digraph system (which is based on RFC 1345) uses the digraph ,.
(comma-followed-by-period) for U+2026 HORIZONTAL ELLIPSIS.
Vim's digraphs are pretty standard too,
rfc1345 does not have a base-line ellipsis, a character frequently used
in English writing. I've also found it surprising that it is not in
groff either considering groff was originally written by a British
person.
It is available as \N'188' in the symbol font or as \[u2026].
Denis
On Mon, 4 Jan
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
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-
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
23 matches
Mail list logo
