Alphabetizing seems straightforward until you hit the edge cases. Does "The Great Gatsby" file under T or G? Does "McDonald" come before or after "MacDonald"? Where does a numbered item like "3M" go? I run into these questions regularly when sorting reference lists, bibliographies, and product catalogues, and the answers depend on which sorting convention you follow.
The line sorter handles standard alphabetical sorting perfectly for most cases. But understanding the conventions behind alphabetization helps you handle the edge cases where automated sorting needs a human decision.
Letter-by-Letter vs Word-by-Word
There are two standard alphabetization methods, and they produce different results. Letter-by-letter sorting ignores spaces and hyphens, treating multi-word entries as single continuous strings. Word-by-word sorting treats each word as a separate sorting unit, giving priority to shorter entries that share a beginning with longer ones.
The practical difference shows up with entries like "New York" and "Newark". In letter-by-letter sorting, "Newark" comes first because when you ignore the space, "newyork" comes after "newark". In word-by-word sorting, "New York" comes first because "New" as a complete first word precedes "Newark" where the first word is longer.
Most dictionaries and encyclopedias use letter-by-letter. Most library catalogues and indexes use word-by-word. For general purposes, either works as long as you apply it consistently. The line sorter uses letter-by-letter comparison by default, which matches how most software and databases sort text.
Sorting Names
Personal names sort by surname first. This is obvious for Western names but gets complicated quickly. Names with prefixes like "van", "de", "von", and "al" follow different conventions by language and personal preference. Dutch names typically sort under the prefix: van Gogh files under V. German names typically ignore the prefix for sorting: von Braun files under B. The safest approach is to check how the person themselves writes their name in professional contexts.
Names with apostrophes and spaces in the surname sort as if the punctuation were not there. O'Brien sorts as "obrien", filing after "Oak" and before "Odd". Mac and Mc prefixes sort exactly as written, so "MacDonald" and "McDonald" sort differently even though they sound similar. This trips people up because the expectation is that they should sort together.
For East Asian names where the family name comes first by convention, determine whether the name has been westernized. "Yoko Ono" in Western order sorts under O. "Mao Zedong" where Mao is the family name could sort under M if treated as surname-first or Z if treated as given-name-first. Context determines the right choice.
Sorting Titles
Articles at the beginning of titles, specifically "A", "An", and "The" in English, are conventionally ignored for sorting purposes. "The Great Gatsby" sorts under G, not T. "A Tale of Two Cities" sorts under T (for Tale), not A. This convention is universal in libraries, bibliographies, and most reference systems.
The line sorter sorts titles exactly as written, including articles. If you need to sort a list of titles following the convention of ignoring leading articles, the simplest approach is to temporarily move the article to the end: "Great Gatsby, The" sorts correctly without any special handling. Sort the list, then move the articles back if needed.
Titles beginning with numbers sort before letters in most systems because digit characters have lower values than letters in character encoding. "1984" sorts before "A Brief History of Time". Some style guides require numbers to be alphabetized as if they were spelled out, so "1984" would sort as "Nineteen Eighty-Four" under N. This is a manual adjustment that no automated sorter handles.
Numbers and Special Characters
Standard computer sorting places special characters first, then numbers, then letters. This means "#hashtag" sorts before "1st" which sorts before "Apple". This order follows the ASCII and Unicode character tables where symbols have the lowest values, digits come next, uppercase letters follow, and lowercase letters come last.
Case sensitivity affects sorting order. In case-sensitive sorting, all uppercase letters come before all lowercase letters, so "Zebra" sorts before "apple". Case-insensitive sorting, which the line sorter uses by default, compares "zebra" and "apple" as lowercase, putting "apple" first as expected.
For lists that mix numbers with text, consider whether numerical or alphabetical order makes more sense. A list of product codes like "A100, A20, A3" sorts alphabetically as "A100, A20, A3" because the character "1" comes before "2" and "3". If you want numerical order within the alpha prefix, you would need "A3, A20, A100", which requires natural sort order. The line sorter provides this option for lists where embedded numbers should sort by numeric value.
Practical Sorting Workflow
When I need to alphabetize a long list, I follow a consistent process. First, clean the data with the whitespace remover to eliminate trailing spaces that would affect sort order. Second, standardise case using the case converter if case inconsistency is a problem. Third, sort with the line sorter. Fourth, scan the sorted output for edge cases that need manual adjustment, like names with prefixes or titles with leading articles.
This four-step process handles 95 percent of sorting tasks correctly. The remaining 5 percent involves the edge cases discussed above, which require human judgment that no automated tool can reliably provide. But getting 95 percent right automatically and fixing 5 percent manually is far faster than sorting the entire list by hand.