From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on inbox.vuxu.org X-Spam-Level: X-Spam-Status: No, score=-0.5 required=5.0 tests=DKIM_INVALID,DKIM_SIGNED, HEADER_FROM_DIFFERENT_DOMAINS,HTML_MESSAGE,MAILING_LIST_MULTI, MIME_QP_LONG_LINE,RCVD_IN_DNSWL_NONE autolearn=ham autolearn_force=no version=3.4.2 Received: from minnie.tuhs.org (minnie.tuhs.org [45.79.103.53]) by inbox.vuxu.org (OpenSMTPD) with ESMTP id da8c39a0 for ; Sat, 12 Oct 2019 00:04:35 +0000 (UTC) Received: by minnie.tuhs.org (Postfix, from userid 112) id 8B8159B95F; Sat, 12 Oct 2019 10:04:34 +1000 (AEST) Received: from minnie.tuhs.org (localhost [127.0.0.1]) by minnie.tuhs.org (Postfix) with ESMTP id E63B4946B9; Sat, 12 Oct 2019 10:04:13 +1000 (AEST) Authentication-Results: minnie.tuhs.org; dkim=fail reason="signature verification failed" (1024-bit key; unprotected) header.d=ccc.com header.i=@ccc.com header.b="H9okjjgk"; dkim-atps=neutral Received: by minnie.tuhs.org (Postfix, from userid 112) id F045A946B9; Sat, 12 Oct 2019 10:04:11 +1000 (AEST) Received: from mail-qk1-f176.google.com (mail-qk1-f176.google.com [209.85.222.176]) by minnie.tuhs.org (Postfix) with ESMTPS id D33CD93DBB for ; Sat, 12 Oct 2019 10:04:10 +1000 (AEST) Received: by mail-qk1-f176.google.com with SMTP id f16so10495005qkl.9 for ; Fri, 11 Oct 2019 17:04:10 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ccc.com; s=google; h=from:content-transfer-encoding:mime-version:subject:date:message-id :references:to; bh=pQMgWUEt7Ah5nMgMeOin/Ufo8sgguMomxtCkGlRG8wM=; b=H9okjjgk6CvhSm8VwaJFQNB1hv633epF/X11b9+Ln7WIbLzSNPctS5QjuWwyU6FTtG zK3Fyr1X0upuyc3A83eXS5FQk6mW7tlgHoYA9NLJHNzvSMJcpsEG7rnNgmasJ0IuW5eb ufYpaPOzhf9fZ9vzcO8dIbLFpqGPyMTet4XK0= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:content-transfer-encoding:mime-version :subject:date:message-id:references:to; bh=pQMgWUEt7Ah5nMgMeOin/Ufo8sgguMomxtCkGlRG8wM=; b=XbicOzI6jx16NNu8BN20dCRlAdrI19YwTLv7vL5S3p5ewz7VvZAOM1uYE83EEb1IH6 sSPHmXyqdqqB8gThQlNaOq7ZyK1NMmynFeMH5ww6k+okSH+ugUrafGKrWMtMtust9X/Q MyDfuqFMjlOrZjGuwlLUJjofQOU7llWenefvLhUesp/A32uWhE3tuUoeBJCp01kiV9Z5 ChkPwcqu1PmGqWMMwRmELHAkFh5xkV35IohER34ScS0Qn8+LsmNKl2yyREmbBmS4/lEN t9F2p6jLH0gLW5NL/CKOcYRf16FlVSn3lpQtBRxmcpctXXozPRhL0F+H8AQ5RV9sz8fl YgNw== X-Gm-Message-State: APjAAAXAzx9CtlFiXDInKh9B4RXRfBVRmUI+mSinMKItjb++e/E3QHJ2 4lYWGJJyLMCBYlKRiaXtVRuIXyC4TCs8TQ== X-Google-Smtp-Source: APXvYqxcekLVPQDGXbDW1zk+qxfYm9PXVudVjXj9mB/w3PzQTFAZFHczi0qRrVwTr6h8+/5xAyD9zg== X-Received: by 2002:a37:4a87:: with SMTP id x129mr18220522qka.43.1570838649581; Fri, 11 Oct 2019 17:04:09 -0700 (PDT) Received: from [192.168.127.101] (pool-173-48-42-254.bstnma.fios.verizon.net. [173.48.42.254]) by smtp.gmail.com with ESMTPSA id k18sm4400341qtj.69.2019.10.11.17.04.08 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 11 Oct 2019 17:04:08 -0700 (PDT) From: Clem cole Content-Type: multipart/alternative; boundary=Apple-Mail-4A0CB7AC-D37B-4648-A383-60E476E2A9F7 Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (1.0) Date: Fri, 11 Oct 2019 20:04:06 -0400 Message-Id: <97E7C5AB-B2C6-4C7F-B6D6-E98066E01038@ccc.com> References: <012a01d5808f$0e56dcf0$2b0496d0$@net> To: tuhs@tuhs.org X-Mailer: iPhone Mail (16G114) Subject: [TUHS] Fwd: Curious Question from the Ether about use of Upper and Lower case at DEC X-BeenThere: tuhs@minnie.tuhs.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: The Unix Heritage Society mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: tuhs-bounces@minnie.tuhs.org Sender: "TUHS" --Apple-Mail-4A0CB7AC-D37B-4648-A383-60E476E2A9F7 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable FYI. I sent this to one of the lead DOC people from the old days to see if s= he knew. Here is her answer. Begin forwarded message: > From: "Janet Egan"=20 > Date: October 11, 2019 at 7:53:16 PM EDT > To: "'Clem Cole'"=20 > Subject: RE: Curious Question from the Ether about use of Upper and Lower c= ase at DEC >=20 > Hi Clem, > =20 > Hmm, I don=E2=80=99t remember whether the style guide addressed that. In t= he docs for RSX-11M and such I always wrote it =E2=80=9CPDP-11=E2=80=9D, th= at is upper case with the dash. I do remember the logo on the machine as al= ways lower case with no dash. The PDP-8 had the same style logo. And you=E2=80= =99re right about seeing the lower case on the cover of the handbooks. I ha= ve never seen the lower case with the dash or the upper case without it. I d= on=E2=80=99t think I still have my copy of the style guide. Maybe I=E2=80=99= ll take a look around my archives for it. =20 > =20 > What a fun question to be thinking about . > Janet > =20 > =20 > From: Clem Cole=20 > Sent: Friday, October 11, 2019 9:47 AM > To: Janet Egan > Subject: Curious Question from the Ether about use of Upper and Lower case= at DEC > =20 > Janet, > I'm part of The Unix Historical Society (TUHS) mailing list and a topic= came up that I thought you might be able to shed some light on. The observ= ation was that 'DEC seemed to have a schizophrenic attitude to wrt to use of= upper and lower case WRT to the PDP-11 brand,' i.e. sometimes using "PDP-11= " and sometimes "pdp11" (but I note rarely if ever PDP11 or pdp-11) . For i= nstance, the logo on the system itself was all lower: PDP-11/40 but DEC docu= mentation mostly used uppercase in the text; but when used on the places lik= e the cover could be either e.g. the "pdp11 peripherals handbook" to transc= ribe the cover exactly but it uses upper case "PDP-11" several times on pg 1= -1 and the same on the binding. But I could not find examples of pdp-11 or P= DP11, i.e. if all lower it was with the dash or all upper without. > =20 > Do you remember if there were rules or guidelines and if so what they mi= ght have been? > =20 > Thanks, > Clem --Apple-Mail-4A0CB7AC-D37B-4648-A383-60E476E2A9F7 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: quoted-printable FYI.  I sent this to one of the lead D= OC people from the old days to see if she knew.  Here is her answer.

Begin forwarded message:

From: "Janet Egan" 
Date: O= ctober 11, 2019 at 7:53:16 PM EDT
To: "'Clem Cole'" 
Su= bject: RE: Curious Question from the Ether about use of Upper and Low= er case at DEC

Hi Clem,

 

Hmm, I don=E2=80=99t remember whether t= he style guide addressed that. In the docs for  RSX-11M and such I alwa= ys wrote it =E2=80=9CPDP-11=E2=80=9D, that is upper case with the dash. &nbs= p;I do remember the logo on the machine as always lower case with no dash. T= he PDP-8 had the same style logo. And you=E2=80=99re right about seeing the l= ower case on the cover of the handbooks.  I have never seen the lower c= ase with the dash or the upper case without it. I don=E2=80=99t think I stil= l have my copy of the style guide. Maybe I=E2=80=99ll take a look around my a= rchives for it.   

 

What a fun question to be thinking about .

Janet

 

 

From:<= span style=3D"font-size:10.0pt;font-family:"Tahoma","sans-ser= if""> Clem Cole 
Sent: Friday, October 11, 2019 9:47 AM<= br>To: Janet Egan
Subject: Curious Question from the Ether a= bout use of Upper and Lower case at DEC

 

Janet,=

   I'm part of The Unix Hist= orical Society (TUHS) mailing list and a topic came up that I thought you mi= ght be able to shed some light on.  The observation was that 'DEC s= eemed to have a schizophrenic attitude to wrt to use of upper and lower= case WRT to the PDP-11 brand,' i.e. sometimes using "PDP-11" and sometimes "= pdp11"  (but I note rarely if ever PDP11 or pdp-11) . For instance, the= logo on the system itself was all lower: P= DP-11/40 but DEC documentation mostly used uppercase in the text; b= ut when used on the places like the cover could be either  e.g.= the "pdp11 peripherals handbook" to transcribe the cover exactly b= ut it uses upper case "PDP-11" several times on pg 1-1 and the same on t= he binding.  But I could not find examples of pdp-11 or PDP11,&nbs= p;i.e. if all lower it was with the dash or all upper without.

 

=

  Do you remember if there were rules or guideline= s and if so what they might have been?

 

Thanks,

Clem

= --Apple-Mail-4A0CB7AC-D37B-4648-A383-60E476E2A9F7--