Hi Mike,
Mike Bianchi wrote on Sat, Feb 02, 2019 at 09:53:43AM -0500:
> ... build a generalize tool where the choice of font or device implies
> a set of desirable (to me) character substitutions and renderings that
> can easily be changed via a personalized configuration file. Say
>.groffto
Hi Ralph,
Ralph Corderoy wrote on Sat, Feb 02, 2019 at 02:59:21PM +:
> Ingo Schwarze wrote:
>> It is not outright impossible, but i doubt that would be a wise
>> course.
> I agree, given your reasoning.
OK, so we can exclude fiddling with each individual macro sets.
>> And the correct way
> "Stamp out US-specific, internationally non-portable usage of ASCII
> that is incompatible with Unicode, ..."
> Is that something we can agree on?
I don't agree because it cannot be done. Documentation, still valuable today,
was written with "US-specific, internationally non-portable usage o
Hi Ingo,
> It is not outright impossible, but i doubt that would be a wise
> course.
I agree, given your reasoning.
> And the correct way to mark up a single-quoted string in low-level
> roff(7) is \(oq...\(cq, with the rendering decided by the output
> device.
I think you're incorrect there.
> ... that doesn't look like a consensus yet, and unfortunately,
> i don't see how to argue further, ...
> :
> Any ideas how to resolve this clash of priorities?
Rephrasing what I said before:
... build a generalize tool where the choice of font or device implies
a set of des
Hi,
Jeff Conrad wrote on Sat, Feb 02, 2019 at 05:46:59AM +:
> On Friday, February 1, 2019 3:31 PM, Ingo Schwarze wrote:
>> And the correct way to mark up a single-quoted string in low-level
>> roff(7) is \(oq...\(cq, with the rendering decided by the output
>> device.
> I think this gets to
