<?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: Matchiness!</title>
	<atom:link href="http://www.chocolateandgarlic.com/2009/03/i-match/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.chocolateandgarlic.com/2009/03/i-match/</link>
	<description>The Sweet, The Savory</description>
	<lastBuildDate>Thu, 09 Sep 2010 04:49:15 -0500</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Pmom</title>
		<link>http://www.chocolateandgarlic.com/2009/03/i-match/comment-page-1/#comment-396</link>
		<dc:creator>Pmom</dc:creator>
		<pubDate>Fri, 06 Mar 2009 05:07:46 +0000</pubDate>
		<guid isPermaLink="false">http://www.chocolateandgarlic.com/?p=1046#comment-396</guid>
		<description>Right.  The true problem is that one of my paid helpers (hosting service) installed the TTF fonts plugin (which I love, because it generates the fancy font for the titles). Another paid helper (design service) did my header and buttons, etc., in a font that I really liked.  In theory, that should have been great, because I could then upload that font to my TTF fonts plugin and I would then have the same great font everywhere on the site--excellent matchy-matchiness.  Unfortunately, the font my header and buttons were done in was not complete--it didn&#039;t include special characters like the ampersand (pretty important for a site named Chocolate &amp; Garlic), the question mark, and the exclamation mark (I find these essential for titles of posts, don&#039;t you?  This meant that that original font was a hopeless failure for use in conjunction with TTF titles.  I found a similar font to use with TTF titles, but I lacked the technical knowledge about how to redo the buttons and header (replacing the TTF failure font with the TTF compatible font) and then upload them to my site.  That&#039;s where Pdad came in.  He didn&#039;t know how to do it either, but as with all things computer related, he figured it out and saved the day!</description>
		<content:encoded><![CDATA[<p>Right.  The true problem is that one of my paid helpers (hosting service) installed the TTF fonts plugin (which I love, because it generates the fancy font for the titles). Another paid helper (design service) did my header and buttons, etc., in a font that I really liked.  In theory, that should have been great, because I could then upload that font to my TTF fonts plugin and I would then have the same great font everywhere on the site&#8211;excellent matchy-matchiness.  Unfortunately, the font my header and buttons were done in was not complete&#8211;it didn&#8217;t include special characters like the ampersand (pretty important for a site named Chocolate &#038; Garlic), the question mark, and the exclamation mark (I find these essential for titles of posts, don&#8217;t you?  This meant that that original font was a hopeless failure for use in conjunction with TTF titles.  I found a similar font to use with TTF titles, but I lacked the technical knowledge about how to redo the buttons and header (replacing the TTF failure font with the TTF compatible font) and then upload them to my site.  That&#8217;s where Pdad came in.  He didn&#8217;t know how to do it either, but as with all things computer related, he figured it out and saved the day!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Pdad</title>
		<link>http://www.chocolateandgarlic.com/2009/03/i-match/comment-page-1/#comment-395</link>
		<dc:creator>Pdad</dc:creator>
		<pubDate>Fri, 06 Mar 2009 04:08:43 +0000</pubDate>
		<guid isPermaLink="false">http://www.chocolateandgarlic.com/?p=1046#comment-395</guid>
		<description>Just for the record though, I definitely cannot do anything better than the paid helpers. I just had longer to work on it. Plus I couldn&#039;t have done this from scratch...I was more in tweaking mode.

The reason I was able to get it all matched correctly was just that there was a lot of trial and error on the fonts, i.e. some didn&#039;t have the complete set of characters, some caused stuff to get out of alignment, etc. If we had elected to pay for a font versus use free fonts we may have saved some time as well.</description>
		<content:encoded><![CDATA[<p>Just for the record though, I definitely cannot do anything better than the paid helpers. I just had longer to work on it. Plus I couldn&#8217;t have done this from scratch&#8230;I was more in tweaking mode.</p>
<p>The reason I was able to get it all matched correctly was just that there was a lot of trial and error on the fonts, i.e. some didn&#8217;t have the complete set of characters, some caused stuff to get out of alignment, etc. If we had elected to pay for a font versus use free fonts we may have saved some time as well.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jim F.</title>
		<link>http://www.chocolateandgarlic.com/2009/03/i-match/comment-page-1/#comment-389</link>
		<dc:creator>Jim F.</dc:creator>
		<pubDate>Thu, 05 Mar 2009 02:08:15 +0000</pubDate>
		<guid isPermaLink="false">http://www.chocolateandgarlic.com/?p=1046#comment-389</guid>
		<description>I noticed when I first started reading your blog that the fonts didn&#039;t match, but I assumed that was just a sign of my lack of graphics understanding. Perhaps it was, but I like the new look better.</description>
		<content:encoded><![CDATA[<p>I noticed when I first started reading your blog that the fonts didn&#8217;t match, but I assumed that was just a sign of my lack of graphics understanding. Perhaps it was, but I like the new look better.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

<!-- Dynamic Page Served (once) in 0.302 seconds -->
