git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andreas Ericsson <ae@op5.se>
To: Nikolai Weibull <now@bitwi.se>
Cc: Junio C Hamano <junkio@cox.net>,
	Horst.H.von.Brand@inf.utfsm.cl, git@vger.kernel.org
Subject: Re: [PATCH 0/27] Documentation: Spelling fixes
Date: Wed, 07 Jun 2006 10:53:31 +0200	[thread overview]
Message-ID: <4486940B.1040905@op5.se> (raw)
In-Reply-To: <dbfc82860606050948t5c952f65m364a455e0e83ec8@mail.gmail.com>

Nikolai Weibull wrote:
> On 6/5/06, Andreas Ericsson <ae@op5.se> wrote:
> 
>> Nikolai Weibull wrote:
>> > On 6/4/06, Junio C Hamano <junkio@cox.net> wrote:
>> >
>> >> Most do not seem to be typoes, depending on where you learned
>> >> the language (XYZour vs XYZor; ok, Ok, and OK; ie vs i.e.).
>> >
>> > Where do you write "ie" instead of "i.e."?
>> >
>>
>> Mailing lists, online conversations, tech docs written in code
>> editors...
> 
> 
> Do you mean that code editors usually don't let you enter a dot into
> the buffer, or what?
> 

No, I mean that people are lazy when writing online and for an audience 
that broadly share the same sort of text-digesting mind, so they don't 
bother with the dots.

>> Compare with online'ish abbrevs (afaict, iirc, imo, fyi).
> 
> 
> That's hardly the same thing.


Why not? Both are examples of one-letter-per-word abbreviations.


>  Most people would upcase AFAICT, IIRC,
> IMO, and FYI.
> 

True, but both forms are common enough. I guess I'm one of the lazier 
ones, since I regularly use lower-case.

> I wouldn't group "i.e." with such abbreviations in any case.  (Hehe.)
> 

I fail to see why not. I also fail to care very much, so feel free not 
to respond. ;)

> 
>> When each character of the abbrev defines one complete word dots are
>> just prettiness-noise, their presence or absence decided by the gravity
>> of the meaning ("R.I.P." vs "ie"). Obviously, correctness never hurts
>> but this is, on two accounts, punktknulleri.
> 
> 
> Considering that people don't want to get stuck on trying to
> understand what the word "ie" is supposed to mean in a manual page
> they're trying to understand what some command does (this happened to
> me), I really think that fucking with the dots is called for.
> 
> Anyway, the general guidelines recommended by "The Chicago Manual of 
> Style" are:
> 
> Use periods with abbreviations that appear in lowercase letters; use
> no periods with abbreviations that appear in full capitals or small
> capitals, whether two letters or more.
> 
> One possible solution is to expand "i.e." to "that is" (or something
> equally befitting) and "e.g." to "for example", "such as", or similar.
> 

This is most likely the best solution as it's easier for foreign readers 
with limited proficiency in reading english and english abbreviations 
borrowed from latin, as they don't make sense if you try to put in 
english words matching the abbreviation, dots or no dots.  This gave me 
quite a headache when I was twelve and tried to install Linux for the 
first time :)

-- 
Andreas Ericsson                   andreas.ericsson@op5.se
OP5 AB                             www.op5.se
Tel: +46 8-230225                  Fax: +46 8-230231

      reply	other threads:[~2006-06-07  8:53 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-03 20:26 [PATCH 0/27] Documentation: Spelling fixes Horst.H.von.Brand
2006-06-03 20:52 ` Jakub Narebski
2006-06-04  1:09 ` Junio C Hamano
2006-06-04  2:02   ` Horst von Brand
2006-06-04 17:59   ` Nikolai Weibull
2006-06-05 12:29     ` Andreas Ericsson
2006-06-05 16:48       ` Nikolai Weibull
2006-06-07  8:53         ` Andreas Ericsson [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4486940B.1040905@op5.se \
    --to=ae@op5.se \
    --cc=Horst.H.von.Brand@inf.utfsm.cl \
    --cc=git@vger.kernel.org \
    --cc=junkio@cox.net \
    --cc=now@bitwi.se \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).