<?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>Noncompositional &#187; Meta</title>
	<atom:link href="http://noncompositional.com/category/meta/feed/" rel="self" type="application/rss+xml" />
	<link>http://noncompositional.com</link>
	<description></description>
	<lastBuildDate>Sat, 05 Jun 2010 16:51:23 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.1</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>Default for now</title>
		<link>http://noncompositional.com/2007/11/default-for-now/</link>
		<comments>http://noncompositional.com/2007/11/default-for-now/#comments</comments>
		<pubDate>Sun, 11 Nov 2007 05:56:22 +0000</pubDate>
		<dc:creator>Russell</dc:creator>
				<category><![CDATA[Meta]]></category>
		<category><![CDATA[themes]]></category>
		<category><![CDATA[wordpress]]></category>

		<guid isPermaLink="false">http://noncompositional.com/2007/11/default-for-now/</guid>
		<description><![CDATA[You may have noticed a theme change around here. Basically it&#8217;s because the theme I was using (and which I still do like very much) didn&#8217;t support some recent wordpress features. I&#8217;ve temporarily gone back to the WP default theme until I have time to figure out what actually to do.
]]></description>
			<content:encoded><![CDATA[<p>You may have noticed a theme change around here. Basically it&#8217;s because the theme I was using (and which I still do like very much) didn&#8217;t support some recent wordpress features. I&#8217;ve temporarily gone back to the WP default theme until I have time to figure out what actually to do.</p>
]]></content:encoded>
			<wfw:commentRss>http://noncompositional.com/2007/11/default-for-now/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Feeds and feed readers</title>
		<link>http://noncompositional.com/2007/01/feeds-and-feed-readers/</link>
		<comments>http://noncompositional.com/2007/01/feeds-and-feed-readers/#comments</comments>
		<pubDate>Tue, 30 Jan 2007 20:05:06 +0000</pubDate>
		<dc:creator>Russell</dc:creator>
				<category><![CDATA[Meta]]></category>
		<category><![CDATA[Miscellaneous]]></category>

		<guid isPermaLink="false">http://noncompositional.com/2007/01/feeds-and-feed-readers/</guid>
		<description><![CDATA[Apologies to anyone who may have found a dead feed over the past few days. Issues with wordpress updates and plugins required a reset of the feed configuration, but all should be working now.

I&#8217;ll also take a moment to sing the praises of the GreatNews RSS reader. It really helps in finding the various new [...]]]></description>
			<content:encoded><![CDATA[<p>Apologies to anyone who may have found a dead feed over the past few days. Issues with wordpress updates and plugins required a reset of the feed configuration, but all should be working now.</p>

<p>I&#8217;ll also take a moment to sing the praises of the GreatNews RSS reader. It really helps in finding the various new articles in all of the feeds you subscribe to (and it&#8217;s enormously helpful if you&#8217;ve spent a few days without checking any of your feeds, since you can view short summaries all at once, newspaper-style, rather than guessing from each title whether the short summary is worth reading at all).</p>
]]></content:encoded>
			<wfw:commentRss>http://noncompositional.com/2007/01/feeds-and-feed-readers/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>A little bit of candy</title>
		<link>http://noncompositional.com/2006/08/a-little-bit-of-candy/</link>
		<comments>http://noncompositional.com/2006/08/a-little-bit-of-candy/#comments</comments>
		<pubDate>Sun, 06 Aug 2006 15:35:34 +0000</pubDate>
		<dc:creator>Russell</dc:creator>
				<category><![CDATA[Meta]]></category>
		<category><![CDATA[Miscellaneous]]></category>

		<guid isPermaLink="false">http://noncompositional.com/2006/08/a-little-bit-of-candy/</guid>
		<description><![CDATA[Well, my apologies to anyone who tried to access this blog&#8217;s feed over the past couple of days and found nothing. I forgot to update a couple of settings after upgrading to the latest version of Wordpress. Anyway, everything should be fixed now.

In return for the error, a small, hopefully amusing item.

Observe this photograph. This [...]]]></description>
			<content:encoded><![CDATA[<p>Well, my apologies to anyone who tried to access this blog&#8217;s feed over the past couple of days and found nothing. I forgot to update a couple of settings after upgrading to the latest version of Wordpress. Anyway, everything should be fixed now.</p>

<p>In return for the error, a small, hopefully amusing item.</p>

<p>Observe <a href="http://noncompositional.com/images/languistic.jpg">this photograph</a>. This is the spine of a book that I found in a local used bookstore which, as you can see, is well-stocked with linguistics books (I&#8217;d say there are usually over a hundred different titles there at any given time). As I recall, the actual book is not by the shown author, though the content is l<s>a</s>inguistics-related. Unfortunately, it has since been purchased, so I cannot investigate further.</p>
]]></content:encoded>
			<wfw:commentRss>http://noncompositional.com/2006/08/a-little-bit-of-candy/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Shaky servers and shifty names</title>
		<link>http://noncompositional.com/2006/06/shaky-servers-and-shifty-names/</link>
		<comments>http://noncompositional.com/2006/06/shaky-servers-and-shifty-names/#comments</comments>
		<pubDate>Sat, 10 Jun 2006 01:52:37 +0000</pubDate>
		<dc:creator>Russell</dc:creator>
				<category><![CDATA[East Asian Languages]]></category>
		<category><![CDATA[Linguistics]]></category>
		<category><![CDATA[Meta]]></category>

		<guid isPermaLink="false">http://noncompositional.com/2006/06/shaky-servers-and-shifty-names/</guid>
		<description><![CDATA[My apologies to anyone who&#8217;s had trouble accessing the site over the past few days &#8211; the server that is hosting it has been going off- and online several times per day. Hopefully it will be all over soon.

And for a small bit of actual content: I was reading through an introductory Mandarin Chinese textbook [...]]]></description>
			<content:encoded><![CDATA[<p>My apologies to anyone who&#8217;s had trouble accessing the site over the past few days &#8211; the server that is hosting it has been going off- and online several times per day. Hopefully it will be all over soon.</p>

<p>And for a small bit of actual content: I was reading through an introductory Mandarin Chinese textbook today (basically to review all that I learned in high school before I start summer classes &#8212; I&#8217;ll have some things to say about the textbook itself at a later date), and found something interesting. It seems that as of January 18, 2005, the (South) Korean &#8220;Committee on the New Chinese Name (&#8216;notation&#8217;) for Seoul&#8221; decided that the name of its capital city should be written 首爾 (Shǒu&#8217;ěr), rather than 漢城 (Hànchéng). This is of course old news in the blogging community, and I recommend <a href="http://hunjang.blogspot.com/2005/01/seouls-new-chinese-name-for-itself.html">this entry</a> on <a href="http://hunjang.blogspot.com/">Hunjangûi karûch&#8217;im</a> for details and links to earlier progress reports on the matter, and <a href="http://www.languagehat.com/archives/001202.php">a post on languagehat</a> on a related matter involving the same committee.</p>

<p>I don&#8217;t want to comment directly on the political or ideological reasons behind the decision or any potential (or actual) controversy. However, I did find this line in the Japanese Wikipedia <a href="http://ja.wikipedia.org/wiki/%E3%82%BD%E3%82%A6%E3%83%AB%E7%89%B9%E5%88%A5%E5%B8%82">entry for Seoul</a> intriguing:</p>

<blockquote>一方、中国側では当初、「漢字表記は中国が決めるもの」として「首爾」の使用に消極的であったが</blockquote>

<p>Which means, &#8216;On the other hand, China was initially negative regarding the use of 首爾, as &#8220;Chinese writing is to be determined by China.&#8221;&#8216; No reference is given to the quote, which may not even be a direct quotation. I&#8217;ve been trying to find a Japanese paper that actually has a line like this, or similar to it, but so far no luck. I&#8217;m not convinced that Chinese officials would actually say that <em>all</em> uses of Chinese characters must be approved by China, and the quote leaves open the possibility that it just refers to China-internal matters (which would not an unreasonable thing to say, I think).</p>

<p>Another point of interest: the Korean committee did not decide to do what Japan has been doing for a long time: invent <em>kun-yomi</em> for Chinese characters. As far as I know, the only way Chinese characters are/were used in Korean is to write actual Chinese loan words from. In contrast, Japanese makes use of characters for their meanings alone. Thus in Japanese a verb like &#8216;read&#8217; is written 読む /yomu/, where the character is pronounced /yo/, with no connection to its Chinese-derived reading, /doku/. In Korean the verb for &#8216;read,&#8217; /ilk-/, is always written with <em>hangul</em>, rather than using 読. That character <em>does</em> exist in borrowed words, though, and it is pronounced /du/. For more details see <a href="http://en.wikipedia.org/wiki/Hanja">Hanja</a> on everyone&#8217;s favorite site.</p>

<p>But getting back to the committee: it would have been interesting if they decided to take the meaning of &#8220;Seoul,&#8221; which is &#8216;capital city,&#8217; and just chose characters that <em>mean</em> that, regardless of their Chinese pronunciations. I&#8217;m not sure what would happen if they asked China to start writing 首都 &#8216;capital city&#8217; for Seoul. It could get confusing. On the other hand, as a (non-native, fluent) speaker of Chinese pointed out to me, if they wanted to go that route they could have chosen a nonexistent compound like 首城 or 首市, both of which clearly mean &#8216;capital city&#8217; but don&#8217;t actually exist as words, AFAIK. It could have been a renaissance of <em>hanja</em> in Korea! Okay, probably not.</p>
]]></content:encoded>
			<wfw:commentRss>http://noncompositional.com/2006/06/shaky-servers-and-shifty-names/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Just a wee change</title>
		<link>http://noncompositional.com/2006/05/just-a-wee-change/</link>
		<comments>http://noncompositional.com/2006/05/just-a-wee-change/#comments</comments>
		<pubDate>Thu, 01 Jun 2006 06:31:45 +0000</pubDate>
		<dc:creator>Russell</dc:creator>
				<category><![CDATA[Meta]]></category>
		<category><![CDATA[Miscellaneous]]></category>

		<guid isPermaLink="false">http://noncompositional.com/2006/05/just-a-wee-change/</guid>
		<description><![CDATA[I&#8217;ve added a feedburner feed link to the list of feeds down there on the sidebar, though there should be no need to switch if you&#8217;re already subscribed, as a redirect should be in effect. If something breaks, try changing the feed link or just give a ring.

I&#8217;ll also use this opportunity to plug my [...]]]></description>
			<content:encoded><![CDATA[<p>I&#8217;ve added a feedburner <a href="http://feeds.feedburner.com/noncompositional">feed link</a> to the list of feeds down there on the sidebar, though there should be no need to switch if you&#8217;re already subscribed, as a redirect should be in effect. If something breaks, try changing the feed link or just give a ring.</p>

<p>I&#8217;ll also use this opportunity to plug my sister&#8217;s new website, <a href="http://eyeburst.net/">Eyeburst</a>, showcasing her art and writing, which I highly recommend.</p>
]]></content:encoded>
			<wfw:commentRss>http://noncompositional.com/2006/05/just-a-wee-change/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>I have an idea why</title>
		<link>http://noncompositional.com/2006/05/i-have-an-idea-why/</link>
		<comments>http://noncompositional.com/2006/05/i-have-an-idea-why/#comments</comments>
		<pubDate>Wed, 03 May 2006 05:05:07 +0000</pubDate>
		<dc:creator>Russell</dc:creator>
				<category><![CDATA[Constructing]]></category>
		<category><![CDATA[Linguistics]]></category>
		<category><![CDATA[Meta]]></category>

		<guid isPermaLink="false">http://noncompositional.com/2006/05/i-have-an-idea-why/</guid>
		<description><![CDATA[My apologies to those who happened upon the site today and were met with a database error message. The problem has miraculously resolved itself and will hopefully not come back (though I&#8217;m fairly sure what the cause is, and if it does come back it may be a few hours after I notice it before [...]]]></description>
			<content:encoded><![CDATA[<p>My apologies to those who happened upon the site today and were met with a database error message. The problem has miraculously resolved itself and will hopefully not come back (though I&#8217;m fairly sure what the cause is, and if it does come back it may be a few hours after I notice it before it is fixed).</p>

<p>Until next time, consider why preposition-deletion should be licenced in the same locations as NPIs are:</p>

<p>Do you have the faintest / any idea who that guy was?
I have no idea who that guy was.
*I&#8217;ve got an idea who that guy was.
I&#8217;ve got an idea of who that guy was.
?I&#8217;ve got <strong>some</strong> idea who that guy was.</p>

<p>(Before anyone tries to give me counterexamples: don&#8217;t worry, I&#8217;ve already found about 30 of them in the BNC. This, however, dwarfs the 1000 or so that <em>are</em> under negation or in otherwise nonveridical contexts (or however you like to talk about NPI licensing.))</p>
]]></content:encoded>
			<wfw:commentRss>http://noncompositional.com/2006/05/i-have-an-idea-why/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>What you see</title>
		<link>http://noncompositional.com/2006/01/what-you-see/</link>
		<comments>http://noncompositional.com/2006/01/what-you-see/#comments</comments>
		<pubDate>Wed, 04 Jan 2006 06:15:59 +0000</pubDate>
		<dc:creator>Russell</dc:creator>
				<category><![CDATA[Meta]]></category>
		<category><![CDATA[Miscellaneous]]></category>

		<guid isPermaLink="false">http://noncompositional.com/2006/01/what-you-see/</guid>
		<description><![CDATA[No linguistics here, just some griping regarding wordpress&#8217;s new WYSIWYG post editor. First, it&#8217;s annoying, as many such editors are, with strange spacing and line-inserting properties that make you format paragraphs in ways you might not want to. What&#8217;s really interesting is how it interacts with a firefox extention that does spell-checking. The extension, when [...]]]></description>
			<content:encoded><![CDATA[<p>No linguistics here, just some griping regarding wordpress&#8217;s new WYSIWYG post editor. First, it&#8217;s annoying, as many such editors are, with strange spacing and line-inserting properties that make you format paragraphs in ways you might not want to. What&#8217;s really interesting is how it interacts with a firefox extention that does spell-checking. The extension, when activated, will highlight in red all words in text fields that are misspelled. Clicking on the words will give a list of alternatives. When you&#8217;re done checking, you deactivate the checker and the red highlighting goes away. Interestingly, when you are using the WYSIWYG editor and use the spell-checker, you get the red highlighting, but the list of alternatives doesn&#8217;t show up. And then, the highlighting stays around after the checker is deactivated. What does this mean? It means that if you post the entry with the red highlighting, the actual post will have red text (with some really messy HTML). Never mind that the editor itself doesn&#8217;t let you change text color: somehow the spellchecker does it for you. That&#8217;s some weird stuff. (It should be obvious that I no longer use the new version of the post editor)</p>
]]></content:encoded>
			<wfw:commentRss>http://noncompositional.com/2006/01/what-you-see/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Orthography and (literary) point of view</title>
		<link>http://noncompositional.com/2006/01/orthography-and-literary-point-of-view/</link>
		<comments>http://noncompositional.com/2006/01/orthography-and-literary-point-of-view/#comments</comments>
		<pubDate>Wed, 04 Jan 2006 05:57:33 +0000</pubDate>
		<dc:creator>Russell</dc:creator>
				<category><![CDATA[Books]]></category>
		<category><![CDATA[Linguistics]]></category>
		<category><![CDATA[Meta]]></category>

		<guid isPermaLink="false">http://noncompositional.com/2006/01/orthography-and-literary-point-of-view/</guid>
		<description><![CDATA[First, sorry for the small feed hiccup that some of you may have experienced. I’m still working out the transition to Wordpress 2.0. (and if anyone out there is getting this weird error message on the draft preview panel about page redirects, and knows why, I’d be glad to hear about it)

As I mentioned last [...]]]></description>
			<content:encoded><![CDATA[<p>First, sorry for the small feed hiccup that some of you may have experienced. I’m still working out the transition to Wordpress 2.0. (and if anyone out there is getting this weird error message on the draft preview panel about page redirects, and knows why, I’d be glad to hear about it)</p>

<p>As I mentioned last post, I’ve been (re-)reading GRRM’s fantasy series <em>A song of ice and fire</em>. Now, Martin’s books take an interesting format, eschewing traditional chapters, which might normally be around 20 pages each in a comparable novel, in place of somewhat shorter (10 to 15 pages) sections. These are unnumbered and headed simply by the name of the character whose POV the section is written from. This makes for a somewhat faster-paced story, and also leads the reader to consider why each section is important to a particular character, rather than just the next section of plot. (Of course, this does not mean that every section from character X’s POV is primarily <em>about</em> X &#8211; there are some characters who seem as though they will never get a POV, so sometimes a section will be from the POV of someone who is near X, but most of the text is devoted to the actions and dialogue of X)</p>

<p><span id="more-76"></span>One of the POV characters, Arya, is 10 years old. In one scene she is speaking with a sort of holy man, who is telling her a story about a miner revolt. He is describing the mine conditions, and the following exchange takes place</p>

<blockquote>“Certain shafts were cut so low that the slaves could not stand upright, but had to crawl or bend. And there were wyrms in that red darkness too.”
“Earthworms?” she asked, frowning.
“Firewyrms. Some say they are akin to dragons, for wyrms breathe fire too.”</blockquote>

<p>Assuming that <em>worm</em> and <em>wyrm</em> are pronounced the same in this fantasy world, what has happened here is that the character Arya is unsure exactly what the significance of “worms” might be in the story, and so asks for clarification, and also may have done some guessing that some other class of worm (unknown to her) is involved, and so specifies the “earth” variety in her question. The holy man corrects her with “firewyrms.”</p>

<p>What’s interesting is that Arya’s representation of the spelling of <em>firewyrm</em> (she is literate) probably has an “o,” not a “y.” The “y” is there because the holy man knows that these are not ordinary worms, but some large worm-like creature that breathes fire. The reader (and possibly Martin) may assume that the holy man is literate, and this is likely. Unfortunately, this sort of dialogue doesn’t occur with the illiterate POV characters, so it’s hard to know what Martin would have done.</p>

<p>But in any case, what this does is highlight an imperfection (if you will) of single-POV prose–the character we see the world from doesn’t know enough to express everything that the author wants to express. Now, in the non-dialogue parts of prose, this normally isn’t that big of a problem. Because there is no actual speech, the author is mostly free to write as he pleases, using words or constructions in ways that the POV character might not use themselves (though keeping away from anachronisms like neon). However, when the POV character speaks the author is constrained to create dialogue that is realistic for that person. One might also think that when non-POV characters speak, the author is similarly constrained to portray that dialogue is the POV character would hear it. In most cases this is observed (ignoring such conveniences as assuming that people in conversation pay attention throughout the interlocutor’s turn, hearing everything perfectly), but in a case like this some orthography sneaks in.</p>

<p>This is less obvious than the sorts of orthographic oddness seen in the Harry Potter books (observed by Eric Bakovic <a href="http://camba.ucsd.edu/phonoloblog/index.php/2005/07/25/orthographic-notes-from-harry-potter/">here</a>), it brings up some interesting questions regarding POV and dialogue. For instance: how much can an author sneak in information (related to the story or related to the author) using spelling, and what is the most “damage” an author can do by subtly altering the words of a speaker? And are illiterate characters/people more susceptible to this sort of intrusion?</p>
]]></content:encoded>
			<wfw:commentRss>http://noncompositional.com/2006/01/orthography-and-literary-point-of-view/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>Occurring unexpectedly, unintentionally, or by chance</title>
		<link>http://noncompositional.com/2005/08/occurring-unexpectedly-unintentionally-or-by-chance/</link>
		<comments>http://noncompositional.com/2005/08/occurring-unexpectedly-unintentionally-or-by-chance/#comments</comments>
		<pubDate>Tue, 16 Aug 2005 02:27:42 +0000</pubDate>
		<dc:creator>Russell</dc:creator>
				<category><![CDATA[Linguistics]]></category>
		<category><![CDATA[Meta]]></category>

		<guid isPermaLink="false">http://www.noncompositional.com/2005/08/occurring-unexpectedly-unintentionally-or-by-chance/</guid>
		<description><![CDATA[Let&#8217;s talk about secrets, and more specifically, about revealing secrets. A secret is some piece of information known to some individual or group, which that group (or some subgroup of it) wants to remain unknown to those who do not know it. To keep a secret is to not tell any unknowing soul the information. [...]]]></description>
			<content:encoded><![CDATA[<p>Let&#8217;s talk about secrets, and more specifically, about revealing secrets. A secret is some piece of information known to some individual or group, which that group (or some subgroup of it) wants to remain unknown to those who do not know it. To keep a secret is to not tell any unknowing soul the information. To reveal a secret is to tell someone who doesn&#8217;t know the secret about it &#8211; or is it? Well, here are some possibilities:</p>

<ul><li>telling someone you know knows the information</li>
<li>telling someone you know doesn&#8217;t know</li>
<li>telling someone who you aren&#8217;t sure if they know</li></ul>

<p>The last two are probably revealing a secret. The first might get you a reprimand (<em>Don&#8217;t just go around babbling that to anyone!  What if I hadn&#8217;t known&#8230;</em>, for instance), or it might just be a normal activity. Depends on the secretive group.</p>

<p>Now, what would it mean to <em>accidentally</em> reveal the secret? (hint: see post title) Well, it probably means that you told the secret to someone who didn&#8217;t know the information carelessly, by a slip of the tongue, as it were.  You may or may not have known that the person knew the information.  And, importantly for this discussion, as soon as you realize that you uttered that information,  you realize your error.</p>

<p>Ah, but there&#8217;s a whole other set of possibilities if we consider the possibility that you <em>don&#8217;t realize</em> that some piece of information is a secret.  First possibility: your friend tells you some information intended to be a secret, but you figure it&#8217;s already common knowledge. Say your friend told you that she was going to join the Navy, and so you figure that this information is widely known, if not among her other friends than at least among her immediate family. But you&#8217;re in luck, because your friend hasn&#8217;t told anyone else yet (what a good friend you must be, then). So, you bring it up in conversation with her parents (<em>So, now that your daughter is leaving college to join the Navy&#8230;</em>), and only then, when the parents are {raging mad / unconscious on the floor / whatever}, do you realize your mistake.  Your utterance of the secret was made perfectly intentionally, with specific goals in mind, though importantly you assumed it was common knowledge when you uttered it.  The question is: did you do anything <em>accidentally</em>?</p>

<p><span id="more-40"></span>Second possibility:  your friend Joan told you in confidence that she actually <em>doesn&#8217;t</em> like her boyfriend&#8217;s red cabbage recipes.  You assume that it&#8217;s probably not common knowledge among all of your mutual acquaintances, and figure that you can go around telling anyone (like, say, the boyfriend’s buddies).  So you do: <em>Hey, Travis, it turns out that Joan actually doesn&#8217;t like Mitch&#8217;s red cabbage recipes.  Wouldn&#8217;t believe it to watch her wolf that stuff down, but hey&#8230;</em> (for instance).  This time, your addressee&#8217;s reaction won&#8217;t be something that will make you realize you&#8217;ve just revealed a secret.  It is only later, when the girlfriend is raging mad at you for telling her boyfriend’s buddies her deep, dark secret that you realize you’ve screwed up.  But did you <em>accidentally</em> reveal a very important secret?</p>

<p>And more importantly, how do you apologize for making these absolutely horrible mistakes?  (and no, she will never tell you anything ever ever again)</p>

<p>First case:</p>

<ol><li>Joan, before your parents call, I should let you know&#8230; I may have accidentally mentioned your secret about joining the Navy.  Sorry!</li>
<li>Joan, before your parents call, I should let you know&#8230; I may have accidentally mentioned that you&#8217;re dropping out to join the Navy.  Sorry!</li></ol>

<p>Second case, subcase 1:
[just after Joan tells you that the cabbage thing was a secret]</p>

<ol><li>Oh [expletive]! You know&#8230;I think I accidentally told {that / that secret / your secret (about the red cabbage)} to Travis. Sorry!</li>
<li>Oh [expletive]! You know&#8230;I think I accidentally told Travis that you don&#8217;t like your boyfriend&#8217;s red cabbage recipes.  Sorry!</li></ol>

<p>Second case, subcase 2:
[a day after Joan tells you not to mention the cabbage thing...you didn't tell her about your revealing it right afterwards because you forgot about it, or because you were nervous about letting her know right then]</p>

<ol><li>Uh&#8230;Joan?  You know&#8230;I think I accidentally told Travis {that / that secret / your secret (about the red cabbage)}. Sorry!</li>
<li>Uh&#8230;Joan?  You know&#8230;I think I accidentally told Travis that you don&#8217;t like your boyfriend&#8217;s red cabbage recipes.  Sorry!</li></ol>

<p>And now the fun part: in each of the above cases, which utterances are felicitous?  Let&#8217;s call the two versions <strong><em>that</em>-clause apologies</strong> and <strong><em>secret</em> apologies</strong>.  It&#8217;s all very wishy-washy for me, but I&#8217;d say that in Case 1, the <em>secret</em> apology is out, though mostly because the speaker just doesn&#8217;t have definitive proof that the information was a secret, just indirect (though quite strong) evidence that it was, namely the parents&#8217; verbal and nonverbal reactions to finding out the news.  However, if you were to use the <em>secret</em> apology, Joan might well think it normal, since it was always a secret to her.  For Case 2:1, again I&#8217;d have to say that although both seem fine, the <em>that</em>-clause might be preferred, though I&#8217;m not sure why.  I can think of two possible reasons: use of the word <em>secret</em> in the immediately preceding discourse, extremely recent revelation of the secrecy of the information (territory effects with recently-acquired information).  Eh, both are fine, I guess.  Finally, for Case 2:2, both versions seem equally fine.  The two reasons I outlined above wouldn&#8217;t apply, by the way.</p>

<p>Maybe others have different judgements, but this sort of surprised me.  Since the actual informing act was not accidental, it would seem that the message-encoding <em>that</em>-clauses would be dispreferred, but other factors seem to outweigh that consideration.</p>

<p>Only thing is, if each of these cases can be described with &#8220;someone accidentally revealed a secret&#8221; (maybe not all of them can), where does all the meaning come from, exactly?  Which of these words is polysemous, and what combinations of senses give you the right meaning.  And does it have to do with <em>reveal</em>, which isn&#8217;t even in any of the utterances I made up? (yeah, sure, it could have been) The answer&#8217;s probably much simpler than I&#8217;m making it out to be.</p>

<p>(Oh, and why the Meta tag?  Eh, I just added the RDF and Atom feed links to various parts of the page, in case anyone wants them)</p>
]]></content:encoded>
			<wfw:commentRss>http://noncompositional.com/2005/08/occurring-unexpectedly-unintentionally-or-by-chance/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Some experimentation</title>
		<link>http://noncompositional.com/2005/07/some-experimentation/</link>
		<comments>http://noncompositional.com/2005/07/some-experimentation/#comments</comments>
		<pubDate>Sun, 10 Jul 2005 09:06:17 +0000</pubDate>
		<dc:creator>Russell</dc:creator>
				<category><![CDATA[Meta]]></category>

		<guid isPermaLink="false">http://www.noncompositional.com/2005/07/some-experimentation/</guid>
		<description><![CDATA[The background images of the Relaxation theme I was using earlier had the annoying property of being rendered later than the text, which annoyed be.  I don&#8217;t think the load times were bad at all, but it just looked bad when loading, to me anyway.  So I&#8217;ve just been doing some experimentation with [...]]]></description>
			<content:encoded><![CDATA[<p>The background images of the <a href="http://www.jowra.de/wp/2005/04/wordpress-theme-relaxation/">Relaxation</a> theme I was using earlier had the annoying property of being rendered later than the text, which annoyed be.  I don&#8217;t think the load times were bad at all, but it just <em>looked</em> bad when loading, to me anyway.  So I&#8217;ve just been doing some experimentation with background-image-less themes, and while I was at it looked for liquid themes (i.e., those with non-fixed-width CSS styles, so it resized based on the size of the &#8220;viewer port&#8221; (browser window) and wasn&#8217;t mean to those with really large or small screen resolutions).  You&#8217;re looking at the <a href="http://steamedpenguin.com/design/Steam/">Steam</a> theme (with some significant modifications).  Anyone with any gripes about the theme (especially colors or font styles &#8212; I have horrible sense), let me know.</p>
]]></content:encoded>
			<wfw:commentRss>http://noncompositional.com/2005/07/some-experimentation/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

