Re: To .jpg or not
Re: To .jpg or not
- Subject: Re: To .jpg or not
- From: Walter Ian Kaye <email@hidden>
- Date: Mon, 22 Mar 2004 05:10:19 -0800
At 01:54a -0700 03/22/2004, LuKreme didst inscribe upon an electronic papyrus:
On Mar 21, 2004, at 11:34 AM, BJ Terry wrote:
(I dislike situations like this, in which I am unsure whether to
put the period inside the quotation marks or not. Inside of the
quotation marks it spoils the literal nature of the contained text.
Outside, it breaks the convention that periods come before
quotation marks.)
Which is why the Brits put punctuation outside the quotes unless it
is part of the quote. makes sense to me.
Makes sense to me, too... and I'm only an American. :)
He said, "No!"
This sentence ends in a "quoted phrase".
Because in this example (and many others), placing a question mark
inside quotes is absurd:
Does this sentence end with a "quoted phrase?"
Does this sentence end with a "quoted phrase"?
Clearly the question mark is not part of the quote
Good ones! Take that, Strunk.
This usage makes more sense to me than the American method, so it's
the style I use.
And therein is the key. It's really just a style, not a rule.
I also place the periods outside of the parenthetical phrase unless
the entire sentence is in parenthesis (it simply looks better).
Umm... hasn't that *always* been the case? I've never heard anything different.
There is NO Rule six!
Only two weapons: fear and surprise. ...and a ruthless efficiency.
At 05:56a -0500 03/22/2004, Bill Cheeseman didst inscribe:
on 2004-03-21 10:22 PM, Christopher Nebel at email@hidden wrote:
Hackers tend to use quotes as balanced delimiters like parentheses,
much to the dismay of American editors.
What I *really* gag at is the use of grave accent ` as a fake left quote,
resulting in a geometrically-unbalanced "\***|" envelope in most fonts.
Anytime I download an RFC or man page with those monstrosities, I do
a bunch of search/replace operations to fix them. It should be
outlawed!
Editors are easily dismayed. Among the many "corrections" that the
editor of my Cocoa book made was correcting the "grammar" of my
code. Even Microsoft Word will mess up your code, if the editor
leaves autocorrect and various other word processing conveniences
turned on.
I disable smart quotes wherever the option appears. I would disable
smart insert/delete as well, if such an option existed (workaround is
to avoid doubleclicking words, but that slows selection down).
For example, AppleScript's double-hyphen comment delimiter becomes
an em-dash. What a nightmare.
And some Cocoa programs try to "correct" straight quotes into curly quotes;
I've already logged this into Bug Reporter and have exchanged
follow-up emails with Apple.
It shows up when using ProFont 9 installed at /System Folder/Fonts/.
Type the following into Script Editor 2, with ProFont Regular 9 for
your comments in formatting preferences:
--"foo"|"bar"|"baz"
Then compile. The quotes change into typographically incorrect curly quotes.
Yuchhhh. (The quotes become left-right|right-right|right-right.)
Safari changes curly quotes too, and also changes "fi" and "fl" into
ligatures, which obviously causes PRE-formatted text to misalign.
-boo
who expects the computer to display what he types (reasonable, yes?)
_______________________________________________
applescript-users mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/applescript-users
Do not post admin requests to the list. They will be ignored.