<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	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:georss="http://www.georss.org/georss" xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#" xmlns:media="http://search.yahoo.com/mrss/"
		>
<channel>
	<title>Comments for Word Travels</title>
	<atom:link href="http://wordtravelstheblog.com/comments/feed/" rel="self" type="application/rss+xml" />
	<link>http://wordtravelstheblog.com</link>
	<description>Musings about language in the digital landscape</description>
	<lastBuildDate>Thu, 18 Apr 2013 14:54:25 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.com/</generator>
	<item>
		<title>Comment on Simply Gibberish by Useful Link</title>
		<link>http://wordtravelstheblog.com/2010/07/09/simply-gibberish/#comment-3710</link>
		<dc:creator><![CDATA[Useful Link]]></dc:creator>
		<pubDate>Thu, 18 Apr 2013 14:54:25 +0000</pubDate>
		<guid isPermaLink="false">http://achouston.wordpress.com/?p=72#comment-3710</guid>
		<description><![CDATA[I believe that is one of the most vital info for me. And i am satisfied studying 
your article. But wanna observation on few basic issues, The website style is ideal, the articles is 
in reality great : D. Just right process, cheers]]></description>
		<content:encoded><![CDATA[<p>I believe that is one of the most vital info for me. And i am satisfied studying<br />
your article. But wanna observation on few basic issues, The website style is ideal, the articles is<br />
in reality great : D. Just right process, cheers</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Seman-tech Changes? by achouston</title>
		<link>http://wordtravelstheblog.com/2013/03/14/seman-tech-changes/#comment-3697</link>
		<dc:creator><![CDATA[achouston]]></dc:creator>
		<pubDate>Thu, 11 Apr 2013 15:13:01 +0000</pubDate>
		<guid isPermaLink="false">http://wordtravelstheblog.com/?p=1685#comment-3697</guid>
		<description><![CDATA[Hi BBear!

Interesting points about the early DOS days wrt to &#039;stack&#039;. Hmmm, maybe we&#039;ll see pejorative semantic development at some future point -- job description -- wanted a full stacker, but overflow stackers need not apply. :- )  Hope you are doing great!]]></description>
		<content:encoded><![CDATA[<p>Hi BBear!</p>
<p>Interesting points about the early DOS days wrt to &#8216;stack&#8217;. Hmmm, maybe we&#8217;ll see pejorative semantic development at some future point &#8212; job description &#8212; wanted a full stacker, but overflow stackers need not apply. :- )  Hope you are doing great!</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Seman-tech Changes? by bbear</title>
		<link>http://wordtravelstheblog.com/2013/03/14/seman-tech-changes/#comment-3694</link>
		<dc:creator><![CDATA[bbear]]></dc:creator>
		<pubDate>Wed, 10 Apr 2013 18:12:10 +0000</pubDate>
		<guid isPermaLink="false">http://wordtravelstheblog.com/?p=1685#comment-3694</guid>
		<description><![CDATA[Back in DOS days &#039;stack&#039; referred to a small, convenient memory segment mostly used in a last-in-first-out fashion: In assembly language you could &#039;push&#039; the contents of, say, a register onto the top of the stack and then later &#039;pop&#039; it off to the same or a different destination, with the stack pointer adjusted accordingly. Under MASM 5.0 the default size for the stack segment was only 1024 bytes, and much smaller stacks were usually more than adequate. This configuration was echoed in Intel&#039;s math coprocessor chips, where a stack of eight registers, ST through ST(7), was directly addressable via assembler&#039;s &#039;f&#039; commands (fadd, fmul, etc)…

Nothing of this earlier, low-level understanding of &#039;stack&#039; appears to remain in the usage &#039;full-stack programmer.&#039; Indeed, since a full stack came right before stack overflow and consequent program crash, we might construe a full-stack programmer to be one given to risky coding, or one insufficiently attentive to deeply recursive routines. ;-)…]]></description>
		<content:encoded><![CDATA[<p>Back in DOS days &#8216;stack&#8217; referred to a small, convenient memory segment mostly used in a last-in-first-out fashion: In assembly language you could &#8216;push&#8217; the contents of, say, a register onto the top of the stack and then later &#8216;pop&#8217; it off to the same or a different destination, with the stack pointer adjusted accordingly. Under MASM 5.0 the default size for the stack segment was only 1024 bytes, and much smaller stacks were usually more than adequate. This configuration was echoed in Intel&#8217;s math coprocessor chips, where a stack of eight registers, ST through ST(7), was directly addressable via assembler&#8217;s &#8216;f&#8217; commands (fadd, fmul, etc)…</p>
<p>Nothing of this earlier, low-level understanding of &#8216;stack&#8217; appears to remain in the usage &#8216;full-stack programmer.&#8217; Indeed, since a full stack came right before stack overflow and consequent program crash, we might construe a full-stack programmer to be one given to risky coding, or one insufficiently attentive to deeply recursive routines. <img src='http://s1.wp.com/wp-includes/images/smilies/icon_wink.gif' alt=';-)' class='wp-smiley' /> …</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Is &#8216;coolth&#8217; catching on? by http://tinyurl.com/go18foot20546</title>
		<link>http://wordtravelstheblog.com/2010/07/06/is-coolth-catching-on/#comment-3355</link>
		<dc:creator><![CDATA[http://tinyurl.com/go18foot20546]]></dc:creator>
		<pubDate>Tue, 05 Feb 2013 03:06:34 +0000</pubDate>
		<guid isPermaLink="false">http://achouston.wordpress.com/?p=35#comment-3355</guid>
		<description><![CDATA[]]></description>
		<content:encoded><![CDATA[<p>“Is coolth catching on? | Word Travels” was indeed a fantastic article.<br />
If solely there were even more weblogs just like this one in the<br />
net. Regardless, thanks a lot for ur time, Lynette</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Word Jumbles #11 by achouston</title>
		<link>http://wordtravelstheblog.com/2012/07/02/word-jumbles-11/#comment-1200</link>
		<dc:creator><![CDATA[achouston]]></dc:creator>
		<pubDate>Mon, 16 Jul 2012 13:47:43 +0000</pubDate>
		<guid isPermaLink="false">http://wordtravelstheblog.com/?p=1629#comment-1200</guid>
		<description><![CDATA[Hey BBear!  You keep me on my toes. Thanks for sharing the alternates AND your travelogue. :-)]]></description>
		<content:encoded><![CDATA[<p>Hey BBear!  You keep me on my toes. Thanks for sharing the alternates AND your travelogue. <img src='http://s0.wp.com/wp-includes/images/smilies/icon_smile.gif' alt=':-)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Word Jumbles #11 by bbear</title>
		<link>http://wordtravelstheblog.com/2012/07/02/word-jumbles-11/#comment-1199</link>
		<dc:creator><![CDATA[bbear]]></dc:creator>
		<pubDate>Mon, 16 Jul 2012 13:22:59 +0000</pubDate>
		<guid isPermaLink="false">http://wordtravelstheblog.com/?p=1629#comment-1199</guid>
		<description><![CDATA[There are some additional answers to this jumble:

rapids
fissure
granite  ingrate  tearing
erosion
desert  rested  deters

I was struck by what a forbidding landscape these word suggest:

&lt;i&gt;Erosion&lt;/i&gt; and geological &lt;i&gt;tearing&lt;/i&gt; have created a &lt;i&gt;fissure&lt;/i&gt; through which &lt;i&gt;rapids&lt;/i&gt; tumble between &lt;i&gt;granite&lt;/i&gt; walls. This feature &lt;i&gt;deters&lt;/i&gt; all but the hardiest traveler, who, once he has &lt;/i&gt;rested&lt;/i&gt; in the parched &lt;i&gt;desert&lt;/i&gt; beyond the canyon rim, may well reproach himself for having been an &lt;i&gt;ingrate&lt;/i&gt; midst the noise and spray of the torrent below.]]></description>
		<content:encoded><![CDATA[<p>There are some additional answers to this jumble:</p>
<p>rapids<br />
fissure<br />
granite  ingrate  tearing<br />
erosion<br />
desert  rested  deters</p>
<p>I was struck by what a forbidding landscape these word suggest:</p>
<p><i>Erosion</i> and geological <i>tearing</i> have created a <i>fissure</i> through which <i>rapids</i> tumble between <i>granite</i> walls. This feature <i>deters</i> all but the hardiest traveler, who, once he has rested in the parched <i>desert</i> beyond the canyon rim, may well reproach himself for having been an <i>ingrate</i> midst the noise and spray of the torrent below.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on More Linguistic Asymmetries by [Traduction] La symétrie en linguistique &#171; Sighild&#039;s Blog</title>
		<link>http://wordtravelstheblog.com/2011/10/21/more-linguistic-asymmetries/#comment-346</link>
		<dc:creator><![CDATA[[Traduction] La symétrie en linguistique &#171; Sighild&#039;s Blog]]></dc:creator>
		<pubDate>Sat, 22 Oct 2011 08:30:47 +0000</pubDate>
		<guid isPermaLink="false">http://wordtravelstheblog.com/?p=1116#comment-346</guid>
		<description><![CDATA[[...] de repartir pour une sieste matinale, je vous donne le lien, libre à vous de réagir : Linguistiques et asymétries &quot;Aimer&quot; ceci :&quot;J&#039;aime&quot;Soyez le premier à aimer ce post.      Comments RSS [...]]]></description>
		<content:encoded><![CDATA[<p>[...] de repartir pour une sieste matinale, je vous donne le lien, libre à vous de réagir : Linguistiques et asymétries &quot;Aimer&quot; ceci :&quot;J&#039;aime&quot;Soyez le premier à aimer ce post.      Comments RSS [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Is &#8216;coolth&#8217; catching on? by Hailey</title>
		<link>http://wordtravelstheblog.com/2010/07/06/is-coolth-catching-on/#comment-319</link>
		<dc:creator><![CDATA[Hailey]]></dc:creator>
		<pubDate>Mon, 26 Sep 2011 11:15:32 +0000</pubDate>
		<guid isPermaLink="false">http://achouston.wordpress.com/?p=35#comment-319</guid>
		<description><![CDATA[You could not be more factual]]></description>
		<content:encoded><![CDATA[<p>You could not be more factual</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Teenage, Middle-age, New Age by bbear</title>
		<link>http://wordtravelstheblog.com/2011/09/06/teenage-middle-age-new-age/#comment-309</link>
		<dc:creator><![CDATA[bbear]]></dc:creator>
		<pubDate>Fri, 09 Sep 2011 18:27:25 +0000</pubDate>
		<guid isPermaLink="false">http://wordtravelstheblog.com/?p=1195#comment-309</guid>
		<description><![CDATA[I think it&#039;s because if you say &#039;new-age men&#039; you mean men whose outlook is characteristic of New Age philosophy, rather than their being newly-aged like newly-aged cheese, where the &#039;-ed&#039; makes it a past participle so it accepts an adverbial modifier. By the same token middle-age men would refer to habitants of the Middle Ages or of any period falling between two others, say between the Age of Enlightenment and the Age of Romance (an enlightened romantic ;-) ). Or to those who reflect attributes thought to characterize such periods... 

And in fact we often use -age in precisely that kind of allusive way. We speak of &#039;teenage music&#039; not to describe music composed 13 to 19 years ago, but rather music that appeals to adolescent tastes. &#039;Middle-age spread&#039; references the fact of the expanded waistlines of many people in their middle years; it doesn&#039;t mean the adipose tissue itself is 35 to 55 years old. So we could construct a formalism in which we use &lt;i&gt;aged&lt;/i&gt; to mean &lt;i&gt;how old&lt;/i&gt; (&#039;...died yesterday at Brighton, aged 91&#039;) and &lt;i&gt;age&lt;/i&gt; as a &lt;i&gt;pointer&lt;/i&gt; to some remote object. Well, we could, but I doubt anybody would start talking about moderately-aged men in shorts...]]></description>
		<content:encoded><![CDATA[<p>I think it&#8217;s because if you say &#8216;new-age men&#8217; you mean men whose outlook is characteristic of New Age philosophy, rather than their being newly-aged like newly-aged cheese, where the &#8216;-ed&#8217; makes it a past participle so it accepts an adverbial modifier. By the same token middle-age men would refer to habitants of the Middle Ages or of any period falling between two others, say between the Age of Enlightenment and the Age of Romance (an enlightened romantic <img src='http://s1.wp.com/wp-includes/images/smilies/icon_wink.gif' alt=';-)' class='wp-smiley' />  ). Or to those who reflect attributes thought to characterize such periods&#8230; </p>
<p>And in fact we often use -age in precisely that kind of allusive way. We speak of &#8216;teenage music&#8217; not to describe music composed 13 to 19 years ago, but rather music that appeals to adolescent tastes. &#8216;Middle-age spread&#8217; references the fact of the expanded waistlines of many people in their middle years; it doesn&#8217;t mean the adipose tissue itself is 35 to 55 years old. So we could construct a formalism in which we use <i>aged</i> to mean <i>how old</i> (&#8216;&#8230;died yesterday at Brighton, aged 91&#8242;) and <i>age</i> as a <i>pointer</i> to some remote object. Well, we could, but I doubt anybody would start talking about moderately-aged men in shorts&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Blind Tasting: the Audiobook Edition by just need to know how to produce music .thanks from victor</title>
		<link>http://wordtravelstheblog.com/2011/07/13/blind-tasting-the-audiobook-edition/#comment-297</link>
		<dc:creator><![CDATA[just need to know how to produce music .thanks from victor]]></dc:creator>
		<pubDate>Sun, 14 Aug 2011 20:35:54 +0000</pubDate>
		<guid isPermaLink="false">http://wordtravelstheblog.com/?p=1094#comment-297</guid>
		<description><![CDATA[direct me]]></description>
		<content:encoded><![CDATA[<p>direct me</p>
]]></content:encoded>
	</item>
</channel>
</rss>
