On Tue, 11 Dec 2018 22:17:54 +0000, Seymour J Metz wrote:
>> That is precisely what "smart quotes" is all about.
>
>That's why I hate them.
>
>BTW, how do I turn off half-smart quotes on the computer of someone who's
>sending me a document?
>
After the fact, copy and paste the code you need, then pipe it through:
sed 's/“/"/g; s/”/"/g'
(or similar Edit macro.)
>________________________________________
>From: Charles Mills
>Sent: Tuesday, December 11, 2018 4:47 PM
>
>FWIW I personally use both: curly quotes when typing for humans and regular
>"ASCII" quotes when writing documentation and training and tech support
>examples, which I do a lot. I have toggled between disabling smart quotes
>and inserting them from the pull-down, versus enabling smart quotes and
>using the pull-down when I want "ASCII" quotes. I have settled on the latter
>approach. When I am "just typing" I get curly quotes and when I am thinking
>about a documentation example then I insert "ASCII" quotes. YMMV.
>
There's considerable value in distinguishing opening from closing brackets.
POSIX does well in providing for command substitution "$( list )" as an
alternative to "` list `". It nests without a cascade of '\' and it cleanly
protects internal punctuation without invalidating prior art. I'd support
adding distinct open and close quotes to any programming language
while retaining compatibility with existing art.
-- gil
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
