<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Posts | λy: B. Slade(linguist)</title><link>https://lambda-y.net/post/</link><atom:link href="https://lambda-y.net/post/index.xml" rel="self" type="application/rss+xml"/><description>Posts</description><generator>Wowchemy (https://wowchemy.com)</generator><language>en-gb</language><image><url>https://lambda-y.net/media/icon_hueeecf3e228d902e5ced7487b7befc65f_38970_512x512_fill_lanczos_center_3.png</url><title>Posts</title><link>https://lambda-y.net/post/</link></image><item><title>LaTeX in half an hour for linguists (and others)</title><link>https://lambda-y.net/post/latex-in-30-minutes-linguists/</link><pubDate>Thu, 04 Jul 2019 22:12:26 -0600</pubDate><guid>https://lambda-y.net/post/latex-in-30-minutes-linguists/</guid><description>&lt;p>A self-illustrating tutorial on using LaTeX, aimed at linguists, but
it should be useful for non-linguists as well: &lt;a href="https://gitlab.com/emacsomancer/latex-for-linguists" target="_blank" rel="noopener">https://gitlab.com/emacsomancer/latex-for-linguists&lt;/a>&lt;/p>
&lt;p>It illustrates a number of basic things: enough to cover all of the
basic things a linguist would need for writing a paper (excluding
bibliography things for the moment), and shows off some of the more
exciting typographical possibilities of LaTeX.&lt;/p>
&lt;p>The &lt;code>.tex&lt;/code> file is directly accessible here: &lt;a href="https://gitlab.com/emacsomancer/latex-for-linguists/blob/master/basic-for-linguists.tex" target="_blank" rel="noopener">https://gitlab.com/emacsomancer/latex-for-linguists/blob/master/basic-for-linguists.tex&lt;/a>&lt;/p>
&lt;p>And the resulting &lt;code>.pdf&lt;/code> here: &lt;a href="https://gitlab.com/emacsomancer/latex-for-linguists/blob/master/basic-for-linguists.pdf" target="_blank" rel="noopener">https://gitlab.com/emacsomancer/latex-for-linguists/blob/master/basic-for-linguists.pdf&lt;/a>&lt;/p></description></item><item><title>Scheming French Geeks, Eunuchs OS, Lisping &amp; lots of Guile</title><link>https://lambda-y.net/post/scheming-french-geeks-with-guile/</link><pubDate>Sat, 04 Aug 2018 09:46:00 -0600</pubDate><guid>https://lambda-y.net/post/scheming-french-geeks-with-guile/</guid><description>&lt;p>I&amp;rsquo;ve recently installed &lt;a href="https://www.gnu.org/software/guix/" target="_blank" rel="noopener">GuixSD&lt;/a>, a distribution of GNU &lt;a href="https://en.wikipedia.org/wiki/Linux" target="_blank" rel="noopener">Linux&lt;/a>, on one
of my machines. GuixSD&lt;sup>&lt;a href="#org2d02451">‖&lt;/a>&lt;/sup>&lt;a id="org65bd8e5">&lt;/a> is notable for having a number of major
components (package manager, init system) written in &lt;a href="https://en.wikipedia.org/wiki/GNU_Guile" target="_blank" rel="noopener">GNU Guile&lt;/a>, an
implementation of &lt;a href="https://en.wikipedia.org/wiki/Scheme_%28programming_language%29" target="_blank" rel="noopener">Scheme&lt;/a>, which is itself a dialect of &lt;a href="https://en.wikipedia.org/wiki/Lisp_%28programming_language%29" target="_blank" rel="noopener">Lisp&lt;/a>
(formerly LISP)&lt;sup>&lt;a href="#org8188f4f">†&lt;/a>&lt;/sup>&lt;a id="org70af563">&lt;/a>. But &lt;em>Guix&lt;/em> is pronounced &lt;code>/ɡiːks/&lt;/code> (i.e. identically
to &lt;em>geeks&lt;/em>). Why?&lt;/p>
&lt;p>The final &lt;em>x&lt;/em> of &lt;em>Guix&lt;/em> is presumably by analogy to &lt;em>Linux&lt;/em>, which
was itself produced by analogy to &lt;a href="https://en.wikipedia.org/wiki/Unix" target="_blank" rel="noopener">&lt;em>Unix&lt;/em>&lt;/a>&lt;sup>&lt;a href="#org7db0f64">‡&lt;/a>&lt;/sup>&lt;a id="org88ffda0">&lt;/a>, based on the first name
of its creator, &lt;a href="https://en.wikipedia.org/wiki/Linus_Torvalds" target="_blank" rel="noopener">&lt;strong>Linus&lt;/strong> Torvalds&lt;/a>.&lt;sup>&lt;a href="#orgc1729f4">*&lt;/a>&lt;/sup>&lt;a id="orga223c44">&lt;/a> Final &lt;em>x&lt;/em> appears in other
software/computer names, including LaTeX (where it is not,
however, pronounced as &lt;code>/ks/&lt;/code> but as &lt;code>/χ/&lt;/code> or at least &lt;code>/k/&lt;/code>).&lt;/p>
&lt;p>So what about the &lt;em>Gui&lt;/em> bit? Transparently that would seem to
derived from the initial part of &lt;em>Guile&lt;/em>, which, however, is of
course pronounced &lt;code>/ɡaɪl/&lt;/code>. So how do we get to &lt;code>/ɡiːks/&lt;/code>
(i.e. &lt;em>geeks&lt;/em>)? Through French orthography (and an obvious
intention). So in French orthography &lt;em>Gui&lt;/em> is pronounced &lt;code>/gi/&lt;/code>,
e.g. in names like &lt;em>Guillaume&lt;/em> (the French equivalent of English
&lt;em>William&lt;/em>). Likewise, &lt;em>x&lt;/em> in French is &lt;code>/ks/&lt;/code>, so the whole
combination would be realised in French as &amp;hellip; &lt;code>/ɡiːks/&lt;/code>. And it&amp;rsquo;s
probably no accident that the Guix team seems to have a number of
Francophone developers, including the project lead &lt;a href="http://web.fdn.fr/~lcourtes/" target="_blank" rel="noopener">Ludovic
Courtès&lt;/a>.&lt;/p>
&lt;p>What&amp;rsquo;s with the tricky names of the programming languages? Guile,
Scheme. Guile is the GNU Foundation&amp;rsquo;s implementation of Scheme,
and so the playful naming-by-synonymy makes sense. Scheme itself
was originally &lt;em>Schemer&lt;/em> (where some sort of file name limitation
resulted in its current name), following a naming convention of
other Lisp dialects/derived languages including &lt;a href="https://en.wikipedia.org/wiki/Planner_%28programming_language%29" target="_blank" rel="noopener">PLANNER&lt;/a> and
CONNIVER (though where the &amp;lsquo;tricky&amp;rsquo; naming scheme originated is
not clear to me).&lt;/p>
&lt;p>Moving away from the recent &amp;lsquo;technological&amp;rsquo; use of these names,
&lt;em>guile&lt;/em> itself is an interesting word. &lt;em>Guile&lt;/em> was borrowed into
English from Old French &lt;em>guile&lt;/em> (though the Francophone spelling),
with cognates in Provençal &lt;em>guila&lt;/em> and Portuguese
&lt;em>guilha&lt;/em>. &lt;em>Guile&lt;/em> appears early in Middle English, at least by the
early 13th century (some representative quotes follow).&lt;/p>
&lt;blockquote>
&lt;p>c1230 (▸?a1200) &lt;em>Ancrene Riwle&lt;/em> (Corpus Cambr.) (1962) 105 Muche gile is i vox.&lt;/p>
&lt;/blockquote>
&lt;!--quoteend-->
&lt;blockquote>
&lt;p>13.. &lt;em>K. Alis.&lt;/em> 1427 The thridde day, withoute gyle, He aryved at Cysile.&lt;/p>
&lt;/blockquote>
&lt;!--quoteend-->
&lt;blockquote>
&lt;p>a1400 &lt;em>Sir Perc.&lt;/em> 1034 He was by-thoghte of a gyle.&lt;/p>
&lt;/blockquote>
&lt;p>In Middle English (and presumably Old French) it would have been
pronounced &lt;code>/giːl/&lt;/code>; the &lt;a href="https://en.wikipedia.org/wiki/Great_Vowel_Shift" target="_blank" rel="noopener">Great English Vowel Shift&lt;/a>, which affected English
long vowels, resulted in modern &lt;code>/gaɪl/&lt;/code>.&lt;/p>
&lt;p>The Old French word itself has been theorised to come from a borrowing from
(Germanic) Frankish &lt;em>*wigila&lt;/em> &amp;ldquo;ruse&amp;rdquo;, and thus makes &lt;em>guile&lt;/em>
cognate with English &lt;em>wile&lt;/em> &amp;ldquo;stratagem practiced for ensnaring or
deception; a sly, insidious artifice&amp;rdquo; (usually in the plural forms
&lt;em>wiles&lt;/em>), which itself has somewhat dark and dubious origins,
potentially an inheritance from native Old English, though
possibly a borrowing from Old Norse, as the earlier attestations
are from areas of the Danelaw of England which were obviously
subject to heavy Scandinavian influence.&lt;/p>
&lt;p>Amusingly, despite its very Francophone orthographic garb, French
lost &lt;em>guile&lt;/em> at some point and so the word is absent in modern
French (the modern equivalent seems to be French &lt;em>ruse&lt;/em>).&lt;/p>
&lt;p>[If you&amp;rsquo;re interested in the technological side of Guix, have a look
at &lt;a href="https://babbagefiles.xyz/guix_maze_of_lispy_little_passages/" target="_blank" rel="noopener">this post over on my tech blog&lt;/a>.]&lt;/p>
&lt;p>&lt;a id="org2d02451">&lt;/a>&lt;a href="#org65bd8e5">‖&lt;/a> The &amp;lsquo;SD&amp;rsquo; stands for &amp;lsquo;software distribution.&lt;/p>
&lt;p>&lt;a id="org8188f4f">&lt;/a>&lt;a href="#org70af563">†&lt;/a> LISP was coined from &amp;ldquo;LISt Processor&amp;rdquo;, since the list is the
central syntactic structure, common to data and code
representation in Lisps. Lisp is an interesting artificial
language in that it has a number of dialects, including &lt;a href="https://common-lisp.net/" target="_blank" rel="noopener">Common
Lisp&lt;/a> (reminiscent of Tolkien&amp;rsquo;s Common Tongue) as well as Scheme,
&lt;a href="https://racket-lang.org/" target="_blank" rel="noopener">Racket&lt;/a> (Scheme-related, thus the name), &lt;a href="https://clojure.org/" target="_blank" rel="noopener">Clojure&lt;/a> and many
others. The originator of Lisp, &lt;a href="https://en.wikipedia.org/wiki/John_McCarthy_%28computer_scientist%29" target="_blank" rel="noopener">John McCarthy&lt;/a>, was strongly
influenced by lambda calculus, the formalism developed by &lt;a href="https://en.wikipedia.org/wiki/Alonzo_Church" target="_blank" rel="noopener">Alonzo
Church&lt;/a> (one of Alan Turing&amp;rsquo;s mentors), which also of course is
important in formal semantics as practised within linguistics.&lt;/p>
&lt;p>&lt;a id="org7db0f64">&lt;/a>&lt;a href="#org88ffda0">‡&lt;/a> Why Unix should be so called is a elaborate instance of word-play
itself. It was in some ways the successor to an earlier operating
system called &lt;em>Multics&lt;/em>. Both Unix and &lt;a href="https://en.wikipedia.org/wiki/Multics" target="_blank" rel="noopener">Multics&lt;/a> were originally
designed to be multi-user/time-sharing operating systems for large
expensive computers in late 60s/early 70s. &lt;em>Multics&lt;/em> is based on a
straight-forward acronym of &lt;em>Multiplexed Information and Computing
Service&lt;/em>, while &lt;em>Unix&lt;/em> is a play on &lt;em>Multics&lt;/em> with &lt;em>multi-&lt;/em> being
substituted by &lt;em>uni-&lt;/em>, and the result sounding like &lt;em>eunuchs&lt;/em>,
with the suggestion of Unix being an &amp;lsquo;emasculated&amp;rsquo; Multics.&lt;/p>
&lt;p>&lt;a id="orgc1729f4">&lt;/a>&lt;a href="#orga223c44">*&lt;/a> Unfortunately &lt;em>Linux&lt;/em> is not based on what would be the more
interesting recursive acronym &amp;ldquo;Linux Is Not UniX&amp;rdquo; – unlike &lt;em>GNU&lt;/em>,
which is indeed the recursive acronym &amp;ldquo;GNU is Not Unix&amp;rdquo;.&lt;/p></description></item><item><title>Of typewriters, runes, and short-hand</title><link>https://lambda-y.net/post/tironian_et_and_ampersand_seven/</link><pubDate>Tue, 19 Jun 2018 14:18:00 -0600</pubDate><guid>https://lambda-y.net/post/tironian_et_and_ampersand_seven/</guid><description>&lt;p>Or, &lt;em>why is the &lt;code>&amp;amp;&lt;/code> on the &lt;code>7&lt;/code> key?&lt;/em>&lt;/p>
&lt;p>Back in ca. 2003, when I was preparing the diplomatic edition of &lt;em>Beowulf&lt;/em> for
&lt;a href="https://heorot.dk" target="_blank" rel="noopener">Beowulf on Steorarume (heorot.dk)&lt;/a>, I noticed the use of what looks like
the Arabic numeral &amp;lsquo;7&amp;rsquo; for &lt;em>and&lt;/em> (Old English &lt;em>ond&lt;/em>).&lt;/p>
&lt;h2 id="beowulf-f-dot-132v-ll-dot-120b-123a">&lt;em>Beowulf&lt;/em> f.132v: ll.120b-123a&lt;/h2>
&lt;figure >
&lt;div class="d-flex justify-content-center">
&lt;div class="w-100" >&lt;img alt="" srcset="
/post/tironian_et_and_ampersand_seven/132v-selection-highlight_hu3c83ab3408d064b8648f023903ad287a_187993_74bed07be818626af9dd1706cc324126.jpg 400w,
/post/tironian_et_and_ampersand_seven/132v-selection-highlight_hu3c83ab3408d064b8648f023903ad287a_187993_d65ef837b28d9f0066033124f32a7e3b.jpg 760w,
/post/tironian_et_and_ampersand_seven/132v-selection-highlight_hu3c83ab3408d064b8648f023903ad287a_187993_1200x1200_fit_q75_lanczos.jpg 1200w"
src="https://lambda-y.net/post/tironian_et_and_ampersand_seven/132v-selection-highlight_hu3c83ab3408d064b8648f023903ad287a_187993_74bed07be818626af9dd1706cc324126.jpg"
width="760"
height="350"
loading="lazy" data-zoomable />&lt;/div>
&lt;/div>&lt;/figure>
&lt;head>
&lt;meta http-equiv="Content-Type" content="text/html; charset=UTF-8" />
&lt;style type="text/css">
/* Left-aligned text in a centered block (does not work in Adobe Digital Editions 1.7) */
.poem {
display: table;
margin-right: auto;
margin-left: auto;
}
&lt;pre>&lt;code>/* Indent wrapping lines */
.stanza {
text-indent: 0;
margin-left: 2em;
}
.verse {
margin-left: -2em;
}
&lt;/code>&lt;/pre>
&lt;p>&lt;/style>&lt;/p>
&lt;/head>
&lt;body style="font-size: 75%;">
&lt;div style="float: left; width: 50%;">
&lt;ul>
&lt;p class="stanza">&lt;span class="verse">wiht unhælo&lt;/span>&lt;br />
&lt;span class="verse">grim &lt;span style="color:red">⁊&lt;/span> grædig gearo sona wæs&lt;/span>&lt;br />
&lt;span class="verse">reoc &lt;span style="color:red">⁊&lt;/span> reþe &lt;span style="color:red">⁊&lt;/span> on ræste genam&lt;/span>&lt;br />
&lt;span class="verse">þritig þegna&lt;/span>
&lt;/p>
&lt;/ul>
&lt;/div>
&lt;div style="float: right; width: 50%;">
&lt;ul>
&lt;p class="stanza">&lt;span class="verse">The unholy creature,&lt;/span>&lt;br />
&lt;span class="verse">grim &lt;span style="color:red">and&lt;/span> greedy, soon was geared-up,&lt;/span>&lt;br />
&lt;span class="verse">wild &lt;span style="color:red">and&lt;/span> savage; &lt;span style="color:red">and&lt;/span> seized from their sleep&lt;/span>&lt;br />
&lt;span class="verse">thirty thanes&lt;/span>
&lt;/p>
&lt;/div>
&lt;/ul>
&lt;/body>
&lt;/html>
&lt;p>This turned out to be a &lt;a href="https://en.wikipedia.org/wiki/Tironian%5Fnotes" target="_blank" rel="noopener">Tironian &lt;em>et&lt;/em> (⁊)&lt;/a> , one of a number of
shorthand symbols devised by Marcus Tullius Cicero&amp;rsquo;s slave and
ppersonal secretary Tiro in the first century which continued to be
used by monastic scribes in the medieval period. The more familiar
abbreviation of &lt;em>et&lt;/em> &amp;ldquo;and&amp;rdquo; is of course the ampersand &lt;code>&amp;amp;&lt;/code>, which,
unlike &lt;code>⁊&lt;/code>, is in fact a stylised &lt;em>et&lt;/em>. (For more discussion of some
of the back history of both the ampersand and the Tironian &lt;em>et&lt;/em> see
these &lt;a href="https://web.archive.org/web/20180318061514/www.shadycharacters.co.uk/2011/06/the-ampersand-part-1-of-2/" target="_blank" rel="noopener">Shady&lt;/a> &lt;a href="https://web.archive.org/web/20180423230942/http://www.shadycharacters.co.uk/2011/06/the-ampersand-part-2-of-2/" target="_blank" rel="noopener">Characters&lt;/a> &lt;a href="https://web.archive.org/web/20180329153622/http://www.shadycharacters.co.uk/2011/07/the-ampersand-part-2%25c2%25bd-of-2/" target="_blank" rel="noopener">posts&lt;/a>.)&lt;/p>
&lt;h2 id="other-shapes-of-the-tironian-et">Other shapes of the Tironian et&lt;/h2>
&lt;figure >
&lt;div class="d-flex justify-content-center">
&lt;div class="w-100" >&lt;img alt="" srcset="
/post/tironian_et_and_ampersand_seven/Tironian_et_shapes_hu4f2d1ac920d5354b777f85d125f40efe_8304_3c0dab8bbb87c0707f92ee2f6fc42115.jpg 400w,
/post/tironian_et_and_ampersand_seven/Tironian_et_shapes_hu4f2d1ac920d5354b777f85d125f40efe_8304_c860f4ee1f5a342928a76f0834ed6d05.jpg 760w,
/post/tironian_et_and_ampersand_seven/Tironian_et_shapes_hu4f2d1ac920d5354b777f85d125f40efe_8304_1200x1200_fit_q75_lanczos.jpg 1200w"
src="https://lambda-y.net/post/tironian_et_and_ampersand_seven/Tironian_et_shapes_hu4f2d1ac920d5354b777f85d125f40efe_8304_3c0dab8bbb87c0707f92ee2f6fc42115.jpg"
width="255"
height="98"
loading="lazy" data-zoomable />&lt;/div>
&lt;/div>&lt;/figure>
&lt;p>The fact that the Tironian &lt;em>et&lt;/em> &lt;code>⁊&lt;/code>, a shorthand &amp;lsquo;quick&amp;rsquo; symbol like
the ampersand &lt;code>&amp;amp;&lt;/code>, looks like an Arabic numeral &lt;code>7&lt;/code> makes the
appearance of the &lt;code>&amp;amp;&lt;/code> above the &lt;code>7&lt;/code> (i.e. as the shifted value of the
&lt;code>7&lt;/code>) seem significant. At the time of creating the diplomatic web
edition of &lt;em>Beowulf&lt;/em> I assumed that this must be the reason for the
particular placement of the &lt;code>&amp;amp;&lt;/code> on keyboards.&lt;/p>
&lt;p>Unsurprisingly, other people have thought of this as well, including a
&lt;a href="https://english.stackexchange.com/questions/200710/did-the-tironian-et-have-any-impact-on-the-ampersand-being-shift-7-on" target="_blank" rel="noopener">StackExchange question&lt;/a> (as well as &lt;a href="https://web.archive.org/web/20180318061514/http://www.shadycharacters.co.uk/2011/06/the-ampersand-part-1-of-2/#comment-699" target="_blank" rel="noopener">a comment on a Shady Characters
post on ampersands&lt;/a>). There the &amp;lsquo;accepted answer&amp;rsquo; to this question says:&lt;/p>
&lt;blockquote>
&lt;p>Although the &lt;code>7&lt;/code> was the ampersand on IBM&amp;rsquo;s standard keyboard layout,
that is hardly universal. The first nine printable characters in ASCII
are &lt;code>!&lt;/code> &lt;code>&amp;quot;&lt;/code> &lt;code>#&lt;/code> &lt;code>$&lt;/code> &lt;code>%&lt;/code> &lt;code>&amp;amp;&lt;/code> &lt;code>'&lt;/code> &lt;code>(&lt;/code> &lt;code>)&lt;/code>, which should give a good clue
as to what the top row of a teletype keyboard looked like. On many
early teletypes and terminals (and also, BTW, on the Apple ][), the
shift key toggled bit 4 of the character being produced, thus it would
turn a &lt;code>1&lt;/code> (011 0001) into &lt;code>!&lt;/code> (010 0001), and &lt;code>,&lt;/code> (010 1100) into &lt;code>&amp;lt;&lt;/code>
(011 1100). Since the digits 1–9 received consecutive code, so did the
characters produced by combining them with the shift key. &lt;code>Shift-7&lt;/code> on
those keyboards was apostrophe; the ampersand was &lt;code>shift-6&lt;/code>.&lt;/p>
&lt;p>Other typewriter keyboards also varied considerably in where they put
the ampersand. Its association with the number &lt;code>7&lt;/code> is nowhere near as
consistent as the association between &lt;code>1&lt;/code> and &lt;code>!&lt;/code>, &lt;code>3&lt;/code> and &lt;code>#&lt;/code>, &lt;code>4&lt;/code>
and &lt;code>$&lt;/code>, or &lt;code>5&lt;/code> and &lt;code>%&lt;/code> which existed in both older computer keyboards
and today&amp;rsquo;s US arrangement.&lt;/p>
&lt;/blockquote>
&lt;figure >
&lt;div class="d-flex justify-content-center">
&lt;div class="w-100" >&lt;img alt="" srcset="
/post/tironian_et_and_ampersand_seven/USASCII_code_chart_hub5fb3e959e3459c329d826a1d165a7f3_35643_87fb19ca3694de30ac53913d965396d7.png 400w,
/post/tironian_et_and_ampersand_seven/USASCII_code_chart_hub5fb3e959e3459c329d826a1d165a7f3_35643_e3c190fd7e7b301ad6b04054c1a8507e.png 760w,
/post/tironian_et_and_ampersand_seven/USASCII_code_chart_hub5fb3e959e3459c329d826a1d165a7f3_35643_1200x1200_fit_lanczos_3.png 1200w"
src="https://lambda-y.net/post/tironian_et_and_ampersand_seven/USASCII_code_chart_hub5fb3e959e3459c329d826a1d165a7f3_35643_87fb19ca3694de30ac53913d965396d7.png"
width="760"
height="547"
loading="lazy" data-zoomable />&lt;/div>
&lt;/div>&lt;/figure>
&lt;p>The association of &lt;code>!&lt;/code> (&amp;lsquo;bang&amp;rsquo;) with &lt;code>1&lt;/code> actually has a fairly tidy
explanation as many of the early typewriters omitted the numeral &lt;code>1&lt;/code>
and the typist was expected just to use the lowercase letter &lt;code>l&lt;/code> in
its place; likewise the &lt;code>!&lt;/code> was omitted and was also typed using the
lowercase &lt;code>l&lt;/code> then backspacing and typing a full-stop &lt;code>.&lt;/code>.&lt;/p>
&lt;p>While &lt;a href="https://en.wikipedia.org/wiki/Ascii" target="_blank" rel="noopener">ASCII&lt;/a> and older computer keyboards may not provide evidence for
early association of &lt;code>7&lt;/code> and &lt;code>&amp;amp;&lt;/code>, an examination of the early
typewriters from &lt;a href="http://www.antiquetypewriters.com/collection" target="_blank" rel="noopener">antiquetypewriters.com&lt;/a> reveals firstly that almost
all of the early typewriters collected there which have symbols as the
result of &amp;lsquo;shifted&amp;rsquo; numerals do in fact place &lt;code>&amp;amp;&lt;/code> with the &lt;code>7&lt;/code>
including the &lt;a href="http://www.antiquetypewriters.com/collection/enlarged.asp?img=pic-norths.jpg&amp;amp;typewritername=Norths" target="_blank" rel="noopener">1892 Norths typewriter (London)&lt;/a>, Wagner Typewriter Co&amp;rsquo;s
(New Jersey) &lt;a href="http://www.antiquetypewriters.com/collection/typewriter.asp?Underwood%25201" target="_blank" rel="noopener">1896 Underwood 1&lt;/a>, the &lt;a href="http://www.antiquetypewriters.com/collection/typewriter.asp?Shimer" target="_blank" rel="noopener">1898 Shimmer (Milton,
Pennsylvania)&lt;/a>, Meiselbach Typewriter Co.&amp;rsquo;s (Kenosha, Wisconsin, USA)
&lt;a href="http://www.antiquetypewriters.com/collection/typewriter.asp?Sholes%2520Visible" target="_blank" rel="noopener">1901 Sholes Visible&lt;/a>, and, secondly, and crucially, the &lt;a href="http://www.antiquetypewriters.com/collection/detailed.asp?img=pic-remington02.jpg&amp;amp;typewritername=Remington%25202" target="_blank" rel="noopener">1878 Remington
Standard Model No. 2&lt;/a> (New York) also positions &lt;code>&amp;amp;&lt;/code> as the shifted
value of &lt;code>7&lt;/code>. The Remington Standard No. 2 is &lt;a href="http://americanhistory.si.edu/collections/search/object/nmah%5F687313" target="_blank" rel="noopener">described&lt;/a> as the first
commercially successful typewriter, and its (QWERTY-style) layout thus
became established as standard.&lt;/p>
&lt;h2 id="remington-standard-no-dot-2">Remington Standard No. 2&lt;/h2>
&lt;figure >
&lt;div class="d-flex justify-content-center">
&lt;div class="w-100" >&lt;img alt="" srcset="
/post/tironian_et_and_ampersand_seven/remington-standard-model-2-1878_huea513dfdf9a95412a0560c4998e03de6_290448_6754385b2d81a94844c04793689fd53a.jpg 400w,
/post/tironian_et_and_ampersand_seven/remington-standard-model-2-1878_huea513dfdf9a95412a0560c4998e03de6_290448_5c6f1ffb880369bb81263f9f63b0f5ed.jpg 760w,
/post/tironian_et_and_ampersand_seven/remington-standard-model-2-1878_huea513dfdf9a95412a0560c4998e03de6_290448_1200x1200_fit_q75_lanczos.jpg 1200w"
src="https://lambda-y.net/post/tironian_et_and_ampersand_seven/remington-standard-model-2-1878_huea513dfdf9a95412a0560c4998e03de6_290448_6754385b2d81a94844c04793689fd53a.jpg"
width="637"
height="760"
loading="lazy" data-zoomable />&lt;/div>
&lt;/div>&lt;/figure>
&lt;figure >
&lt;div class="d-flex justify-content-center">
&lt;div class="w-100" >&lt;img alt="" srcset="
/post/tironian_et_and_ampersand_seven/remington02-keyboard_hu64e6bb470c4374079fa4ad8e0aa29bba_57927_f93b1ffb13d952d4fae45d47a34d730a.jpg 400w,
/post/tironian_et_and_ampersand_seven/remington02-keyboard_hu64e6bb470c4374079fa4ad8e0aa29bba_57927_7e3f9eaf70e0f409752de640b982d912.jpg 760w,
/post/tironian_et_and_ampersand_seven/remington02-keyboard_hu64e6bb470c4374079fa4ad8e0aa29bba_57927_1200x1200_fit_q75_lanczos.jpg 1200w"
src="https://lambda-y.net/post/tironian_et_and_ampersand_seven/remington02-keyboard_hu64e6bb470c4374079fa4ad8e0aa29bba_57927_f93b1ffb13d952d4fae45d47a34d730a.jpg"
width="702"
height="155"
loading="lazy" data-zoomable />&lt;/div>
&lt;/div>&lt;/figure>
&lt;p>The one early typewriter I found with shifted numerals as symbols which
&lt;strong>didn&amp;rsquo;t&lt;/strong> associate &lt;code>7&lt;/code> and &lt;code>&amp;amp;&lt;/code> is the &lt;a href="http://www.antiquetypewriters.com/collection/typewriter.asp?Waverley" target="_blank" rel="noopener">1895 Waverly&lt;/a> (London) where the
&lt;code>&amp;amp;&lt;/code> is above the &lt;code>6&lt;/code> and the &lt;code>7&lt;/code> has a &lt;code>/&lt;/code> above it.&lt;/p>
&lt;p>So an association between &lt;code>&amp;amp;&lt;/code> and &lt;code>7&lt;/code> for keyboard does seem to have
been established in the 19th century, presumably through the success
of the Remington Standard No. 2. The question then shifts to whether
or not the placement of the &lt;code>&amp;amp;&lt;/code> above the &lt;code>7&lt;/code> by the designers of the
Remington Standard No. 2 was motivated by Tironian sensibilities or
not.&lt;/p>
&lt;p>The Tironian &lt;em>et&lt;/em> has disappeared from most everywhere, excepting in
&lt;a href="https://stancarey.wordpress.com/2014/09/18/the-tironian-et-in-galway-ireland/" target="_blank" rel="noopener">modern Irish typography&lt;/a>. Interestingly, &lt;a href="https://web.archive.org/web/20170214010810/http://evertype.com/celtscript/type-keys.html" target="_blank" rel="noopener">some Irish typewriters&lt;/a> place
the Tironian &lt;em>et&lt;/em> &lt;code>⁊&lt;/code> above the &lt;code>7&lt;/code> key.&lt;/p>
&lt;p>Keith Houston at the Shady Characters website &lt;a href="https://web.archive.org/web/20180423230942/http://www.shadycharacters.co.uk/2011/06/the-ampersand-part-2-of-2/#paperref%5F16" target="_blank" rel="noopener">suggests&lt;/a> that:&lt;/p>
&lt;blockquote>
&lt;p>the Tironian notes suffered near-extinction in the Middle Ages,
victim of a curious linguistic witch hunt. The secrecy and
cipher-like nature of both traditional runic writing and
short­hand did not sit well with the distrust of witch­craft and
magic prevalent in those times, and Tiro’s system fell out of use.&lt;/p>
&lt;/blockquote>
&lt;p>Indeed, in Old English manuscripts, runes sometimes appear, standing
in for the words which are borne by the particular runes as names,
including &lt;a href="https://en.wikipedia.org/wiki/Mannaz" target="_blank" rel="noopener">ᛗ&lt;/a> (&lt;em>mann&lt;/em> &amp;ldquo;man&amp;rdquo;), &lt;a href="https://en.wikipedia.org/wiki/Dagaz" target="_blank" rel="noopener">ᛞ&lt;/a> (&lt;em>dæg&lt;/em> &amp;ldquo;day&amp;rdquo;), and &lt;a href="https://en.wikipedia.org/wiki/Odal%5F%28rune%29" target="_blank" rel="noopener">ᛟ&lt;/a> (&lt;em>œþel&lt;/em> &amp;ldquo;ancestral
land&amp;rdquo;). The last of these is used three times in the extant text of &lt;em>Beowulf&lt;/em>.&lt;/p>
&lt;h2 id="beowulf-f-dot-141v-ll-dot-520-521">&lt;em>Beowulf&lt;/em> f.141v: ll.520–521&lt;/h2>
&lt;figure >
&lt;div class="d-flex justify-content-center">
&lt;div class="w-100" >&lt;img alt="" srcset="
/post/tironian_et_and_ampersand_seven/141v-ethel_hu7bdb9ca6b28f52b376f83f504bc3e87a_84242_d63a6f73be03e7dc3cc84710866e7970.jpg 400w,
/post/tironian_et_and_ampersand_seven/141v-ethel_hu7bdb9ca6b28f52b376f83f504bc3e87a_84242_f4435de9512ff87ae1019b7eab533504.jpg 760w,
/post/tironian_et_and_ampersand_seven/141v-ethel_hu7bdb9ca6b28f52b376f83f504bc3e87a_84242_1200x1200_fit_q75_lanczos.jpg 1200w"
src="https://lambda-y.net/post/tironian_et_and_ampersand_seven/141v-ethel_hu7bdb9ca6b28f52b376f83f504bc3e87a_84242_d63a6f73be03e7dc3cc84710866e7970.jpg"
width="760"
height="214"
loading="lazy" data-zoomable />&lt;/div>
&lt;/div>&lt;/figure>
&lt;head>
&lt;meta http-equiv="Content-Type" content="text/html; charset=UTF-8" />
&lt;style type="text/css">
/* Left-aligned text in a centered block (does not work in Adobe Digital Editions 1.7) */
.poem {
display: table;
margin-right: auto;
margin-left: auto;
}
&lt;pre>&lt;code>/* Indent wrapping lines */
.stanza {
text-indent: 0;
margin-left: 2em;
}
.verse {
margin-left: -2em;
}
&lt;/code>&lt;/pre>
&lt;p>&lt;/style>&lt;/p>
&lt;/head>
&lt;body style="font-size: 75%;">
&lt;div style="float: left; width: 50%;">
&lt;ul>
&lt;p class="stanza">&lt;span class="verse">ðonon he gesohte swæsne &lt;span style="color:red">·ᛟ·&lt;/span>&lt;br />
&lt;span class="verse">leof his leodum lond brondinga&lt;/span>
&lt;/p>
&lt;/ul>
&lt;/div>
&lt;div style="float: right; width: 50%;">
&lt;ul>
&lt;p class="stanza">&lt;span class="verse">then he sought his own sweet &lt;span style="color:red">·ancestral homeland·&lt;/span>&lt;/span>&lt;br />
&lt;span class="verse">– loved by his people – the land of Brondings &lt;/span>
&lt;/p>
&lt;/div>
&lt;/ul>
&lt;/body>
&lt;/html>
&lt;p>In any event, what of the question of &amp;ldquo;why is the &lt;code>&amp;amp;&lt;/code> on the &lt;code>7&lt;/code> key?&amp;rdquo;&lt;/p>
&lt;p>It would seem in all likelihood that the placement of the &lt;code>&amp;amp;&lt;/code> on the
&lt;code>7&lt;/code> is a happy accident. Outside of Ireland, Tironian ⁊s would have
been long enough out of fashion that it seems unlikely anyone (or, at
least, typewriter engineers) would have associated &lt;code>&amp;amp;&lt;/code> with &lt;code>7&lt;/code>. The
positioning of the Tironian &lt;code>⁊&lt;/code> above the &lt;code>7&lt;/code> key on some Irish
typewriters, on the other hand, is then doubly predestined, given the
largely standard positioning of the semantically-equivalent &lt;code>&amp;amp;&lt;/code> over
the &lt;code>7&lt;/code> on many typewriters and the similarity in appearance of the
Arabic &lt;code>7&lt;/code> numeral and the Tironian &lt;code>⁊&lt;/code> symbol.&lt;/p></description></item><item><title>Blog posts ensue</title><link>https://lambda-y.net/post/blog-posts-ensue/</link><pubDate>Thu, 07 Jun 2018 21:13:00 -0600</pubDate><guid>https://lambda-y.net/post/blog-posts-ensue/</guid><description>&lt;p>I&amp;rsquo;m still working on the back-end technology, but hopefully more blog
posts should start appearing here soon(ish), acting as a (prettier and
less &lt;del>privacy-invading&lt;/del> blogspot-ish) continuation of my old
linguistics blog, &lt;a href="https://staefcraeft.blogspot.com/" target="_blank" rel="noopener">Stæfcræft &amp;amp; Vyākaraṇa&lt;/a>.&lt;/p>
&lt;p>If you&amp;rsquo;re interested in my &lt;del>musings&lt;/del> scribblings on topics outside of
natural language, you might visit my other blog, &lt;a href="https://babbagefiles.xyz" target="_blank" rel="noopener">The Neo-Babbage
Files&lt;/a>.&lt;/p>
&lt;p>In the meantime, here&amp;rsquo;s a clever Nepali tongue-twister my wife came up
with:p&lt;/p>
&lt;blockquote>
&lt;p>पारसीले परसि फरसि खान्छ रे&lt;/p>
&lt;p>&lt;em>pārsī parsi pharsi khāncha re&lt;/em>&lt;/p>
&lt;p>&amp;ldquo;[They say:] A/The Parsi (Zoroastrian) will eat (some) pumpkin the day after tomorrow.&amp;rdquo;&lt;/p>
&lt;/blockquote>
&lt;p>पारसी (pārsī) is &amp;ldquo;&lt;a href="https://en.wikipedia.org/wiki/Parsi" target="_blank" rel="noopener">Parsi&lt;/a>&amp;rdquo;, परसि (parsi) is &amp;ldquo;the day after tomorrow&amp;rdquo;,
and फरसि (pharsi) is &amp;ldquo;pumpkin&amp;rdquo; (often in the sense of a pumpkin
dish). (रे (re) is a Nepali quotative particle.)&lt;/p></description></item></channel></rss>