<?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: Seriously, let&#8217;s make fonts not suck!</title>
	<atom:link href="http://abock.org/2007/02/01/seriously-lets-make-fonts-not-suck/feed/" rel="self" type="application/rss+xml" />
	<link>http://abock.org/2007/02/01/seriously-lets-make-fonts-not-suck/</link>
	<description></description>
	<lastBuildDate>Sun, 07 Mar 2010 08:30:50 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Randy Kramer</title>
		<link>http://abock.org/2007/02/01/seriously-lets-make-fonts-not-suck/comment-page-1/#comment-36739</link>
		<dc:creator>Randy Kramer</dc:creator>
		<pubDate>Wed, 07 Feb 2007 15:51:30 +0000</pubDate>
		<guid isPermaLink="false">http://abock.org/2007/02/01/seriously-lets-make-fonts-not-suck/#comment-36739</guid>
		<description>This may be just a little OT, but I hope that font size in points always reflects the (standard) size when printed on paper.

And, as I think somebody else mentioned, many of us have a reasonable feel for the size of a 12 point font on paper.

To state it another way, I want to choose my font sizes (in documents/applications I might print) to create &quot;standard&quot; type sizes when printed.  Then, if I need to, I might magnify (zoom) in or out to get easily readable sizes on the display.

Like I (almost) said, I&#039;m not sure anybody is advocating anything different.  (I guess, among other things, this means I support the poster who suggested that point sizes be shown on the font style/size selector.</description>
		<content:encoded><![CDATA[<p>This may be just a little OT, but I hope that font size in points always reflects the (standard) size when printed on paper.</p>
<p>And, as I think somebody else mentioned, many of us have a reasonable feel for the size of a 12 point font on paper.</p>
<p>To state it another way, I want to choose my font sizes (in documents/applications I might print) to create &#8220;standard&#8221; type sizes when printed.  Then, if I need to, I might magnify (zoom) in or out to get easily readable sizes on the display.</p>
<p>Like I (almost) said, I&#8217;m not sure anybody is advocating anything different.  (I guess, among other things, this means I support the poster who suggested that point sizes be shown on the font style/size selector.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tamara</title>
		<link>http://abock.org/2007/02/01/seriously-lets-make-fonts-not-suck/comment-page-1/#comment-35905</link>
		<dc:creator>Tamara</dc:creator>
		<pubDate>Sun, 04 Feb 2007 23:24:19 +0000</pubDate>
		<guid isPermaLink="false">http://abock.org/2007/02/01/seriously-lets-make-fonts-not-suck/#comment-35905</guid>
		<description>Well, I&#039;m in favor of OO for desktop applications, C is harder to maintain than C#.

Here are some numbers for my aging system (PII 300, 64Mb ram*):

This is my low-tech test of the differences between C and C# as it pertains to this prototype.  Differences in the program should be minimal, as they are of relative complexity.  Of most concern is how long it takes for Mono to start up and how much memory it takes.  I simply used &#039;time&#039; (&quot;real time&quot;) and hit Alt-F4 as soon as I saw the window finish displaying.

Aaron: 3.5-5.0s / 14,120kb rss
Mathias: 1.5-2.0s / 7,612kb rss

on a Intel Celeron D 346 (3GHz) with 512mb, i got these results (running over ssh on a home network):

Aaron:  1,1-1.4s / 16,000kb rss
Mathias: 1.0-1.2s / 10,244kb rss

* - Currently running XFCE4, not Gnome.

So, it&#039;s fair to say that the C# prototype takes twice as long to load and twice the RAM on the older computer but only slightly longer (</description>
		<content:encoded><![CDATA[<p>Well, I&#8217;m in favor of OO for desktop applications, C is harder to maintain than C#.</p>
<p>Here are some numbers for my aging system (PII 300, 64Mb ram*):</p>
<p>This is my low-tech test of the differences between C and C# as it pertains to this prototype.  Differences in the program should be minimal, as they are of relative complexity.  Of most concern is how long it takes for Mono to start up and how much memory it takes.  I simply used &#8216;time&#8217; (&#8220;real time&#8221;) and hit Alt-F4 as soon as I saw the window finish displaying.</p>
<p>Aaron: 3.5-5.0s / 14,120kb rss<br />
Mathias: 1.5-2.0s / 7,612kb rss</p>
<p>on a Intel Celeron D 346 (3GHz) with 512mb, i got these results (running over ssh on a home network):</p>
<p>Aaron:  1,1-1.4s / 16,000kb rss<br />
Mathias: 1.0-1.2s / 10,244kb rss</p>
<p>* &#8211; Currently running XFCE4, not Gnome.</p>
<p>So, it&#8217;s fair to say that the C# prototype takes twice as long to load and twice the RAM on the older computer but only slightly longer (</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: drÃ©</title>
		<link>http://abock.org/2007/02/01/seriously-lets-make-fonts-not-suck/comment-page-1/#comment-35796</link>
		<dc:creator>drÃ©</dc:creator>
		<pubDate>Sun, 04 Feb 2007 11:08:30 +0000</pubDate>
		<guid isPermaLink="false">http://abock.org/2007/02/01/seriously-lets-make-fonts-not-suck/#comment-35796</guid>
		<description>@Ho Chi Minh: The first mock just shows small/large while the second shows the aczual size. Please see Sven Neumann&#039;s comment [1] why showing the size could make sense.

Furher discussion should better happen on bugzilla instad of hijacking abock&#039;s blog.

[1] http://bugzilla.gnome.org/show_bug.cgi?id=378338#c16</description>
		<content:encoded><![CDATA[<p>@Ho Chi Minh: The first mock just shows small/large while the second shows the aczual size. Please see Sven Neumann&#8217;s comment [1] why showing the size could make sense.</p>
<p>Furher discussion should better happen on bugzilla instad of hijacking abock&#8217;s blog.</p>
<p>[1] <a href="http://bugzilla.gnome.org/show_bug.cgi?id=378338#c16" rel="nofollow">http://bugzilla.gnome.org/show_bug.cgi?id=378338#c16</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Vytas</title>
		<link>http://abock.org/2007/02/01/seriously-lets-make-fonts-not-suck/comment-page-1/#comment-35578</link>
		<dc:creator>Vytas</dc:creator>
		<pubDate>Sat, 03 Feb 2007 18:55:48 +0000</pubDate>
		<guid isPermaLink="false">http://abock.org/2007/02/01/seriously-lets-make-fonts-not-suck/#comment-35578</guid>
		<description>@ken: if those units are inaccurate, lets make them pixels, milimeters or whatever, but leave them in the dialog somewhere</description>
		<content:encoded><![CDATA[<p>@ken: if those units are inaccurate, lets make them pixels, milimeters or whatever, but leave them in the dialog somewhere</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ho Chi Minh</title>
		<link>http://abock.org/2007/02/01/seriously-lets-make-fonts-not-suck/comment-page-1/#comment-35340</link>
		<dc:creator>Ho Chi Minh</dc:creator>
		<pubDate>Sat, 03 Feb 2007 02:41:10 +0000</pubDate>
		<guid isPermaLink="false">http://abock.org/2007/02/01/seriously-lets-make-fonts-not-suck/#comment-35340</guid>
		<description>@dre: I love your mockup, it looks simpler and more supportive for disabled users. I am just wondering if we should users know the size of the font?</description>
		<content:encoded><![CDATA[<p>@dre: I love your mockup, it looks simpler and more supportive for disabled users. I am just wondering if we should users know the size of the font?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: ken</title>
		<link>http://abock.org/2007/02/01/seriously-lets-make-fonts-not-suck/comment-page-1/#comment-35300</link>
		<dc:creator>ken</dc:creator>
		<pubDate>Fri, 02 Feb 2007 22:21:34 +0000</pubDate>
		<guid isPermaLink="false">http://abock.org/2007/02/01/seriously-lets-make-fonts-not-suck/#comment-35300</guid>
		<description>I guess &quot;without a precise correspondence with reality&quot; is the new euphamism for &quot;wrong&quot;.  :-)

I am a bit confused by the claim that numbers don&#039;t force you to guess, but showing the actual size does.</description>
		<content:encoded><![CDATA[<p>I guess &#8220;without a precise correspondence with reality&#8221; is the new euphamism for &#8220;wrong&#8221;.  <img src='http://abock.org/wp-includes/images/smilies/face-smile.png' alt=':-)' class='wp-smiley' /><br />
I am a bit confused by the claim that numbers don&#8217;t force you to guess, but showing the actual size does.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: yosch</title>
		<link>http://abock.org/2007/02/01/seriously-lets-make-fonts-not-suck/comment-page-1/#comment-35202</link>
		<dc:creator>yosch</dc:creator>
		<pubDate>Fri, 02 Feb 2007 13:20:16 +0000</pubDate>
		<guid isPermaLink="false">http://abock.org/2007/02/01/seriously-lets-make-fonts-not-suck/#comment-35202</guid>
		<description>very cool work :-)

You might want to take a look at this fontManagement spec for more ideas https://wiki.ubuntu.com/FontManagement. 

This wiki entry has some more ideas and links:
http://live.gnome.org/fonts</description>
		<content:encoded><![CDATA[<p>very cool work <img src='http://abock.org/wp-includes/images/smilies/face-smile.png' alt=':-)' class='wp-smiley' /><br />
You might want to take a look at this fontManagement spec for more ideas <a href="https://wiki.ubuntu.com/FontManagement" rel="nofollow">https://wiki.ubuntu.com/FontManagement</a>. </p>
<p>This wiki entry has some more ideas and links:<br />
<a href="http://live.gnome.org/fonts" rel="nofollow">http://live.gnome.org/fonts</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: P</title>
		<link>http://abock.org/2007/02/01/seriously-lets-make-fonts-not-suck/comment-page-1/#comment-35163</link>
		<dc:creator>P</dc:creator>
		<pubDate>Fri, 02 Feb 2007 10:42:06 +0000</pubDate>
		<guid isPermaLink="false">http://abock.org/2007/02/01/seriously-lets-make-fonts-not-suck/#comment-35163</guid>
		<description>Just a usability engineering remark: Plus (positive) is always to the right and to the top, minus (negative) is to the left or to the bottom. At least in most parts of the word, except maybe right-to-left countries.

Anyways, nice mockup and a good idea Aaron!

P</description>
		<content:encoded><![CDATA[<p>Just a usability engineering remark: Plus (positive) is always to the right and to the top, minus (negative) is to the left or to the bottom. At least in most parts of the word, except maybe right-to-left countries.</p>
<p>Anyways, nice mockup and a good idea Aaron!</p>
<p>P</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Hongli Lai</title>
		<link>http://abock.org/2007/02/01/seriously-lets-make-fonts-not-suck/comment-page-1/#comment-35127</link>
		<dc:creator>Hongli Lai</dc:creator>
		<pubDate>Fri, 02 Feb 2007 08:31:28 +0000</pubDate>
		<guid isPermaLink="false">http://abock.org/2007/02/01/seriously-lets-make-fonts-not-suck/#comment-35127</guid>
		<description>Since the   and - buttons are only for increasing and decreasing the font sizes, why not put font sizes, in increasing order, in a list box with *scroll bars*? I think that&#039;s a lot more consistent with the rest of the system.

The   and - buttons look a bit weird imo, but if you use a scrollbar then it should be clear that you&#039;re able to choose from many choices.</description>
		<content:encoded><![CDATA[<p>Since the   and &#8211; buttons are only for increasing and decreasing the font sizes, why not put font sizes, in increasing order, in a list box with *scroll bars*? I think that&#8217;s a lot more consistent with the rest of the system.</p>
<p>The   and &#8211; buttons look a bit weird imo, but if you use a scrollbar then it should be clear that you&#8217;re able to choose from many choices.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: drÃ©</title>
		<link>http://abock.org/2007/02/01/seriously-lets-make-fonts-not-suck/comment-page-1/#comment-35121</link>
		<dc:creator>drÃ©</dc:creator>
		<pubDate>Fri, 02 Feb 2007 08:05:16 +0000</pubDate>
		<guid isPermaLink="false">http://abock.org/2007/02/01/seriously-lets-make-fonts-not-suck/#comment-35121</guid>
		<description>Please check the two mockups I have made: first attempt[1] and another one with fonts size displayed[2]. Suggestions welcome!

Thanks,
drÃ©

[1] http://bugzilla.gnome.org/attachment.cgi?id=81709
[2] http://bugzilla.gnome.org/attachment.cgi?id=81711</description>
		<content:encoded><![CDATA[<p>Please check the two mockups I have made: first attempt[1] and another one with fonts size displayed[2]. Suggestions welcome!</p>
<p>Thanks,<br />
drÃ©</p>
<p>[1] <a href="http://bugzilla.gnome.org/attachment.cgi?id=81709" rel="nofollow">http://bugzilla.gnome.org/attachment.cgi?id=81709</a><br />
[2] <a href="http://bugzilla.gnome.org/attachment.cgi?id=81711" rel="nofollow">http://bugzilla.gnome.org/attachment.cgi?id=81711</a></p>
]]></content:encoded>
	</item>
</channel>
</rss>
