Branden wrote
Ingo's proposal would not mandate that + and \- come from the special
font.
It also would not mandate that \(pl and \(mi come from the current font.
--
I was previously told that \(mi is the true minus sign. But the
true minus sign, at least in my mind, must come from the cu
At 2017-05-02T17:47:50+, Bjarni Ingi Gislason wrote:
> On Sat, Apr 29, 2017 at 06:25:29AM -0400, G. Branden Robinson wrote:
> > Any advice on how I can improve this? (I'll take "no, don't even try to
> > do this" as read, from those who hate man(7). ;-) )
> >
>
> You did not check the macr
Ingo Schwarze wrote:
|Steffen Nurpmeso wrote on Tue, May 02, 2017 at 11:50:31AM +0200:
|> I now think it is better to revert all those per-macro adjustments
|> altogether and be pure; if people use \- to get "nicer" (smoother
|> and finer that is) output then pasting from manual is simply
|>
On Sat, Apr 29, 2017 at 06:25:29AM -0400, G. Branden Robinson wrote:
> Any advice on how I can improve this? (I'll take "no, don't even try to
> do this" as read, from those who hate man(7). ;-) )
>
You did not check the macro for errors (correctness, portability)!
> This is a private macro,
Hi,
Ingo Schwarze wrote on Tue, May 02, 2017 at 03:45:01PM +0200:
> By the way, in the meantime, i also received support from NetBSD/pkgsrc
> for my proposal (\- always U+002D, \(mi always U+2212). That's
> Ralph, Branden, NetBSD/pkgsrc, and one relevant FreeBSD developer
> then, and no protest
At 2017-05-02T18:34:50+0200, Ingo Schwarze wrote:
> But you are right that i should probably adjust the in-line macros
> (that is, .B, .I, .SM, .SB) as well, even though for them, the
> damage is minor, wrong font at the worst - and even that is unlikely
> to happen in practice, because why would a
Hi,
G. Branden Robinson wrote on Tue, May 02, 2017 at 11:48:56AM -0400:
> Note that the commits also affected the .SH, .SS, .B, .I, .SM, and .SB
> macros as well. Basically it affected anything that set an input trap.
True. What i committed to mandoc(1) so far only adjusts the block
macros (th
Hi Doug,
You didn't quote to whom you're responding so I may be a little
confused.
At 2017-05-01T22:06:38-0400, Doug McIlroy wrote:
> Originally \(pl and \(mi came from a fixed font (S) while + and \-
> came from the current font.
Yes, I believe you're correct, going by CSTR #54. (And, of cours
At 2017-05-02T01:57:54+0200, Ingo Schwarze wrote:
> Purely FYI:
>
> Given that the man(7) .TP .itc hack got committed to groff,
Some men just want to watch the world burn. ;-)
> A few days ago, a patch from
> got committed to groff which changed .TP from using .it to using .itc,
> such that gr
Hi,
Steffen Nurpmeso wrote on Tue, May 02, 2017 at 11:50:31AM +0200:
> I now think it is better to revert all those per-macro adjustments
> altogether and be pure; if people use \- to get "nicer" (smoother
> and finer that is) output then pasting from manual is simply
> impossible.
That is clear
"G. Branden Robinson" wrote:
|At 2017-05-01T19:30:02+0200, Steffen Nurpmeso wrote:
|> "G. Branden Robinson" wrote:
|>|Please find a patch attached.
...
|> I for one always found those one/two/one/two/.. macros very
|> suspicious, but now i see actual use cases.
|
|One of the advantages o
Doug McIlroy wrote:
|Originally \(pl and \(mi came from a fixed font (S) while + and \-
|came from the current font. As I understand your comment, groff
|has reversed this troff convention. Additionally groff interprets - as
|a compromise HYPHEN-MINUS.
|
|man groff_char, however, tells the o
12 matches
Mail list logo
