From: cym224@gmail.com (Nemo)
Subject: [TUHS] Slashes (was: MS-DOS)
Date: Thu, 7 Jul 2016 09:43:05 -0400 [thread overview]
Message-ID: <CAJfiPzxSvYj=H5Gz+D6mgVU-K19JKX5yetpA0h9enEGTnCGmOw@mail.gmail.com> (raw)
In-Reply-To: <20160707050242.GD78278@eureka.lemis.com>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1387 bytes --]
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.
>>>
>>> If that's too oblique for some of you, I can't help.
>>
>> I think the proper term is "Virgule" anyway. ;)
>
> For some definition of "proper". But it's doubly ambiguous: it's the
> French word for comma, and OED states:
>
> A thin sloping or upright line (/, |) occurring in mediæval MSS. as
> a mark for the cæsura or as a punctuation-mark (frequently with the
> same value as the modern comma).
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.
N.
>
> In modern context, it might apply equally to \\.
> Clearly that has even more capacity to confuse.
>
> Greg
> --
> Sent from my desktop computer.
> Finger grog at FreeBSD.org for PGP public key.
> See complete headers for address and phone numbers.
> This message is digitally signed. If your Microsoft mail program
> reports problems, please read http://lemis.com/broken-MUA
next prev parent reply other threads:[~2016-07-07 13:43 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 [this message]
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
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='CAJfiPzxSvYj=H5Gz+D6mgVU-K19JKX5yetpA0h9enEGTnCGmOw@mail.gmail.com' \
--to=cym224@gmail.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 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).