From: Benjamin Peterson (email@example.com)
Date: Tue Mar 23 2004 - 06:29:28 EST
On Tue, 23 Mar 2004 11:56:52 +0100, "Philippe Verdy" <firstname.lastname@example.org>
> From: "Doug Ewell" <email@example.com>
> > Recently I found an unexpected "Unicode moment" buried in the
> > documentation for Microsoft Visual Studio .NET. This was written by
> > Bobby Schmidt in 2000.
> > > The name "C sharp" is really spelled as shown in my column's banner
> > > graphic: The capital letter C followed by a musical sharp sign.
> > > Because this sign does not exist in ASCII, most of us approximate the
> > > name as C#. This approximation leads to witty derivatives such as "C
> > > hash," "C pound," and the tortuous "C octothorpe"—all based on a
> > > convenient but incorrect typography. My personal favorite is "D flat,"
> > > which has the twin virtues of cleverness and correctness, but would
> > > actually require equally un-ASCII typography.
> > The "musical sharp sign," of course, is U+266F, making the correct
> > spelling C♯.
> But the "orthograph" is unambiguously "C#" with ASCII characters at least
> its standard source file extension, not "C♯", so the correct spelling
> should be
> "C number sign" (or spelled in French "C croisillon", or more commonly "C
> even though it is the French spelling for the sharp musical symbol).
The file extension is '.cs', since including punctuation marks would
cause problems on many systems.
The correct spelling is with a sharp sign, not a number sign, as
documented by Microsoft themselves in various places:
> I wonder how Microsoft came to the conclusion to use the "#" cymbol which
> problems in various shell environments, including make scripts. Is it an
> to exclude its language from Unix and Mac environments where these names
> be impractical to use as file extensions?
A simple Google search before posting can be a wise move.
-- Benjamin Peterson firstname.lastname@example.org
This archive was generated by hypermail 2.1.5 : Tue Mar 23 2004 - 07:04:40 EST