<?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: Formata Non Grata</title>
	<atom:link href="http://schepers.cc/formata-non-grata/feed" rel="self" type="application/rss+xml" />
	<link>http://schepers.cc/formata-non-grata</link>
	<description>Technology upside down and backwards</description>
	<lastBuildDate>Mon, 14 Nov 2011 22:51:10 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
	<item>
		<title>By: Schepers</title>
		<link>http://schepers.cc/formata-non-grata#comment-191</link>
		<dc:creator>Schepers</dc:creator>
		<pubDate>Wed, 21 Jul 2010 14:36:54 +0000</pubDate>
		<guid isPermaLink="false">http://schepers.cc/?p=160#comment-191</guid>
		<description>John, thanks for replying! I will pull together some examples, and get back to you. Optimizing SVG searchability should be a collaborative effort between search engines, the SVG Working Group, authoring tool vendors, and content creators, so we are happy to have an ongoing discussion with the Google search team.</description>
		<content:encoded><![CDATA[<p>John, thanks for replying! I will pull together some examples, and get back to you. Optimizing SVG searchability should be a collaborative effort between search engines, the SVG Working Group, authoring tool vendors, and content creators, so we are happy to have an ongoing discussion with the Google search team.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: chris</title>
		<link>http://schepers.cc/formata-non-grata#comment-188</link>
		<dc:creator>chris</dc:creator>
		<pubDate>Wed, 21 Jul 2010 05:07:35 +0000</pubDate>
		<guid isPermaLink="false">http://schepers.cc/?p=160#comment-188</guid>
		<description>SVG is great. Even this fairly extensive post doesn&#039;t cover all aspects of SVG. SVG enjoys similar love other open source and web 2.0, and potential is still largely untapped. SVG will most likely remain a developers technology, even though it helps publish great web content. For example a relative newcomer to SVG can quickly design some compelling svg content without learning flash programming or css+javascript hacks or worse publishing content with text as a jpeg.
In early svg days i stumbled onto and got very excited by tkzink, but that hasn&#039;t progressed. Anyway, all these things I&#039;m writing about is a fairly hard slog to discover on the web using a search engine. Getting to yet undiscovered svg content (even if it&#039;s a blog about SVG such as this) is a losing proposition from the outset. You have to be prepared to cast your search net far and wide, and spend time wading through false hits. No wonder the general internet public has little or no exposure or say about SVG. In the end the results will show in the pudding, so to speak, when SVG content becomes more discoverable.
Better indexing of SVG web content by google would be most welcome. Just like web2.0/ajax, wikipedia, youtube and many other great developments..this sort of thing will be driven by people who have courage and can reach some buttons.</description>
		<content:encoded><![CDATA[<p>SVG is great. Even this fairly extensive post doesn&#8217;t cover all aspects of SVG. SVG enjoys similar love other open source and web 2.0, and potential is still largely untapped. SVG will most likely remain a developers technology, even though it helps publish great web content. For example a relative newcomer to SVG can quickly design some compelling svg content without learning flash programming or css+javascript hacks or worse publishing content with text as a jpeg.<br />
In early svg days i stumbled onto and got very excited by tkzink, but that hasn&#8217;t progressed. Anyway, all these things I&#8217;m writing about is a fairly hard slog to discover on the web using a search engine. Getting to yet undiscovered svg content (even if it&#8217;s a blog about SVG such as this) is a losing proposition from the outset. You have to be prepared to cast your search net far and wide, and spend time wading through false hits. No wonder the general internet public has little or no exposure or say about SVG. In the end the results will show in the pudding, so to speak, when SVG content becomes more discoverable.<br />
Better indexing of SVG web content by google would be most welcome. Just like web2.0/ajax, wikipedia, youtube and many other great developments..this sort of thing will be driven by people who have courage and can reach some buttons.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: John Mueller</title>
		<link>http://schepers.cc/formata-non-grata#comment-187</link>
		<dc:creator>John Mueller</dc:creator>
		<pubDate>Tue, 20 Jul 2010 14:31:57 +0000</pubDate>
		<guid isPermaLink="false">http://schepers.cc/?p=160#comment-187</guid>
		<description>Hi! I am a webmaster trends analyst here at Google and one of the things that I do is to get our engineers in touch with issues like this :). This is an interesting blog post and a great discussion about SVG files. I&#039;m not completely in the picture on SVG files and how their contents might be indexable or useful in web-search, but I&#039;ll certainly pass this on to the teams here at Google to review.
 
If you have more compelling use-cases where the contents in SVG files would be highly relevant (but not findable in the search results at the moment), it would be great to hear about them. I realize that adoption always depends on a number of factors; I know our teams are aware of SVG content, but maybe there&#039;s something here that can help speed things up on our side as well :).</description>
		<content:encoded><![CDATA[<p>Hi! I am a webmaster trends analyst here at Google and one of the things that I do is to get our engineers in touch with issues like this <img src='http://schepers.cc/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> . This is an interesting blog post and a great discussion about SVG files. I&#8217;m not completely in the picture on SVG files and how their contents might be indexable or useful in web-search, but I&#8217;ll certainly pass this on to the teams here at Google to review.<br />
 <br />
If you have more compelling use-cases where the contents in SVG files would be highly relevant (but not findable in the search results at the moment), it would be great to hear about them. I realize that adoption always depends on a number of factors; I know our teams are aware of SVG content, but maybe there&#8217;s something here that can help speed things up on our side as well <img src='http://schepers.cc/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> .</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Schepers</title>
		<link>http://schepers.cc/formata-non-grata#comment-184</link>
		<dc:creator>Schepers</dc:creator>
		<pubDate>Fri, 16 Jul 2010 22:19:18 +0000</pubDate>
		<guid isPermaLink="false">http://schepers.cc/?p=160#comment-184</guid>
		<description>Susan, yes, great point. It shows that Google apparently does index the contents of SVG files, and could present them in their search results in more useful ways.  Your specific search is clever and useful for a particular kind of search, but it should be more broadly applicable.</description>
		<content:encoded><![CDATA[<p>Susan, yes, great point. It shows that Google apparently does index the contents of SVG files, and could present them in their search results in more useful ways.  Your specific search is clever and useful for a particular kind of search, but it should be more broadly applicable.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: MarkC</title>
		<link>http://schepers.cc/formata-non-grata#comment-177</link>
		<dc:creator>MarkC</dc:creator>
		<pubDate>Wed, 14 Jul 2010 07:15:57 +0000</pubDate>
		<guid isPermaLink="false">http://schepers.cc/?p=160#comment-177</guid>
		<description>Jeff, the Wordpress side of the problem is more down to using the ComicPress theme which inserts our comic images directly without providing access to the code.
 
There&#039;s also the mixed capabilities of SVG-enabled browsers to consider. It&#039;s not too bad right now, but when IE9 lands anyone using it to view the SVG versions of our comics won&#039;t get any of the filters appearing, for example. The object tag lets you fall back to PNG when the browser doesn&#039;t support SVG at all, but to fallback when there &lt;em&gt;is&lt;/em&gt; SVG support but it lacks some essential features would require quite a bit more work.
 
Hopefully in a post-IE9 future ComicPress, or something similar, will make it easier to automate this process. Perhaps let you upload an SVG file, auto-parse it for essential requirements, and auto-fallback based on the browser capabilities. I suppose I can dream...
 
Even where support is present the rendering isn&#039;t always the same, of course - the  text on your comics (love the OuijaPad, BTW) tends to leak out of the  speech bubbles on my Ubuntu+Firefox system, and I&#039;ve noticed similar  issues with my own comics when viewed in a browser.</description>
		<content:encoded><![CDATA[<p>Jeff, the WordPress side of the problem is more down to using the ComicPress theme which inserts our comic images directly without providing access to the code.<br />
 <br />
There&#8217;s also the mixed capabilities of SVG-enabled browsers to consider. It&#8217;s not too bad right now, but when IE9 lands anyone using it to view the SVG versions of our comics won&#8217;t get any of the filters appearing, for example. The object tag lets you fall back to PNG when the browser doesn&#8217;t support SVG at all, but to fallback when there <em>is</em> SVG support but it lacks some essential features would require quite a bit more work.<br />
 <br />
Hopefully in a post-IE9 future ComicPress, or something similar, will make it easier to automate this process. Perhaps let you upload an SVG file, auto-parse it for essential requirements, and auto-fallback based on the browser capabilities. I suppose I can dream&#8230;<br />
 <br />
Even where support is present the rendering isn&#8217;t always the same, of course &#8211; the  text on your comics (love the OuijaPad, BTW) tends to leak out of the  speech bubbles on my Ubuntu+Firefox system, and I&#8217;ve noticed similar  issues with my own comics when viewed in a browser.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Susan</title>
		<link>http://schepers.cc/formata-non-grata#comment-174</link>
		<dc:creator>Susan</dc:creator>
		<pubDate>Tue, 13 Jul 2010 23:31:43 +0000</pubDate>
		<guid isPermaLink="false">http://schepers.cc/?p=160#comment-174</guid>
		<description>As a newbie to SVG, I find examples by searching for the string i&#039;m looking for, such as &#039;path d=&#039;  and I get some nice hits.  The search results are based on the content of the document.</description>
		<content:encoded><![CDATA[<p>As a newbie to SVG, I find examples by searching for the string i&#8217;m looking for, such as &#8216;path d=&#8217;  and I get some nice hits.  The search results are based on the content of the document.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jeff Schiller</title>
		<link>http://schepers.cc/formata-non-grata#comment-172</link>
		<dc:creator>Jeff Schiller</dc:creator>
		<pubDate>Tue, 13 Jul 2010 19:25:27 +0000</pubDate>
		<guid isPermaLink="false">http://schepers.cc/?p=160#comment-172</guid>
		<description>Ergh, I never know when angly-brackets will get escaped or not.  That should be
 
&lt;object style=&quot;padding-left:75px&quot; width=&quot;600&quot; height=&quot;900&quot; type=&quot;image/svg+xml&quot; data=&quot;http://www.codedread.com/comics/005.svgz&quot;&gt;[img element with png fallback here]&lt;/object&gt;</description>
		<content:encoded><![CDATA[<p>Ergh, I never know when angly-brackets will get escaped or not.  That should be<br />
 <br />
&lt;object style=&#8221;padding-left:75px&#8221; width=&#8221;600&#8243; height=&#8221;900&#8243; type=&#8221;image/svg+xml&#8221; data=&#8221;http://www.codedread.com/comics/005.svgz&#8221;&gt;[img element with png fallback here]&lt;/object&gt;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jeff Schiller</title>
		<link>http://schepers.cc/formata-non-grata#comment-171</link>
		<dc:creator>Jeff Schiller</dc:creator>
		<pubDate>Tue, 13 Jul 2010 19:24:36 +0000</pubDate>
		<guid isPermaLink="false">http://schepers.cc/?p=160#comment-171</guid>
		<description>MarkC, Cool - I like to hide a couple easer eggs in my SVG comics too.  I haven&#039;t figured out the right way to automate the rasterize, fallback, embedding thing, but I found it pretty straightforward to just do this:
 
&lt;object style=&quot;padding-left:75px&quot; width=&quot;600&quot; height=&quot;900&quot; type=&quot;image/svg+xml&quot; data=&quot;http://www.codedread.com/comics/005.svgz&quot;&gt; ... put img referencing png here ... &lt;/object&gt;
 
directly in the WordPress editor.  As long as it&#039;s one line, I don&#039;t think WP should munge up the elements...
 
See http://www.codedread.com/blog/archives/2010/04/01/005/</description>
		<content:encoded><![CDATA[<p>MarkC, Cool &#8211; I like to hide a couple easer eggs in my SVG comics too.  I haven&#8217;t figured out the right way to automate the rasterize, fallback, embedding thing, but I found it pretty straightforward to just do this:<br />
 <br />
&amp;lt;object style=&#8221;padding-left:75px&#8221; width=&#8221;600&#8243; height=&#8221;900&#8243; type=&#8221;image/svg+xml&#8221; data=&#8221;http://www.codedread.com/comics/005.svgz&#8221;&amp;gt; &#8230; put img referencing png here &#8230; &amp;lt;/object&amp;gt;<br />
 <br />
directly in the WordPress editor.  As long as it&#8217;s one line, I don&#8217;t think WP should munge up the elements&#8230;<br />
 <br />
See http://www.codedread.com/blog/archives/2010/04/01/005/</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: MarkC</title>
		<link>http://schepers.cc/formata-non-grata#comment-164</link>
		<dc:creator>MarkC</dc:creator>
		<pubDate>Tue, 13 Jul 2010 11:18:38 +0000</pubDate>
		<guid isPermaLink="false">http://schepers.cc/?p=160#comment-164</guid>
		<description>&quot;MarkC, have you considered proactively publishing in SVG with a PNG  fallback?&quot;
I did consider it early on, but decided against it for a couple of reasons:
1) We use Wordpress with the ComicPress theme for the site for speed and simplicity, and I don&#039;t know of a straightforward way to implement SVG+fallback code in that environment without creating the sort of maintenance issues we&#039;re trying to avoid in the first place
2) Even amongst browsers that do display SVG, not all renderers are equal. I usually test with Firefox which does a reasonable job of rendering the comics, but not perfect (when compared with the results we see in Inkscape). As we consider our primary output to be the comic itself, with promoting Inkscape and SVG as secondary to that, we&#039;d rather have a &quot;fixed&quot; version of each strip that renders essentially identically across browsers.
I&#039;d like to use the SVG as the primary output eventually - the filesizes (expecially when gzipped) are usually smaller for a start, not to mention the possibilities offered by SMIL and Javascript*, but the browser support and associated tools just aren&#039;t good enough yet. I will continue to keep an eye on the situation though, and hope to be able to revise that position one day.
 
* As an incentive to download the SVG files, each of our comics contains one or more Easter Eggs, which are usually only accessible in the SVG. Some of those eggs do use JS if the file is loaded in a browser, and we&#039;re experimenting with SMIL-based Easter Eggs which will probably be used once Firefox 4 is released.</description>
		<content:encoded><![CDATA[<p>&#8220;MarkC, have you considered proactively publishing in SVG with a PNG  fallback?&#8221;<br />
I did consider it early on, but decided against it for a couple of reasons:<br />
1) We use WordPress with the ComicPress theme for the site for speed and simplicity, and I don&#8217;t know of a straightforward way to implement SVG+fallback code in that environment without creating the sort of maintenance issues we&#8217;re trying to avoid in the first place<br />
2) Even amongst browsers that do display SVG, not all renderers are equal. I usually test with Firefox which does a reasonable job of rendering the comics, but not perfect (when compared with the results we see in Inkscape). As we consider our primary output to be the comic itself, with promoting Inkscape and SVG as secondary to that, we&#8217;d rather have a &#8220;fixed&#8221; version of each strip that renders essentially identically across browsers.<br />
I&#8217;d like to use the SVG as the primary output eventually &#8211; the filesizes (expecially when gzipped) are usually smaller for a start, not to mention the possibilities offered by SMIL and Javascript*, but the browser support and associated tools just aren&#8217;t good enough yet. I will continue to keep an eye on the situation though, and hope to be able to revise that position one day.<br />
 <br />
* As an incentive to download the SVG files, each of our comics contains one or more Easter Eggs, which are usually only accessible in the SVG. Some of those eggs do use JS if the file is loaded in a browser, and we&#8217;re experimenting with SMIL-based Easter Eggs which will probably be used once Firefox 4 is released.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: ddailey</title>
		<link>http://schepers.cc/formata-non-grata#comment-162</link>
		<dc:creator>ddailey</dc:creator>
		<pubDate>Mon, 12 Jul 2010 21:04:04 +0000</pubDate>
		<guid isPermaLink="false">http://schepers.cc/?p=160#comment-162</guid>
		<description>Doug, some historic data on Google and other search engines as one looks for SVG and allied terms may be found at 

&lt;a href=&quot;http://portal.acm.org/citation.cfm?id=1414614&amp;coll=GUIDE&amp;dl=GUIDE&amp;CFID=62775187&amp;CFTOKEN=83901696&amp;ret=1#Fulltext&quot; rel=&quot;nofollow&quot;&gt;http://portal.acm.org/citation.cfm?id=1414614&amp;coll=GUIDE&amp;dl=GUIDE&amp;CFID=62775187&amp;CFTOKEN=83901696&amp;ret=1#Fulltext&lt;/a&gt;

cheers
David</description>
		<content:encoded><![CDATA[<p>Doug, some historic data on Google and other search engines as one looks for SVG and allied terms may be found at </p>
<p><a href="http://portal.acm.org/citation.cfm?id=1414614&amp;coll=GUIDE&amp;dl=GUIDE&amp;CFID=62775187&amp;CFTOKEN=83901696&amp;ret=1#Fulltext" rel="nofollow">http://portal.acm.org/citation.cfm?id=1414614&#038;coll=GUIDE&#038;dl=GUIDE&#038;CFID=62775187&#038;CFTOKEN=83901696&#038;ret=1#Fulltext</a></p>
<p>cheers<br />
David</p>
]]></content:encoded>
	</item>
</channel>
</rss>

