Re: [Telecom] Exchange Name pronounciation

Have a question or want to start a discussion? Post it! No Registration Necessary.  Now with pictures!


-------------------------------1198544822
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit

 
 
In a message dated Fri, 21 Dec 2007 13:41:44 -0800  
(PST),hancock4@bbs.cpcn.com
writes:

Quoted text here. Click to load it




This was one of the examples cited in  the Bell System instructions
on names.  Not even inward operators might  recognize the c..o. name from
the pronouncition presented by the originating or  tandem operator.  For
the record, this exchange was presented in the  material as Bala-Cynwyd,
and, as I say, was presented as a horrible  example.
 
      As I have noted  before, there was a reverse problem, too, when the
calling party did not know the correct  pronunciation.  I placed a call once
from Dallas in the 1950s to Mexia, Texas, a place  some 50 or 75 miles
from Dallas and well-know to the operator.   But she did not know what
place I wanted until I spelled it.  (The  prnounciation is Muh-HAY-uh).
 
      [ ,,, ]

Quoted text here. Click to load it
 
       Another problem name was YUkon.   Many customers were likely to dial it
as UK(on).  However, it was the only name presented in the recommended  list
Lisa referred to, so no better one could be found.
 
       Generaly there were four or five names  on the recommnded list that
fit the
first two numerals.  A notable case occurred when the Chevrolet dealer  in
Waco, Texas. was assigned a number in the PLymouth  exchange.  Fortunately
he complained early enough before the actual Xbar conversion (before that  
Waco was step with no letter prefixes) that the name for that dial pull was  
changed to PLaza.



Wes  Leatherock
wesrock@aol.com
wleathus@yahoo.com



**************************************See AOL's top rated recipes
(http://food.aol.com/top-rated-recipes?NCID=aoltop00030000000004 )

-------------------------------1198544822
Content-Type: text/html; charset="US-ASCII"
Content-Transfer-Encoding

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; charset=3DUS-ASCII">
<META content=3D"MSHTML 6.00.6000.16587" name=3DGENERATOR></HEAD>
<BODY id=3Drole_body=20
style=3D"FONT-SIZE: 12pt; COLOR: #000000; FONT-FAMILY: Palatino Linotype"=20
bottomMargin=3D7 leftMargin=3D7 topMargin=3D7 rightMargin=3D7><FONT id=3Drol=
e_document=20
face=3D"Palatino Linotype" color=3D#000000 size=3D3>
<DIV>
<DIV>
<DIV>In a message dated <FONT face=3DArial size=3D2>Fri, 21 Dec 2007 13:41:44 -0800=20
(PST),hancock4@bbs.cpcn.com</FONT><BR>writes:</DIV><FONT=20
style=3D"BACKGROUND-COLOR: transparent" face=3DArial color=3D#000000 size=
=3D2>

<DIV><STRONG><FONT face=3D"Palatino Linotype" size=3D3></FONT></STRONG><STRONG><FONT=20
face=3D"Palatino Linotype" size=3D3></FONT></STRONG><BR>&gt; When operators
could=20
dial toll calls themselves (and later<BR>&gt; subscribers), confusing names=20
caused problems.&nbsp; During the 1950s the<BR>&gt; Bell System renamed many=
=20
local exchanges for that reason and used a<BR>&gt; standardized=20

list.<BR><STRONG><FONT face=3D"Palatino Linotype"=20
size=3D3>&gt;</FONT></STRONG><BR>&gt; For instance, outside Phila there was
a town=20
and exchange "Cynwyd".<BR>&gt; It was pronounced "Kinwood".&nbsp; Obviously
in=20
dialing a name like that<BR>&gt; would cause problems.&nbsp; It was=20
changed.<BR></DIV><STRONG><FONT face=3D"Palatino Linotype"=20
size=3D3></FONT></STRONG></FONT></DIV>
<DIV><FONT style=3D"BACKGROUND-COLOR: transparent" face=3DArial color=3D#000000=20
size=3D2><STRONG><FONT face=3D"Palatino Linotype"=20
size=3D3></FONT></STRONG></FONT>&nbsp;</DIV><FONT=20
style=3D"BACKGROUND-COLOR: transparent" face=3DArial color=3D#000000=20
size=3D2></FONT></DIV>
<DIV><FONT style=3D"BACKGROUND-COLOR: transparent" face=3DArial color=3D#000000=20
size=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;This was one of the examples cited in=20
the Bell System instructions</FONT></DIV>

<DIV><FONT face=3DArial size=3D2>on names.&nbsp; Not even inward operators might=20
recognize the c..o. name from</FONT></DIV>

<DIV><FONT face=3DArial size=3D2>the pronouncition presented by the originating or=20
tandem operator.&nbsp; For </FONT></DIV>

<DIV><FONT face=3DArial size=3D2>the record, this exchange was presented in
the=20
material as Bala-Cynwyd,</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>and, as I say, was presented as a horrible=20
example.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; As I have noted=20
before, there&nbsp;was a reverse problem, too, when the</FONT></DIV>

<DIV><FONT face=3DArial size=3D2>calling party did not know the correct=20
pronunciation.&nbsp; I placed a call once</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>from Dallas in the 1950s to Mexia, Texas, a place=20
some 50 or 75 miles</FONT></DIV>

<DIV><FONT face=3DArial size=3D2>from Dallas and well-know to the operator.&nbsp;=20
But she did not know what</FONT></DIV>

<DIV><FONT face=3DArial size=3D2>place I wanted until I spelled it.&nbsp; (The=20
prnounciation is Muh-HAY-uh).</FONT></DIV>

<DIV><FONT style=3D"BACKGROUND-COLOR: transparent" face=3DArial color=3D#000000=20
size=3D2><STRONG><FONT face=3D"Palatino Linotype"=20
size=3D3></FONT></STRONG></FONT>&nbsp;</DIV>
<DIV><FONT style=3D"BACKGROUND-COLOR: transparent" face=3DArial color=3D#000000=20
size=3D2><STRONG><FONT face=3D"Palatino Linotype"=20
size=3D3>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; [ ,,, ]</FONT></STRONG></FONT></DIV><FONT=20
style=3D"BACKGROUND-COLOR: transparent" face=3DArial color=3D#000000=20

size=3D2><STRONG><FONT face=3D"Palatino Linotype" size=3D3></FONT></STRONG>
<DIV><STRONG><FONT face=3D"Palatino Linotype" size=3D3></FONT></STRONG><STRONG><FONT=20
face=3D"Palatino Linotype" size=3D3></FONT></STRONG><BR>&gt; Also, the Bell
System=20
used many names with potential confusion, such<BR>&gt; as HYatt and HYacinth=
,=20
which could be easily dialed as HI instead of<BR>&gt; HY.&nbsp; Using "Y" (9=
) as=20
a vowel could be confusing but coming up with<BR>&gt; names for n9x wasn't t=
oo=20
easy.&nbsp; (CYpress, EXport, HYatt, LYric, OWen,<BR>&gt; SYosset/SWinburne,=
=20
TYler, WYmouth.)&nbsp; </DIV>

<DIV><STRONG><FONT face=3D"Palatino Linotype" size=3D3></FONT></STRONG>&nbsp;</DIV>
<DIV>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Another problem name was YUkon.&nbsp;=20
Many customers were likely to dial it</DIV>

<DIV>as UK(on).&nbsp; However, it was the only name presented in the recommended=20
list</DIV>

<DIV>Lisa referred to, so no better one could be found.</DIV>
<DIV>&nbsp;</DIV>
<DIV>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Generaly there were four or five names=20
on the recommnded list that fit the</DIV>

<DIV>first two numerals.&nbsp; A notable case occurred when the Chevrolet dealer=20
in</DIV>

<DIV>Waco,&nbsp;Texas. was assigned a number in the PLymouth=20
exchange.&nbsp;&nbsp;Fortunately</DIV>
<DIV>he complained early enough before the actual Xbar conversion (before that=20
Waco was step with no letter prefixes) that the name for that dial pull was=20
changed to PLaza.</DIV>
<DIV><BR>&nbsp;</DIV></FONT>
<DIV><STRONG></STRONG>&nbsp;</DIV>

<DIV><FONT lang=3D0 face=3DArial color=3D#400040 size=3D3 FAMILY=3D"SANSSERIF"=20
PTSIZE=3D"12">Wes=20
BR><BR><DIV><FONT style=3D"color: black; font: normal 10pt ARIAL, SAN-SERIF;=
"><HR style=3D"MARGIN-TOP: 10px">See AOL's <A title=3D"http://food.aol.com/top-rated-recipes?NCID=3Daoltop00030000000004 " href=3D"http://food.aol.com/to =
p-rated-recipes?NCID=3Daoltop00030000000004" target=3D"_blank">top rated rec=

ipes</A> and <A title=3D"http://body.aol.com/fitness/winter-exercise?NCID=3Daoltop00030000000003 " href=3D"http://body.aol.com/fitness/winter-exercise =
?NCID=3Daoltop00030000000003" target=3D"_blank">easy ways to stay in shape</=

A> for winter.</FONT></DIV></BODY></HTML>

-------------------------------1198544822--