<?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:georss="http://www.georss.org/georss" xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#" xmlns:media="http://search.yahoo.com/mrss/"
		>
<channel>
	<title>Comments on: Designing for the long read on Inside Government</title>
	<atom:link href="http://digital.cabinetoffice.gov.uk/2012/11/13/designing-for-the-long-read-on-inside-government/feed/" rel="self" type="application/rss+xml" />
	<link>http://digital.cabinetoffice.gov.uk/2012/11/13/designing-for-the-long-read-on-inside-government/</link>
	<description>Putting the public first in delivering digital public services</description>
	<lastBuildDate>Fri, 17 May 2013 09:57:43 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.com/</generator>
	<item>
		<title>By: Foden Grealy &#8211; A very good thing&#8230;</title>
		<link>http://digital.cabinetoffice.gov.uk/2012/11/13/designing-for-the-long-read-on-inside-government/#comment-35493</link>
		<dc:creator><![CDATA[Foden Grealy &#8211; A very good thing&#8230;]]></dc:creator>
		<pubDate>Sat, 13 Apr 2013 18:10:32 +0000</pubDate>
		<guid isPermaLink="false">http://digital.cabinetoffice.gov.uk/?p=7265#comment-35493</guid>
		<description><![CDATA[[...] English that I can read quickly and understand readily. I love that the pages look smart and that huge care has been taken about the layout and small things like the choice of typefaces. I think it is great [...]]]></description>
		<content:encoded><![CDATA[<p>[...] English that I can read quickly and understand readily. I love that the pages look smart and that huge care has been taken about the layout and small things like the choice of typefaces. I think it is great [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ben B</title>
		<link>http://digital.cabinetoffice.gov.uk/2012/11/13/designing-for-the-long-read-on-inside-government/#comment-22961</link>
		<dc:creator><![CDATA[Ben B]]></dc:creator>
		<pubDate>Sat, 05 Jan 2013 10:17:33 +0000</pubDate>
		<guid isPermaLink="false">http://digital.cabinetoffice.gov.uk/?p=7265#comment-22961</guid>
		<description><![CDATA[There&#039;s mention here of 30+ content types/templates. Without wanting the complete details, could you publish the list of the content types? I ask only because smaller initiatives (say, a town council) could use the list as a way of grouping the information types they publish. 

Thanks]]></description>
		<content:encoded><![CDATA[<p>There&#8217;s mention here of 30+ content types/templates. Without wanting the complete details, could you publish the list of the content types? I ask only because smaller initiatives (say, a town council) could use the list as a way of grouping the information types they publish. </p>
<p>Thanks</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: A quick tour of Inside Government &#124; Government Digital Service</title>
		<link>http://digital.cabinetoffice.gov.uk/2012/11/13/designing-for-the-long-read-on-inside-government/#comment-15366</link>
		<dc:creator><![CDATA[A quick tour of Inside Government &#124; Government Digital Service]]></dc:creator>
		<pubDate>Thu, 15 Nov 2012 10:37:33 +0000</pubDate>
		<guid isPermaLink="false">http://digital.cabinetoffice.gov.uk/?p=7265#comment-15366</guid>
		<description><![CDATA[[...] Designing for the long read on Inside Government [...]]]></description>
		<content:encoded><![CDATA[<p>[...] Designing for the long read on Inside Government [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: What we know about the users of Inside Government &#124; Government Digital Service</title>
		<link>http://digital.cabinetoffice.gov.uk/2012/11/13/designing-for-the-long-read-on-inside-government/#comment-15176</link>
		<dc:creator><![CDATA[What we know about the users of Inside Government &#124; Government Digital Service]]></dc:creator>
		<pubDate>Wed, 14 Nov 2012 15:56:23 +0000</pubDate>
		<guid isPermaLink="false">http://digital.cabinetoffice.gov.uk/?p=7265#comment-15176</guid>
		<description><![CDATA[[...] want the latest information and to be able to get an overview quickly, but they are also willing to engage in the depth and technicalities. That said, they will not tolerate jargon or [...]]]></description>
		<content:encoded><![CDATA[<p>[...] want the latest information and to be able to get an overview quickly, but they are also willing to engage in the depth and technicalities. That said, they will not tolerate jargon or [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: mhurrell</title>
		<link>http://digital.cabinetoffice.gov.uk/2012/11/13/designing-for-the-long-read-on-inside-government/#comment-15106</link>
		<dc:creator><![CDATA[mhurrell]]></dc:creator>
		<pubDate>Wed, 14 Nov 2012 12:00:55 +0000</pubDate>
		<guid isPermaLink="false">http://digital.cabinetoffice.gov.uk/?p=7265#comment-15106</guid>
		<description><![CDATA[Hi Gerry, agree with both your points - for those reasons I deliberately chose to scope this post to the tone of the interface rather than the mechanics of typographic legibility. I don&#039;t think Transport itself is any more or less readable than other typefaces of similar proportions, but it does carry a cultural expectation of the type of information that it should convey. 

That said, many web fonts are both badly spaced and not especially suited for the screen, which is compounded by CSS not really offering much in the way of fine-grained tracking control to compensate. With New Transport the high quality of Henrik&#039;s redrawing in addition to his openness to feedback about the spacing has made a difference.]]></description>
		<content:encoded><![CDATA[<p>Hi Gerry, agree with both your points &#8211; for those reasons I deliberately chose to scope this post to the tone of the interface rather than the mechanics of typographic legibility. I don&#8217;t think Transport itself is any more or less readable than other typefaces of similar proportions, but it does carry a cultural expectation of the type of information that it should convey. </p>
<p>That said, many web fonts are both badly spaced and not especially suited for the screen, which is compounded by CSS not really offering much in the way of fine-grained tracking control to compensate. With New Transport the high quality of Henrik&#8217;s redrawing in addition to his openness to feedback about the spacing has made a difference.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Gerry Leonidas</title>
		<link>http://digital.cabinetoffice.gov.uk/2012/11/13/designing-for-the-long-read-on-inside-government/#comment-15022</link>
		<dc:creator><![CDATA[Gerry Leonidas]]></dc:creator>
		<pubDate>Wed, 14 Nov 2012 00:48:00 +0000</pubDate>
		<guid isPermaLink="false">http://digital.cabinetoffice.gov.uk/?p=7265#comment-15022</guid>
		<description><![CDATA[You seem to be suggesting that Transport made texts less readable than Times, which prompted authors to rewrite. It could be argued just as easily (with perhaps more anecdotal evidence, for the general point) that Transport made the texts *more* readable, since the authors were able to detect that the language needed editing. Either is open to investigation. 
As you note in your last paragraph, readability is, ceteris paribus, a compound of typeface, layout, and style – so a simple typeface swap may be misleading. (For example, the ratio of x-height to linespacing in your image above is different for Times and Transport, which is a critical factor for paragraph typography.) I applaud your efforts, but I would like to make the point that a more nuanced approach when considering typefaces may be helpful.]]></description>
		<content:encoded><![CDATA[<p>You seem to be suggesting that Transport made texts less readable than Times, which prompted authors to rewrite. It could be argued just as easily (with perhaps more anecdotal evidence, for the general point) that Transport made the texts *more* readable, since the authors were able to detect that the language needed editing. Either is open to investigation.<br />
As you note in your last paragraph, readability is, ceteris paribus, a compound of typeface, layout, and style – so a simple typeface swap may be misleading. (For example, the ratio of x-height to linespacing in your image above is different for Times and Transport, which is a critical factor for paragraph typography.) I applaud your efforts, but I would like to make the point that a more nuanced approach when considering typefaces may be helpful.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Frances Berriman</title>
		<link>http://digital.cabinetoffice.gov.uk/2012/11/13/designing-for-the-long-read-on-inside-government/#comment-14951</link>
		<dc:creator><![CDATA[Frances Berriman]]></dc:creator>
		<pubDate>Tue, 13 Nov 2012 16:44:09 +0000</pubDate>
		<guid isPermaLink="false">http://digital.cabinetoffice.gov.uk/?p=7265#comment-14951</guid>
		<description><![CDATA[In this case, I believe &quot;affect&quot; is actually correct.  Affect can generally be replaced by the word &quot;influenced&quot;, as in... the influence of the typefaces on sentences.  Effect is generally used as a noun which would mean &quot;the impression of typefaces on sentences&quot;.  Essentially, you could use either in this sentence and it would have relevant meaning.]]></description>
		<content:encoded><![CDATA[<p>In this case, I believe &#8220;affect&#8221; is actually correct.  Affect can generally be replaced by the word &#8220;influenced&#8221;, as in&#8230; the influence of the typefaces on sentences.  Effect is generally used as a noun which would mean &#8220;the impression of typefaces on sentences&#8221;.  Essentially, you could use either in this sentence and it would have relevant meaning.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: mhurrell</title>
		<link>http://digital.cabinetoffice.gov.uk/2012/11/13/designing-for-the-long-read-on-inside-government/#comment-14945</link>
		<dc:creator><![CDATA[mhurrell]]></dc:creator>
		<pubDate>Tue, 13 Nov 2012 16:11:37 +0000</pubDate>
		<guid isPermaLink="false">http://digital.cabinetoffice.gov.uk/?p=7265#comment-14945</guid>
		<description><![CDATA[Hi Graham, you&#039;re right and we&#039;re working towards that. Our content designers have contributed a lot to Inside Government and all writers will be encouraged to follow the &lt;a href=&quot;https://www.gov.uk/designprinciples/styleguide&quot; title=&quot;The style guide for written content on the GOV.UK website&quot; rel=&quot;nofollow&quot;&gt;GDS Style guide&lt;/a&gt;. That said, we probably won&#039;t see a huge change happen overnight. You can &lt;a href=&quot;http://digital.cabinetoffice.gov.uk/2012/11/13/explaining-gov-policy-gov-uk/&quot; title=&quot;Explaining government policy on GOV.UK&quot; rel=&quot;nofollow&quot;&gt;read more in this post&lt;/a&gt;.]]></description>
		<content:encoded><![CDATA[<p>Hi Graham, you&#8217;re right and we&#8217;re working towards that. Our content designers have contributed a lot to Inside Government and all writers will be encouraged to follow the <a href="https://www.gov.uk/designprinciples/styleguide" title="The style guide for written content on the GOV.UK website" rel="nofollow">GDS Style guide</a>. That said, we probably won&#8217;t see a huge change happen overnight. You can <a href="http://digital.cabinetoffice.gov.uk/2012/11/13/explaining-gov-policy-gov-uk/" title="Explaining government policy on GOV.UK" rel="nofollow">read more in this post</a>.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: frankieroberto</title>
		<link>http://digital.cabinetoffice.gov.uk/2012/11/13/designing-for-the-long-read-on-inside-government/#comment-14919</link>
		<dc:creator><![CDATA[frankieroberto]]></dc:creator>
		<pubDate>Tue, 13 Nov 2012 14:30:14 +0000</pubDate>
		<guid isPermaLink="false">http://digital.cabinetoffice.gov.uk/?p=7265#comment-14919</guid>
		<description><![CDATA[&quot;The affect of typefaces on sentences&quot; - ouch. Embarrassing mistake for an article on writing... :)]]></description>
		<content:encoded><![CDATA[<p>&#8220;The affect of typefaces on sentences&#8221; &#8211; ouch. Embarrassing mistake for an article on writing&#8230; :)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Graham Lee</title>
		<link>http://digital.cabinetoffice.gov.uk/2012/11/13/designing-for-the-long-read-on-inside-government/#comment-14896</link>
		<dc:creator><![CDATA[Graham Lee]]></dc:creator>
		<pubDate>Tue, 13 Nov 2012 12:51:26 +0000</pubDate>
		<guid isPermaLink="false">http://digital.cabinetoffice.gov.uk/?p=7265#comment-14896</guid>
		<description><![CDATA[Sorry - meant to say &#039;hence should be...&#039;]]></description>
		<content:encoded><![CDATA[<p>Sorry &#8211; meant to say &#8216;hence should be&#8230;&#8217;</p>
]]></content:encoded>
	</item>
</channel>
</rss>
