<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title>Roget22 on diary</title>
		<link>/tags/roget22/</link>
		<description>Recent content in Roget22 on diary</description>
		<generator>Hugo</generator>
		<language>en-us</language>
		
		
		
			<copyright>shawn boyette</copyright>
		
		
			<lastBuildDate>Fri, 27 Mar 2026 09:47:43 -0600</lastBuildDate>
		
			<atom:link href="/tags/roget22/index.xml" rel="self" type="application/rss+xml" />
			<item>
				<title>Roget22 Is Back Again</title>
				<link>/posts/roget22/roget22-is-back-again/</link>
				<pubDate>Fri, 27 Mar 2026 09:47:43 -0600</pubDate>
				<guid>/posts/roget22/roget22-is-back-again/</guid>
				<description>&lt;p&gt;Well, after about a year of inactivity (partially my fault, partially&#xA;not) I’m back to the Roget 22 project. If you don’t remember what this&#xA;is about, I can hardly blame you; here’s the &lt;a href=&#34;/posts/roget22/roget22_is_back/&#34;&gt;post where I explained&#xA;things&lt;/a&gt;&#xA;.&lt;/p&gt;&#xA;&lt;p&gt;I’m not going to make any big predictions or lay out a lot in the way&#xA;of plans right now, but I did just re-read my last batch up devlog&#xA;entries, and some things have changed from my thinking at that&#xA;point. So here’s a list of what’s happening:&lt;/p&gt;</description>
			</item>
			<item>
				<title>Roget22 Dev Diary 0003</title>
				<link>/posts/roget22/roget22-dev-diary-0003/</link>
				<pubDate>Sun, 24 Nov 2024 11:16:54 -0700</pubDate>
				<guid>/posts/roget22/roget22-dev-diary-0003/</guid>
				<description>&lt;p&gt;Sometimes when you work on something long enough you get tunnel&#xA;vision. This is a pretty well-known phenomenon, and I had a&#xA;particularly intense episode of it around the Roget22 project &amp;ndash; but I&#xA;now see a clearer, easier path to making things happen.&lt;/p&gt;&#xA;&lt;p&gt;Yes, compared to what I last wrote.&lt;/p&gt;&#xA;&lt;p&gt;I don&amp;rsquo;t think the why of it is particularly difficult to describe or&#xA;understand. Many years of dealing with bottomlessly problematic source&#xA;material led to the following assumptions:&lt;/p&gt;</description>
			</item>
			<item>
				<title>Roget22 Dev Diary 0002</title>
				<link>/posts/roget22/roget22-dev-diary-0002/</link>
				<pubDate>Sun, 17 Nov 2024 22:57:04 -0700</pubDate>
				<guid>/posts/roget22/roget22-dev-diary-0002/</guid>
				<description>&lt;p&gt;I almost started scanning today, but I didn&amp;rsquo;t. Instead I sat down and&#xA;started working on the hairiest problem not caused by PG&amp;rsquo;s edits over&#xA;the years: references.&lt;/p&gt;&#xA;&lt;p&gt;In a modern paper edition of Roget&amp;rsquo;s, references to other headwords&#xA;look something like &lt;code&gt;TERM 584.2&lt;/code&gt; to indicate that for other terms&#xA;similar in meaning to &lt;code&gt;TERM&lt;/code&gt;, refer to sense 2 of headword 584.&lt;/p&gt;&#xA;&lt;p&gt;This is largely inherited from Roget&amp;rsquo;s original design of &lt;code&gt;argument &amp;amp;c 476&lt;/code&gt;, read as &amp;ldquo;for more terms like this meaning of &amp;lsquo;argument&amp;rsquo;, see&#xA;headword 476&amp;rdquo;. But there are also variants like &lt;code&gt;manifest &amp;amp;c (be evidence of) 467&lt;/code&gt; where the reader is pointed into a specific sense of&#xA;a headword by use of another term, because early editions did not&#xA;number the senses within a headword.&lt;/p&gt;</description>
			</item>
			<item>
				<title>Roget22 is back (Dev Diary 0001)</title>
				<link>/posts/roget22/roget22_is_back/</link>
				<pubDate>Sat, 26 Oct 2024 12:51:12 -0600</pubDate>
				<guid>/posts/roget22/roget22_is_back/</guid>
				<description>&lt;p&gt;One of my longest-running projects is about to come out of dormancy,&#xA;again. The thing that would eventually get the name &amp;ldquo;Roget22&amp;rdquo; started&#xA;in, I believe, 2004, when I stumbled on the OCR&amp;rsquo;d text of the 1921&#xA;edition of Roget&amp;rsquo;s Thesaurus on the Project Gutenberg site.&lt;/p&gt;&#xA;&lt;p&gt;For the unfamiliar, I point you toward the &lt;a href=&#34;https://en.wikipedia.org/wiki/Project_Gutenberg&#34; target=&#34;_blank&#34;&gt;wiki&#xA;entry&lt;/a&gt;&#xA; for Project&#xA;Gutenberg (hereafter &amp;ldquo;PG&amp;rdquo;).&lt;/p&gt;&#xA;&lt;p&gt;According to the credits in the file, the original OCR job had been&#xA;done in 1984 at MICRA Corp. However, it turns out that MICRA is still&#xA;around, and their own website contradicts this on a few grounds:&lt;/p&gt;</description>
			</item>
	</channel>
</rss>
