<?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"
	>
<channel>
	<title>Comments on: Frank and the sons of Ishmael</title>
	<atom:link href="http://oreneta.com/kalebeul/2003/12/18/frank-and-the-sons-of-ishmael/feed/rss2/" rel="self" type="application/rss+xml" />
	<link>http://oreneta.com/kalebeul/2003/12/18/frank-and-the-sons-of-ishmael/</link>
	<description>anythingarian bubbles and troubles from the land of the fretting nun</description>
	<pubDate>Sun, 06 Jul 2008 21:00:43 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.5.1</generator>
		<item>
		<title>By: Trevor</title>
		<link>http://oreneta.com/kalebeul/2003/12/18/frank-and-the-sons-of-ishmael/#comment-256</link>
		<dc:creator>Trevor</dc:creator>
		<pubDate>Tue, 30 Nov 1999 00:00:00 +0000</pubDate>
		<guid isPermaLink="false">http://oreneta.com/kalebeul/2003/12/18/frank-and-the-sons-of-ishmael/#comment-256</guid>
		<description>Thanks very much for that. I'm into the season of heavy drinking at the mo, so won't begin to digest until the weekend, but I'll get back to you on your query.</description>
		<content:encoded><![CDATA[<p>Thanks very much for that. I&#8217;m into the season of heavy drinking at the mo, so won&#8217;t begin to digest until the weekend, but I&#8217;ll get back to you on your query.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Aidan Kehoe</title>
		<link>http://oreneta.com/kalebeul/2003/12/18/frank-and-the-sons-of-ishmael/#comment-257</link>
		<dc:creator>Aidan Kehoe</dc:creator>
		<pubDate>Tue, 30 Nov 1999 00:00:00 +0000</pubDate>
		<guid isPermaLink="false">http://oreneta.com/kalebeul/2003/12/18/frank-and-the-sons-of-ishmael/#comment-257</guid>
		<description>Long term, the font family shouldn't have much bearing on anything, as browsers get intelligent enough about searching the available characters in each of them. Mozilla and MSIE, for example, do this pretty intelligently now. (Because what you're doing is working at the moment, I assume it's the long term you're worrying about.) 

Moving to UTF-8 is The Right Thing, because when you tell Windows machines to use ISO-8859-1 they actually use Code Page 1252, which is subtly incompatible with ISO-8859-1. (Cf; you can input the Euro sign, which isn't in ISO-8859-1. Ditto directed quotation marks, em-dashes, en-dashes et al--in short, it's a much better character set for the Roman script languages. Except that, in practical terms, it's not, because when you do translate from it to Unicode, most programs are buggy and don't check whether any of the input is in those 32 characters marked "control"  in ISO-8859-1 and actually used in Windows-1252. Bad programmers.)

Your issue seems to be the program you're using to input stuff. If it's Internet Explorer, _perhaps_ checking the "Always send URLs as UTF-8 (requires restart)" preference will work--that is, you'll be able to input e-acute, Euro sign etc. normally and they'll get to the server encoded as %A9%C3, %82%E2%0A%AC etc. as is correct for UTF-8. If you're using the HTML escape codes at http://www.phon.ucl.ac.uk/home/wells/ipa-unicode.htm, be aware that you're using something separate from UTF-8. Browsers, notably Netscape 4, supported the HTML escape codes before they properly supported UTF-8, but today which to use is much of a muchness.

Give me a shout if the "Always send URLs as UTF-8" thing works; I use Windows machines rarely enough that it'll be a while before I get to check.</description>
		<content:encoded><![CDATA[<p>Long term, the font family shouldn&#8217;t have much bearing on anything, as browsers get intelligent enough about searching the available characters in each of them. Mozilla and MSIE, for example, do this pretty intelligently now. (Because what you&#8217;re doing is working at the moment, I assume it&#8217;s the long term you&#8217;re worrying about.) </p>
<p>Moving to UTF-8 is The Right Thing, because when you tell Windows machines to use ISO-8859-1 they actually use Code Page 1252, which is subtly incompatible with ISO-8859-1. (Cf; you can input the Euro sign, which isn&#8217;t in ISO-8859-1. Ditto directed quotation marks, em-dashes, en-dashes et al&#8211;in short, it&#8217;s a much better character set for the Roman script languages. Except that, in practical terms, it&#8217;s not, because when you do translate from it to Unicode, most programs are buggy and don&#8217;t check whether any of the input is in those 32 characters marked &#8220;control&#8221;  in ISO-8859-1 and actually used in Windows-1252. Bad programmers.)</p>
<p>Your issue seems to be the program you&#8217;re using to input stuff. If it&#8217;s Internet Explorer, _perhaps_ checking the &#8220;Always send URLs as UTF-8 (requires restart)&#8221; preference will work&#8211;that is, you&#8217;ll be able to input e-acute, Euro sign etc. normally and they&#8217;ll get to the server encoded as %A9%C3, %82%E2%0A%AC etc. as is correct for UTF-8. If you&#8217;re using the HTML escape codes at <a href="http://www.phon.ucl.ac.uk/home/wells/ipa-unicode.htm" rel="nofollow">http://www.phon.ucl.ac.uk/home/wells/ipa-unicode.htm</a>, be aware that you&#8217;re using something separate from UTF-8. Browsers, notably Netscape 4, supported the HTML escape codes before they properly supported UTF-8, but today which to use is much of a muchness.</p>
<p>Give me a shout if the &#8220;Always send URLs as UTF-8&#8243; thing works; I use Windows machines rarely enough that it&#8217;ll be a while before I get to check.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: James Fennell</title>
		<link>http://oreneta.com/kalebeul/2003/12/18/frank-and-the-sons-of-ishmael/#comment-258</link>
		<dc:creator>James Fennell</dc:creator>
		<pubDate>Tue, 30 Nov 1999 00:00:00 +0000</pubDate>
		<guid isPermaLink="false">http://oreneta.com/kalebeul/2003/12/18/frank-and-the-sons-of-ishmael/#comment-258</guid>
		<description>Read Robert Bartlett, The Making of Modern Europe: Conquest Colonisation and Cultural Change 950-1350 to understand the adoption of the term Frank first, as you say, by those attacked by the west, but eventually by the 'westerners' themselves (through the medium of the crusades).  Incidentially the latin francum = freedom (the western notion of freedom to share one law, one religoin and title to ones land).  So western notions of freedom are perhaps more about being free to be a westerner, than universal freedom.


</description>
		<content:encoded><![CDATA[<p>Read Robert Bartlett, The Making of Modern Europe: Conquest Colonisation and Cultural Change 950-1350 to understand the adoption of the term Frank first, as you say, by those attacked by the west, but eventually by the &#8216;westerners&#8217; themselves (through the medium of the crusades).  Incidentially the latin francum = freedom (the western notion of freedom to share one law, one religoin and title to ones land).  So western notions of freedom are perhaps more about being free to be a westerner, than universal freedom.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
