<?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: Site</title>
	<atom:link href="http://climbtothestars.org/archives/2001/07/10/site/feed/" rel="self" type="application/rss+xml" />
	<link>http://climbtothestars.org/archives/2001/07/10/site/</link>
	<description>Stephanie Booth's online ramblings.</description>
	<pubDate>Mon, 01 Dec 2008 20:28:00 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.1</generator>
		<item>
		<title>By: sniffles</title>
		<link>http://climbtothestars.org/archives/2001/07/10/site/#comment-430395</link>
		<dc:creator>sniffles</dc:creator>
		<pubDate>Tue, 17 Jul 2001 08:41:00 +0000</pubDate>
		<guid isPermaLink="false">http://climbtothestars.org/archives/2001/07/10/site/#comment-430395</guid>
		<description>&lt;p&gt;Why do I get the feeling the guy who wrote that article is a Mac user :)&lt;br&gt;  &lt;br&gt; I use pt rather than px for accessibility reasons, which the article &lt;br&gt;outlines. I think  it is saying that if you want to create print-perfect &lt;br&gt;kind of designs, px is the go.&lt;br&gt; &lt;a href="http://alistapart.com/stories/fear4/3.html"&gt;http://alistapart.com/stories/fear4/3.html&lt;/a&gt;&lt;br&gt; Running in px, do you have complaints from users of different &lt;br&gt;resolutions? I&#39;ve just found that using pt, resolution isn&#39;t a problem so &lt;br&gt;much (because it shouldn&#39;t be). And with px there is the issue that &lt;br&gt;printers understand pixels differently from screen. I don&#39;t know the &lt;br&gt;extent of support for media="print". (someone else might?) &lt;br&gt; I was also in a corporate environment where NS4 was the standard - in pt, &lt;br&gt;you can easily adjust change the size of the font as it appears within &lt;br&gt;your browser (Ctrl+[ and Ctrl+]), not so in px. I later discovered that &lt;br&gt;this is the contrary in IE 5, &lt;em&gt;and&lt;/em&gt; it isn&#39;t particularly obvious how this &lt;br&gt;&#39;accessibility&#39; feature can be used. Bleh.&lt;br&gt; Sorry I&#39;m not much help :)&lt;/p&gt;</description>
		<content:encoded><![CDATA[<p>Why do I get the feeling the guy who wrote that article is a Mac user <img src='http://climbtothestars.org/wp/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
<p> I use pt rather than px for accessibility reasons, which the article <br />outlines. I think  it is saying that if you want to create print-perfect <br />kind of designs, px is the go.<br /> <a href="http://alistapart.com/stories/fear4/3.html">http://alistapart.com/stories/fear4/3.html</a><br /> Running in px, do you have complaints from users of different <br />resolutions? I&#39;ve just found that using pt, resolution isn&#39;t a problem so <br />much (because it shouldn&#39;t be). And with px there is the issue that <br />printers understand pixels differently from screen. I don&#39;t know the <br />extent of support for media=&#8221;print&#8221;. (someone else might?) <br /> I was also in a corporate environment where NS4 was the standard - in pt, <br />you can easily adjust change the size of the font as it appears within <br />your browser (Ctrl+[ and Ctrl+]), not so in px. I later discovered that <br />this is the contrary in IE 5, <em>and</em> it isn&#39;t particularly obvious how this <br />&#39;accessibility&#39; feature can be used. Bleh.<br /> Sorry I&#39;m not much help <img src='http://climbtothestars.org/wp/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tara</title>
		<link>http://climbtothestars.org/archives/2001/07/10/site/#comment-430394</link>
		<dc:creator>Tara</dc:creator>
		<pubDate>Mon, 16 Jul 2001 16:17:00 +0000</pubDate>
		<guid isPermaLink="false">http://climbtothestars.org/archives/2001/07/10/site/#comment-430394</guid>
		<description>&lt;p&gt;Does this mean that in your experience, pt is more "stable" than px??&lt;br&gt; &lt;em&gt;confused&lt;/em&gt;: &lt;a href="http://alistapart.com/stories/fear4/"&gt;http://alistapart.com/stories/fear4/&lt;/a&gt;&lt;/p&gt;</description>
		<content:encoded><![CDATA[<p>Does this mean that in your experience, pt is more &#8220;stable&#8221; than px??<br /> <em>confused</em>: <a href="http://alistapart.com/stories/fear4/">http://alistapart.com/stories/fear4/</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: sniffles</title>
		<link>http://climbtothestars.org/archives/2001/07/10/site/#comment-430393</link>
		<dc:creator>sniffles</dc:creator>
		<pubDate>Mon, 16 Jul 2001 09:35:00 +0000</pubDate>
		<guid isPermaLink="false">http://climbtothestars.org/archives/2001/07/10/site/#comment-430393</guid>
		<description>&lt;p&gt;eew. that didn&#39;t work. &lt;br&gt;  &lt;br&gt; That was supposed to have said:&lt;br&gt;  &lt;br&gt; I&#39;ve stuck to using pt&#39;s for now, because it seems a lesser sin than &lt;br&gt;using px&#39;s &#60;-- this could present problems with printing.&lt;br&gt;  &lt;br&gt; Bring on CSS3. And the browsers which support it, of course. :)&lt;/p&gt;</description>
		<content:encoded><![CDATA[<p>eew. that didn&#39;t work. </p>
<p> That was supposed to have said:</p>
<p> I&#39;ve stuck to using pt&#39;s for now, because it seems a lesser sin than <br />using px&#39;s &lt;&#8211; this could present problems with printing.</p>
<p> Bring on CSS3. And the browsers which support it, of course. <img src='http://climbtothestars.org/wp/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: sniffles</title>
		<link>http://climbtothestars.org/archives/2001/07/10/site/#comment-430392</link>
		<dc:creator>sniffles</dc:creator>
		<pubDate>Mon, 16 Jul 2001 09:33:00 +0000</pubDate>
		<guid isPermaLink="false">http://climbtothestars.org/archives/2001/07/10/site/#comment-430392</guid>
		<description>&lt;p&gt;My past experience with relative font sizes haven&#39;t been particularly &lt;br&gt;good.&lt;br&gt; Using x-small&#124;small&#124;large presents problems across platforms - fonts tend &lt;br&gt;to look too small on a Macs and unpredictable on Unix - and they may not &lt;br&gt;give you the granularity in different font sizes that you might need. &lt;br&gt; I&#39;ve stuck to using pt&#39;s for now, because it seems a lesser sin than &lt;br&gt;using px&#39;s&lt;/p&gt;</description>
		<content:encoded><![CDATA[<p>My past experience with relative font sizes haven&#39;t been particularly <br />good.<br /> Using x-small|small|large presents problems across platforms - fonts tend <br />to look too small on a Macs and unpredictable on Unix - and they may not <br />give you the granularity in different font sizes that you might need. <br /> I&#39;ve stuck to using pt&#39;s for now, because it seems a lesser sin than <br />using px&#39;s</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tara</title>
		<link>http://climbtothestars.org/archives/2001/07/10/site/#comment-430391</link>
		<dc:creator>Tara</dc:creator>
		<pubDate>Sat, 14 Jul 2001 08:31:00 +0000</pubDate>
		<guid isPermaLink="false">http://climbtothestars.org/archives/2001/07/10/site/#comment-430391</guid>
		<description>&lt;p&gt;Karl, I&#39;m not sure I get you, in fact. The text was unreadably small for &lt;br&gt;you when I specified it as 0.75 em (which I now understand, is a &lt;br&gt;ridiculous thing to do), but what about when I specified it as 13px? That &lt;br&gt;shouldn&#39;t be affected by the font size you have chosen as default in your &lt;br&gt;browser, should it?&lt;/p&gt;</description>
		<content:encoded><![CDATA[<p>Karl, I&#39;m not sure I get you, in fact. The text was unreadably small for <br />you when I specified it as 0.75 em (which I now understand, is a <br />ridiculous thing to do), but what about when I specified it as 13px? That <br />shouldn&#39;t be affected by the font size you have chosen as default in your <br />browser, should it?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: darren</title>
		<link>http://climbtothestars.org/archives/2001/07/10/site/#comment-430390</link>
		<dc:creator>darren</dc:creator>
		<pubDate>Sat, 14 Jul 2001 06:19:00 +0000</pubDate>
		<guid isPermaLink="false">http://climbtothestars.org/archives/2001/07/10/site/#comment-430390</guid>
		<description>&lt;p&gt;Do what I&#39;ve done, and simply use relative font sizes.. ie: font-size: &lt;br&gt;small&#124;x-small&#124;xx-small;  That way, it&#39;ll still be scalable, but you can &lt;br&gt;have things smaller as well.&lt;/p&gt;</description>
		<content:encoded><![CDATA[<p>Do what I&#39;ve done, and simply use relative font sizes.. ie: font-size: <br />small|x-small|xx-small;  That way, it&#39;ll still be scalable, but you can <br />have things smaller as well.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Stephanie</title>
		<link>http://climbtothestars.org/archives/2001/07/10/site/#comment-430389</link>
		<dc:creator>Stephanie</dc:creator>
		<pubDate>Thu, 12 Jul 2001 11:55:00 +0000</pubDate>
		<guid isPermaLink="false">http://climbtothestars.org/archives/2001/07/10/site/#comment-430389</guid>
		<description>&lt;p&gt;gah. what do I do now then?&lt;br&gt; &lt;em&gt;choke&lt;/em&gt;&lt;/p&gt;</description>
		<content:encoded><![CDATA[<p>gah. what do I do now then?<br /> <em>choke</em></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tara</title>
		<link>http://climbtothestars.org/archives/2001/07/10/site/#comment-430388</link>
		<dc:creator>Tara</dc:creator>
		<pubDate>Thu, 12 Jul 2001 06:55:00 +0000</pubDate>
		<guid isPermaLink="false">http://climbtothestars.org/archives/2001/07/10/site/#comment-430388</guid>
		<description>&lt;p&gt;gah. what do I do now then?&lt;br&gt; &lt;em&gt;choke&lt;/em&gt;&lt;/p&gt;</description>
		<content:encoded><![CDATA[<p>gah. what do I do now then?<br /> <em>choke</em></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Karl Dubost</title>
		<link>http://climbtothestars.org/archives/2001/07/10/site/#comment-430387</link>
		<dc:creator>Karl Dubost</dc:creator>
		<pubDate>Wed, 11 Jul 2001 21:16:00 +0000</pubDate>
		<guid isPermaLink="false">http://climbtothestars.org/archives/2001/07/10/site/#comment-430387</guid>
		<description>&lt;p&gt;this one is better... because before it was unreadable....&lt;br&gt; So we&#39;re faced to a problem. The problem is in fact people have different &lt;br&gt;font-size preferences in their own browser.&lt;br&gt; I decided myself, that defaut font-size in my browser is 10pt. So when &lt;br&gt;I&#39;m designing style sheets, I recommend to use 100% for the smallest font &lt;br&gt;in your page.&lt;br&gt; and gives in your stylesheet for others biggest size.&lt;br&gt; 100%  150% or 200%&lt;br&gt; but the minimum is 100%. For me if you give 80% or  95%, the font will &lt;br&gt;become unreadable on screen.&lt;br&gt; In the future (CSS3) there will be a possibility to specify, something &lt;br&gt;like&lt;br&gt;      80%, but with a lower limit of 10pt for example.&lt;/p&gt;</description>
		<content:encoded><![CDATA[<p>this one is better&#8230; because before it was unreadable&#8230;.<br /> So we&#39;re faced to a problem. The problem is in fact people have different <br />font-size preferences in their own browser.<br /> I decided myself, that defaut font-size in my browser is 10pt. So when <br />I&#39;m designing style sheets, I recommend to use 100% for the smallest font <br />in your page.<br /> and gives in your stylesheet for others biggest size.<br /> 100%  150% or 200%<br /> but the minimum is 100%. For me if you give 80% or  95%, the font will <br />become unreadable on screen.<br /> In the future (CSS3) there will be a possibility to specify, something <br />like<br />      80%, but with a lower limit of 10pt for example.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Lars</title>
		<link>http://climbtothestars.org/archives/2001/07/10/site/#comment-430386</link>
		<dc:creator>Lars</dc:creator>
		<pubDate>Wed, 11 Jul 2001 17:26:00 +0000</pubDate>
		<guid isPermaLink="false">http://climbtothestars.org/archives/2001/07/10/site/#comment-430386</guid>
		<description>&lt;p&gt;Hi Tara,&lt;br&gt; I prefer the pixel size you used to this one. This one&#39;s big - too big!&lt;br&gt; Lars!&lt;/p&gt;</description>
		<content:encoded><![CDATA[<p>Hi Tara,<br /> I prefer the pixel size you used to this one. This one&#39;s big - too big!<br /> Lars!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Baud</title>
		<link>http://climbtothestars.org/archives/2001/07/10/site/#comment-430385</link>
		<dc:creator>Baud</dc:creator>
		<pubDate>Wed, 11 Jul 2001 04:33:00 +0000</pubDate>
		<guid isPermaLink="false">http://climbtothestars.org/archives/2001/07/10/site/#comment-430385</guid>
		<description>&lt;p&gt;C&#39;est un peu grand pour mon 1024*768 (PC) &lt;br&gt; Le genre de taille de texte que je réserverais à  un titre ou à  un &lt;br&gt;intertitre pas au corps du texte. A vue de nez on dirait du corps 16 ou du &lt;br&gt;18. Je me trompe?&lt;/p&gt;</description>
		<content:encoded><![CDATA[<p>C&#39;est un peu grand pour mon 1024*768 (PC) <br /> Le genre de taille de texte que je réserverais à  un titre ou à  un <br />intertitre pas au corps du texte. A vue de nez on dirait du corps 16 ou du <br />18. Je me trompe?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Baud</title>
		<link>http://climbtothestars.org/archives/2001/07/10/site/#comment-228</link>
		<dc:creator>Baud</dc:creator>
		<pubDate>Tue, 30 Nov 1999 00:00:00 +0000</pubDate>
		<guid isPermaLink="false">http://climbtothestars.org/archives/2001/07/10/site/#comment-228</guid>
		<description>&lt;p&gt;C'est un peu grand pour mon 1024*768 (PC) 
 Le genre de taille de texte que je réserverais à  un titre ou à  un 
intertitre pas au corps du texte. A vue de nez on dirait du corps 16 ou du 
18. Je me trompe?&lt;/p&gt;</description>
		<content:encoded><![CDATA[<p>C&#8217;est un peu grand pour mon 1024*768 (PC)<br />
 Le genre de taille de texte que je réserverais à  un titre ou à  un<br />
intertitre pas au corps du texte. A vue de nez on dirait du corps 16 ou du<br />
18. Je me trompe?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Lars</title>
		<link>http://climbtothestars.org/archives/2001/07/10/site/#comment-229</link>
		<dc:creator>Lars</dc:creator>
		<pubDate>Tue, 30 Nov 1999 00:00:00 +0000</pubDate>
		<guid isPermaLink="false">http://climbtothestars.org/archives/2001/07/10/site/#comment-229</guid>
		<description>&lt;p&gt;Hi Tara,
 I prefer the pixel size you used to this one. This one's big - too big!
 Lars!&lt;/p&gt;</description>
		<content:encoded><![CDATA[<p>Hi Tara,<br />
 I prefer the pixel size you used to this one. This one&#8217;s big - too big!<br />
 Lars!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Karl Dubost</title>
		<link>http://climbtothestars.org/archives/2001/07/10/site/#comment-230</link>
		<dc:creator>Karl Dubost</dc:creator>
		<pubDate>Tue, 30 Nov 1999 00:00:00 +0000</pubDate>
		<guid isPermaLink="false">http://climbtothestars.org/archives/2001/07/10/site/#comment-230</guid>
		<description>&lt;p&gt;this one is better... because before it was unreadable....
 So we're faced to a problem. The problem is in fact people have different 
font-size preferences in their own browser.
 I decided myself, that defaut font-size in my browser is 10pt. So when 
I'm designing style sheets, I recommend to use 100% for the smallest font 
in your page.
 and gives in your stylesheet for others biggest size.
 100%  150% or 200%
 but the minimum is 100%. For me if you give 80% or  95%, the font will 
become unreadable on screen.
 In the future (CSS3) there will be a possibility to specify, something 
like
      80%, but with a lower limit of 10pt for example.&lt;/p&gt;</description>
		<content:encoded><![CDATA[<p>this one is better&#8230; because before it was unreadable&#8230;.<br />
 So we&#8217;re faced to a problem. The problem is in fact people have different<br />
font-size preferences in their own browser.<br />
 I decided myself, that defaut font-size in my browser is 10pt. So when<br />
I&#8217;m designing style sheets, I recommend to use 100% for the smallest font<br />
in your page.<br />
 and gives in your stylesheet for others biggest size.<br />
 100%  150% or 200%<br />
 but the minimum is 100%. For me if you give 80% or  95%, the font will<br />
become unreadable on screen.<br />
 In the future (CSS3) there will be a possibility to specify, something<br />
like<br />
      80%, but with a lower limit of 10pt for example.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tara</title>
		<link>http://climbtothestars.org/archives/2001/07/10/site/#comment-231</link>
		<dc:creator>Tara</dc:creator>
		<pubDate>Tue, 30 Nov 1999 00:00:00 +0000</pubDate>
		<guid isPermaLink="false">http://climbtothestars.org/archives/2001/07/10/site/#comment-231</guid>
		<description>&lt;p&gt;gah. what do I do now then?
 &lt;em&gt;choke&lt;/em&gt;&lt;/p&gt;</description>
		<content:encoded><![CDATA[<p>gah. what do I do now then?<br />
 <em>choke</em></p>
]]></content:encoded>
	</item>
</channel>
</rss>
