<?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/"
	xmlns:itunes="http://www.itunes.com/dtds/podcast-1.0.dtd"
xmlns:rawvoice="http://www.rawvoice.com/rawvoiceRssModule/"
	>
<channel>
	<title>Comments on: UIEtips: In Defense of Lorem Ipsum</title>
	<atom:link href="http://www.uie.com/brainsparks/2012/06/27/uietips-lorem-ipsum-defense/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.uie.com/brainsparks/2012/06/27/uietips-lorem-ipsum-defense/</link>
	<description>UIE\'s latest insights on the world of design</description>
	<lastBuildDate>Sat, 25 May 2013 00:51:34 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.4.1</generator>
	<item>
		<title>By: Karen McGrane</title>
		<link>http://www.uie.com/brainsparks/2012/06/27/uietips-lorem-ipsum-defense/comment-page-1/#comment-225307</link>
		<dc:creator>Karen McGrane</dc:creator>
		<pubDate>Thu, 28 Jun 2012 19:23:48 +0000</pubDate>
		<guid isPermaLink="false">http://www.uie.com/brainsparks/?p=7265#comment-225307</guid>
		<description>Lorem ipsum is indeed Latin, and more background about this passage by Cicero, including translations, can be found at http://www.lipsum.com/.

The process of displaying placeholder copy is often referred to as “greeked” text, probably from the phrase, &quot;It&#039;s Greek to me.&quot; Learn more at: http://en.wikipedia.org/wiki/Greeking</description>
		<content:encoded><![CDATA[<p>Lorem ipsum is indeed Latin, and more background about this passage by Cicero, including translations, can be found at <a href="http://www.lipsum.com/" rel="nofollow">http://www.lipsum.com/</a>.</p>
<p>The process of displaying placeholder copy is often referred to as “greeked” text, probably from the phrase, &#8220;It&#8217;s Greek to me.&#8221; Learn more at: <a href="http://en.wikipedia.org/wiki/Greeking" rel="nofollow">http://en.wikipedia.org/wiki/Greeking</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jeremias</title>
		<link>http://www.uie.com/brainsparks/2012/06/27/uietips-lorem-ipsum-defense/comment-page-1/#comment-225231</link>
		<dc:creator>Jeremias</dc:creator>
		<pubDate>Thu, 28 Jun 2012 09:00:23 +0000</pubDate>
		<guid isPermaLink="false">http://www.uie.com/brainsparks/?p=7265#comment-225231</guid>
		<description>I so agree, it is just one of the tools in the box and it indeed has a place there. 

I just recently ran into one of the problems caused by using actual copy instead of Lorem Ipsum and plain descriptive titles for headers, links and navigation in the wire frames shown to the client. This was the first meeting with the client as a designer (our manager and sales reps had been in contact with them). The conversation pretty soon veered off to content because the journalist who is working on the actual copy started to re-arrange the sitemap on the printed out wire frames and handing out tasks to us... We made notes of them and navigated on.

This is actually not that big of a problem but it is illustrates the fact that people usually focus their attention to what is meaningful and familiar to them at the expense of the bigger picture and how they are guided and asked to interpret it.

Like wire frames for example, where others see concepts, models and their relations and can easily identify them some see the literal meaning of the words instead of layout elements/data types and their function in the layout/system. 

For designers, seeing the actual data and designing on it is vitally important (as much as designing with clients/users is).

What you show to clients and at which phase is a different thing altogether and as soon as the move to a functional and interactive prototype can be achieved the better. There Lorem Ipsum shouldn&#039;t have a place anymore.</description>
		<content:encoded><![CDATA[<p>I so agree, it is just one of the tools in the box and it indeed has a place there. </p>
<p>I just recently ran into one of the problems caused by using actual copy instead of Lorem Ipsum and plain descriptive titles for headers, links and navigation in the wire frames shown to the client. This was the first meeting with the client as a designer (our manager and sales reps had been in contact with them). The conversation pretty soon veered off to content because the journalist who is working on the actual copy started to re-arrange the sitemap on the printed out wire frames and handing out tasks to us&#8230; We made notes of them and navigated on.</p>
<p>This is actually not that big of a problem but it is illustrates the fact that people usually focus their attention to what is meaningful and familiar to them at the expense of the bigger picture and how they are guided and asked to interpret it.</p>
<p>Like wire frames for example, where others see concepts, models and their relations and can easily identify them some see the literal meaning of the words instead of layout elements/data types and their function in the layout/system. </p>
<p>For designers, seeing the actual data and designing on it is vitally important (as much as designing with clients/users is).</p>
<p>What you show to clients and at which phase is a different thing altogether and as soon as the move to a functional and interactive prototype can be achieved the better. There Lorem Ipsum shouldn&#8217;t have a place anymore.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Virginia (Ginger) Bisek</title>
		<link>http://www.uie.com/brainsparks/2012/06/27/uietips-lorem-ipsum-defense/comment-page-1/#comment-225161</link>
		<dc:creator>Virginia (Ginger) Bisek</dc:creator>
		<pubDate>Wed, 27 Jun 2012 21:01:59 +0000</pubDate>
		<guid isPermaLink="false">http://www.uie.com/brainsparks/?p=7265#comment-225161</guid>
		<description>Totally agree with the author. It&#039;s a balance. And sometimes using copy in design gets the client thinking ahead - about issues that need to be covered NOW, and not pushed off until later. 

Plus, as a copywriter, I present all my copy in a visual manner similar to a website (using Word and tables) so that low-techie clients get on board as soon as possible. Yes, be prepared to field a lot of questions, but when has a copywriter ever NOT had this problem?

I used to have a &quot;hands off&quot; approach to design (after all, designers are responsible for design, right?) - but that&#039;s not an approach toward what I like to call &quot;efficient success.&quot; Website design is a team project. And I welcome copy critiques from designers as well. 

I really appreciate how UIE is covering more and more content development issues. Thank you!

- Ginger</description>
		<content:encoded><![CDATA[<p>Totally agree with the author. It&#8217;s a balance. And sometimes using copy in design gets the client thinking ahead &#8211; about issues that need to be covered NOW, and not pushed off until later. </p>
<p>Plus, as a copywriter, I present all my copy in a visual manner similar to a website (using Word and tables) so that low-techie clients get on board as soon as possible. Yes, be prepared to field a lot of questions, but when has a copywriter ever NOT had this problem?</p>
<p>I used to have a &#8220;hands off&#8221; approach to design (after all, designers are responsible for design, right?) &#8211; but that&#8217;s not an approach toward what I like to call &#8220;efficient success.&#8221; Website design is a team project. And I welcome copy critiques from designers as well. </p>
<p>I really appreciate how UIE is covering more and more content development issues. Thank you!</p>
<p>- Ginger</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jane</title>
		<link>http://www.uie.com/brainsparks/2012/06/27/uietips-lorem-ipsum-defense/comment-page-1/#comment-225159</link>
		<dc:creator>Jane</dc:creator>
		<pubDate>Wed, 27 Jun 2012 20:50:56 +0000</pubDate>
		<guid isPermaLink="false">http://www.uie.com/brainsparks/?p=7265#comment-225159</guid>
		<description>Great, balanced article from Karen, but FYI Lorem ipsum is Latin, not Greek.</description>
		<content:encoded><![CDATA[<p>Great, balanced article from Karen, but FYI Lorem ipsum is Latin, not Greek.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
