From: Mike Edenfield <kutulu@kutulu.org>
To: gentoo-user@lists.gentoo.org
Subject: [WAY OT] Parenthese, was Re: [gentoo-user] I can RTFM, but can I understand it: re elog messages
Date: Fri, 20 Aug 2010 13:07:54 -0400 [thread overview]
Message-ID: <4C6EB66A.80100@kutulu.org> (raw)
In-Reply-To: <AANLkTi=UFrsOpU_afhexCE-Xv+wMfXEbpwbTtZr69L94@mail.gmail.com>
On 8/20/2010 11:40 AM, Kevin O'Gorman wrote:
> As to the thingies, I enjoyed discovering that to many people a
> parenthesis is not a glyph or punctuation mark, but instead the contents
> of the language set aside in one way or another. I had always regarded
> parentheses as the round glyphs (), but this turns out to be normative
> primarily in mathematics, computer programming languages and similar
> fields. But I find several competing meanings and sources using
> http://dictionary.reference.com/cite.html?qh=parenthesis&ia=luna
> <http://dictionary.reference.com/cite.html?qh=parenthesis&ia=luna>
In American English usage, the three forms of puncutation mark have
distinct names. Contrary to previous assertions, these names are not
informal; authoritative American English dictionaries like M-W define
"bracket", "brace", and "parenthesis" separately as punctuation marks.
In British English they're all called "brackets", e.g. square, curly, or
round.
The Romance languages are somewhat varied, but they mostly use the Greek
word parenthesis to derive their term for () marks; in some cases, that
word is use for *all* brackets; in other cases [] and {} have separate
terms:
() = parenthèses (Fr.), paréntesis (Sp.), parentesi tonde (It.)
[] = crochets (Fr.), corchetes (Sp.), parentesi quadre (It.)
{} = accolades (Fr.), corchetes (Sp.), parentesi graffe (It.)
For what it's worth, Unicode defines U+0028 AND U+0029 as "LEFT
PARENTHESIS" and "RIGHT PARENTHESIS" (also "OPENING PARENTHESIS" and
"CLOSING PARENTHESIS").
--Mike
next prev parent reply other threads:[~2010-08-20 17:08 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-19 20:21 [gentoo-user] I can RTFM, but can I understand it: re elog messages Kevin O'Gorman
2010-08-19 22:01 ` Neil Bothwick
2010-08-19 23:38 ` Peter Humphrey
2010-08-20 7:20 ` Dale
2010-08-20 8:01 ` Neil Bothwick
2010-08-20 8:39 ` Dale
2010-08-20 8:03 ` Neil Bothwick
2010-08-20 9:01 ` Alan McKinnon
2010-08-20 9:23 ` Neil Bothwick
2010-08-20 14:53 ` Peter Humphrey
2010-09-02 16:15 ` Neil Bothwick
2010-08-20 9:06 ` Alan McKinnon
2010-08-20 13:20 ` Bill Longman
2010-08-20 14:58 ` Peter Humphrey
2010-08-20 15:12 ` Bill Longman
2010-08-20 15:40 ` Kevin O'Gorman
2010-08-20 17:07 ` Mike Edenfield [this message]
2010-08-20 19:00 ` [WAY OT] Parenthese, was " Alan McKinnon
2010-08-20 19:32 ` [gentoo-user] Re: [WAY OT] Parenthese Alex Schuster
2010-08-20 20:14 ` Alan McKinnon
2010-08-21 9:53 ` Peter Humphrey
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=4C6EB66A.80100@kutulu.org \
--to=kutulu@kutulu.org \
--cc=gentoo-user@lists.gentoo.org \
/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