Apostrophes (was: Check out Computer glitch...)

[Paul Gilmartin]

On Sun, 22 Nov 2009 07:05:33 -0600, Jim Elliott, IBM wrote:

>On Sat, 21 Nov 2009 10:18:42 -0500, P S wrote:
>
>>Jim, what were the weird characters after "65" and "50" supposed to be? Just
>>curious.
>>
>Weird, they are apostrophes.
>
... which your editor, too smart by half, converted to right-single-quotes,
and which P S's viewer (along with one I tried) doesn't understand.

>four Model 65's, three Model 50's
>
As someone lately screamed on ISPF-L, "Leave my text alone unless I tell
you to change it!" I wasn't the screamer, but I'll echo it. Know what
happens when a busybody editor smart-quotes the apostrophes in a JCL
snippet?

-- gil

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to list...@bama.ua.edu with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html

[Shmuel Metz , Seymour J.]

In <LISTSERV%20091122085...@BAMA.UA.EDU>, on 11/22/2009

at 08:52 AM, Paul Gilmartin <PaulGB...@AIM.COM> said:

>... which your editor, too smart by half, converted to
>right-single-quotes,

Right single quote in ISO-8859-1 is ' ('27'x), not � (dipthong AE, '92'X).

>and which P S's viewer (along with one I tried) doesn't understand.

The header specified charset=ISO-8859-1; why would you expect a
MIME-capable[1] e-mail viewer to interpret '92'X as anything but the
8859-1 code point?

>Know what happens when a busybody editor smart-quotes the
>apostrophes in a JCL snippet?

Know what happens when a busybody printer word wraps JCL?

[1] Without MIME anything greater than '7F'x would be invalid.

--
Shmuel (Seymour J.) Metz, SysProg and JOAT
ISO position; see <http://patriot.net/~shmuel/resume/brief.html>
We don't care. We don't have to care, we're Congress.
(S877: The Shut up and Eat Your spam act of 2003)