<?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/"
	>
<channel>
	<title>Comments on: Case sensitivity is hard - for companies like Adobe</title>
	<atom:link href="http://blog.gtuhl.com/2008/01/13/case-sensitivity-is-hard-for-companies-like-adobe/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.gtuhl.com/2008/01/13/case-sensitivity-is-hard-for-companies-like-adobe/</link>
	<description>Software Development, IT, Gadgets, and Startups</description>
	<pubDate>Tue, 06 Jan 2009 05:53:27 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.7</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: gtuhl</title>
		<link>http://blog.gtuhl.com/2008/01/13/case-sensitivity-is-hard-for-companies-like-adobe/comment-page-1/#comment-130</link>
		<dc:creator>gtuhl</dc:creator>
		<pubDate>Mon, 14 Jan 2008 00:35:26 +0000</pubDate>
		<guid isPermaLink="false">http://blog.gtuhl.com/2008/01/13/case-sensitivity-is-hard-for-companies-like-adobe/#comment-130</guid>
		<description>Yeah, from reading around it appears I should have left the sensitivity setting alone (case-insensitive was the default).  I just saw case-sensitive and that logically seemed like the correct option.

My bigger beef is with Adobe.  It boggles my mind to think about how a piece of software could be written such that the case of file paths would make it inoperable.  I guess its just from using Linux for a long while but I never assume case insensitivity when looking at a file path, even in windows where it is insensitive.</description>
		<content:encoded><![CDATA[<p>Yeah, from reading around it appears I should have left the sensitivity setting alone (case-insensitive was the default).  I just saw case-sensitive and that logically seemed like the correct option.</p>
<p>My bigger beef is with Adobe.  It boggles my mind to think about how a piece of software could be written such that the case of file paths would make it inoperable.  I guess its just from using Linux for a long while but I never assume case insensitivity when looking at a file path, even in windows where it is insensitive.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tejus Parikh</title>
		<link>http://blog.gtuhl.com/2008/01/13/case-sensitivity-is-hard-for-companies-like-adobe/comment-page-1/#comment-129</link>
		<dc:creator>Tejus Parikh</dc:creator>
		<pubDate>Mon, 14 Jan 2008 00:19:21 +0000</pubDate>
		<guid isPermaLink="false">http://blog.gtuhl.com/2008/01/13/case-sensitivity-is-hard-for-companies-like-adobe/#comment-129</guid>
		<description>OSX has is preserved case since 10.3, however, it would just complain if you had a file called AdobeSucks.swf and tried to create a file called ADOBESUCKS.swf.  If you attempted to access AdobeSucks.swf as ADOBESUCKS.swf, the system give you a file not found.

Which makes the whole thing more bizarre.</description>
		<content:encoded><![CDATA[<p>OSX has is preserved case since 10.3, however, it would just complain if you had a file called AdobeSucks.swf and tried to create a file called ADOBESUCKS.swf.  If you attempted to access AdobeSucks.swf as ADOBESUCKS.swf, the system give you a file not found.</p>
<p>Which makes the whole thing more bizarre.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
