All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andy Walls <awalls@radix.net>
To: Hans Verkuil <hverkuil@xs4all.nl>
Cc: video4linux-list@redhat.com,
	Mauro Carvalho Chehab <mchehab@redhat.com>,
	Michael Schimek <mschimek@gmx.at>
Subject: Re: [PATCH v2 3/4] v4l2: Add missing control names
Date: Fri, 12 Dec 2008 12:51:20 -0500	[thread overview]
Message-ID: <1229104280.3176.18.camel@palomino.walls.org> (raw)
In-Reply-To: <200812121425.01922.hverkuil@xs4all.nl>

On Fri, 2008-12-12 at 14:25 +0100, Hans Verkuil wrote:
> Hi Laurent,
> 
> Just one tiny suggestion:
> 
> On Friday 12 December 2008 14:10:36 Laurent Pinchart wrote:
> > +	/* CAMERA controls */
> > +	case V4L2_CID_CAMERA_CLASS:		return "Camera Controls";
> > +	case V4L2_CID_EXPOSURE_AUTO:		return "Auto-Exposure";
> 
> I would suggest "Auto Exposure" (no dash). It seems to be the most 
> common way to write it. At least to my eyes the dash looks strange. 
> Perhaps some native English speakers can help out here?

You actually need a professional English teacher, professor, editor, or
writer for that answer.  The hyphen has, to me, rather confusing rules.

IANAET, but....

For example when modifying a noun you, would likely hyphenate
adjective-noun modifiers:

"Auto-exposure setting"

But in simple adjective-noun pairs, you would not, as adjectives are
understood to modify nouns:

"Auto exposure"


Also, new compound words in English often get hyphenated when
introduced, but the hyphen disappears when the word comes into common
usage: e-mail vs. email.  But even if this were the path "auto-exposure"
took initially in English, I, as a native English speaker, would likely
never write "autoexposure".  "o" and "e" as directly adjacent syllabic
vowels in a written word just seems "wrong".  

Regards,
Andy

> 
> Regards,
> 
> 	Hans
> 

--
video4linux-list mailing list
Unsubscribe mailto:video4linux-list-request@redhat.com?subject=unsubscribe
https://www.redhat.com/mailman/listinfo/video4linux-list

  reply	other threads:[~2008-12-12 17:51 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-12 13:01 [PATCH v2 0/4] Add zoom and privacy controls Laurent Pinchart
2008-12-12 13:04 ` [PATCH v2 1/4] v4l2: Add camera zoom controls Laurent Pinchart
2008-12-12 13:06 ` [PATCH v2 2/4] v4l2: Add privacy control Laurent Pinchart
2008-12-12 13:10 ` [PATCH v2 3/4] v4l2: Add missing control names Laurent Pinchart
2008-12-12 13:25   ` Hans Verkuil
2008-12-12 17:51     ` Andy Walls [this message]
2008-12-14 19:18       ` Laurent Pinchart
2008-12-12 13:11 ` [PATCH v2 4/4] v4l2: Document zoom and privacy controls Laurent Pinchart

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=1229104280.3176.18.camel@palomino.walls.org \
    --to=awalls@radix.net \
    --cc=hverkuil@xs4all.nl \
    --cc=mchehab@redhat.com \
    --cc=mschimek@gmx.at \
    --cc=video4linux-list@redhat.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.