<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0"
    xmlns:dc="http://purl.org/dc/elements/1.1/"
     xmlns:admin="http://webns.net/mvcb/"
     xmlns:content="http://purl.org/rss/1.0/modules/content/"
     xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#">
	<channel> 

	<title>Comments on: Two be or not 2 be</title>
	<link>http://ask.metafilter.com/80802/Two-be-or-not-2-be/</link>
	<description>Comments on Ask MetaFilter post Two be or not 2 be</description>
	<pubDate>Fri, 11 Jan 2008 19:34:09 -0800</pubDate>
	<lastBuildDate>Fri, 11 Jan 2008 19:34:09 -0800</lastBuildDate>
	<language>en-us</language>
	<docs>http://blogs.law.harvard.edu/tech/rss</docs>
	<ttl>60</ttl>

	<item>
		<title>Question: Two be or not 2 be</title>
		<link>http://ask.metafilter.com/80802/Two-be-or-not-2-be</link>	
		<description>How would you go about proving that numerals are more &quot;readable&quot; than numbers? &lt;br /&gt;&lt;br /&gt; I&apos;m looking for a way to prove that numerals (&quot;2&quot;) are more readable than words (&quot;two&quot;) in headlines and running text. &lt;br&gt;
&lt;br&gt;
Yes, yes, it makes sense intuitively (at least, &lt;i&gt;I&lt;/i&gt; think it does). But how do you &lt;b&gt;prove&lt;/b&gt; it? How does 1 go about testing &quot;&lt;a href=&quot;http://en.wikipedia.org/wiki/Readability#In_writing&quot;&gt;readability&lt;/a&gt;&quot; objectively? Is &lt;em&gt;shorter &lt;/em&gt;necessarily &lt;em&gt;more &lt;/em&gt;readable?&lt;br&gt;
&lt;br&gt;
This is exclusively for Web writing, if it matters. Googling turns up style guides. I don&apos;t want style guides. We use CMS 15 at work and I want to subvert it, but not with another style guide.</description>
		<guid isPermaLink="false">post:ask.metafilter.com,2008:site.80802</guid>
		<pubDate>Fri, 11 Jan 2008 19:28:07 -0800</pubDate>
		<dc:creator>YamwotIam</dc:creator>
		
			<category>twono2</category>
		
			<category>styleguide</category>
		
			<category>readability</category>
		
			<category>downwithchicago</category>
		
	</item> <item>
		<title>By: Sticherbeast</title>
		<link>http://ask.metafilter.com/80802/Two-be-or-not-2-be#1198446</link>	
		<description>Interesting question! Maybe you could set up a controlled experiment where volunteers read three paragraphs with numerals, &quot;number words,&quot; and mixtures of the two, respectively. Mix up the order of these paragraphs so that you&apos;re not simply testing how tired people get of memorizing number amounts. After each paragraph, test the volunteers for their recollection of the material, and see which information comes back more easily.&lt;br&gt;
&lt;br&gt;
The tricky part is making sure you design the experiment fairly. I might also completely be smoking crack on this one.</description>
		<guid isPermaLink="false">comment:ask.metafilter.com,2008:site.80802-1198446</guid>
		<pubDate>Fri, 11 Jan 2008 19:34:09 -0800</pubDate>
		<dc:creator>Sticherbeast</dc:creator>
	</item><item>
		<title>By: iguanapolitico</title>
		<link>http://ask.metafilter.com/80802/Two-be-or-not-2-be#1198448</link>	
		<description>Well, this may get deleted because it&apos;s not answering your question, but I find it less readable.  A number where I am expecting a group of letters interrupts the flow for me.  &lt;br&gt;
&lt;br&gt;
Similar to reading all caps -- it&apos;s not what you&apos;re used to, so it&apos;s harder to read.  It is of course &quot;readable,&quot; but less so.&lt;br&gt;
&lt;br&gt;
So, I wouldn&apos;t know how to prove the opposite.  :)</description>
		<guid isPermaLink="false">comment:ask.metafilter.com,2008:site.80802-1198448</guid>
		<pubDate>Fri, 11 Jan 2008 19:35:01 -0800</pubDate>
		<dc:creator>iguanapolitico</dc:creator>
	</item><item>
		<title>By: iguanapolitico</title>
		<link>http://ask.metafilter.com/80802/Two-be-or-not-2-be#1198449</link>	
		<description>For instance, I triple-taked the &quot;1&quot; in your second to last paragraph, thinking it was an &quot;I&quot; and being unable to make sense out of the sentence.</description>
		<guid isPermaLink="false">comment:ask.metafilter.com,2008:site.80802-1198449</guid>
		<pubDate>Fri, 11 Jan 2008 19:35:50 -0800</pubDate>
		<dc:creator>iguanapolitico</dc:creator>
	</item><item>
		<title>By: iguanapolitico</title>
		<link>http://ask.metafilter.com/80802/Two-be-or-not-2-be#1198451</link>	
		<description>I&apos;m sorry, I should be thinking more before I type.  But I should also note that I prefer listening to music on CDs over mp3 players, and sometimes I even call them &quot;albums.&quot;  It could be that because I didn&apos;t grow up text messaging that I don&apos;t expect numbers in place of words in sentences.  :)  It may in fact be easier for, uh, younger folks to read numbers as you describe.&lt;br&gt;
&lt;br&gt;
So, to test it, get a whole bunch of people in a room with some written text.  Give your own reading comprehension test.  Find out how many people respond as I did, and how many respond as if I&apos;m a dinosaur.  But get people from all demographics so you can report complete findings.</description>
		<guid isPermaLink="false">comment:ask.metafilter.com,2008:site.80802-1198451</guid>
		<pubDate>Fri, 11 Jan 2008 19:41:11 -0800</pubDate>
		<dc:creator>iguanapolitico</dc:creator>
	</item><item>
		<title>By: qxntpqbbbqxl</title>
		<link>http://ask.metafilter.com/80802/Two-be-or-not-2-be#1198453</link>	
		<description>You could flash headlines at test subjects very briefly, and ask them to write down the headline.  If numerals are more &quot;readable&quot;, then it would be reasonable to expect a better recall rate for headlines with numerals than the equivalent headline with spelled numbers.&lt;br&gt;
&lt;br&gt;
But I agree with the others here-- at least for numbers less than 10, the spelled words are more readable.  Seeing a single digit makes my brain attempt a context switch, which takes an extra split-second to resolve (e.g., &quot;Are we enumerating things now?  Is this point in a list?  Is that the end-of-sentence? Etc.&quot;)</description>
		<guid isPermaLink="false">comment:ask.metafilter.com,2008:site.80802-1198453</guid>
		<pubDate>Fri, 11 Jan 2008 19:46:04 -0800</pubDate>
		<dc:creator>qxntpqbbbqxl</dc:creator>
	</item><item>
		<title>By: Mick</title>
		<link>http://ask.metafilter.com/80802/Two-be-or-not-2-be#1198459</link>	
		<description>Everything I&apos;ve read has been the exact opposite.&lt;br&gt;
&lt;br&gt;
(sorry, I&apos;m too lazy to go digging through my books for support)</description>
		<guid isPermaLink="false">comment:ask.metafilter.com,2008:site.80802-1198459</guid>
		<pubDate>Fri, 11 Jan 2008 19:52:32 -0800</pubDate>
		<dc:creator>Mick</dc:creator>
	</item><item>
		<title>By: backseatpilot</title>
		<link>http://ask.metafilter.com/80802/Two-be-or-not-2-be#1198461</link>	
		<description>This would be an excellent thing to run an experiment on, I think.  Really, though, first you need to define what you mean by &quot;readability&quot;.  The first thing I thought of was how quickly one can read a sentence, but I notice others think it has to do with memory retention.  So, define that first and then build an experiment out of it.  Sticherbeast has a good suggestion, but I would add reading the entire thing aloud so an external observer can measure the results, especially if you&apos;re looking to see how quickly someone can read.</description>
		<guid isPermaLink="false">comment:ask.metafilter.com,2008:site.80802-1198461</guid>
		<pubDate>Fri, 11 Jan 2008 20:01:37 -0800</pubDate>
		<dc:creator>backseatpilot</dc:creator>
	</item><item>
		<title>By: grumblebee</title>
		<link>http://ask.metafilter.com/80802/Two-be-or-not-2-be#1198468</link>	
		<description>For me it depends:&lt;br&gt;
&lt;br&gt;
37 is easier for me to parse than thirty-seven (though not much).&lt;br&gt;
&lt;br&gt;
Eleven million, two-hundred two thousand and one is easier than 11,202,001.&lt;br&gt;
&lt;br&gt;
When I see large numbers (millions, billions, trillions, etc.), I often have to count up, from right to left (ones, tens, hundreds, thousands...) before I can understand the magnitude. &lt;br&gt;
&lt;br&gt;
Whatever test you do, I think it&apos;s import that you test each word and numeral separately. You&apos;re making an assumption that ALL numerals (or words) are easier. What if 2 is easier than two, but five is easier than 5? For me, zero is definitely easier than 0.</description>
		<guid isPermaLink="false">comment:ask.metafilter.com,2008:site.80802-1198468</guid>
		<pubDate>Fri, 11 Jan 2008 20:18:31 -0800</pubDate>
		<dc:creator>grumblebee</dc:creator>
	</item><item>
		<title>By: juv3nal</title>
		<link>http://ask.metafilter.com/80802/Two-be-or-not-2-be#1198474</link>	
		<description>I think you need to consider carefully what you mean by &quot;readable&quot; and how you&apos;re going to measure it.  For instance, assuming same type size, a spelled out number is going to be larger/take more space, etc and generally be more visible from greater distances or when the chosen type size is particularly small. &lt;br&gt;
&lt;br&gt;
When small enough or far enough away, 5 can pretty easily be mistaken for an S or an 8 for a B, but you&apos;d probably have much less of a problem with &quot;FIVE&quot; or &quot;EIGHT.&quot;</description>
		<guid isPermaLink="false">comment:ask.metafilter.com,2008:site.80802-1198474</guid>
		<pubDate>Fri, 11 Jan 2008 20:31:56 -0800</pubDate>
		<dc:creator>juv3nal</dc:creator>
	</item><item>
		<title>By: explosion</title>
		<link>http://ask.metafilter.com/80802/Two-be-or-not-2-be#1198481</link>	
		<description>It may just be different for different people, so a careful study of readers in your intended market might be in order.&lt;br&gt;
&lt;br&gt;
For example, I am the exact opposite of Grumblebee, apparently. I prefer small numbers to be written out (&quot;I invited five friends over for dinner,&quot;) but larger numbers in numerals (&quot;Bill Gates spent $1,235,690 on Doritos last year.&quot;)&lt;br&gt;
&lt;br&gt;
The context of the numbers may also be important. A lot of us are so used to digital clocks that reading &quot;11:39 pm&quot; is easier and faster than &quot;eleven thirty-nine p.m.&quot; Keep context in mind when you&apos;re deciding which way to go!</description>
		<guid isPermaLink="false">comment:ask.metafilter.com,2008:site.80802-1198481</guid>
		<pubDate>Fri, 11 Jan 2008 20:41:54 -0800</pubDate>
		<dc:creator>explosion</dc:creator>
	</item><item>
		<title>By: dobbs</title>
		<link>http://ask.metafilter.com/80802/Two-be-or-not-2-be#1198492</link>	
		<description>You&apos;re trying to prove something you are already convinced of. That&apos;s bad, no? If you want to do a study, you should be approaching it as &quot;Which is easier to read: numerals or numbers written in text?&quot; &lt;br&gt;
&lt;br&gt;
For me, it&apos;s usually the opposite of your current belief and everything I&apos;ve read on the topic agrees with me.</description>
		<guid isPermaLink="false">comment:ask.metafilter.com,2008:site.80802-1198492</guid>
		<pubDate>Fri, 11 Jan 2008 21:01:24 -0800</pubDate>
		<dc:creator>dobbs</dc:creator>
	</item><item>
		<title>By: jepler</title>
		<link>http://ask.metafilter.com/80802/Two-be-or-not-2-be#1198495</link>	
		<description>Just to be clear, you&apos;re not asking about using the numeral &quot;2&quot; as a replacement for &quot;too&quot; or &quot;to&quot; (&quot;ya me 2&quot;, or &quot;go 2 the store&quot;) but just the word &quot;two&quot;?</description>
		<guid isPermaLink="false">comment:ask.metafilter.com,2008:site.80802-1198495</guid>
		<pubDate>Fri, 11 Jan 2008 21:02:56 -0800</pubDate>
		<dc:creator>jepler</dc:creator>
	</item><item>
		<title>By: YamwotIam</title>
		<link>http://ask.metafilter.com/80802/Two-be-or-not-2-be#1198496</link>	
		<description>&lt;i&gt;Just to be clear&lt;/i&gt;&lt;br&gt;
&lt;br&gt;
Right, right. &quot;2&quot; vs. &quot;two&quot; is the question.</description>
		<guid isPermaLink="false">comment:ask.metafilter.com,2008:site.80802-1198496</guid>
		<pubDate>Fri, 11 Jan 2008 21:04:36 -0800</pubDate>
		<dc:creator>YamwotIam</dc:creator>
	</item><item>
		<title>By: Dee Xtrovert</title>
		<link>http://ask.metafilter.com/80802/Two-be-or-not-2-be#1198498</link>	
		<description>The convention (as I know it in my native language) was always that one should write out small numbers (say, anything from zero to twenty) and use numerals for bigger (i.e, 21, 457) numbers.  I stand by this in English as well, and in most intelligently written articles, books and letters I read, it&apos;s done this way.&lt;br&gt;
&lt;br&gt;
I suspect that because this is the &quot;accepted&quot; convention and the most popular usage as well, that that&apos;s what people &quot;expect.&quot;  What deviates from it is probably much less &quot;readable&quot; because it slows us down.  This is exactly what happened to me (as it did to iguanapolitico) when I read that &lt;br&gt;
&quot;1&quot; in the next-to-last paragraph . . . it definitely slowed me down.&lt;br&gt;
&lt;br&gt;
In any case, one could &quot;prove&quot; it either way.  &quot;11,250,305&quot; is probably more &quot;readable&quot; than &quot;eleven million two hundred fifty thousand three hundred and five,&quot; but it&apos;s got a lot to do with context.  That &quot;1&quot; in the middle of a sentence causes pause when used in place of &quot;one&quot; because it just looks wrong.  Hence, I believe, the convention of writing out smaller numbers and just using numbers themselves past a certain point.  Intuitively, &lt;i&gt;this&lt;/i&gt; makes sense, but doing it for every number simply doesn&apos;t.  Credibility would be an issue for many people, as well.</description>
		<guid isPermaLink="false">comment:ask.metafilter.com,2008:site.80802-1198498</guid>
		<pubDate>Fri, 11 Jan 2008 21:05:14 -0800</pubDate>
		<dc:creator>Dee Xtrovert</dc:creator>
	</item><item>
		<title>By: jepler</title>
		<link>http://ask.metafilter.com/80802/Two-be-or-not-2-be#1198501</link>	
		<description>&lt;a href=&quot;http://www.useit.com/alertbox/writing-numbers.html&quot;&gt;Show numbers as numerals when writing for online readers&lt;/a&gt;</description>
		<guid isPermaLink="false">comment:ask.metafilter.com,2008:site.80802-1198501</guid>
		<pubDate>Fri, 11 Jan 2008 21:07:10 -0800</pubDate>
		<dc:creator>jepler</dc:creator>
	</item><item>
		<title>By: pgoes</title>
		<link>http://ask.metafilter.com/80802/Two-be-or-not-2-be#1198504</link>	
		<description>What a cool idea; someone must have done a Masters thesis on this. Whether the presentation if web based or not seems irrelevant.   I can only offer this g&lt;a href=&quot;http://www.google.com/search?hl=en&amp;q=comprehension+of+numerals+vs.+written+numbers&amp;btnG=Search&quot;&gt;oogle search&lt;/a&gt;.&lt;br&gt;
&lt;br&gt;
On preview, awesome relevant link by jepler!</description>
		<guid isPermaLink="false">comment:ask.metafilter.com,2008:site.80802-1198504</guid>
		<pubDate>Fri, 11 Jan 2008 21:13:18 -0800</pubDate>
		<dc:creator>pgoes</dc:creator>
	</item><item>
		<title>By: YamwotIam</title>
		<link>http://ask.metafilter.com/80802/Two-be-or-not-2-be#1198506</link>	
		<description>Thank you jepler--eye-tracking data is exactly what I&apos;m looking for. Is Jakob Nielsen generally considered the last word on usability among the Web-design savvy these days?</description>
		<guid isPermaLink="false">comment:ask.metafilter.com,2008:site.80802-1198506</guid>
		<pubDate>Fri, 11 Jan 2008 21:13:57 -0800</pubDate>
		<dc:creator>YamwotIam</dc:creator>
	</item><item>
		<title>By: ook</title>
		<link>http://ask.metafilter.com/80802/Two-be-or-not-2-be#1198517</link>	
		<description>Careful about that; he appears to be saying not that numerals are more readable, but that people tend to fixate on them when skimming text.  Not the same thing.</description>
		<guid isPermaLink="false">comment:ask.metafilter.com,2008:site.80802-1198517</guid>
		<pubDate>Fri, 11 Jan 2008 21:25:26 -0800</pubDate>
		<dc:creator>ook</dc:creator>
	</item><item>
		<title>By: deeaytch</title>
		<link>http://ask.metafilter.com/80802/Two-be-or-not-2-be#1198526</link>	
		<description>The people who commented on the &quot;1&apos;&quot;s causing a pause are an example of Nielsen&apos;s point.  Do you want people to stop reading and stare at the number, or do you want them to be able to read normally without a &quot;forced&quot; fixation on it?</description>
		<guid isPermaLink="false">comment:ask.metafilter.com,2008:site.80802-1198526</guid>
		<pubDate>Fri, 11 Jan 2008 21:36:56 -0800</pubDate>
		<dc:creator>deeaytch</dc:creator>
	</item><item>
		<title>By: jamjam</title>
		<link>http://ask.metafilter.com/80802/Two-be-or-not-2-be#1198534</link>	
		<description>A friend of mine suffered a head injury which made his bad handwriting almost completely uninterpretable, but did not affect his ability to write numerals at all.&lt;br&gt;
&lt;br&gt;
If a similar separation in brain areas involved in &lt;em&gt;reading&lt;/em&gt; numerals and letters  is common, and certainly the received view seems to be that reading and numerical calculation are in different places, you could  argue that in order to use a written-out number in any kind of mental calculation, you have to translate it into numerals and this slows you down and potentially confuses you (&apos;two plus two equals four&apos; is much more difficult to read than 2+2=4 for me, for example).&lt;br&gt;
&lt;br&gt;
There is also always the straightforward information theoretic argument, of course; representing most numbers in numerals requires fewer bits than writing them out, and it&apos;s reasonable to guess that this makes them more easily handled by the brain in the absence of other information.</description>
		<guid isPermaLink="false">comment:ask.metafilter.com,2008:site.80802-1198534</guid>
		<pubDate>Fri, 11 Jan 2008 21:46:46 -0800</pubDate>
		<dc:creator>jamjam</dc:creator>
	</item><item>
		<title>By: YamwotIam</title>
		<link>http://ask.metafilter.com/80802/Two-be-or-not-2-be#1198535</link>	
		<description>Huh. Good points, ook and deeaytch. But for B2B Web writing, I wonder if &quot;stopping and staring&quot; and readability converge somewhat.</description>
		<guid isPermaLink="false">comment:ask.metafilter.com,2008:site.80802-1198535</guid>
		<pubDate>Fri, 11 Jan 2008 21:48:09 -0800</pubDate>
		<dc:creator>YamwotIam</dc:creator>
	</item><item>
		<title>By: mrw</title>
		<link>http://ask.metafilter.com/80802/Two-be-or-not-2-be#1198543</link>	
		<description>What most people find as more readable is likely to have a lot to do with their strong points in school. I know that myself, having been very strong in the sciences and maths, find reading numerals (1, 2, 3) a lot easier than reading numbers (one, two, three). I would speculate that someone with less strength in math, and more in language (&quot;english&quot; or literature) would find more comfort in the opposite. This second part is pure speculation, if there are any english majors out there that can confirm this, I too have become a little inquisitive on this one.</description>
		<guid isPermaLink="false">comment:ask.metafilter.com,2008:site.80802-1198543</guid>
		<pubDate>Fri, 11 Jan 2008 22:02:24 -0800</pubDate>
		<dc:creator>mrw</dc:creator>
	</item><item>
		<title>By: desuetude</title>
		<link>http://ask.metafilter.com/80802/Two-be-or-not-2-be#1198602</link>	
		<description>Echoing that I had to double-take on your &quot;1&quot; to figure out the context. (Even more confusingly,  you weren&apos;t using a number in that instance to express a quantity.)&lt;br&gt;
&lt;br&gt;
I would think that you would want to test reading comprehension?</description>
		<guid isPermaLink="false">comment:ask.metafilter.com,2008:site.80802-1198602</guid>
		<pubDate>Fri, 11 Jan 2008 23:36:08 -0800</pubDate>
		<dc:creator>desuetude</dc:creator>
	</item><item>
		<title>By: eritain</title>
		<link>http://ask.metafilter.com/80802/Two-be-or-not-2-be#1198642</link>	
		<description>IANA psycholinguist or a statistician, but I am studying both.&lt;br&gt;
&lt;br&gt;
Spelled numbers have more distinctive shapes than numerals, because of ascenders and descenders, and so they are easier to recognize provided the whole number can still be read at one glance. The average reading saccade is 7-9 letters, so I&apos;d guess that&apos;s about the width of an eyeful, and that any number under ten letters is better spelled out.&lt;br&gt;
&lt;br&gt;
That said, &apos;readable&apos; is different in different settings, and not always the same thing as &apos;legible&apos; either. Are you trying to optimize through-reading or scanning? If there &lt;i&gt;is&lt;/i&gt; text that needs to be with the numbers, you&apos;re looking at through-reading; if there isn&apos;t, IMO, the numbers should be in a table, and not in running text at all.&lt;br&gt;
&lt;br&gt;
Anyway, here&apos;s a sketch of an experimental design you could use. Give your experimental subjects short paragraphs to read with two or three numeric quantities in each, and tell them you&apos;ll check their comprehension with a question or two after each. Turns out some of your questions will involve the numbers, but some should not or they&apos;ll give up through-reading and start scanning anyway. They also don&apos;t know that you&apos;ve got a spelled version and a numeral version of each paragraph, which you&apos;ve presented randomly. I&apos;m not sure whether they should know that you&apos;re timing them. &lt;br&gt;
&lt;br&gt;
Now your analysis needs to check whether the differences in accuracy and reading rates are significant. In particular, this means knowing what the center and spread of of these are are (for a paragraph taking all respondents and for a respondent taking all paragraphs). Then you calculate how much the center changed across the spelled/numeral pairs, and see whether each falls outside the spread of the other (there are standard statistical techniques for all of this; consult a statistician). If so, you have support for a claim; if not, you have bupkis. It&apos;s a lot of work, but, well, knowing what you&apos;re talking about always is.&lt;br&gt;
&lt;br&gt;
Or you could, you know, &lt;ul&gt;&lt;li&gt;ignore the difference between scanning and through-reading, &lt;li&gt;ignore the principles that dictate two different, good document designs for two different informative purposes, &lt;li&gt;ignore the nagging doubt that says writing text that you mean people not to read is bad design, &lt;li&gt;ignore the overwhelming consensus of MeFites, stylists, and editors, and &lt;li&gt;try to make your point by appeals to the authority of some random web page. &lt;li&gt;You should also be prepared to ignore the ridicule, when someone points out that this alleged expert on readability has used sans-serif for running text and black on white for on-screen display, with lines too wide and leading too small for an effective, accurate eye return at line breaks. &lt;li&gt;And  if his point is scanning, he should have used a smaller face so that each eyeful and each screenful takes more in; you&apos;ll also have to ignore that.&lt;/li&gt;&lt;/li&gt;&lt;/li&gt;&lt;/li&gt;&lt;/li&gt;&lt;/li&gt;&lt;/li&gt;&lt;/ul&gt; Probably easier that way. Just depends whether the &apos;argument&apos; you&apos;re after is &apos;a connected series of statements intended to establish a proposition,&apos; or &apos;just the automatic gainsaying of any statement the other person makes&apos; (Python 1972). Up to you.</description>
		<guid isPermaLink="false">comment:ask.metafilter.com,2008:site.80802-1198642</guid>
		<pubDate>Sat, 12 Jan 2008 01:30:19 -0800</pubDate>
		<dc:creator>eritain</dc:creator>
	</item><item>
		<title>By: iguanapolitico</title>
		<link>http://ask.metafilter.com/80802/Two-be-or-not-2-be#1198699</link>	
		<description>Well.  I thought you meant numerals in place of their phonemes!  (Well, that&apos;s how you used them twice in your post.  Spelling out &quot;two&quot; was in the minority and I thought you were just choosing any random phoneme.  :)  So my early comments can officially go ahead and delete themselves now, because we were talking about different things.&lt;br&gt;
&lt;br&gt;
So just to have a do-over on my prefs, easiest to read are numerals for numbers over ten (or 10 and over ... I can never remember and am personally undecided) and words for numbers under that.  But again, it&apos;s what we *expect* because that&apos;s the basic writing guideline and has been for a long time, so that makes it easier to read.&lt;br&gt;
&lt;br&gt;
jepler&apos;s link is fantastic.  Scanability is a real issue on the internets.</description>
		<guid isPermaLink="false">comment:ask.metafilter.com,2008:site.80802-1198699</guid>
		<pubDate>Sat, 12 Jan 2008 06:16:29 -0800</pubDate>
		<dc:creator>iguanapolitico</dc:creator>
	</item><item>
		<title>By: iguanapolitico</title>
		<link>http://ask.metafilter.com/80802/Two-be-or-not-2-be#1198702</link>	
		<description>(Ugh, my reading comprehension officially sucks this week: it was only once that you used &quot;2&quot; in place of a non-number, &quot;to,&quot; and twice that you used numbers in place of actual numbers.  Still, sorry about misunderstanding the question.)&lt;br&gt;
&lt;br&gt;
Nielsen is basically the most *famous* web usability guy, but his opinions shouldn&apos;t be taken as gospel.  Plenty of web developers and users disagree with his strict rules.  (I personally love rules and do worship him, though, yes.)</description>
		<guid isPermaLink="false">comment:ask.metafilter.com,2008:site.80802-1198702</guid>
		<pubDate>Sat, 12 Jan 2008 06:20:29 -0800</pubDate>
		<dc:creator>iguanapolitico</dc:creator>
	</item><item>
		<title>By: adamrice</title>
		<link>http://ask.metafilter.com/80802/Two-be-or-not-2-be#1198985</link>	
		<description>eritain has it.&lt;br&gt;
&lt;br&gt;
Another question you need to ask is what impression you create. When you wrote &quot;one&quot; as &quot;1&quot; in the question, I had to stare at that for a few seconds, and frankly, thought &quot;this person is a quasi-literate raised on SMSing.&quot; I&apos;m conservative with my use of language, so if you were writing for an audience of me, you&apos;d want to avoid that.</description>
		<guid isPermaLink="false">comment:ask.metafilter.com,2008:site.80802-1198985</guid>
		<pubDate>Sat, 12 Jan 2008 12:50:01 -0800</pubDate>
		<dc:creator>adamrice</dc:creator>
	</item>
	</channel>
</rss>
