<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/1.5.2" -->
<rss version="2.0" 
	xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel>
	<title>Comments on: Unicode development under Apache</title>
	<link>http://www.chrisdolan.net/talk/2005/05/18/unicode-development-under-apache/</link>
	<description>Ideas and tools to improve programming throughput.</description>
	<pubDate>Wed, 20 Aug 2008 18:05:18 +0000</pubDate>
	<generator>http://wordpress.org/?v=1.5.2</generator>

	<item>
 		<title>Comment on Unicode development under Apache by: Joshua</title>
		<link>http://www.chrisdolan.net/talk/2005/05/18/unicode-development-under-apache/#comment-2</link>
		<pubDate>Wed, 18 May 2005 16:55:57 +0000</pubDate>
		<guid>http://www.chrisdolan.net/talk/2005/05/18/unicode-development-under-apache/#comment-2</guid>
					<description>Two questions/thoughts:

1. Can't you put the content encoding in an .htaccess file? What I mean is: That would appear to be an option between &quot;ignore all coding&quot; and &quot;use one coding everywhere&quot;.

See http://www.w3.org/International/questions/qa-htaccess-charset

2. Does  normally change the HTTP header info sent by Apache? I'm not as familiar with that as I should be, I guess. But, it seems like this might be a browser content-negotiation issue. (As in, Apache's HTTP Headers say one thing, the HTML file headers say something else.)</description>
		<content:encoded><![CDATA[	<p>Two questions/thoughts:</p>
	<ol>
	<li>Can&#8217;t you put the content encoding in an .htaccess file? What I mean is: That would appear to be an option between &#8220;ignore all coding&#8221; and &#8220;use one coding everywhere&#8221;.</li>
	</ol>
	<p>See <a href='http://www.w3.org/International/questions/qa-htaccess-charset' rel='nofollow'>http://www.w3.org/International/questions/qa-htaccess-charset</a></p>
	<ol>
	<li>Does  normally change the HTTP header info sent by Apache? I&#8217;m not as familiar with that as I should be, I guess. But, it seems like this might be a browser content-negotiation issue. (As in, Apache&#8217;s HTTP Headers say one thing, the HTML file headers say something else.)</li>
	</ol>
]]></content:encoded>
				</item>
</channel>
</rss>
