<?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: How do you include unique styles in a particular blog post?</title>
	<atom:link href="http://blog.dolphinling.net/2005/02/how-do-you-include-unique-styles-in-a-particular-blog-post/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.dolphinling.net/2005/02/how-do-you-include-unique-styles-in-a-particular-blog-post/</link>
	<description>...whatever goes through my head...</description>
	<lastBuildDate>Fri, 22 Jan 2010 11:50:20 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Arve</title>
		<link>http://blog.dolphinling.net/2005/02/how-do-you-include-unique-styles-in-a-particular-blog-post/comment-page-1/#comment-18</link>
		<dc:creator>Arve</dc:creator>
		<pubDate>Wed, 16 Feb 2005 15:37:10 +0000</pubDate>
		<guid isPermaLink="false">/?p=40#comment-18</guid>
		<description>&lt;p&gt;You should also note that having &lt;code&gt;&lt;a href=&quot;data:...&quot; &gt;Link text&lt;/a&gt;&lt;/code&gt; is perfectly legal.&lt;/p&gt;
	&lt;p&gt;But, since you say you&#039;re in need of embedding the styled portion within the original: Either inlining it fully, using &lt;code&gt;&lt;style&gt;&lt;/code&gt; in a head section, or the style attribute on the affected elements also &quot;work&quot;. At least until you write something in your stylesheet that overrides your current styles.
&lt;/p&gt;</description>
		<content:encoded><![CDATA[<p>You should also note that having <code>&lt;a href="data:..." &gt;Link text&lt;/a&gt;</code> is perfectly legal.</p>
<p>But, since you say you&#8217;re in need of embedding the styled portion within the original: Either inlining it fully, using <code>&lt;style&gt;</code> in a head section, or the style attribute on the affected elements also &#8220;work&#8221;. At least until you write something in your stylesheet that overrides your current styles.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: dolphinling</title>
		<link>http://blog.dolphinling.net/2005/02/how-do-you-include-unique-styles-in-a-particular-blog-post/comment-page-1/#comment-17</link>
		<dc:creator>dolphinling</dc:creator>
		<pubDate>Sat, 12 Feb 2005 00:17:16 +0000</pubDate>
		<guid isPermaLink="false">/?p=40#comment-17</guid>
		<description>&lt;p&gt;&lt;code&gt;object&lt;/code&gt; is for embedding things that can&#039;t be described by the original language (namely (x)html), like images, movies, etc., or aren&#039;t considered part of the original document for some other reason. While it&#039;s valid and acceptable in some cases to have another (x)html page be that object, in this case it implies (to me) a separation between the original document and the post, when what I &lt;em&gt;want&lt;/em&gt; is to have the post be a &lt;em&gt;part&lt;/em&gt; of the original document.&lt;/p&gt;
	&lt;p&gt;It also adds another set of html/head/body tags in each post, which changes the semantics quite visibly. And also, it looks really hackish.&lt;/p&gt;
	&lt;p&gt;P.S.: If I&#039;m going to use an &lt;code&gt;object&lt;/code&gt;, why do I need to use a data url? I&#039;d rather just have the post be its own page and use an http url.
&lt;/p&gt;</description>
		<content:encoded><![CDATA[<p><code>object</code> is for embedding things that can&#8217;t be described by the original language (namely (x)html), like images, movies, etc., or aren&#8217;t considered part of the original document for some other reason. While it&#8217;s valid and acceptable in some cases to have another (x)html page be that object, in this case it implies (to me) a separation between the original document and the post, when what I <em>want</em> is to have the post be a <em>part</em> of the original document.</p>
<p>It also adds another set of html/head/body tags in each post, which changes the semantics quite visibly. And also, it looks really hackish.</p>
<p>P.S.: If I&#8217;m going to use an <code>object</code>, why do I need to use a data url? I&#8217;d rather just have the post be its own page and use an http url.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Anne</title>
		<link>http://blog.dolphinling.net/2005/02/how-do-you-include-unique-styles-in-a-particular-blog-post/comment-page-1/#comment-16</link>
		<dc:creator>Anne</dc:creator>
		<pubDate>Fri, 11 Feb 2005 10:29:03 +0000</pubDate>
		<guid isPermaLink="false">/?p=40#comment-16</guid>
		<description>&lt;p&gt;What semantics does it change? I think &lt;code&gt;data:&lt;/code&gt; is perfectly acceptable since you can use it to embed complete example pages and you are for sure that when you redesign your site your examples are not messed up.
&lt;/p&gt;</description>
		<content:encoded><![CDATA[<p>What semantics does it change? I think <code>data:</code> is perfectly acceptable since you can use it to embed complete example pages and you are for sure that when you redesign your site your examples are not messed up.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: dolphinling</title>
		<link>http://blog.dolphinling.net/2005/02/how-do-you-include-unique-styles-in-a-particular-blog-post/comment-page-1/#comment-14</link>
		<dc:creator>dolphinling</dc:creator>
		<pubDate>Fri, 11 Feb 2005 08:15:21 +0000</pubDate>
		<guid isPermaLink="false">/?p=40#comment-14</guid>
		<description>&lt;p&gt;The problem with a data: representation is that it changes the semantics. I want to still have normal (X)HTML semantics, not what an object and a data url implies.&lt;/p&gt;
	&lt;p&gt;I think I was right in what I posted: the best way to go about it is to have each post (that needs one) have its own stylesheet, and the link is dynamically included on every page that includes that post.&lt;/p&gt;</description>
		<content:encoded><![CDATA[<p>The problem with a data: representation is that it changes the semantics. I want to still have normal (X)HTML semantics, not what an object and a data url implies.</p>
<p>I think I was right in what I posted: the best way to go about it is to have each post (that needs one) have its own stylesheet, and the link is dynamically included on every page that includes that post.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Anne</title>
		<link>http://blog.dolphinling.net/2005/02/how-do-you-include-unique-styles-in-a-particular-blog-post/comment-page-1/#comment-13</link>
		<dc:creator>Anne</dc:creator>
		<pubDate>Wed, 09 Feb 2005 09:47:31 +0000</pubDate>
		<guid isPermaLink="false">/?p=40#comment-13</guid>
		<description>&lt;p&gt;The &lt;code&gt;data:&lt;/code&gt; thing is a cool suggestion! Perhaps in combination with the &lt;code&gt;OBJECT&lt;/code&gt; element or so, so you can also provide alternative content for screen readers.
&lt;/p&gt;</description>
		<content:encoded><![CDATA[<p>The <code>data:</code> thing is a cool suggestion! Perhaps in combination with the <code>OBJECT</code> element or so, so you can also provide alternative content for screen readers.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Arve Bersvendsen</title>
		<link>http://blog.dolphinling.net/2005/02/how-do-you-include-unique-styles-in-a-particular-blog-post/comment-page-1/#comment-12</link>
		<dc:creator>Arve Bersvendsen</dc:creator>
		<pubDate>Tue, 08 Feb 2005 19:32:00 +0000</pubDate>
		<guid isPermaLink="false">/?p=40#comment-12</guid>
		<description>&lt;p&gt;Since you don&#039;t know in which context you are serving the styles, I&#039;d say that &lt;code&gt;&lt;style&gt; is the most compatible way to go.&lt;/code&gt;&lt;/p&gt;
	&lt;p&gt; you could go about this is by using the &lt;samp&gt;data:&lt;/samp&gt; URI scheme, &lt;a href=&quot;http://www.ietf.org/rfc/rfc2397.txt&quot;&gt;RFC 2397&lt;/a&gt;, to include a free-standing HTML representation. However, that would leave IE out in the cold&lt;/p&gt;</description>
		<content:encoded><![CDATA[<p>Since you don&#8217;t know in which context you are serving the styles, I&#8217;d say that <code>&lt;style&gt; is the most compatible way to go.</code></p>
<p> you could go about this is by using the <samp>data:</samp> URI scheme, <a href="http://www.ietf.org/rfc/rfc2397.txt">RFC 2397</a>, to include a free-standing HTML representation. However, that would leave IE out in the cold</p>
]]></content:encoded>
	</item>
</channel>
</rss>

