<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:georss="http://www.georss.org/georss" xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#" xmlns:media="http://search.yahoo.com/mrss/"
		>
<channel>
	<title>Comments on: Of Secret Codes, Abbreviations, and Knowledge Lost and Gained</title>
	<atom:link href="http://blog.thehenryford.org/2009/05/27/of-secret-codes-abbreviations-and-knowledge-lost-and-gained/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.thehenryford.org/2009/05/27/of-secret-codes-abbreviations-and-knowledge-lost-and-gained/</link>
	<description>Offical blog of The Henry Ford</description>
	<lastBuildDate>Thu, 19 Nov 2009 14:33:36 +0000</lastBuildDate>
	<generator>http://wordpress.com/</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Nathan and his Open Ideals &#187; ITP2800 – Week 3 – Nathan&#8217;s Story, Secret Videos and Student Proposals</title>
		<link>http://blog.thehenryford.org/2009/05/27/of-secret-codes-abbreviations-and-knowledge-lost-and-gained/#comment-392</link>
		<dc:creator>Nathan and his Open Ideals &#187; ITP2800 – Week 3 – Nathan&#8217;s Story, Secret Videos and Student Proposals</dc:creator>
		<pubDate>Fri, 25 Sep 2009 06:28:06 +0000</pubDate>
		<guid isPermaLink="false">http://thehenryford.wordpress.com/?p=28#comment-392</guid>
		<description>[...] &#8220;Of Secret Codes, Abbreviations, and Knowledge Lost and Gained&#8221; http://blog.thehenryford.org/2009/05/27/of-secret-codes-abbreviations-and-knowledge-lost-and-gained/ [...]</description>
		<content:encoded><![CDATA[<p>[...] &#8220;Of Secret Codes, Abbreviations, and Knowledge Lost and Gained&#8221; <a href="http://blog.thehenryford.org/2009/05/27/of-secret-codes-abbreviations-and-knowledge-lost-and-gained/" rel="nofollow">http://blog.thehenryford.org/2009/05/27/of-secret-codes-abbreviations-and-knowledge-lost-and-gained/</a> [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: links for 2009-08-24 &#124; Nathan and his Open Ideals</title>
		<link>http://blog.thehenryford.org/2009/05/27/of-secret-codes-abbreviations-and-knowledge-lost-and-gained/#comment-239</link>
		<dc:creator>links for 2009-08-24 &#124; Nathan and his Open Ideals</dc:creator>
		<pubDate>Mon, 24 Aug 2009 16:03:01 +0000</pubDate>
		<guid isPermaLink="false">http://thehenryford.wordpress.com/?p=28#comment-239</guid>
		<description>[...] Of Secret Codes, Abbreviations, and Knowledge Lost and Gained « The Henry Ford Blog It turned out that what I had instead was a commercial telegraphic code. From the 19th through the mid-20th centuries, telegrams were integral to business and personal communications. Telegraph codes proliferated as a way to correspond economically and privately. Readily available code books such as the ABC Universal Commercial Electric Telegraph Code, not to mention many others, were published, with many businesses creating in-house codes. According to telegraphy historian-enthusiast John McVey, “Thousands of codes were published or issued privately, but they are largely forgotten now. They present a finely-grained window into their respective domains and their time. And they provide instances of sometimes stunning visual, technical, lexicographic and unwitting poetic achievement.” (tags: language telegraph)     Share and Enjoy: [...]</description>
		<content:encoded><![CDATA[<p>[...] Of Secret Codes, Abbreviations, and Knowledge Lost and Gained « The Henry Ford Blog It turned out that what I had instead was a commercial telegraphic code. From the 19th through the mid-20th centuries, telegrams were integral to business and personal communications. Telegraph codes proliferated as a way to correspond economically and privately. Readily available code books such as the ABC Universal Commercial Electric Telegraph Code, not to mention many others, were published, with many businesses creating in-house codes. According to telegraphy historian-enthusiast John McVey, “Thousands of codes were published or issued privately, but they are largely forgotten now. They present a finely-grained window into their respective domains and their time. And they provide instances of sometimes stunning visual, technical, lexicographic and unwitting poetic achievement.” (tags: language telegraph)     Share and Enjoy: [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Edward Vielmetti</title>
		<link>http://blog.thehenryford.org/2009/05/27/of-secret-codes-abbreviations-and-knowledge-lost-and-gained/#comment-34</link>
		<dc:creator>Edward Vielmetti</dc:creator>
		<pubDate>Thu, 04 Jun 2009 03:41:01 +0000</pubDate>
		<guid isPermaLink="false">http://thehenryford.wordpress.com/?p=28#comment-34</guid>
		<description>Telegraphic codes persisted a long time - there is a lovely poem in the Atlantic

http://www.theatlantic.com/doc/200505/bradfield

about the code used in the Australian Antarctic research expeditions as late as 1961, where transmissions were in Morse over terrible radio conditions.  the first part reads

Compressed for Morse, compressed to better the odds
this first, flimsy signal might send sense across ocean
unbroken, I type just WYSSA, which you know means
all my love, darling in this telegraph of foreseen
longing.</description>
		<content:encoded><![CDATA[<p>Telegraphic codes persisted a long time &#8211; there is a lovely poem in the Atlantic</p>
<p><a href="http://www.theatlantic.com/doc/200505/bradfield" rel="nofollow">http://www.theatlantic.com/doc/200505/bradfield</a></p>
<p>about the code used in the Australian Antarctic research expeditions as late as 1961, where transmissions were in Morse over terrible radio conditions.  the first part reads</p>
<p>Compressed for Morse, compressed to better the odds<br />
this first, flimsy signal might send sense across ocean<br />
unbroken, I type just WYSSA, which you know means<br />
all my love, darling in this telegraph of foreseen<br />
longing.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: John McVey</title>
		<link>http://blog.thehenryford.org/2009/05/27/of-secret-codes-abbreviations-and-knowledge-lost-and-gained/#comment-31</link>
		<dc:creator>John McVey</dc:creator>
		<pubDate>Tue, 02 Jun 2009 01:28:58 +0000</pubDate>
		<guid isPermaLink="false">http://thehenryford.wordpress.com/?p=28#comment-31</guid>
		<description>I might add that published codes tended to leave blank or &quot;skeleton&quot; sections, in which code words had no phrases printed next to them. These blank sections typically were at the back of the book, but might also be distributed here and there throughout its length. But I suspect you&#039;re right in this case, that this code was abandoned.</description>
		<content:encoded><![CDATA[<p>I might add that published codes tended to leave blank or &#8220;skeleton&#8221; sections, in which code words had no phrases printed next to them. These blank sections typically were at the back of the book, but might also be distributed here and there throughout its length. But I suspect you&#8217;re right in this case, that this code was abandoned.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: John McVey</title>
		<link>http://blog.thehenryford.org/2009/05/27/of-secret-codes-abbreviations-and-knowledge-lost-and-gained/#comment-30</link>
		<dc:creator>John McVey</dc:creator>
		<pubDate>Tue, 02 Jun 2009 01:24:45 +0000</pubDate>
		<guid isPermaLink="false">http://thehenryford.wordpress.com/?p=28#comment-30</guid>
		<description>Thanks for posting this.

There would have been telegraphic codes for supply of automobiles and particularly parts. Their main purpose would have been economy : because telegrams and especially cablegrams (via submarine cable) were priced by the word, communications could be quite expensive.

Secrecy would have likely been at least as important in Liebold&#039;s case, as communications from Ford&#039;s office would have involved managemet, strategic, labor and other issues.

I am surprised there are not published telegraph codes within the Ford archives; even parts lists would have incorporated codes as a matter of course. Keep digging! I&#039;ve seen codes incorporated in parts lists and catalogues for GM, International Harvester, etc.

The codewords shown here seem to me naive for so late a date (ca 1919). For one thing, they do not use the so-called two-letter difference rule, where every code word is at least two letters different from every other (thereby providing some protection from mutilation in transmission). Also, they&#039;re of different lengths. But the codewords interest me less than the phrases, and their organization. I wonder if what you have here is a draft to a later code. Do these sheets come with an instruction in their use?

The &quot;science&quot; of selecting and arranging phrases is different from the science of selecting codes words, or making a &quot;figure code.&quot; Specialists were around for both jobs, although individual business people (men and some women too) were able to crank a code in short order, e.g., for a &quot;present emergency.&quot;

It&#039;s my guess that the item you describe as &quot;guidelines for encoding proper names&quot; is a simple substitution code for encipherment of names that were not otherwise contained in the codebook. But I&#039;m not sure that the first of the two examples you give under that head, actually does that. It may have more to do with encryption of names... I&#039;m just not sure. So-called &quot;s-p-e=l-l-i-n-g&quot; was always a headache when it came to codes, going back to nautical signal codes as well. It was too laborious: you preferred to use code standing for names and phrases, so you didn&#039;t have to spell things out.

Here&#039;s an example of how the ACE &quot;Is base of code and means figures&quot; sheet would work:
TR + ACE = cars (I presume railroad)
GA = 30

thus, FACE FIU = 20 million dollars

I&#039;d love to see more of this. The Ford Company&#039;s cabling to operations overseas, let&#039;s say, Japan, would without doubt have been coded, probably with the company&#039;s proprietary code, perhaps in conjunction with something like Liebers or the ABC 5th or 6th edition.

The telegram of 27 February 1917 examples the common practice of penciling translation on the face (or back) of the telegram itself.</description>
		<content:encoded><![CDATA[<p>Thanks for posting this.</p>
<p>There would have been telegraphic codes for supply of automobiles and particularly parts. Their main purpose would have been economy : because telegrams and especially cablegrams (via submarine cable) were priced by the word, communications could be quite expensive.</p>
<p>Secrecy would have likely been at least as important in Liebold&#8217;s case, as communications from Ford&#8217;s office would have involved managemet, strategic, labor and other issues.</p>
<p>I am surprised there are not published telegraph codes within the Ford archives; even parts lists would have incorporated codes as a matter of course. Keep digging! I&#8217;ve seen codes incorporated in parts lists and catalogues for GM, International Harvester, etc.</p>
<p>The codewords shown here seem to me naive for so late a date (ca 1919). For one thing, they do not use the so-called two-letter difference rule, where every code word is at least two letters different from every other (thereby providing some protection from mutilation in transmission). Also, they&#8217;re of different lengths. But the codewords interest me less than the phrases, and their organization. I wonder if what you have here is a draft to a later code. Do these sheets come with an instruction in their use?</p>
<p>The &#8220;science&#8221; of selecting and arranging phrases is different from the science of selecting codes words, or making a &#8220;figure code.&#8221; Specialists were around for both jobs, although individual business people (men and some women too) were able to crank a code in short order, e.g., for a &#8220;present emergency.&#8221;</p>
<p>It&#8217;s my guess that the item you describe as &#8220;guidelines for encoding proper names&#8221; is a simple substitution code for encipherment of names that were not otherwise contained in the codebook. But I&#8217;m not sure that the first of the two examples you give under that head, actually does that. It may have more to do with encryption of names&#8230; I&#8217;m just not sure. So-called &#8220;s-p-e=l-l-i-n-g&#8221; was always a headache when it came to codes, going back to nautical signal codes as well. It was too laborious: you preferred to use code standing for names and phrases, so you didn&#8217;t have to spell things out.</p>
<p>Here&#8217;s an example of how the ACE &#8220;Is base of code and means figures&#8221; sheet would work:<br />
TR + ACE = cars (I presume railroad)<br />
GA = 30</p>
<p>thus, FACE FIU = 20 million dollars</p>
<p>I&#8217;d love to see more of this. The Ford Company&#8217;s cabling to operations overseas, let&#8217;s say, Japan, would without doubt have been coded, probably with the company&#8217;s proprietary code, perhaps in conjunction with something like Liebers or the ABC 5th or 6th edition.</p>
<p>The telegram of 27 February 1917 examples the common practice of penciling translation on the face (or back) of the telegram itself.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
