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 the essence of the matter. The character table for
-Tascii should recog
Hi Ralph,
Ralph Corderoy wrote on Fri, Feb 01, 2019 at 06:42:48PM +:
> Doug wrote:
>> Still, this is a cautionary tale. What other sorts of
>> documents would suffer badly under this change?
> groff_char(7) here currently contains
>
> Output Input PostScript Unicode Notes
>
> Thus losing the ability to tell if I mistyped \(oq as \(cq with -Tascii
> or -Tlatin1?
To be fair, -Tascii and -Tlatin1 already lack the ability to
distinguish \(lq from \(rq -- and \(fo from \(la, and several others
(far more in -Tascii, of course).
Currently, \(ga and \(oq render the same. U
Doug McIlroy writes:
> If I were conscientious in writing about m4, I might choose
> to use \(oq and \(cq to assure pretty typesetting.
That would break any sort of copy and paste in typeset output or even
a UTF-8 terminal. The correct method would be to use \(aq (not \(aa) and
\(ga for source cod
On Fri, Feb 01, 2019 at 01:33:08PM +, Ralph Corderoy wrote:
> Subject: Re: [groff] Announcement and call for project submissions
>
> I've pointed all this out because you'll encounter it again unless you
> think https://www.xaprb.com/blog/you-might-be-right/
Good pointer. It may be right --
Hi,
Doug wrote:
> Still, this is a cautionary tale. What other sorts of
> documents would suffer badly under this change?
groff_char(7) here currently contains
Output Input PostScript Unicode Notes
...
\[oq] \e[oq] quoteleft u2018 single open (left) quote
\[cq]
If I were conscientious in writing about m4, I might choose
to use \(oq and \(cq to assure pretty typesetting. It
would be a disaster to have both come out as apostrophes
in -T ascii. Knowing that, I could use \(aa and \(ga instead.
Still, this is a cautionary tale. What other sorts of
documents w
>:
> The point of -T ascii is to get intelligible output on stunted devices, ...
In my opinion the point of -T ascii is to preserve the behaviour of
groff -T ascii
from back then until forever. The proposed changes do not correct bugs.
(We are not talking core dumps here.)
They pr
I just mistakenly hit control-D, sending a half-baked message. Please
ignore it. Full message will follow.
doug
The proposal to use the same character for left- and right-quote,
as is customary in C, would be devastating to m4.
The notion that it would make "kan pages look less antique"
Hi Ingo,
> The point of -T ascii is to get intelligible output on stunted
> devices, not to convey the fine details of typesetting. That doesn't
> imply that it needs to look ugly or dated [for those with corrupted
> fonts], though.
Sounds fair.
--
Cheers, Ralph.
Hi Ralph,
Ralph Corderoy wrote on Fri, Feb 01, 2019 at 03:22:56PM +:
> Ingo Schwarze wrote:
>> If i remember correctly, some time ago, people went through error
>> messages and manual pages and changed single-quoted strings where the
>> opening quote was an "accent grave" to the normal ASCII
Hi Doug,
> I'm puzzled. How can one "modernize" ascii? Or to put the question
> another way, what universally available character set does -T ascii
> evoke?
I think Ingo means: change -Tascii and -Tlatin1's output for \(oq from
the ASCII ` to the ASCII ' because the more modern displays some of t
Hi Ingo,
> If i remember correctly, some time ago, people went through error
> messages and manual pages and changed single-quoted strings where the
> opening quote was an "accent grave" to the normal ASCII U+0027
> APOSTROPHE-QUOTE because rendering single quotes like `this' was
> considered an a
Hi Werner,
> Many years ago, in the age of bitmap fonts, they *were* symmetric.
> However, the symbols are *intentionally* asymmetric today to avoid
> confusion with real quote characters.
>
> That I still use `foo' indicates that I became old :-)
I still use it too, and a few months back I retur
Hi Doug,
Doug McIlroy wrote on Fri, Feb 01, 2019 at 09:39:41AM -0500:
> I'm puzzled. How can one "modernize" ascii?
One cannot. When i wrote
modernize -T ascii rendering
i meant: modernize the rendering when groff is run
with the "-T ascii" option.
> Or to put the question another way, wha
I'm puzzled. How can one "modernize" ascii? Or to put the question
another way, what universally available character set does -T ascii
evoke?
doug
Hi John,
> > It's not obvious to me what offense John gave. Reading the thread,
> > there's a certain schoolmarmish officiousness in the reprimands. He
> > caught it on the chin for "sigh", "groan", and "ridiculous".
>
> I was also *banned* immediately after the PR got closed... Glad I'm
> not
Hi Ingo,
> So i think installing the binaries with a command prefix is a very
> reasonable choice.
I don't. :-) Not unless a user typically wants to keep both
accessible, e.g. on Sun OS where some things depend on other's old
behaviour.
For man(1), a user doesn't want to alter muscle memory fo
*> OT: It's not obvious to me what offense John gave. Reading the thread,>
there's a certain schoolmarmish officiousness in the reprimands. He>
caught it on the chin for "sigh", "groan", and "ridiculous". He didn't>
attack anyone. I'm left wondering which emoticons are prohibited.*
I was also
20 matches
Mail list logo
