Re: [groff] seeking fixed-width breakable space

2019-02-21 Thread Dave Kemper
On 2/21/19, G. Branden Robinson wrote: > At 2019-02-21T19:40:18-0600, Dave Kemper wrote: >> As far as I can determine, groff does not offer a fixed-width, >> breakable space. > > Will the digit space (\0) do? It would if it were breakable. printf '.ll 1c\na b c d e f g\n' | groff -a printf '.ll

Re: [groff] seeking fixed-width breakable space

2019-02-21 Thread G. Branden Robinson
At 2019-02-21T19:40:18-0600, Dave Kemper wrote: > Space characters have two different, independent attributes: > > 1. They can have a fixed width, or they can stretch for line adjustments. > 2. They can be breakable or unbreakable. > > This results in four different types of spaces: > - stretcha

[groff] seeking fixed-width breakable space

2019-02-21 Thread Dave Kemper
Space characters have two different, independent attributes: 1. They can have a fixed width, or they can stretch for line adjustments. 2. They can be breakable or unbreakable. This results in four different types of spaces: - stretchable breakable (a normal space in groff) - stretchable unbreak

Re: [groff] [patch] modernize -T ascii rendering of opening single quote

2019-02-21 Thread Jeff Conrad
On Thursday, February 21, 2019 3:10 AM, G. Branden Robinson wrote: > At 2019-02-21T10:01:07+, Jeff Conrad wrote: > > The Chicago Manual of Style, 13th ed., says “a single quotation mark, > > however, should not be used to indicate an accent, because it could be > > either a grave or an acute a

Re: [groff] Upgrade to 1.22.4 breaks PDF font

2019-02-21 Thread Richard Morse
On Feb 19, 2019, at 06:37 PM, Bertrand Garrigues wrote: On Tue, Feb 19 2019 at 10:58:17 PM, Colin Watson wrote: It's likely that this is a bug in the Homebrew formula: you can confirm this by looking for "URW fonts for pdf" in the configure output (it should say "yes", but I bet it says "no").

Re: [groff] Upgrade to 1.22.4 breaks PDF font

2019-02-21 Thread Richard Morse
On Feb 19, 2019, at 05:58 PM, Colin Watson wrote: It's likely that this is a bug in the Homebrew formula: you can confirm this by looking for "URW fonts for pdf" in the configure output (it should say "yes", but I bet it says "no"). The formula needs to make sure that whatever provides a010013l.

Re: [groff] [patch] modernize -T ascii rendering of opening single quote

2019-02-21 Thread Mike Bianchi
On Thu, Feb 21, 2019 at 10:01:07AM +, Jeff Conrad wrote: > > We still have the question about what is (or was) a Genuine ASCII™ > device, I don't think "Genuine" is a question. There ain't no such thing. Just look at your various keyboards. I have keycaps (unshift ") with straight and a

Re: [groff] [patch] modernize -T ascii rendering of opening single quote

2019-02-21 Thread John Gardner
If my opinion matters in this discussion, then I'm tentatively opposed to this change. Reasons: — Folks limited to ASCII environments may be using a screen font with more suitable-looking quotes (e.g., Gallant) — Regression tests that assert man(1) output will break on systems with a modern groff(1

Re: [groff] [patch] modernize -T ascii rendering of opening single quote

2019-02-21 Thread Ingo Schwarze
Hi Branden, G. Branden Robinson wrote on Thu, Feb 21, 2019 at 04:07:28PM +1100: > At 2019-02-20T20:06:17+0100, Ingo Schwarze wrote: >> after reviewing all feedback, i come to the conclusion that there is no >> consensus for the change: >> >> OPPOSED: Mike Bianchi, Tadziu Hoffmann >> SCEPTICAL:

Re: [groff] [patch] modernize -T ascii rendering of opening single quote

2019-02-21 Thread Jeff Conrad
On Wednesday, February 20, 2019 9:07 PM, G. Branden Robinson wrote: > > The Savannah ticket[1] says: > > rendering single quotes like `this' was considered an anachronism from > the mechanical typewriter era." I never did this with a mechanical (or electric) typewriter ... The Chicago Manual of