The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: steffen@sdaoden.eu (Steffen Nurpmeso)
Subject: [TUHS] Slashes (was: MS-DOS)
Date: Fri, 08 Jul 2016 13:09:12 +0200	[thread overview]
Message-ID: <20160708110912._pmH11Mqe%steffen@sdaoden.eu> (raw)
In-Reply-To: <20160707234722.GF78278@eureka.lemis.com>

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 2173 bytes --]

Greg 'groggy' Lehey <grog at lemis.com> wrote:
 |On Thursday,  7 July 2016 at 16:18:41 +0200, Steffen Nurpmeso wrote:
 |> Nemo <cym224 at gmail.com> wrote:
 |>> On 7 July 2016 at 01:02, Greg 'groggy' Lehey <grog at lemis.com> wrote:
 |>>> On Friday,  1 July 2016 at 21:13:00 -0400, Steve Nickolas wrote:
 |>>>> On Fri, 1 Jul 2016, Norman Wilson wrote:
 |>>>>
 |>>>>> I suspect Yanks being pedantic about `slash' versus `forward slash'
 |>>>>> would give an Englishman a stroke.

 |>> On the other hand, the OED has the following.
 |>>
 |>> slash 5. A thin sloping line, thus /
 |>>
 |>> solidus 2. A sloping line used to separate shillings from pence, as 12/6,
 |>> in writing fractions, and for other separations of figures and letters; a
 |>> shilling-mark.

 |>> I would argue "solidus" is closer.
 |>
 |> SOLIDUS is the Unicode name, too, as is REVERSE SOLIDUS, giving
 |> SLASH and BACKSLASH as secondaries.
 |
 |Finally we have clarity!  From now on it's only (without shouting)

Copied and pasted from UnicodeData.txt.

 |solidus and reverse solidus.  No confusion any more, at least not for
 |those in the know.

Maybe it helps that the German «Schrägstrich» will desert into
Slash («Herkunft: englisch slash, eigentlich = (harter, kurzer)
Schlag, Hieb, laut- und bewegungsnachahmend oder zu altfranzösisch
esclachier = (zer)teilen») and that a furtherly described
Schrägstrich will wind up in «Backslash» («Herkunft: englisch
backslash, aus: back = zurück und slash = Hieb, Schnitt»)

It gives me cause for concern that we replace a civil word like
«Schrägstrich» ("oblique bar") with something aggressive and
dismembering that slash seems to represent.  That may be a reason
for Linguists to promote solidus and ban the other words into the
commentary, one might think.

...and that actually makes me wonder why the engineers that
created what became POSIX preferred slash instead -- i hope it is
not the proud of high skills in using (maybe light) sabers that
some people of the engineer community seem to foster.  But it
could be the sober truth.  Or, it could be a bug caused by
inconsideration.  And that seems very likely now.

--steffen


  parent reply	other threads:[~2016-07-08 11:09 UTC|newest]

Thread overview: 45+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-02  0:12 [TUHS] MS-DOS Norman Wilson
2016-07-02  1:13 ` Steve Nickolas
2016-07-02  4:52   ` Random832
2016-07-03 19:40   ` scj
2016-07-07  5:02   ` [TUHS] Slashes (was: MS-DOS) Greg 'groggy' Lehey
2016-07-07 13:43     ` Nemo
2016-07-07 14:11       ` John Cowan
2016-07-07 14:18       ` Steffen Nurpmeso
2016-07-07 23:47         ` Greg 'groggy' Lehey
2016-07-08  5:40           ` scj
2016-07-08  7:06             ` Greg 'groggy' Lehey
2016-07-08 11:09           ` Steffen Nurpmeso [this message]
2016-07-09  0:03             ` Greg 'groggy' Lehey
2016-07-09 14:24               ` Steffen Nurpmeso
2016-07-09 16:38                 ` John Cowan
2016-07-11 11:20           ` Tony Finch
2016-07-11 11:54             ` Nemo
2016-07-11 13:15             ` Joerg Schilling
2016-07-08 11:25 Norman Wilson
2016-07-08 13:16 ` John Cowan
2016-07-08 14:06   ` Brantley Coile
2016-07-08 14:52 Clem Cole
2016-07-08 14:59 ` Clem Cole
2016-07-08 15:47 ` Nemo
2016-07-08 16:31   ` Steffen Nurpmeso
2016-07-08 20:29   ` Clem Cole
2016-07-08 16:27 ` Steffen Nurpmeso
2016-07-08 18:00 ` Steve Nickolas
2016-07-08 18:23 ` Random832
2016-07-08 20:49   ` Clem Cole
2016-07-08 21:09     ` Ron Natalie
2016-07-08 21:16       ` John Cowan
2016-07-08 21:45         ` Ron Natalie
2016-07-09 16:47 ` Dave Horsfall
2016-07-09 17:03   ` John Cowan
2016-07-09 17:21     ` Milo Velimirovic
2016-07-08 17:36 Norman Wilson
2016-07-10  1:41 Norman Wilson
2016-07-10  1:46 ` Steve Nickolas
2016-07-10  1:52   ` John Cowan
2016-07-12 17:53   ` Tim Bradshaw
2016-07-12 18:05     ` Ronald Natalie
2016-07-13  9:24       ` Wesley Parish
2016-07-13 10:09         ` Joerg Schilling
2016-07-10 21:10 ` Sven Mascheck

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=20160708110912._pmH11Mqe%steffen@sdaoden.eu \
    --to=steffen@sdaoden.eu \
    /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;
as well as URLs for NNTP newsgroup(s).