From: Stefan Richter <stefanr@s5r6.in-berlin.de>
To: Miguel Ojeda <maxextreme@gmail.com>
Cc: akpm@osdl.org, Randy Dunlap <rdunlap@xenotime.net>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2.6.18 V7] drivers: add lcd display support
Date: Sun, 01 Oct 2006 15:51:24 +0200 [thread overview]
Message-ID: <451FC7DC.7070909@s5r6.in-berlin.de> (raw)
In-Reply-To: <653402b90610010553p23819d2bsd7a07fabaee7ecf3@mail.gmail.com>
Miguel Ojeda wrote:
> On 10/1/06, Stefan Richter <stefanr@s5r6.in-berlin.de> wrote:
...
>> It is as common as it is wrong.
...
>> "LCD" and "LC display" are correct.
>>
>
> Sure it is wrong, the point is what is the best to understading. "LCD
> display" seems better to me than just "LC display".
...
> tristate "ks0108 LCD controller"
> tristate "cfag12864b LCD"
>
> That is the correct spelling, however, does it look good?
>
> (I really don't know what is the best way to write it in english, I'm
> spanish and here it is more common to say "LCD display").
"LCD display" is wrong and, excuse me, dumb in *all* languages. The fact
that it is common doesn't make it a smart thing to say or write. :-)
If you find "LCD" or "LC display" ugly to look at or hard to understand
(IMO it is not hard to understand if it appears in a computer technology
related context), you could write "liquid crystal display". I suppose
you could also just write "cfag12864b display".
I am not sure which looks prettiest. But I know that "LCD display" looks
really bad to everybody who knows what the D stands for. :-)
--
Stefan Richter
-=====-=-==- =-=- ----=
http://arcgraph.de/sr/
next prev parent reply other threads:[~2006-10-01 13:53 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-30 23:24 Miguel Ojeda Sandonis
2006-10-01 12:53 ` Miguel Ojeda
2006-10-01 13:51 ` Stefan Richter [this message]
2006-10-01 14:25 ` Miguel Ojeda
2006-10-01 16:48 ` Stefan Richter
2006-10-01 17:58 ` Miguel Ojeda
2008-04-28 23:36 ` monitordelcd
2006-10-01 16:05 ` Valdis.Kletnieks
2006-10-01 16:17 ` Andreas Schwab
2006-10-01 17:33 ` Valdis.Kletnieks
2006-10-01 16:43 ` Randy Dunlap
2006-10-01 17:27 ` Alexander van Heukelum
2006-10-01 17:52 ` Miguel Ojeda
2006-10-01 18:25 ` Alexander van Heukelum
2006-10-01 16:53 ` Stefan Richter
2006-10-02 18:49 ` Andrew James Wade
2006-10-02 21:40 ` Miguel Ojeda
2006-10-03 0:06 ` Andrew James Wade
2006-10-03 12:55 ` Miguel Ojeda
2006-10-03 15:29 ` Randy Dunlap
2006-10-02 22:06 ` Alan Cox
2006-10-02 21:45 ` Miguel Ojeda
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=451FC7DC.7070909@s5r6.in-berlin.de \
--to=stefanr@s5r6.in-berlin.de \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maxextreme@gmail.com \
--cc=rdunlap@xenotime.net \
/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
Powered by JetHome