<?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: Clarification Regarding IE5/Win</title>
	<atom:link href="http://simplebits.com/notebook/2005/01/12/clarification/feed/" rel="self" type="application/rss+xml" />
	<link>http://simplebits.com/notebook/2005/01/12/clarification/</link>
	<description>Handcrafted pixels &#38; text from Salem, Massachusetts.</description>
	<lastBuildDate>Tue, 08 Dec 2009 23:15:49 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.1.2</generator>
	<item>
		<title>By: Kristy Ulrich</title>
		<link>http://simplebits.com/notebook/2005/01/12/clarification/#comment-6187</link>
		<dc:creator>Kristy Ulrich</dc:creator>
		<pubDate>Fri, 11 Feb 2005 21:53:25 +0000</pubDate>
		<guid isPermaLink="false">http://www.simplebits.com/wp/notebook/2005/01/12/clarification/#comment-6187</guid>
		<description>As a designer working on a Mac in an office that is all PC, I find making sites work on many different browsers a challenge.
I just recently (last few months) began using and learning CSS in all the sites I develop.  The last few days I&#039;ve run into my first major glitches and they were on IE6 on PC.
I generally end up making the sites I do display properly on IE for PCs even if I lose some of the graphical aspects that looked better on my iMac.
A site I&#039;ve begun developing in my offtime (&lt;a href=&quot;http://www.kaylashay.com&quot; rel=&quot;nofollow&quot;&gt;kaylashay.com&lt;/a&gt;) and using it as a playground of sorts for trying new things looked wonderful on Safari on my Mac until I saw it on a PC at work. Now I am upset to have to lose that feel to make it work on the PC, but oh well.
</description>
		<content:encoded><![CDATA[<p>As a designer working on a Mac in an office that is all PC, I find making sites work on many different browsers a challenge.<br />
I just recently (last few months) began using and learning CSS in all the sites I develop.  The last few days I&#8217;ve run into my first major glitches and they were on IE6 on PC.<br />
I generally end up making the sites I do display properly on IE for PCs even if I lose some of the graphical aspects that looked better on my iMac.<br />
A site I&#8217;ve begun developing in my offtime (<a href="http://www.kaylashay.com" rel="nofollow">kaylashay.com</a>) and using it as a playground of sorts for trying new things looked wonderful on Safari on my Mac until I saw it on a PC at work. Now I am upset to have to lose that feel to make it work on the PC, but oh well.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Creford</title>
		<link>http://simplebits.com/notebook/2005/01/12/clarification/#comment-6186</link>
		<dc:creator>Creford</dc:creator>
		<pubDate>Sun, 06 Feb 2005 20:49:11 +0000</pubDate>
		<guid isPermaLink="false">http://www.simplebits.com/wp/notebook/2005/01/12/clarification/#comment-6186</guid>
		<description>I often use the Firefox to check on the compatibility of my website.
I think it&#039;s necessary.
</description>
		<content:encoded><![CDATA[<p>I often use the Firefox to check on the compatibility of my website.<br />
I think it&#8217;s necessary.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Skinner</title>
		<link>http://simplebits.com/notebook/2005/01/12/clarification/#comment-6185</link>
		<dc:creator>Skinner</dc:creator>
		<pubDate>Sun, 06 Feb 2005 16:39:56 +0000</pubDate>
		<guid isPermaLink="false">http://www.simplebits.com/wp/notebook/2005/01/12/clarification/#comment-6185</guid>
		<description>IE 5 came as standard with Win 2000 too though, Nikolai Bailey.
I use Opera (because it&#039;s the best), but I refuse to update the exsisting IE on my computer because it takes up far too much space for something I don&#039;t use more than once a month.
</description>
		<content:encoded><![CDATA[<p>IE 5 came as standard with Win 2000 too though, Nikolai Bailey.<br />
I use Opera (because it&#8217;s the best), but I refuse to update the exsisting IE on my computer because it takes up far too much space for something I don&#8217;t use more than once a month.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: BD</title>
		<link>http://simplebits.com/notebook/2005/01/12/clarification/#comment-6184</link>
		<dc:creator>BD</dc:creator>
		<pubDate>Thu, 03 Feb 2005 09:28:49 +0000</pubDate>
		<guid isPermaLink="false">http://www.simplebits.com/wp/notebook/2005/01/12/clarification/#comment-6184</guid>
		<description>I am almost at the point myself of just serving up plain-vanilla (X)HTML to any version of IE. I have wasted so much of my good time, both now and in the &quot;hey-day&quot; of my FrontPage clients, that I am seriously considering dropping support for IE altogether on my web site. I no longer accept projects that require any Microsoft .NET crap, since it only really runs right using IE (go figure?), and I inform all of my clients to &lt;a href=&quot;http://getfirefox.com/&quot; title=&quot;external: GetFirefox.com&quot; rel=&quot;nofollow&quot;&gt;make the switch&lt;/a&gt;.
Thanks Dan for a great web site and I look forward to reading your book. After years of trying to punch my monitor in the eye, it will be refreshing to learn a different approach. :)
</description>
		<content:encoded><![CDATA[<p>I am almost at the point myself of just serving up plain-vanilla (X)HTML to any version of IE. I have wasted so much of my good time, both now and in the &#8220;hey-day&#8221; of my FrontPage clients, that I am seriously considering dropping support for IE altogether on my web site. I no longer accept projects that require any Microsoft .NET crap, since it only really runs right using IE (go figure?), and I inform all of my clients to <a href="http://getfirefox.com/" title="external: GetFirefox.com" rel="nofollow">make the switch</a>.<br />
Thanks Dan for a great web site and I look forward to reading your book. After years of trying to punch my monitor in the eye, it will be refreshing to learn a different approach. :)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: mitchell</title>
		<link>http://simplebits.com/notebook/2005/01/12/clarification/#comment-6183</link>
		<dc:creator>mitchell</dc:creator>
		<pubDate>Sat, 29 Jan 2005 10:26:03 +0000</pubDate>
		<guid isPermaLink="false">http://www.simplebits.com/wp/notebook/2005/01/12/clarification/#comment-6183</guid>
		<description>First of all, great web site!....one of the best Ive seen in terms of clean colorful design, XHTML, CSS, and font control. A real inspiration to me personally!
Second, I think that XHTML has answered everyones questions by default, in terms of whether or not to support IE 5 for PC, for MAC, designing for other agents, and &quot;graceful degradation&quot; of your web sites in general using. What you will find, if you move to XHTML and separate out your presentation from the markup using CSS, is it naturally does a pretty decent job delivering usable content to older agents! Its the style sheets that stir up trouble. Ive found that a simple strategy of import and link tricks which blocks most styles from older agents and delivers advanced layout style sheets only to say, version 6 and greater browsers, means they get your fancy web designs, and the older ones get what I call &quot;linearized content&quot;, or plain text pages, which is what plain xhtml and all those divs become when you disconnect css from those pages. In other words, you can design a style strategy where you send say MAC IE 5 and IE3-5 for PC and Netscape 4 series plain markup without styles or minimal styles, and even though it doesnt make your web site look the same as the newer browsers, its &quot;usable&quot; and &quot;readable&quot; and &quot;accessible&quot; by that tiny percentage of people out there in a simple linear text-reader format. The same applies for addressing most mobile devices as well, many of which still,, like Pocket PC 2002 version, dont support linked styles anyway. The newer ones support everything. But XHTML can send this diverse group &quot;digestible&quot; text-based html content, if you use it wisely.
Thats the whole point of moving to XHTML....it almost takes care of the problem of content delivery and cross-browser issues, for you. Why? Because XHTML is seen as HTML in the older browsers and so comes with some default formatting in all browsers...its essentially the same element set as HTML. So it will allow you to reach say 99.9% of users, if you are creative with how you deliver CSS and who gets which styles. All the many CSS hacks out there in cyberland will help you with that. And as for IE 5-5.5 representing 4% of the market currently, thats also what my logs show....but that is still a good sized demographic that can still see your site. There is only a handful of issues with that agent however, and they can be fixed in CSS so it can and should get your full CSS design. Its not hard to fix those bugs. Just keep in mind, if you do decide to ignore style modifications for say IE 5, you can use a style strick to send it plain xhtml without styles. However, what will you do when IE 7 arrives? You still will need to support IE 6 and its &quot;quirks&quot; for some years to come as well, as it will die the same slow death as version 5. Did you know that IE 6 drops into IE 5 mode or quirks mode when you dont put in a valid doctype? So,thats why, understanding XHTML, your CSS sheets, the browsers quirks, and accessibility now, and delivering the right mix, you can now and in the future give everyone usable content. Excluding anyone is not a good excuse.
The whole premise behind moving to XHTML is inclusion! If you design your xhtml markup well, and content and structure well, most of those issues will resolve themselves and when you test your site with a text-based agent like Lynx, or even Netscape 2.0, you may be suprised at how well your content reads in those simple agents, even if they are less than 1% of users in your servers log files.
</description>
		<content:encoded><![CDATA[<p>First of all, great web site!&#8230;.one of the best Ive seen in terms of clean colorful design, XHTML, CSS, and font control. A real inspiration to me personally!<br />
Second, I think that XHTML has answered everyones questions by default, in terms of whether or not to support IE 5 for PC, for MAC, designing for other agents, and &#8220;graceful degradation&#8221; of your web sites in general using. What you will find, if you move to XHTML and separate out your presentation from the markup using CSS, is it naturally does a pretty decent job delivering usable content to older agents! Its the style sheets that stir up trouble. Ive found that a simple strategy of import and link tricks which blocks most styles from older agents and delivers advanced layout style sheets only to say, version 6 and greater browsers, means they get your fancy web designs, and the older ones get what I call &#8220;linearized content&#8221;, or plain text pages, which is what plain xhtml and all those divs become when you disconnect css from those pages. In other words, you can design a style strategy where you send say MAC IE 5 and IE3-5 for PC and Netscape 4 series plain markup without styles or minimal styles, and even though it doesnt make your web site look the same as the newer browsers, its &#8220;usable&#8221; and &#8220;readable&#8221; and &#8220;accessible&#8221; by that tiny percentage of people out there in a simple linear text-reader format. The same applies for addressing most mobile devices as well, many of which still,, like Pocket PC 2002 version, dont support linked styles anyway. The newer ones support everything. But XHTML can send this diverse group &#8220;digestible&#8221; text-based html content, if you use it wisely.<br />
Thats the whole point of moving to XHTML&#8230;.it almost takes care of the problem of content delivery and cross-browser issues, for you. Why? Because XHTML is seen as HTML in the older browsers and so comes with some default formatting in all browsers&#8230;its essentially the same element set as HTML. So it will allow you to reach say 99.9% of users, if you are creative with how you deliver CSS and who gets which styles. All the many CSS hacks out there in cyberland will help you with that. And as for IE 5-5.5 representing 4% of the market currently, thats also what my logs show&#8230;.but that is still a good sized demographic that can still see your site. There is only a handful of issues with that agent however, and they can be fixed in CSS so it can and should get your full CSS design. Its not hard to fix those bugs. Just keep in mind, if you do decide to ignore style modifications for say IE 5, you can use a style strick to send it plain xhtml without styles. However, what will you do when IE 7 arrives? You still will need to support IE 6 and its &#8220;quirks&#8221; for some years to come as well, as it will die the same slow death as version 5. Did you know that IE 6 drops into IE 5 mode or quirks mode when you dont put in a valid doctype? So,thats why, understanding XHTML, your CSS sheets, the browsers quirks, and accessibility now, and delivering the right mix, you can now and in the future give everyone usable content. Excluding anyone is not a good excuse.<br />
The whole premise behind moving to XHTML is inclusion! If you design your xhtml markup well, and content and structure well, most of those issues will resolve themselves and when you test your site with a text-based agent like Lynx, or even Netscape 2.0, you may be suprised at how well your content reads in those simple agents, even if they are less than 1% of users in your servers log files.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Sylvia Anderson</title>
		<link>http://simplebits.com/notebook/2005/01/12/clarification/#comment-6182</link>
		<dc:creator>Sylvia Anderson</dc:creator>
		<pubDate>Tue, 25 Jan 2005 15:23:55 +0000</pubDate>
		<guid isPermaLink="false">http://www.simplebits.com/wp/notebook/2005/01/12/clarification/#comment-6182</guid>
		<description>F-i-r-e-f-o-x.
I&#039;m loooooving it. :-)
</description>
		<content:encoded><![CDATA[<p>F-i-r-e-f-o-x.<br />
I&#8217;m loooooving it. :-)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Anonymous</title>
		<link>http://simplebits.com/notebook/2005/01/12/clarification/#comment-6181</link>
		<dc:creator>Anonymous</dc:creator>
		<pubDate>Fri, 21 Jan 2005 14:03:22 +0000</pubDate>
		<guid isPermaLink="false">http://www.simplebits.com/wp/notebook/2005/01/12/clarification/#comment-6181</guid>
		<description>&lt;em&gt;Should we forget about $432 million just to be lazy? No, of course not.&lt;/em&gt;
MS has $60 billion cash, why would I fix IE5 quircks for them? I wonder who is lazy...
</description>
		<content:encoded><![CDATA[<p><em>Should we forget about $432 million just to be lazy? No, of course not.</em><br />
MS has $60 billion cash, why would I fix IE5 quircks for them? I wonder who is lazy&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tony</title>
		<link>http://simplebits.com/notebook/2005/01/12/clarification/#comment-6180</link>
		<dc:creator>Tony</dc:creator>
		<pubDate>Fri, 21 Jan 2005 07:20:58 +0000</pubDate>
		<guid isPermaLink="false">http://www.simplebits.com/wp/notebook/2005/01/12/clarification/#comment-6180</guid>
		<description>Ellen said:
&quot;With MS discontinuing all support for MacIE later this year, we Mac types will all be on Firefox anyways, so the IE obsolescence issue will become moot - but the marginalization one won’t, necessarily.&quot;
That will be interesting, just don&#039;t forget that Safari is there too.
I work as technical support for an ISP, and frankly we don&#039;t provide support for any product no longer supported by Microsoft. At the same time, we only provide browser support for Internet Explorer. If IE fails we refer them to OEM and suggest they install an alterntate browser in the meantime.
I don&#039;t get many calls with people using Macs, maybe 3 or 4 per week, so it really makes me wonder how the policy is going to change for Mac users.
Another note I would like to make isn&#039;t necessarily about IE versions, but IE cypher strength. If the browser doesn&#039;t have a mimumum of 128 bit cypher encryption support ends and we request they upgrade their IE. This is especially important for web designs over a secure server. Just something else to consider when deciding if that 3 or 4% is worth developing for.
However, I agree with most of you, I&#039;m not a novice at CSS, but I&#039;m not an expert either. If my client requests development for all browsers, then so be it. otherwise I&#039;ll let it degrade, sometimes not quite so gracefully.
</description>
		<content:encoded><![CDATA[<p>Ellen said:<br />
&#8220;With MS discontinuing all support for MacIE later this year, we Mac types will all be on Firefox anyways, so the IE obsolescence issue will become moot &#8211; but the marginalization one won’t, necessarily.&#8221;<br />
That will be interesting, just don&#8217;t forget that Safari is there too.<br />
I work as technical support for an ISP, and frankly we don&#8217;t provide support for any product no longer supported by Microsoft. At the same time, we only provide browser support for Internet Explorer. If IE fails we refer them to OEM and suggest they install an alterntate browser in the meantime.<br />
I don&#8217;t get many calls with people using Macs, maybe 3 or 4 per week, so it really makes me wonder how the policy is going to change for Mac users.<br />
Another note I would like to make isn&#8217;t necessarily about IE versions, but IE cypher strength. If the browser doesn&#8217;t have a mimumum of 128 bit cypher encryption support ends and we request they upgrade their IE. This is especially important for web designs over a secure server. Just something else to consider when deciding if that 3 or 4% is worth developing for.<br />
However, I agree with most of you, I&#8217;m not a novice at CSS, but I&#8217;m not an expert either. If my client requests development for all browsers, then so be it. otherwise I&#8217;ll let it degrade, sometimes not quite so gracefully.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ellen</title>
		<link>http://simplebits.com/notebook/2005/01/12/clarification/#comment-6179</link>
		<dc:creator>Ellen</dc:creator>
		<pubDate>Wed, 19 Jan 2005 02:11:47 +0000</pubDate>
		<guid isPermaLink="false">http://www.simplebits.com/wp/notebook/2005/01/12/clarification/#comment-6179</guid>
		<description>An important factor that one should probably take into account when mulling over all these flat access stats (.6% MacIE, etc) is the actual &lt;em&gt;distribution&lt;/em&gt; of browser types per capita of browser users.
As an academic, for instance, my community accounts for an easy .6 of that .6% - but given our educational and economic demographic, we may well account for many times that % of actual  patronage of internet services/resources.
Obsolescence versus marginalization are two different dilemmas that seem to get conflated pretty often.  With MS discontinuing all support for MacIE later this year, we Mac types will all be on Firefox anyways, so the IE obsolescence issue will become moot - but the marginalization one won&#039;t, necessarily.  A zillionaire or influential visitor using Netscape 4 (or IE5) is a much less likely scenario than a desirable up-to-date target community simply using a non-Windows-based browser.
If anyone knows of any crushingly relevant market studies on browser types &amp; market demographics, I&#039;d be intrigued to see what the breakdown looks like.
</description>
		<content:encoded><![CDATA[<p>An important factor that one should probably take into account when mulling over all these flat access stats (.6% MacIE, etc) is the actual <em>distribution</em> of browser types per capita of browser users.<br />
As an academic, for instance, my community accounts for an easy .6 of that .6% &#8211; but given our educational and economic demographic, we may well account for many times that % of actual  patronage of internet services/resources.<br />
Obsolescence versus marginalization are two different dilemmas that seem to get conflated pretty often.  With MS discontinuing all support for MacIE later this year, we Mac types will all be on Firefox anyways, so the IE obsolescence issue will become moot &#8211; but the marginalization one won&#8217;t, necessarily.  A zillionaire or influential visitor using Netscape 4 (or IE5) is a much less likely scenario than a desirable up-to-date target community simply using a non-Windows-based browser.<br />
If anyone knows of any crushingly relevant market studies on browser types &#038; market demographics, I&#8217;d be intrigued to see what the breakdown looks like.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: G. I.</title>
		<link>http://simplebits.com/notebook/2005/01/12/clarification/#comment-6178</link>
		<dc:creator>G. I.</dc:creator>
		<pubDate>Sun, 16 Jan 2005 20:15:37 +0000</pubDate>
		<guid isPermaLink="false">http://www.simplebits.com/wp/notebook/2005/01/12/clarification/#comment-6178</guid>
		<description>OT: Nick Toye, your website&#039;s background color hasn&#039;t been set, so in my browser it&#039;s light gray, because I&#039;ve changed the default white. I guess you&#039;d like to show it white for everyone, wouldn&#039;t ya? :o)
</description>
		<content:encoded><![CDATA[<p>OT: Nick Toye, your website&#8217;s background color hasn&#8217;t been set, so in my browser it&#8217;s light gray, because I&#8217;ve changed the default white. I guess you&#8217;d like to show it white for everyone, wouldn&#8217;t ya? :o)</p>
]]></content:encoded>
	</item>
</channel>
</rss>

