<?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: S5 1.1a5</title>
	<atom:link href="http://meyerweb.com/eric/thoughts/2004/11/18/s5-11a5/feed/" rel="self" type="application/rss+xml" />
	<link>http://meyerweb.com/eric/thoughts/2004/11/18/s5-11a5/</link>
	<description>Things that Eric A. Meyer, CSS expert, writes about on his personal Web site; it&#039;s largely Web standards and Web technology, but also various bits of culture, politics, personal observations, and other miscellaneous stuff</description>
	<lastBuildDate>Tue, 18 Jun 2013 15:30:40 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.5.1</generator>
	<item>
		<title>By: Thanks for the great idea! :)</title>
		<link>http://meyerweb.com/eric/thoughts/2004/11/18/s5-11a5/#comment-2371</link>
		<dc:creator>Thanks for the great idea! :)</dc:creator>
		<pubDate>Wed, 01 Dec 2004 18:59:40 +0000</pubDate>
		<guid isPermaLink="false">http://meyerweb.com/eric/thoughts/2004/11/18/s5-11a5/#comment-2371</guid>
		<description><![CDATA[Yeah, Good luck with the project. Keep it up!! :)]]></description>
		<content:encoded><![CDATA[<p>Yeah, Good luck with the project. Keep it up!! :)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Stephen O'Brien</title>
		<link>http://meyerweb.com/eric/thoughts/2004/11/18/s5-11a5/#comment-2160</link>
		<dc:creator>Stephen O'Brien</dc:creator>
		<pubDate>Thu, 25 Nov 2004 21:53:06 +0000</pubDate>
		<guid isPermaLink="false">http://meyerweb.com/eric/thoughts/2004/11/18/s5-11a5/#comment-2160</guid>
		<description><![CDATA[First off, really great work on this project Eric.

I&#039;d like if holding down the right/left arrow acted for multiple strokes - at the moment if you hold it counts for a single hit. Changing this would make it more user-centric IMO.

Good luck with the project.]]></description>
		<content:encoded><![CDATA[<p>First off, really great work on this project Eric.</p>
<p>I&#8217;d like if holding down the right/left arrow acted for multiple strokes &#8211; at the moment if you hold it counts for a single hit. Changing this would make it more user-centric IMO.</p>
<p>Good luck with the project.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: John West</title>
		<link>http://meyerweb.com/eric/thoughts/2004/11/18/s5-11a5/#comment-2144</link>
		<dc:creator>John West</dc:creator>
		<pubDate>Wed, 24 Nov 2004 15:23:59 +0000</pubDate>
		<guid isPermaLink="false">http://meyerweb.com/eric/thoughts/2004/11/18/s5-11a5/#comment-2144</guid>
		<description><![CDATA[Re: controls outside the footer - absolutely! I&#039;d like to be able to eliminate the header/footer on slide#0 and that&#039;s much harder to do if the controls are embedded in one of them. The layout of the zero slide is often standard for the event it&#039;s given for, but the content slides are at the presenter&#039;s discretion.]]></description>
		<content:encoded><![CDATA[<p>Re: controls outside the footer &#8211; absolutely! I&#8217;d like to be able to eliminate the header/footer on slide#0 and that&#8217;s much harder to do if the controls are embedded in one of them. The layout of the zero slide is often standard for the event it&#8217;s given for, but the content slides are at the presenter&#8217;s discretion.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Block Sheep</title>
		<link>http://meyerweb.com/eric/thoughts/2004/11/18/s5-11a5/#comment-1996</link>
		<dc:creator>Block Sheep</dc:creator>
		<pubDate>Mon, 22 Nov 2004 04:01:22 +0000</pubDate>
		<guid isPermaLink="false">http://meyerweb.com/eric/thoughts/2004/11/18/s5-11a5/#comment-1996</guid>
		<description><![CDATA[This validates as strict, and degrades gracefully:
&lt;a href=&quot;http://www.example.com/&quot; onclick=&quot;if (window.open) {window.open(this.href);return false;}&quot;&gt;Example Destination&lt;/a&gt;

Also, yes the author should be able to pick which links open in a new window.]]></description>
		<content:encoded><![CDATA[<p>This validates as strict, and degrades gracefully:<br />
&lt;a href=&#8221;http://www.example.com/&#8221; onclick=&#8221;if (window.open) {window.open(this.href);return false;}&#8221;&gt;Example Destination&lt;/a&gt;</p>
<p>Also, yes the author should be able to pick which links open in a new window.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Eric</title>
		<link>http://meyerweb.com/eric/thoughts/2004/11/18/s5-11a5/#comment-1968</link>
		<dc:creator>Eric</dc:creator>
		<pubDate>Fri, 19 Nov 2004 15:44:25 +0000</pubDate>
		<guid isPermaLink="false">http://meyerweb.com/eric/thoughts/2004/11/18/s5-11a5/#comment-1968</guid>
		<description><![CDATA[Lachlan: sorry, but the external-link window spawning stays, as it is entirely in keeping with the goals of this project.  The external-link window spawning&#039;s purpose is to allow a presentation author, who is most likely the person that will be using the file, to define which links are external to the slide show, and should thus spawn new windows.  As Peter Murray pointed out in posts on 1.1a4, not doing so means that if you follow an external link and then hit &quot;Back&quot; to return to the slide show, it resets itself to the title slide, which is clearly unacceptable.

In other words: the author is, most of the time, the user, and decides when he will spawn a new window.  Obviously, when you create your own presentation, you can choose to not mark any of your links as external, and handle the &quot;reset avoidance&quot; problem your own way.  Granted, if a presentation is put online for public consumption, the spawning may be inflicted on others.  For those who really dislike spawning, there are the solutions you documented.  Theme authors could also distinctively style external links if they like in order to provide some warning.  Perhaps I&#039;ll add a class to any external link so that IE/Win will be able to style such links.

Remember, the goal of S&lt;sup&gt;5&lt;/sup&gt; is to provide a lightweight presentation solution, not to be a well-behaved (for certain definitions of &quot;well-behaved&quot;) Web denzien.  Its primary use case is to be operated by the file&#039;s author on a known machine with a known resolution.  The only reason I added font scaling was to account for unexpected projector resolutions (&quot;Oh no, I wrote this for 1024x768 and the projector only goes up to 800x600!&quot;).  It had basically nothing to do with the variegated nature of user agents on the Web.

Matt: no, those won&#039;t show up in IE/Win, because it doesn&#039;t support generated content.  It doesn&#039;t have to, since as Lachlan pointed out, those class names are diagnostic-- they help me see how the JS is altering class names on incremental slides-- and won&#039;t appear in the final version.]]></description>
		<content:encoded><![CDATA[<p>Lachlan: sorry, but the external-link window spawning stays, as it is entirely in keeping with the goals of this project.  The external-link window spawning&#8217;s purpose is to allow a presentation author, who is most likely the person that will be using the file, to define which links are external to the slide show, and should thus spawn new windows.  As Peter Murray pointed out in posts on 1.1a4, not doing so means that if you follow an external link and then hit &#8220;Back&#8221; to return to the slide show, it resets itself to the title slide, which is clearly unacceptable.</p>
<p>In other words: the author is, most of the time, the user, and decides when he will spawn a new window.  Obviously, when you create your own presentation, you can choose to not mark any of your links as external, and handle the &#8220;reset avoidance&#8221; problem your own way.  Granted, if a presentation is put online for public consumption, the spawning may be inflicted on others.  For those who really dislike spawning, there are the solutions you documented.  Theme authors could also distinctively style external links if they like in order to provide some warning.  Perhaps I&#8217;ll add a class to any external link so that IE/Win will be able to style such links.</p>
<p>Remember, the goal of S<sup>5</sup> is to provide a lightweight presentation solution, not to be a well-behaved (for certain definitions of &#8220;well-behaved&#8221;) Web denzien.  Its primary use case is to be operated by the file&#8217;s author on a known machine with a known resolution.  The only reason I added font scaling was to account for unexpected projector resolutions (&#8220;Oh no, I wrote this for 1024&#215;768 and the projector only goes up to 800&#215;600!&#8221;).  It had basically nothing to do with the variegated nature of user agents on the Web.</p>
<p>Matt: no, those won&#8217;t show up in IE/Win, because it doesn&#8217;t support generated content.  It doesn&#8217;t have to, since as Lachlan pointed out, those class names are diagnostic&#8211; they help me see how the JS is altering class names on incremental slides&#8211; and won&#8217;t appear in the final version.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: matt</title>
		<link>http://meyerweb.com/eric/thoughts/2004/11/18/s5-11a5/#comment-1966</link>
		<dc:creator>matt</dc:creator>
		<pubDate>Fri, 19 Nov 2004 12:47:54 +0000</pubDate>
		<guid isPermaLink="false">http://meyerweb.com/eric/thoughts/2004/11/18/s5-11a5/#comment-1966</guid>
		<description><![CDATA[thanks Lachlan, not to up on my css, and when i checked the page in IE (sp2) they didn&#039;t show up at all.]]></description>
		<content:encoded><![CDATA[<p>thanks Lachlan, not to up on my css, and when i checked the page in IE (sp2) they didn&#8217;t show up at all.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Lachlan Hunt</title>
		<link>http://meyerweb.com/eric/thoughts/2004/11/18/s5-11a5/#comment-1965</link>
		<dc:creator>Lachlan Hunt</dc:creator>
		<pubDate>Fri, 19 Nov 2004 11:01:56 +0000</pubDate>
		<guid isPermaLink="false">http://meyerweb.com/eric/thoughts/2004/11/18/s5-11a5/#comment-1965</guid>
		<description><![CDATA[Matt, they are supposed to be there, obviosuly for development purposes.  This line of CSS at the end of &lt;a href=&quot;http://www.meyerweb.com/eric/tools/s5/ui2/pretty.css&quot;&gt;pretty.css&lt;/a&gt; adds displays the class within square brackets after each list item, as you are seeing.

&lt;code&gt;li:after {content: &quot; [&quot; attr(class) &quot;]&quot;; color: #F88;}&lt;/code&gt;]]></description>
		<content:encoded><![CDATA[<p>Matt, they are supposed to be there, obviosuly for development purposes.  This line of CSS at the end of <a href="http://www.meyerweb.com/eric/tools/s5/ui2/pretty.css">pretty.css</a> adds displays the class within square brackets after each list item, as you are seeing.</p>
<p><code>li:after {content: " [" attr(class) "]"; color: #F88;}</code></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: matt</title>
		<link>http://meyerweb.com/eric/thoughts/2004/11/18/s5-11a5/#comment-1964</link>
		<dc:creator>matt</dc:creator>
		<pubDate>Fri, 19 Nov 2004 09:46:59 +0000</pubDate>
		<guid isPermaLink="false">http://meyerweb.com/eric/thoughts/2004/11/18/s5-11a5/#comment-1964</guid>
		<description><![CDATA[i&#039;m getting [] [inc] and [current] showing up in light red during the slideshow. they cannot be selected but are present. i have a screen cap if needed, i&#039;ve cleared my cache and the problem remains, and disabled obvious extensions that may have been the cause such as linkification.. but still remains.. or am i supposed to be seeing them on the test bed?

Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.5) Gecko/20041107 Firefox/1.0]]></description>
		<content:encoded><![CDATA[<p>i&#8217;m getting [] [inc] and [current] showing up in light red during the slideshow. they cannot be selected but are present. i have a screen cap if needed, i&#8217;ve cleared my cache and the problem remains, and disabled obvious extensions that may have been the cause such as linkification.. but still remains.. or am i supposed to be seeing them on the test bed?</p>
<p>Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.5) Gecko/20041107 Firefox/1.0</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Lachlan Hunt</title>
		<link>http://meyerweb.com/eric/thoughts/2004/11/18/s5-11a5/#comment-1962</link>
		<dc:creator>Lachlan Hunt</dc:creator>
		<pubDate>Fri, 19 Nov 2004 06:34:33 +0000</pubDate>
		<guid isPermaLink="false">http://meyerweb.com/eric/thoughts/2004/11/18/s5-11a5/#comment-1962</guid>
		<description><![CDATA[Please don&#039;t use the &lt;code&gt;target&lt;/code&gt; attribute!  I will decide when I want a new window to open, not you.  I wrote a &lt;a href=&quot;http://lachy.id.au/blogs/nettwits/2004/10/dont-target-me&quot; title=&quot;Don&#039;t Target Me!&quot;&gt;rant about the target attribute&lt;/a&gt; recently, which covers many reasons why it should not be used, but also gives a solution for those that are annoyed by it as I am.  I recommend you return to a strict DOCTYPE, and indicate external links using some other means, such as an icon, different colour, italics or whatever alternate style you like.  HTML 4.01 Strict would be best, though I&#039;m sure you would have read all the arguments for and against serving XTHML as &lt;code&gt;text/html&lt;/code&gt;, so I won&#039;t bother ranting about that too.]]></description>
		<content:encoded><![CDATA[<p>Please don&#8217;t use the <code>target</code> attribute!  I will decide when I want a new window to open, not you.  I wrote a <a href="http://lachy.id.au/blogs/nettwits/2004/10/dont-target-me" title="Don't Target Me!">rant about the target attribute</a> recently, which covers many reasons why it should not be used, but also gives a solution for those that are annoyed by it as I am.  I recommend you return to a strict DOCTYPE, and indicate external links using some other means, such as an icon, different colour, italics or whatever alternate style you like.  HTML 4.01 Strict would be best, though I&#8217;m sure you would have read all the arguments for and against serving XTHML as <code>text/html</code>, so I won&#8217;t bother ranting about that too.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Eric</title>
		<link>http://meyerweb.com/eric/thoughts/2004/11/18/s5-11a5/#comment-1961</link>
		<dc:creator>Eric</dc:creator>
		<pubDate>Fri, 19 Nov 2004 03:18:32 +0000</pubDate>
		<guid isPermaLink="false">http://meyerweb.com/eric/thoughts/2004/11/18/s5-11a5/#comment-1961</guid>
		<description><![CDATA[Micha&#235;l: It may not have been that way before.  That was caused by a desire to not have all of the &quot;layout&quot; stuff appear in the outline view.  I&#039;ve adjusted &lt;code&gt;outline.css&lt;/code&gt; to let the toggle button show even in outline view.  Note, however, that you can always toggle the views with the &quot;T&quot; key on the keyboard, whether or not the link is visible.

The CSS would have been more straightforward if the controls &lt;code&gt;div&lt;/code&gt; were outside the footer, structurally speaking, instead of inside it.  Theme authors: would it be a major problem for you if I move the controls &lt;code&gt;div&lt;/code&gt; out of the footer &lt;code&gt;div&lt;/code&gt; in v1.1?  If it will be, or you aren&#039;t sure, say so and I&#039;ll push the change off until later.  I think it&#039;s going to have to happen eventually, so if you can make the change easily, it seems to me that now is the time to do it.]]></description>
		<content:encoded><![CDATA[<p>Micha&euml;l: It may not have been that way before.  That was caused by a desire to not have all of the &#8220;layout&#8221; stuff appear in the outline view.  I&#8217;ve adjusted <code>outline.css</code> to let the toggle button show even in outline view.  Note, however, that you can always toggle the views with the &#8220;T&#8221; key on the keyboard, whether or not the link is visible.</p>
<p>The CSS would have been more straightforward if the controls <code>div</code> were outside the footer, structurally speaking, instead of inside it.  Theme authors: would it be a major problem for you if I move the controls <code>div</code> out of the footer <code>div</code> in v1.1?  If it will be, or you aren&#8217;t sure, say so and I&#8217;ll push the change off until later.  I think it&#8217;s going to have to happen eventually, so if you can make the change easily, it seems to me that now is the time to do it.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Micha</title>
		<link>http://meyerweb.com/eric/thoughts/2004/11/18/s5-11a5/#comment-1955</link>
		<dc:creator>Micha</dc:creator>
		<pubDate>Thu, 18 Nov 2004 23:26:19 +0000</pubDate>
		<guid isPermaLink="false">http://meyerweb.com/eric/thoughts/2004/11/18/s5-11a5/#comment-1955</guid>
		<description><![CDATA[When I open the testbed in Firefox, reveal the controls in the lower right corner, click the toggle button (or whatever it is called), I end up in the &#039;Basic Page Style View&#039;. There, I cannot find a toggle button to go back to the &#039;Slide View&#039;. I found that going in the Firefox menus selecting View/Page Style/No style, revealed the toggle button, but it doesn&#039;t do anything.

So, there&#039;s no way to go back to the slides without going back to your blog entry and reloading the testbed.

This is not how it was before, is it?]]></description>
		<content:encoded><![CDATA[<p>When I open the testbed in Firefox, reveal the controls in the lower right corner, click the toggle button (or whatever it is called), I end up in the &#8216;Basic Page Style View&#8217;. There, I cannot find a toggle button to go back to the &#8216;Slide View&#8217;. I found that going in the Firefox menus selecting View/Page Style/No style, revealed the toggle button, but it doesn&#8217;t do anything.</p>
<p>So, there&#8217;s no way to go back to the slides without going back to your blog entry and reloading the testbed.</p>
<p>This is not how it was before, is it?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Eric</title>
		<link>http://meyerweb.com/eric/thoughts/2004/11/18/s5-11a5/#comment-1954</link>
		<dc:creator>Eric</dc:creator>
		<pubDate>Thu, 18 Nov 2004 23:13:26 +0000</pubDate>
		<guid isPermaLink="false">http://meyerweb.com/eric/thoughts/2004/11/18/s5-11a5/#comment-1954</guid>
		<description><![CDATA[Bruce: I&#039;ll have to think about that after 1.1 is finished.  Sorry about the lack of preview, but I haven&#039;t had time to find a plugin that will do it on my hacked-up copy of WP.  I have these dreams that WP 1.3 will just have the capability built in and ready to turn on...

WysG: Hm, yes.  That was unintended, and will need to be fixed.  Great catch!]]></description>
		<content:encoded><![CDATA[<p>Bruce: I&#8217;ll have to think about that after 1.1 is finished.  Sorry about the lack of preview, but I haven&#8217;t had time to find a plugin that will do it on my hacked-up copy of WP.  I have these dreams that WP 1.3 will just have the capability built in and ready to turn on&#8230;</p>
<p>WysG: Hm, yes.  That was unintended, and will need to be fixed.  Great catch!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: WysG</title>
		<link>http://meyerweb.com/eric/thoughts/2004/11/18/s5-11a5/#comment-1950</link>
		<dc:creator>WysG</dc:creator>
		<pubDate>Thu, 18 Nov 2004 22:24:27 +0000</pubDate>
		<guid isPermaLink="false">http://meyerweb.com/eric/thoughts/2004/11/18/s5-11a5/#comment-1950</guid>
		<description><![CDATA[Not sure if this is intended, but once you&#039;ve backed up from a slide that the first element is set to inc, you&#039;ll have to click (or press right arrow) twice to get pass the first element

Step To Reproduce (in IE 6 and Firefox 1.0 on Win2000) :
- Load the testbed
- Right Arrow (or Click) twice, now your at the slide &quot;Operatic Origins&quot;
- Right Arrow once, now you have highlighted &quot;Allows a single XHTML document to be turned into a PowerPoint-like slide show&quot;
- Left Arrow once, now you&#039;re back at the slide &quot;What Is S5?&quot;
- Right Arrow once, you&#039;re at &quot;Operatic Origins&quot; with &quot;Allows a single XHTML document to be turned into a PowerPoint-like slide show&quot; highlighted
- Right Arrow once more, the &quot;Adding screen and print style sheets allows for multi-medium views of a single document&quot; should be highlighted but instead it&#039;s still at the first one, you&#039;ll have to Right Arrow once more to get to the one you intended

You can do the same thing slide 3 so I don&#039;t thins it&#039;s related with psf]]></description>
		<content:encoded><![CDATA[<p>Not sure if this is intended, but once you&#8217;ve backed up from a slide that the first element is set to inc, you&#8217;ll have to click (or press right arrow) twice to get pass the first element</p>
<p>Step To Reproduce (in IE 6 and Firefox 1.0 on Win2000) :<br />
- Load the testbed<br />
- Right Arrow (or Click) twice, now your at the slide &#8220;Operatic Origins&#8221;<br />
- Right Arrow once, now you have highlighted &#8220;Allows a single XHTML document to be turned into a PowerPoint-like slide show&#8221;<br />
- Left Arrow once, now you&#8217;re back at the slide &#8220;What Is S5?&#8221;<br />
- Right Arrow once, you&#8217;re at &#8220;Operatic Origins&#8221; with &#8220;Allows a single XHTML document to be turned into a PowerPoint-like slide show&#8221; highlighted<br />
- Right Arrow once more, the &#8220;Adding screen and print style sheets allows for multi-medium views of a single document&#8221; should be highlighted but instead it&#8217;s still at the first one, you&#8217;ll have to Right Arrow once more to get to the one you intended</p>
<p>You can do the same thing slide 3 so I don&#8217;t thins it&#8217;s related with psf</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tig</title>
		<link>http://meyerweb.com/eric/thoughts/2004/11/18/s5-11a5/#comment-1947</link>
		<dc:creator>Tig</dc:creator>
		<pubDate>Thu, 18 Nov 2004 21:40:20 +0000</pubDate>
		<guid isPermaLink="false">http://meyerweb.com/eric/thoughts/2004/11/18/s5-11a5/#comment-1947</guid>
		<description><![CDATA[This gets around the Strict validation...

function popup(url) {
    window.open(url);
    return false;
}

&lt;a href=&quot;http://www.mydomain.com&#8221; onclick=&quot;return popup(this.href);&quot;&gt;my domain&lt;/a&gt;


... not exactly what you&#039;re looking for, but it&#039;s a start.]]></description>
		<content:encoded><![CDATA[<p>This gets around the Strict validation&#8230;</p>
<p>function popup(url) {<br />
    window.open(url);<br />
    return false;<br />
}</p>
<p>&lt;a href=&#8221;http://www.mydomain.com&#8221; onclick=&#8221;return popup(this.href);&#8221;&gt;my domain&lt;/a&gt;</p>
<p>&#8230; not exactly what you&#8217;re looking for, but it&#8217;s a start.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Bruce D'Arcus</title>
		<link>http://meyerweb.com/eric/thoughts/2004/11/18/s5-11a5/#comment-1949</link>
		<dc:creator>Bruce D'Arcus</dc:creator>
		<pubDate>Thu, 18 Nov 2004 21:14:11 +0000</pubDate>
		<guid isPermaLink="false">http://meyerweb.com/eric/thoughts/2004/11/18/s5-11a5/#comment-1949</guid>
		<description><![CDATA[Eric: on blockquotes and attributions, I&#039;m just looking for the cleanest (simple, and semantic) way to get output something like this on a slide:

&lt;blockquote&gt;
&lt;p&gt;Some long quote with a lot of text text text text text text.&lt;/p&gt;
&lt;p style=&quot;text-align: right;&quot;&gt;— John Doe&lt;/p&gt;
&lt;/blockquote&gt;

I currently am doing by using a div with a &quot;quote&quot; class, and then within that having another &quot;attribution&quot; div with a cite element.  I&#039;m thinking there&#039;s likely a more elegant way, however.  I&#039;ve seen a few things on the web, for example, that use some clever CSS to take the content in a blockquote cite attribute and render it after the quote.  I don&#039;t have the url handy, but can dig it up later if need be.

Oh, BTW, it&#039;d be nice to have a preview option on comments.  Am not sure how this is going to render.]]></description>
		<content:encoded><![CDATA[<p>Eric: on blockquotes and attributions, I&#8217;m just looking for the cleanest (simple, and semantic) way to get output something like this on a slide:</p>
<blockquote>
<p>Some long quote with a lot of text text text text text text.</p>
<p style="text-align: right;">— John Doe</p>
</blockquote>
<p>I currently am doing by using a div with a &#8220;quote&#8221; class, and then within that having another &#8220;attribution&#8221; div with a cite element.  I&#8217;m thinking there&#8217;s likely a more elegant way, however.  I&#8217;ve seen a few things on the web, for example, that use some clever CSS to take the content in a blockquote cite attribute and render it after the quote.  I don&#8217;t have the url handy, but can dig it up later if need be.</p>
<p>Oh, BTW, it&#8217;d be nice to have a preview option on comments.  Am not sure how this is going to render.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
<!-- WP Super Cache is installed but broken. The path to wp-cache-phase1.php in wp-content/advanced-cache.php must be fixed! -->