<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>alphabetical sorting - Stephen Ullstrom</title>
	<atom:link href="https://stephenullstrom.com/tag/alphabetical-sorting/feed/" rel="self" type="application/rss+xml" />
	<link>https://stephenullstrom.com</link>
	<description>Indexing &#38; Writing</description>
	<lastBuildDate>Tue, 15 Apr 2025 15:55:53 +0000</lastBuildDate>
	<language>en-CA</language>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<generator>https://wordpress.org/?v=7.1.3</generator>

<image>
	<url>https://i0.wp.com/stephenullstrom.com/wp-content/uploads/2014/12/w0BqQSga-54a1c676v1_site_icon.png?fit=32%2C32&#038;ssl=1</url>
	<title>alphabetical sorting - Stephen Ullstrom</title>
	<link>https://stephenullstrom.com</link>
	<width>32</width>
	<height>32</height>
</image> 
<site xmlns="com-wordpress:feed-additions:1">66154179</site>	<item>
		<title>Sorting: Putting Entries in Order</title>
		<link>https://stephenullstrom.com/sorting-putting-entries-in-order/</link>
					<comments>https://stephenullstrom.com/sorting-putting-entries-in-order/#respond</comments>
		
		<dc:creator><![CDATA[Stephen]]></dc:creator>
		<pubDate>Tue, 15 Apr 2025 19:00:27 +0000</pubDate>
				<category><![CDATA[Indexing]]></category>
		<category><![CDATA[Indexing Insights]]></category>
		<category><![CDATA[alphabetical sorting]]></category>
		<category><![CDATA[book indexing]]></category>
		<category><![CDATA[Index]]></category>
		<category><![CDATA[indexes]]></category>
		<category><![CDATA[indexing]]></category>
		<category><![CDATA[sorting]]></category>
		<category><![CDATA[term selection]]></category>
		<guid isPermaLink="false">https://stephenullstrom.com/?p=1758</guid>

					<description><![CDATA[Welcome to this last reflection in the mini-series on the basic elements of an index! Over the last three months I’ve discussed entries and arrays, main headings and subheadings, locators, cross-references, and format. Today I look at sorting. Sorting and format are like twins. They both have to do with how the index is arranged.&#8230;&#160;<a href="https://stephenullstrom.com/sorting-putting-entries-in-order/" rel="bookmark">Read More &#187;<span class="screen-reader-text">Sorting: Putting Entries in Order</span></a>]]></description>
										<content:encoded><![CDATA[<p>Welcome to this last reflection in the mini-series on the basic elements of an index! Over the last three months I’ve discussed <a href="https://stephenullstrom.com/the-building-blocks-of-an-index/">entries and arrays</a>, <a href="https://stephenullstrom.com/telling-readers-what-this-thing-is/">main headings and subheadings</a>, <a href="https://stephenullstrom.com/pointing-readers-in-the-right-direction/">locators</a>, <a href="https://stephenullstrom.com/signposts-within-the-index/">cross-references</a>, and <a href="https://stephenullstrom.com/format-pulling-the-index-together/">format</a>. Today I look at sorting.</p>
<p>Sorting and format are like twins. They both have to do with how the index is arranged. But whereas format is more about the visual aspect of the index—how the index appears on the page—sorting is about how entries and arrays are arranged one after the other.</p>
<p>As I like to emphasize, indexes need to be easy to use in order to be effective. This also applies to sorting. Arrays and entries need to be organized in a way that meets the reader’s expectations, so that the reader can seamlessly being searching.</p>
<p>For the most part, this means alphabetical sort. The index begins with A and ends with Z. This applies to main headings, stacking arrays one after the other. This also applies to sorting subheadings within an array.</p>
<p>The alternative to alphabetical sort is to leave entries unsorted, either in the order in which they are written or randomly thrown together. Either way, with no discernible pattern, the index would be very difficult to search. Alternatively, the index could be organized in page order (I’ve occasionally seen subheadings arranged in page order), but page order is not quick to scan and and the reader may just as well flip through the book. So, alphabetical sort has emerged as the universal standard for all languages which use an alphabet.<span class="Apple-converted-space"> </span></p>
<p>A few pointers on sorting:</p>
<ul>
<li>Alphabetical sort is either letter-by-letter or word-by-word. In letter-by-letter, spaces between words are ignored, whereas in word-by-word alphabetization begins again after each space. For both, alphabetization also ends and begins again after punctuation. In my experience, letter-by-letter sorting is more common, though the Chicago Manual of Style recently changed their recommendation to word-by-word (<a href="https://stephenullstrom.com/making-the-index-invisible/">as I discuss here</a>). So far the publishers I work with are cautious about implementing this change, but we may be in the midst of an industry-wide shift.</li>
<li>Sorting is typically according to the first significant word in the heading or subheading. Prepositions, such as A, An, And, and The, are usually ignored. At the main heading level, the preposition, as in The Metals Company<i>, </i>can either be ignored when sorting or the name can be inverted: Metals Company, The. In subheadings, where prepositions are more common within phrases, prepositions are simply ignored.<span class="Apple-converted-space"> </span></li>
<li>Because sorting is based on the first significant word, pay attention to term selection, especially in subheadings. Try to lead with the key element, so that readers will see the key term first as they scan the array and so that the subheading will sort to where readers expect. Leading with a less important term tends to bury the subheading, making it difficult for the key term to stand out. That said, subheadings should also read naturally, and trade-offs may need to be made between readability and sorting.</li>
<li>Entries beginning with a numeral can be handled in one of two ways. Either sort the entries to the top of the index or array, with all the numbers gathered together and sorted in numerical order, or sort the number as if spelled out. For example, 33 Acres Brewing Company would be sorted as if spelled Thirty-Three. For the most part, I think numbers should be sorted as if spelled out, especially if there are only a handful of such entries and there isn’t anything that connects them. The two main exceptions, for me, are dates and military units. Sometimes, in subheadings, it is helpful to show a chronology, such as a series of elections (for example, 2019 federal election, 2021 federal election, 2025 federal election, etc…). For these, keeping the dates together, at the top of the array, clearly shows the chronological progression. For military units, such as 1<sup>st</sup> Battalion, 3<sup>rd</sup> Brigade, 4<sup>th</sup> Army, etc…, these arrays are all the same type of entry (military units), and readers are likely familiar with the convention of numbered units, and so it makes sense to sort together at the top of the index, before the A section.</li>
<li>Entries beginning with a symbol, such as chemical or mathematical symbols, can, similar to numbers, be either sorted together at the top of the index or as if spelled out. Be careful, however, as different people may pronounce or spell these symbols differently. Probably best to consult with the client on how they think readers will search.<span class="Apple-converted-space"> </span></li>
<li>If absolutely necessary, entries and arrays can also be force-sorted. This means deliberately placing an entry outside of the normal alphabetical sort. For example, placing a subheading for “overview” at the top of an array. Force-sorting should be done sparingly, to avoid confusing readers. But sometimes alphabetical sort isn’t the most intuitive approach for a particular array or subheading, and a small adjustment should be made.<span class="Apple-converted-space"> </span></li>
</ul>
<p>Sorting is about how arrays and entries—main headings and subheadings—are organized. Ideally, the sorting simply works and readers don’t really notice because they are too busy searching. Alphabetical sort is either letter-by-letter or word-by-word. Word-by-word is CMS’s current recommendation. Whichever you choose, be consistent.</p>
]]></content:encoded>
					
					<wfw:commentRss>https://stephenullstrom.com/sorting-putting-entries-in-order/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
		<post-id xmlns="com-wordpress:feed-additions:1">1758</post-id>	</item>
		<item>
		<title>Making the Index Invisible</title>
		<link>https://stephenullstrom.com/making-the-index-invisible/</link>
					<comments>https://stephenullstrom.com/making-the-index-invisible/#respond</comments>
		
		<dc:creator><![CDATA[Stephen]]></dc:creator>
		<pubDate>Wed, 20 Nov 2024 20:00:33 +0000</pubDate>
				<category><![CDATA[Indexing]]></category>
		<category><![CDATA[Indexing Insights]]></category>
		<category><![CDATA[Work Process]]></category>
		<category><![CDATA[alphabetical sorting]]></category>
		<category><![CDATA[book indexing]]></category>
		<category><![CDATA[Chicago Manual of Style]]></category>
		<category><![CDATA[CMOS]]></category>
		<category><![CDATA[Index]]></category>
		<category><![CDATA[indexing]]></category>
		<category><![CDATA[work process]]></category>
		<guid isPermaLink="false">https://stephenullstrom.com/?p=1253</guid>

					<description><![CDATA[So the 18th edition of the Chicago Manual of Style dropped in September. I have to admit I have not bought a copy. While I think their recommendations are solid, I find I don’t use it very much, since I only index and not edit. But I do know some editors who are very excited&#8230;&#160;<a href="https://stephenullstrom.com/making-the-index-invisible/" rel="bookmark">Read More &#187;<span class="screen-reader-text">Making the Index Invisible</span></a>]]></description>
										<content:encoded><![CDATA[<p class="">So the 18th edition of the <em>Chicago Manual of Style </em>dropped in September. I have to admit I have not bought a copy. While I think their recommendations are solid, I find I don’t use it very much, since I only index and not edit. But I do know some editors who are very excited about the new edition, and there has been chatter among indexers as well on the changes to the chapter on indexing.</p>
<p class="">The main change in regards to indexing is 15.66, which states:</p>
<div class="blockquotes">
<blockquote>
<div class="blockquotes-line">Chicago now prefers the word-by-word system of alphabetization over the letter-by-letter system (but will accept either in a well-prepared index).</div>
</blockquote>
</div>
<p>&nbsp;</p>
<p class="">I think this change makes sense.</p>
<p class="">I personally most notice the difference in sorting when indexing Asian studies books, where I tend to see a lot of surnames like Chen, Kim, and Liu. Being so short, these names often get mixed up with other headings when sorted letter-by-letter, whereas I think the index is easier to scan if all of the surnames are sorted together. I’ve also received instructions from a scholarly press to sort the index letter-by-letter except for the names, which the press wants force-sorted word-by-word. Which begs the question: why not sort the entire index word-by-word?</p>
<p class="">For example, here is a comparison of letter-by-letter compared to word-by-word.</p>
<div class="blockquotes">
<div class="blockquotes-line" style="padding-left: 40px;"><strong>Letter-by-letter sorting</strong></div>
<div class="blockquotes-line" style="padding-left: 40px;">Liang Ji</div>
<div class="blockquotes-line" style="padding-left: 40px;">Liang Qichao</div>
<div class="blockquotes-line" style="padding-left: 40px;"><em>Libailiu </em>(<em>Saturday</em>)</div>
<div class="blockquotes-line" style="padding-left: 40px;">Li Boyuan</div>
<div class="blockquotes-line" style="padding-left: 40px;">Li Chen</div>
<div class="blockquotes-line" style="padding-left: 40px;"><em>Life Weekly</em></div>
<div class="blockquotes-line" style="padding-left: 40px;">Lin Meijing</div>
<div class="blockquotes-line" style="padding-left: 40px;">Li Shirui</div>
<div class="blockquotes-line" style="padding-left: 40px;">List, Friedrich</div>
<div class="blockquotes-line" style="padding-left: 40px;">Liu Denghan</div>
<div class="blockquotes-line" style="padding-left: 40px;">Liu Jiang</div>
<div class="blockquotes-line" style="padding-left: 40px;">Liu, Jianmei</div>
<div class="blockquotes-line" style="padding-left: 40px;">Liu, Lydia</div>
<div class="blockquotes-line" style="padding-left: 40px;"><em>Liushou nüshi</em> (<em>Those Left Behind;</em> film)</div>
<div class="blockquotes-line" style="padding-left: 40px;"><em>Liuxuesheng </em>(overseas Chinese students)</div>
<div class="blockquotes-line" style="padding-left: 40px;">Liu Yiqing</div>
<div class="blockquotes-line" style="padding-left: 40px;">Li Yuanhong</div>
</div>
<div class="blockquotes" style="padding-left: 40px;">
<div style="padding-left: 40px;">&nbsp;</div>
<div class="blockquotes-line"><strong>Word-by-word sorting</strong></div>
<div class="blockquotes-line">Li Boyuan</div>
<div class="blockquotes-line">Li Chen</div>
<div class="blockquotes-line">Li Shirui</div>
<div class="blockquotes-line">Li Yuanhong</div>
<div class="blockquotes-line">Liang Ji</div>
<div class="blockquotes-line">Liang Qichao</div>
<div class="blockquotes-line"><em>Libailiu </em>(<em>Saturday</em>)</div>
<div class="blockquotes-line"><em>Life Weekly</em></div>
<div class="blockquotes-line">Lin Meijing</div>
<div class="blockquotes-line">List, Friedrich</div>
<div class="blockquotes-line">Liu Denghan</div>
<div class="blockquotes-line">Liu Jiang</div>
<div class="blockquotes-line">Liu, Jianmei</div>
<div class="blockquotes-line">Liu, Lydia</div>
<div class="blockquotes-line">Liu Yiqing</div>
<div class="blockquotes-line"><em>Liushou nüshi</em> (<em>Those Left Behind;</em> film)</div>
<div class="blockquotes-line"><em>Liuxuesheng </em>(overseas Chinese students)</div>
<div>&nbsp;</div>
</div>
<p class="">The word-by-word sorting, for me, is a lot easier to scan and parse when like surnames are grouped together, and when names are sorted together above other terms. It makes me confident that I am seeing all of the names present, rather than being concerned that I am missing a name that is buried below.</p>
<p class="">Also note that the Liu names are sorted according to the clarified 15.85, which states:</p>
<div class="blockquotes">
<blockquote>
<div class="blockquotes-line">When the same family name is inverted for one person but not for another (e.g., “Li Jinghan” and “Li, Lillian”), the names may be listed together and alphabetized by first names regardless of the comma.</div>
</blockquote>
</div>
<p>&nbsp;</p>
<p class="">This also makes a lot of sense and has been my practice for a long time. By ignoring the comma, the second portion of the name is treated equally for all names, whereas if the comma is taken into account, all the names with commas sort to the top and may cause some names to appear out of order. For example,</p>
<div class="blockquotes">
<div class="blockquotes-line" style="padding-left: 40px;">Liu, Jianmei, 48</div>
<div class="blockquotes-line" style="padding-left: 40px;">Liu, Lydia, 91</div>
<div class="blockquotes-line" style="padding-left: 40px;">Liu Denghan, 148n6</div>
<div class="blockquotes-line" style="padding-left: 40px;">Liu Jiang, 105</div>
<div class="blockquotes-line" style="padding-left: 40px;">Liu Yiqing, 27, 144n13</div>
<div>&nbsp;</div>
</div>
<p class="">For another interesting comparison, as a colleague pointed out, try looking for the sorting differences in the indexes between the 17th and 18th editions of the <em>CMOS. </em>And if you’d like to see a full list of the changes to the indexing chapter in <em>CMOS </em>18<em>,</em>see <a href="https://www.chicagomanualofstyle.org/help-tools/what-s-new.html" target="_blank" rel="noopener noreferrer">here</a>.</p>
<p class="">So will I now unilaterally switch to word-by-word sorting for all of my clients who request that the index follows <em>CMOS</em>? I don’t think so, unless I think that the index will really benefit. I think it is better if I first ask my clients if they want to change, so we are both on the same page and I am not springing a surprise on them. And, to be honest, for most indexes I don’t think that the difference between word-by-word and letter-by-letter sorting will be that noticeable.</p>
<p class="">This brings me to my larger point, which is that the mechanics of a well written index should be invisible to the user. I doubt that any reader will browse the index and think, “I wonder what the alphabetical sort is?” That is not the reader’s concern. What the reader cares about is quickly finding information.</p>
<p class="">To facilitate finding information, every aspect of the index needs to work together. This includes the sorting, the structure, term selection, phrasing, and cross-references. When it works, the reader shouldn’t notice <em>how </em>the index works because the reader is too busy digging into the book. When the index <em>does not </em>work—that is the point when the reader is pulled out of the index and is frustrated at their inability to access the information they want. The reader may not be able to articulate <em>why</em>the index is not working, but something about the contents and mechanics of the index is wrong.</p>
<p class="">Bringing this back to sorting, for many indexes the difference will be negligible between letter-by-letter and word-by-word sorting. As <em>CMOS </em>states, they will accept either in a well-prepared index. For other books, like for me with Asian studies titles, the difference will be more pronounced.</p>
<p class="">When indexing, pay attention to when the difference matters. Make decisions based on what will make the user experience the most seamless. Pay attention to how the different elements of the index fit together. Striving to make the index invisible may be an odd way to think about indexing, but to be invisible means that the index works, which is what we ultimately want for our readers.</p>
]]></content:encoded>
					
					<wfw:commentRss>https://stephenullstrom.com/making-the-index-invisible/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
		<post-id xmlns="com-wordpress:feed-additions:1">1373</post-id>	</item>
	</channel>
</rss>
