<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>ThinkCreation &#187; typography</title>
	<atom:link href="http://thinkcreation.net/blog/category/typography/feed/" rel="self" type="application/rss+xml" />
	<link>http://thinkcreation.net/blog</link>
	<description>Graphic Design services, desktop publishing and design articles</description>
	<lastBuildDate>Tue, 11 Aug 2009 12:13:25 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.3</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>Creating Faux Bold with Strokes: the Catch</title>
		<link>http://thinkcreation.net/blog/desktop-publishing/creating-faux-bold-with-strokes%e2%80%94the-catch/</link>
		<comments>http://thinkcreation.net/blog/desktop-publishing/creating-faux-bold-with-strokes%e2%80%94the-catch/#comments</comments>
		<pubDate>Mon, 04 Jun 2007 09:57:09 +0000</pubDate>
		<dc:creator>Elisabetta Bruno</dc:creator>
				<category><![CDATA[Desktop Publishing]]></category>
		<category><![CDATA[prepress]]></category>
		<category><![CDATA[typography]]></category>
		<category><![CDATA[software]]></category>
		<category><![CDATA[tutorials]]></category>

		<guid isPermaLink="false">http://thinkcreation.net/blog/?p=254</guid>
		<description><![CDATA[Many of you probably know that if you don&#8217;t have the bold or italics version of a font installed in your system, you shouldn&#8217;t use your DTP application&#8217;s option to make it bold or italics, because that will simply result in a simulation which might work on screen or with a desktop printer, but that [...]]]></description>
			<content:encoded><![CDATA[<p>Many of you probably know that if you don&#8217;t have the bold or italics version of a font installed in your system, you shouldn&#8217;t use your DTP application&#8217;s option to make it bold or italics, because that will simply result in a simulation which might work on screen or with a desktop printer, but that can cause problems once your file is sent to an external printer using a RIP.</p>
<p>A solution to this can be adding a border around type. Applications such as Illustrator, Corel Draw, InDesign and others allow you to do that. However there is a catch, which I discovered not long ago while working a my company&#8217;s logo (that I didn&#8217;t design).<span id="more-254"></span></p>
<p>When I was first hired by this company I was told that sometimes the logo looks thinner than it should. They had asked the designer to make it bolder when it was designed, so he added a stroke around the text since he had no bold version of the font (Andale Mono). The text in the logo is outlined by the way. Despite this the logo often just looked thinner than it should have.</p>
<p>One day I was making some tags for a packaging project and I used the logo. Since the tags were small, I had to shrink the logo. I made my PDF, did my preflight checks in Adobe Acrobat Professional and no matter what I did I kept getting an error about a stroke being less than 0.25 pt. For those who don&#8217;t know, printing a stroke or a line that is less wide than 0.25 pt often will not print because it&#8217;s too thin. Finally I figured out that the stroke was around the logo. In the original file, since the logo is bigger, the stroke is wider than 1pt, but once the logo is resized it becomes a hairline, thus being ignored by the printers&#8217; RIP once it goes to press. That was why the logo was thinner sometimes. It wasn&#8217;t the designer taking &#8220;artistic license&#8221; it was just a technical problem.</p>
<p>Moral of the story: don&#8217;t use faux bold or italics, and when you use a stroke around text to simulate the bold version make sure you keep in mind how the design, logo, whatever you are doing may be used in the future. If the logo/graphic will be made very small, then try not to use strokes around text as it may not be printed.</p>
]]></content:encoded>
			<wfw:commentRss>http://thinkcreation.net/blog/desktop-publishing/creating-faux-bold-with-strokes%e2%80%94the-catch/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>Typography Upside Down</title>
		<link>http://thinkcreation.net/blog/typography/typography-upside-down/</link>
		<comments>http://thinkcreation.net/blog/typography/typography-upside-down/#comments</comments>
		<pubDate>Sun, 05 Feb 2006 23:38:05 +0000</pubDate>
		<dc:creator>Elisabetta Bruno</dc:creator>
				<category><![CDATA[typography]]></category>

		<guid isPermaLink="false">http://thinkcreation.net/blog/?p=75</guid>
		<description><![CDATA[Put your head on the floor, balance yourself so that your crossed legs stick up in the air and your head holds your body. Now start typing. All right! That's not quite what I mean by upside down typography... ]]></description>
			<content:encoded><![CDATA[<p>Actually I am talking about kerning. There&#8217;s a great typography tip on <a target="_blank" href="http://www.prepressology.com/">Prepressology</a> on how to kern letters:</p>
<blockquote><p>Kerning can be a tricky part of dealing with typography. Recently a fellow designer shared a method she uses and I thought it was really clever. Trying to deal with kerning can sometimes be a bit frustrating but this little tip can take some of that frustration away.</p>
<p>Flip the text 180 degrees. Yes, thatâ€™s it!</p></blockquote>
<p>I advise you read the <a target="_blank" href="http://www.prepressology.com/typography-tip-1-kerning-upside-down/">rest of the article</a>, because it will turn very useful.</p>
<p>Technorati Tags: <a href="http://technorati.com/tag/typography" rel="tag">typography</a>, <a href="http://technorati.com/tag/desktop+publishing" rel="tag"> desktop publishing</a></p>
<blockquote />
]]></content:encoded>
			<wfw:commentRss>http://thinkcreation.net/blog/typography/typography-upside-down/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>Tip O&#8217; the Day: Open Type Fonts Are Cross Platform</title>
		<link>http://thinkcreation.net/blog/tip-of-the-day/tip-o-the-day-open-type-fonts-are-cross-platform/</link>
		<comments>http://thinkcreation.net/blog/tip-of-the-day/tip-o-the-day-open-type-fonts-are-cross-platform/#comments</comments>
		<pubDate>Wed, 01 Feb 2006 15:48:51 +0000</pubDate>
		<dc:creator>Elisabetta Bruno</dc:creator>
				<category><![CDATA[Tip Of The Day]]></category>
		<category><![CDATA[typography]]></category>

		<guid isPermaLink="false">http://thinkcreation.net/blog/?p=73</guid>
		<description><![CDATA[Macs don't have the monopoly of the graphic design market anymore, so how do you work with a designer who doesn't use your same OS?]]></description>
			<content:encoded><![CDATA[<p>As techonology advanced, PCs have quickly caught up with Macs. A designer can do his job on both platforms with the same amount of effort.</p>
<p>I have heard many times the myth that Macs cannot read files created by a Windows program and vice versa. That might have been true some time ago, but it is no longer. Files created by a Windows application can be opened by the same application run on a Mac. When going  from Mac to PC, it is often necessary to add a file extension, as Mac software usually doesn&#8217;t append it at the end of a file nameâ€”that&#8217;s about it. There are other minor differences, but they&#8217;re easy to outdo.</p>
<p>The main problem remains fonts. Usually fonts used on a platform won&#8217;t work with the other one. Sometimes there are problems even using Mac OS X fonts on a Mac OS 9 platform. Luckily there are exceptions:</p>
<ol>
<li>Open Type fonts are cross platform. You can use them both with Windows and Mac OS X without problems.</li>
<li>Mac OS X handles also Windows True Type fonts, yet this doesn&#8217;t work in reverse.</li>
</ol>
<p>If you know your job will be dealt with by another designer using another OS, remember this and you&#8217;ll save you both a lot of pain.</p>
<p>[tag]Mac OS, Machintosh, fonts, type Windows, PC, Mac[/tags]</p>
]]></content:encoded>
			<wfw:commentRss>http://thinkcreation.net/blog/tip-of-the-day/tip-o-the-day-open-type-fonts-are-cross-platform/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Comic Sans Must Die</title>
		<link>http://thinkcreation.net/blog/typography/comics-sans-must-die/</link>
		<comments>http://thinkcreation.net/blog/typography/comics-sans-must-die/#comments</comments>
		<pubDate>Tue, 24 Jan 2006 23:59:19 +0000</pubDate>
		<dc:creator>Elisabetta Bruno</dc:creator>
				<category><![CDATA[typography]]></category>

		<guid isPermaLink="false">http://thinkcreation.net/blog/?p=63</guid>
		<description><![CDATA[Disclaimer: This site does not approve violence nor does it intend to incite riot or other social dischord]]></description>
			<content:encoded><![CDATA[<p>Professional designers will tell you that Comic Sans is used and abused just as much as Times New Roman. Some of them have sworn by their life they will never use Comic Sans. But is it right to kill a font like this, without interrogation or due justice procedures to find out its uses?</p>
<p>Samuel John Klein at <a target="_blank" href="http://designorati.com/typography/news-5/2006/comic-sans-why/">Designorati:Typography</a> brings to light <a target="_blank" href="http://www.connare.com/comic.htm">an excellent explanation</a> from Comic Sans designer, Vincent Connare.</p>
<p>Now, <em>please</em>, don&#8217;t use Rotisan for comic books, will you?</p>
<p>Technorati Tags: <a href="http://technorati.com/tag/typography" rel="tag">typography</a>, <a href="http://technorati.com/tag/fonts" rel="tag"> fonts</a>, <a href="http://technorati.com/tag/comic+sans" rel="tag"> comic sans</a></p>
]]></content:encoded>
			<wfw:commentRss>http://thinkcreation.net/blog/typography/comics-sans-must-die/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
	</channel>
</rss>
