pg.ddx.io pgsql-docs@postgresql.org mailing list archive
help / color / mirror / Atom feed"May", "can", "might"
7+ messages / 6 participants
[nested] [flat]
* "May", "can", "might"
@ 2007-01-30 17:39 Bruce Momjian <bruce@momjian.us>
0 siblings, 4 replies; 7+ messages in thread
From: Bruce Momjian @ 2007-01-30 17:39 UTC (permalink / raw)
To: PostgreSQL-development <pgsql-hackers@postgreSQL.org>; pgsql-docs
Standard English uses "may", "can", and "might" in different ways:
may - permission, "You may borrow my rake."
can - ability, "I can lift that log."
might - possibility, "It might rain today."
Unfortunately, in conversational English, their use is often mixed, as
in, "You may use this variable to do X", when in fact, "can" is a better
choice. Similarly, "It may crash" is better stated, "It might crash".
I would like to clean up our documentation to consistently use these
words. Objections?
(Who says were obsessive?) :-)
--
Bruce Momjian bruce@momjian.us
EnterpriseDB http://www.enterprisedb.com
+ If your life is a hard drive, Christ can be your backup. +
^ permalink raw reply [nested|flat] 7+ messages in thread
* Re: "May", "can", "might"
@ 2007-01-30 17:52 Andrej Ricnik-Bay <andrej.groups@gmail.com>
parent: Bruce Momjian <bruce@momjian.us>
3 siblings, 1 reply; 7+ messages in thread
From: Andrej Ricnik-Bay @ 2007-01-30 17:52 UTC (permalink / raw)
To: Bruce Momjian <bruce@momjian.us>; +Cc: pgsql-docs
On 1/31/07, Bruce Momjian <bruce@momjian.us> wrote:
> Standard English uses "may", "can", and "might" in different ways:
>
> may - permission, "You may borrow my rake."
>
> can - ability, "I can lift that log."
>
> might - possibility, "It might rain today."
>
> Unfortunately, in conversational English, their use is often mixed, as
> in, "You may use this variable to do X", when in fact, "can" is a better
> choice. Similarly, "It may crash" is better stated, "It might crash".
>
> I would like to clean up our documentation to consistently use these
> words. Objections?
My full support. :} I like clarity, specially on such important things
as communication!
> (Who says were obsessive?) :-)
^ permalink raw reply [nested|flat] 7+ messages in thread
* Re: [HACKERS] "May", "can", "might"
@ 2007-01-30 17:58 Gregory Stark <stark@enterprisedb.com>
parent: Bruce Momjian <bruce@momjian.us>
3 siblings, 1 reply; 7+ messages in thread
From: Gregory Stark @ 2007-01-30 17:58 UTC (permalink / raw)
To: Bruce Momjian <bruce@momjian.us>; +Cc: PostgreSQL-development <pgsql-hackers@postgreSQL.org>; pgsql-docs
"Bruce Momjian" <bruce@momjian.us> writes:
> (Who says were obsessive?) :-)
I may not fall into your clever trap...
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
^ permalink raw reply [nested|flat] 7+ messages in thread
* Re: "May", "can", "might"
@ 2007-01-30 17:59 Bruce Momjian <bruce@momjian.us>
parent: Andrej Ricnik-Bay <andrej.groups@gmail.com>
0 siblings, 0 replies; 7+ messages in thread
From: Bruce Momjian @ 2007-01-30 17:59 UTC (permalink / raw)
To: Andrej Ricnik-Bay <andrej.groups@gmail.com>; +Cc: pgsql-docs
Andrej Ricnik-Bay wrote:
> On 1/31/07, Bruce Momjian <bruce@momjian.us> wrote:
> > Standard English uses "may", "can", and "might" in different ways:
> >
> > may - permission, "You may borrow my rake."
> >
> > can - ability, "I can lift that log."
> >
> > might - possibility, "It might rain today."
> >
> > Unfortunately, in conversational English, their use is often mixed, as
> > in, "You may use this variable to do X", when in fact, "can" is a better
> > choice. Similarly, "It may crash" is better stated, "It might crash".
> >
> > I would like to clean up our documentation to consistently use these
> > words. Objections?
> My full support. :} I like clarity, specially on such important things
> as communication!
>
>
> > (Who says were obsessive?) :-)
Ah, someone already got me with were -> we're. "Who says we're
obsessive?" Perfect!
--
Bruce Momjian bruce@momjian.us
EnterpriseDB http://www.enterprisedb.com
+ If your life is a hard drive, Christ can be your backup. +
^ permalink raw reply [nested|flat] 7+ messages in thread
* Re: [HACKERS] "May", "can", "might"
@ 2007-01-30 18:23 Mike Rylander <mrylander@gmail.com>
parent: Gregory Stark <stark@enterprisedb.com>
0 siblings, 0 replies; 7+ messages in thread
From: Mike Rylander @ 2007-01-30 18:23 UTC (permalink / raw)
To: Gregory Stark <stark@enterprisedb.com>; +Cc: Bruce Momjian <bruce@momjian.us>; PostgreSQL-development <pgsql-hackers@postgresql.org>; pgsql-docs
On 1/30/07, Gregory Stark <stark@enterprisedb.com> wrote:
>
> "Bruce Momjian" <bruce@momjian.us> writes:
>
> > (Who says were obsessive?) :-)
>
> I may not fall into your clever trap...
But you certainly can!
<cymbal_crash/>
(sorry...)
>
> --
> Gregory Stark
> EnterpriseDB http://www.enterprisedb.com
>
> ---------------------------(end of broadcast)---------------------------
> TIP 1: if posting/reading through Usenet, please send an appropriate
> subscribe-nomail command to majordomo@postgresql.org so that your
> message can get through to the mailing list cleanly
>
--
Mike Rylander
mrylander@gmail.com
GPLS -- PINES Development
Database Developer
http://open-ils.org
^ permalink raw reply [nested|flat] 7+ messages in thread
* Re: "May", "can", "might"
@ 2007-01-30 20:35 Guillaume Lelarge <guillaume@lelarge.info>
parent: Bruce Momjian <bruce@momjian.us>
3 siblings, 0 replies; 7+ messages in thread
From: Guillaume Lelarge @ 2007-01-30 20:35 UTC (permalink / raw)
To: Bruce Momjian <bruce@momjian.us>; +Cc: PostgreSQL-development <pgsql-hackers@postgreSQL.org>; pgsql-docs
Bruce Momjian a écrit :
> Standard English uses "may", "can", and "might" in different ways:
>
> may - permission, "You may borrow my rake."
>
> can - ability, "I can lift that log."
>
> might - possibility, "It might rain today."
>
> Unfortunately, in conversational English, their use is often mixed, as
> in, "You may use this variable to do X", when in fact, "can" is a better
> choice. Similarly, "It may crash" is better stated, "It might crash".
>
> I would like to clean up our documentation to consistently use these
> words. Objections?
>
No objections at all... it can only ease translations.
> (Who says were obsessive?) :-)
>
:)
--
Guillaume.
<!-- http://abs.traduc.org/
http://lfs.traduc.org/
http://docs.postgresqlfr.org/ -->
^ permalink raw reply [nested|flat] 7+ messages in thread
* Re: "May", "can", "might"
@ 2007-02-02 16:46 Andrew Sullivan <ajs@crankycanuck.ca>
parent: Bruce Momjian <bruce@momjian.us>
3 siblings, 0 replies; 7+ messages in thread
From: Andrew Sullivan @ 2007-02-02 16:46 UTC (permalink / raw)
To: pgsql-hackers@postgresql.org
On Tue, Jan 30, 2007 at 12:39:26PM -0500, Bruce Momjian wrote:
> I would like to clean up our documentation to consistently use these
> words. Objections?
None here, but if you're going to go to the trouble, you might want
to have a look at how others have faced this problem too.
In my line of work, we've taken to adopting the RFC 2119 words for
cases where we want to be super-clear and unambiguous. I don't think
those formulations would be much use for user manuals, but it's nice
to see that another group of people who work by converging on
consensus can still do that by (for example) agreeing that "MAY" and
"may" are not the same word.
A
--
Andrew Sullivan | ajs@crankycanuck.ca
The whole tendency of modern prose is away from concreteness.
--George Orwell
^ permalink raw reply [nested|flat] 7+ messages in thread
end of thread, other threads:[~2007-02-02 16:46 UTC | newest]
Thread overview: 7+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2007-01-30 17:39 "May", "can", "might" Bruce Momjian <bruce@momjian.us>
2007-01-30 17:52 ` Andrej Ricnik-Bay <andrej.groups@gmail.com>
2007-01-30 17:59 ` Bruce Momjian <bruce@momjian.us>
2007-01-30 17:58 ` Gregory Stark <stark@enterprisedb.com>
2007-01-30 18:23 ` Mike Rylander <mrylander@gmail.com>
2007-01-30 20:35 ` Guillaume Lelarge <guillaume@lelarge.info>
2007-02-02 16:46 ` Andrew Sullivan <ajs@crankycanuck.ca>
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox