<?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 for Web Graphics I</title>
	<atom:link href="http://www.cashdollardesign.com/drexel/blog/comments/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.cashdollardesign.com/drexel/blog</link>
	<description>General class outline and project instructions for Winter 2011</description>
	<lastBuildDate>Wed, 26 Jan 2011 04:06:31 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.4</generator>
	<item>
		<title>Comment on Typography Focused Articles by Chris</title>
		<link>http://www.cashdollardesign.com/drexel/blog/2011/01/19/typography-focused-articles/comment-page-1/#comment-81</link>
		<dc:creator>Chris</dc:creator>
		<pubDate>Wed, 26 Jan 2011 04:06:31 +0000</pubDate>
		<guid isPermaLink="false">http://www.cashdollardesign.com/drexel/blog/?p=142#comment-81</guid>
		<description>Don&#039;t get too frustrated with the standardization or legal battles brewing. I let the browser makers and the foundries sort it out. We&#039;ve come very far in just the last couple of year – smoother sailing is ahead. I expect in another two years, purchasing fonts for online use will be as simple and painless as purchasing legal .mp3s from Amazon or iTunes.

Instead, for now, focus on familiarizing yourself with the services and the body of typefaces at your disposal.</description>
		<content:encoded><![CDATA[<p>Don&#8217;t get too frustrated with the standardization or legal battles brewing. I let the browser makers and the foundries sort it out. We&#8217;ve come very far in just the last couple of year – smoother sailing is ahead. I expect in another two years, purchasing fonts for online use will be as simple and painless as purchasing legal .mp3s from Amazon or iTunes.</p>
<p>Instead, for now, focus on familiarizing yourself with the services and the body of typefaces at your disposal.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Typography Focused Articles by Chris</title>
		<link>http://www.cashdollardesign.com/drexel/blog/2011/01/19/typography-focused-articles/comment-page-1/#comment-80</link>
		<dc:creator>Chris</dc:creator>
		<pubDate>Wed, 26 Jan 2011 04:02:30 +0000</pubDate>
		<guid isPermaLink="false">http://www.cashdollardesign.com/drexel/blog/?p=142#comment-80</guid>
		<description>I appreciate the positivity in your summary. Web fonts, despite the current complexity, are getting easier and easier to design with and implement every day. 

Your iTunes analogy is a good one. Type Foundries want to be protected, much like the record labels want. iTunes provides a service that satisfies both the music love and the music distributor. I think services like Typekit are the web-font version of iTunes.</description>
		<content:encoded><![CDATA[<p>I appreciate the positivity in your summary. Web fonts, despite the current complexity, are getting easier and easier to design with and implement every day. </p>
<p>Your iTunes analogy is a good one. Type Foundries want to be protected, much like the record labels want. iTunes provides a service that satisfies both the music love and the music distributor. I think services like Typekit are the web-font version of iTunes.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Typography Focused Articles by Chris</title>
		<link>http://www.cashdollardesign.com/drexel/blog/2011/01/19/typography-focused-articles/comment-page-1/#comment-79</link>
		<dc:creator>Chris</dc:creator>
		<pubDate>Wed, 26 Jan 2011 03:58:58 +0000</pubDate>
		<guid isPermaLink="false">http://www.cashdollardesign.com/drexel/blog/?p=142#comment-79</guid>
		<description>I think you hit the nail on the head; we are only in the infancy of what web typography means. The activity of the last 2 years has eclipsed the combined efforts of the previous 15. 

I&#039;m glad you have a better understanding and hopefully our typographic palette for the web has opened up!</description>
		<content:encoded><![CDATA[<p>I think you hit the nail on the head; we are only in the infancy of what web typography means. The activity of the last 2 years has eclipsed the combined efforts of the previous 15. </p>
<p>I&#8217;m glad you have a better understanding and hopefully our typographic palette for the web has opened up!</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Typography Focused Articles by Chris</title>
		<link>http://www.cashdollardesign.com/drexel/blog/2011/01/19/typography-focused-articles/comment-page-1/#comment-78</link>
		<dc:creator>Chris</dc:creator>
		<pubDate>Wed, 26 Jan 2011 03:55:34 +0000</pubDate>
		<guid isPermaLink="false">http://www.cashdollardesign.com/drexel/blog/?p=142#comment-78</guid>
		<description>The growth of web licensing in the past year has been unbelievable. Yet, all web-specific versions of typefaces are not created equally. Look for the next 2-3 years be about &quot;quality&quot; of the typeface as it ports itself into the web version. Things like screen &quot;hinting&quot; are going to be big deals.

Meanwhile, I don&#039;t see the foundries charging to simply raise money. They charge their prices to protect their investments and to also tier their costs per views. If you use a fonts.com web font, you must specify the amount of page-views. The more views, the higher the cost. Data costs money.</description>
		<content:encoded><![CDATA[<p>The growth of web licensing in the past year has been unbelievable. Yet, all web-specific versions of typefaces are not created equally. Look for the next 2-3 years be about &#8220;quality&#8221; of the typeface as it ports itself into the web version. Things like screen &#8220;hinting&#8221; are going to be big deals.</p>
<p>Meanwhile, I don&#8217;t see the foundries charging to simply raise money. They charge their prices to protect their investments and to also tier their costs per views. If you use a fonts.com web font, you must specify the amount of page-views. The more views, the higher the cost. Data costs money.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Photoshop Etiquette Primer by Chris</title>
		<link>http://www.cashdollardesign.com/drexel/blog/2011/01/19/photoshop-etiquette-primer/comment-page-1/#comment-77</link>
		<dc:creator>Chris</dc:creator>
		<pubDate>Wed, 26 Jan 2011 03:50:46 +0000</pubDate>
		<guid isPermaLink="false">http://www.cashdollardesign.com/drexel/blog/?p=138#comment-77</guid>
		<description>We&#039;ve had issues with consistency in how we organize files. For instance, if there is a tight deadline on a project, sometimes designers (myself included) get a bit sloppy with the details. Usually, this is caught before the file gets into the hands of the front-end developers. I&#039;ve never had to get &lt;em&gt;too&lt;/em&gt; angry about it; everyone on my team understands that, at any moment, your Photoshop file might end up in the hands of a different designer. If someone else&#039;s PSD ended up on your desktop, you&#039;d hope that it was organized rationally and vice versa.

Remind me to talk about masks the next time we have class. Also, if you have any other questions regarding Photoshop etiquette, just let me know.</description>
		<content:encoded><![CDATA[<p>We&#8217;ve had issues with consistency in how we organize files. For instance, if there is a tight deadline on a project, sometimes designers (myself included) get a bit sloppy with the details. Usually, this is caught before the file gets into the hands of the front-end developers. I&#8217;ve never had to get <em>too</em> angry about it; everyone on my team understands that, at any moment, your Photoshop file might end up in the hands of a different designer. If someone else&#8217;s PSD ended up on your desktop, you&#8217;d hope that it was organized rationally and vice versa.</p>
<p>Remind me to talk about masks the next time we have class. Also, if you have any other questions regarding Photoshop etiquette, just let me know.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Typography Focused Articles by Peter J.</title>
		<link>http://www.cashdollardesign.com/drexel/blog/2011/01/19/typography-focused-articles/comment-page-1/#comment-76</link>
		<dc:creator>Peter J.</dc:creator>
		<pubDate>Mon, 24 Jan 2011 22:53:29 +0000</pubDate>
		<guid isPermaLink="false">http://www.cashdollardesign.com/drexel/blog/?p=142#comment-76</guid>
		<description>Reading through these articles, especially after starting with the Typedia blog entries on alternatives to Ariel &amp; Georgia was very interesting. In the past I was always aware that MAC fonts were at risk of not displaying correctly on PC’s and vice versa, but I had no idea to what extent. After reading the list of alternatives and reading about which typefaces could cross platform successfully I was shocked. 
	I also found it interesting the rate at which more web fonts are becoming available. It seems as though it were just a year ago that we were instructed as graphic designers to stick to the basic web safe typefaces such as Arial, Georgia, Lucida, and Verdana, and now foundries all across the internet are opening their doors to new possibilities and a wider range of web safe fonts.
	The downside to this growth of more web safe fonts is the cost vs. quality ratio. It seems that while many new typefaces are emerging as supposed, “Web safe fonts” they do not necessarily standup to the quality that traditional non web safe typefaces uphold. As a result these typefaces are free. Typefaces that are better quality however, are being sold at costly prices, in an effort to raise money for the type foundries that produce them.</description>
		<content:encoded><![CDATA[<p>Reading through these articles, especially after starting with the Typedia blog entries on alternatives to Ariel &amp; Georgia was very interesting. In the past I was always aware that MAC fonts were at risk of not displaying correctly on PC’s and vice versa, but I had no idea to what extent. After reading the list of alternatives and reading about which typefaces could cross platform successfully I was shocked.<br />
	I also found it interesting the rate at which more web fonts are becoming available. It seems as though it were just a year ago that we were instructed as graphic designers to stick to the basic web safe typefaces such as Arial, Georgia, Lucida, and Verdana, and now foundries all across the internet are opening their doors to new possibilities and a wider range of web safe fonts.<br />
	The downside to this growth of more web safe fonts is the cost vs. quality ratio. It seems that while many new typefaces are emerging as supposed, “Web safe fonts” they do not necessarily standup to the quality that traditional non web safe typefaces uphold. As a result these typefaces are free. Typefaces that are better quality however, are being sold at costly prices, in an effort to raise money for the type foundries that produce them.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Typography Focused Articles by Alana</title>
		<link>http://www.cashdollardesign.com/drexel/blog/2011/01/19/typography-focused-articles/comment-page-1/#comment-75</link>
		<dc:creator>Alana</dc:creator>
		<pubDate>Mon, 24 Jan 2011 21:45:41 +0000</pubDate>
		<guid isPermaLink="false">http://www.cashdollardesign.com/drexel/blog/?p=142#comment-75</guid>
		<description>I feel as though the use of type on the web is something that has the potential to really blossom in the next few years. Already the amount of typefaces available has significantly spiked and if things keep going the way that they are, I think soon the web and print will become a lot more similar. We are continuing to discover everything we can do with the web, which 30 years ago would have never been anything we could even imagine. As we learn more and more about what we can do with typography on the web, there will be a definite growth in the use of web instead of print. Though I understand the need for paying for fonts, I also understand the fear web designers have of purchasing a font that may not end up suiting their web needs in the end. Maybe as typography on the web continues to grow, prices will go down or things will shift. However, in the long run, typography on the web definitely needs much more consideration that print typography. It’s a more complicated art that needs to be designed to allow for shifts that will happen with different browsers and computers. More thought needs to go into the choices that you make because there is a lot more increase in variables. I used to feel more trapped in my options with typography and now that I know there is more options, I’ll be able to loosen up more with my type choices. The articles were very interesting and showed a lot of different opinions and ways of seeing things that I had never even considered. Though I previously knew very little about typography on the web, I now feel much more informed and will be able to make better choices in the future in regards to my web typography.</description>
		<content:encoded><![CDATA[<p>I feel as though the use of type on the web is something that has the potential to really blossom in the next few years. Already the amount of typefaces available has significantly spiked and if things keep going the way that they are, I think soon the web and print will become a lot more similar. We are continuing to discover everything we can do with the web, which 30 years ago would have never been anything we could even imagine. As we learn more and more about what we can do with typography on the web, there will be a definite growth in the use of web instead of print. Though I understand the need for paying for fonts, I also understand the fear web designers have of purchasing a font that may not end up suiting their web needs in the end. Maybe as typography on the web continues to grow, prices will go down or things will shift. However, in the long run, typography on the web definitely needs much more consideration that print typography. It’s a more complicated art that needs to be designed to allow for shifts that will happen with different browsers and computers. More thought needs to go into the choices that you make because there is a lot more increase in variables. I used to feel more trapped in my options with typography and now that I know there is more options, I’ll be able to loosen up more with my type choices. The articles were very interesting and showed a lot of different opinions and ways of seeing things that I had never even considered. Though I previously knew very little about typography on the web, I now feel much more informed and will be able to make better choices in the future in regards to my web typography.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Typography Focused Articles by Hannah</title>
		<link>http://www.cashdollardesign.com/drexel/blog/2011/01/19/typography-focused-articles/comment-page-1/#comment-74</link>
		<dc:creator>Hannah</dc:creator>
		<pubDate>Mon, 24 Jan 2011 21:02:06 +0000</pubDate>
		<guid isPermaLink="false">http://www.cashdollardesign.com/drexel/blog/?p=142#comment-74</guid>
		<description>I know that in my limited experience designing for the web, I have ignored the looming possibility of the typefaces I choose to not be available to use, or at a large cost to me. I knew there were limitations, but I also knew that I have visited hundreds of websites with beautiful typography, that clearly worked around the issue and did not limit themselves to Georgia, or Times. These articles “woke me up” in a sense, because while the projects I have worked on as a student probably will never be coded and put into use, being aware of the current state of web typography will force me to get into the habit of researching what my options are, and not approaching my typography decisions the same way as I would with print. I also find it interesting that some typefaces are being designed specifically for the screen, rather than print. 

These articles also portrayed a pretty fair look at each sides of the problem. While limitations are frustrating, I can see why most type designers aren’t being generous with their typefaces and contributing to the kind of disarray web typography is in. I found the comparisons to the iTunes solution to pirating music as hopeful. This “battle” is very similar to those in other fields, so while we might be in a grey area now, I think a solution that satisfies both parties will be reached. I also hope to get more comfortable with all the different acronyms of the type files. The first article that had three different acronyms in one sentence seemed like another language to me at first. But as I continued to read, I did gain some clarity, and glad I am aware of the developments on the technical side.</description>
		<content:encoded><![CDATA[<p>I know that in my limited experience designing for the web, I have ignored the looming possibility of the typefaces I choose to not be available to use, or at a large cost to me. I knew there were limitations, but I also knew that I have visited hundreds of websites with beautiful typography, that clearly worked around the issue and did not limit themselves to Georgia, or Times. These articles “woke me up” in a sense, because while the projects I have worked on as a student probably will never be coded and put into use, being aware of the current state of web typography will force me to get into the habit of researching what my options are, and not approaching my typography decisions the same way as I would with print. I also find it interesting that some typefaces are being designed specifically for the screen, rather than print. </p>
<p>These articles also portrayed a pretty fair look at each sides of the problem. While limitations are frustrating, I can see why most type designers aren’t being generous with their typefaces and contributing to the kind of disarray web typography is in. I found the comparisons to the iTunes solution to pirating music as hopeful. This “battle” is very similar to those in other fields, so while we might be in a grey area now, I think a solution that satisfies both parties will be reached. I also hope to get more comfortable with all the different acronyms of the type files. The first article that had three different acronyms in one sentence seemed like another language to me at first. But as I continued to read, I did gain some clarity, and glad I am aware of the developments on the technical side.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Photoshop Etiquette Primer by Peter J.</title>
		<link>http://www.cashdollardesign.com/drexel/blog/2011/01/19/photoshop-etiquette-primer/comment-page-1/#comment-73</link>
		<dc:creator>Peter J.</dc:creator>
		<pubDate>Mon, 24 Jan 2011 20:37:32 +0000</pubDate>
		<guid isPermaLink="false">http://www.cashdollardesign.com/drexel/blog/?p=138#comment-73</guid>
		<description>I understand that you work with professionals, but has anyone from your firm ever butchered the organization of layers/ folders? If so did you ream them out for it? Whats the worst organizational nightmare you&#039;ve had in terms of clients?

Could you speak about masks and grouping masks in one folder as opposed to masking each individual layer?</description>
		<content:encoded><![CDATA[<p>I understand that you work with professionals, but has anyone from your firm ever butchered the organization of layers/ folders? If so did you ream them out for it? Whats the worst organizational nightmare you&#8217;ve had in terms of clients?</p>
<p>Could you speak about masks and grouping masks in one folder as opposed to masking each individual layer?</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Typography Focused Articles by Jeremy Bloom</title>
		<link>http://www.cashdollardesign.com/drexel/blog/2011/01/19/typography-focused-articles/comment-page-1/#comment-72</link>
		<dc:creator>Jeremy Bloom</dc:creator>
		<pubDate>Mon, 24 Jan 2011 20:12:37 +0000</pubDate>
		<guid isPermaLink="false">http://www.cashdollardesign.com/drexel/blog/?p=142#comment-72</guid>
		<description>If strategically using WOFF systems for Fonts is so effective, than why haven’t all browsers agreed to accept it? Though I understand that for type sellers, this would be a great tool to enforce the legal use of their typefaces. This would allow creators to license their type making it more easily accessible for us designers. But what I don’t get is how there going to be able to regulate all these Fonts from a legal standpoint. If the font is posted on a website, cant anyone get it from the page source? Also, how would breaking these license terms be so evident? It sounds like a lot of added work and stress. If these sites (such as fontsquirrel and font.com) are hosting all these fonts that are currently on our private websites, where is the security that nothing will happen to jeopardize the functionality of our sites given a problem should happen to the host site? 

From a design perspective, I found it interesting how professionals have broken down using specified type to a science. Especially the idea of the “legibility spectrum” or 4 quadrant graph.  I did not know so much thought and energy went into this choice. The idea of type contrast is another fascinating element to the design decision, in particular, very different typefaces can play off of each other in complementary ways or resist each other to create a bit of tension, while typefaces that appear too similar can weaken the message and confuse a design’s visual language. I hope to gain more valuable insight into this methodology.</description>
		<content:encoded><![CDATA[<p>If strategically using WOFF systems for Fonts is so effective, than why haven’t all browsers agreed to accept it? Though I understand that for type sellers, this would be a great tool to enforce the legal use of their typefaces. This would allow creators to license their type making it more easily accessible for us designers. But what I don’t get is how there going to be able to regulate all these Fonts from a legal standpoint. If the font is posted on a website, cant anyone get it from the page source? Also, how would breaking these license terms be so evident? It sounds like a lot of added work and stress. If these sites (such as fontsquirrel and font.com) are hosting all these fonts that are currently on our private websites, where is the security that nothing will happen to jeopardize the functionality of our sites given a problem should happen to the host site? </p>
<p>From a design perspective, I found it interesting how professionals have broken down using specified type to a science. Especially the idea of the “legibility spectrum” or 4 quadrant graph.  I did not know so much thought and energy went into this choice. The idea of type contrast is another fascinating element to the design decision, in particular, very different typefaces can play off of each other in complementary ways or resist each other to create a bit of tension, while typefaces that appear too similar can weaken the message and confuse a design’s visual language. I hope to gain more valuable insight into this methodology.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

