<?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 for Simplish</title>
	<atom:link href="http://simplish.pomfolio.com/comments/feed/" rel="self" type="application/rss+xml" />
	<link>http://simplish.pomfolio.com</link>
	<description>is a kind of Scribbish</description>
	<lastBuildDate>Wed, 26 Jan 2011 00:04:29 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.5.1</generator>
	<item>
		<title>Comment on Simplish version 2.5.1 by Simplish version 2.5.2 &#8211; Simplish</title>
		<link>http://simplish.pomfolio.com/dev/2011/01/18/simplish-251/comment-page-1/#comment-235</link>
		<dc:creator>Simplish version 2.5.2 &#8211; Simplish</dc:creator>
		<pubDate>Wed, 26 Jan 2011 00:04:29 +0000</pubDate>
		<guid isPermaLink="false">http://simplish.pomfolio.com/?p=356#comment-235</guid>
		<description><![CDATA[[...] 2.5.2 has all the fixes and features noted in the posts for 2.4.1 and 2.5.1, and adds an updated Greek localization courtesy of Demetris, and a couple fixes for ol and ul list [...]]]></description>
		<content:encoded><![CDATA[<p>[...] 2.5.2 has all the fixes and features noted in the posts for 2.4.1 and 2.5.1, and adds an updated Greek localization courtesy of Demetris, and a couple fixes for ol and ul list [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Simplish version 2.5.1 by Josh</title>
		<link>http://simplish.pomfolio.com/dev/2011/01/18/simplish-251/comment-page-1/#comment-232</link>
		<dc:creator>Josh</dc:creator>
		<pubDate>Fri, 21 Jan 2011 05:30:02 +0000</pubDate>
		<guid isPermaLink="false">http://simplish.pomfolio.com/?p=356#comment-232</guid>
		<description><![CDATA[See the Greek translation become more and more Laconic! Ha!

(Everyone says, oh i see what you did there…)

Anyway I filed the two bug reports over at the google code and I think fixed one of them. I must have broken numbered lists back when I added the CSS reset (v2.4 or so).

Thanks as usual and as always for the help &amp; interest, D.]]></description>
		<content:encoded><![CDATA[<p>See the Greek translation become more and more Laconic! Ha!</p>
<p>(Everyone says, oh i see what you did there…)</p>
<p>Anyway I filed the two bug reports over at the google code and I think fixed one of them. I must have broken numbered lists back when I added the CSS reset (v2.4 or so).</p>
<p>Thanks as usual and as always for the help &amp; interest, D.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Simplish version 2.5.1 by demetris</title>
		<link>http://simplish.pomfolio.com/dev/2011/01/18/simplish-251/comment-page-1/#comment-230</link>
		<dc:creator>demetris</dc:creator>
		<pubDate>Wed, 19 Jan 2011 10:55:04 +0000</pubDate>
		<guid isPermaLink="false">http://simplish.pomfolio.com/?p=356#comment-230</guid>
		<description><![CDATA[Congratulations!

I just updated and pushed the Greek translations.  The number of strings has decreased pleasantly. :-)

A couple of stylistic issues I noticed:

First, OL lists do not have item numbers. It seems that their styling is reset at the beginning of the stylesheet and then no list-style-type is specified.

Second, if a list, OL or UL, is immediately followed by an element without margin-top (like a heading) the result does not look good because there is no space between the two.

A way to deal with this would be to add some margin-bottom to OL and UL. (In that case, margin-bottom:0 should be specified for OL OL, OL UL, UL OL and UL UL, to avoid extraneous spacing within lists with nested lists.)

Also, v2.5.1 made me rethink how I should deal with themes that filter get_the_excerpt in my Extra Options plugin. (I need the manual excerpt in its raw form in order to use it as a meta-description in the HTML head.) I ended up using remove_all_filters, which seems to work well for now.

Cheers!]]></description>
		<content:encoded><![CDATA[<p>Congratulations!</p>
<p>I just updated and pushed the Greek translations.  The number of strings has decreased pleasantly. :-)</p>
<p>A couple of stylistic issues I noticed:</p>
<p>First, OL lists do not have item numbers. It seems that their styling is reset at the beginning of the stylesheet and then no list-style-type is specified.</p>
<p>Second, if a list, OL or UL, is immediately followed by an element without margin-top (like a heading) the result does not look good because there is no space between the two.</p>
<p>A way to deal with this would be to add some margin-bottom to OL and UL. (In that case, margin-bottom:0 should be specified for OL OL, OL UL, UL OL and UL UL, to avoid extraneous spacing within lists with nested lists.)</p>
<p>Also, v2.5.1 made me rethink how I should deal with themes that filter get_the_excerpt in my Extra Options plugin. (I need the manual excerpt in its raw form in order to use it as a meta-description in the HTML head.) I ended up using remove_all_filters, which seems to work well for now.</p>
<p>Cheers!</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Simplish version 2.4.1 by Utopian</title>
		<link>http://simplish.pomfolio.com/dev/2010/08/06/simplish-241/comment-page-1/#comment-224</link>
		<dc:creator>Utopian</dc:creator>
		<pubDate>Tue, 10 Aug 2010 02:48:05 +0000</pubDate>
		<guid isPermaLink="false">http://simplish.pomfolio.com/?p=334#comment-224</guid>
		<description><![CDATA[The 2.4.1 version did not pass an improved WordPress/extend review process. While the 2.4.1 code works with the latest WordPress, the review pointed out many possible improvements and we expect a cleaned up new version to be re-submitted for approval soon, along with a couple of new surprise features.

You can see the review&#039;s specific objections in this ticket: https://code.google.com/p/simplish/issues/detail?id=30

And the work since on those issues and other improvements in the many changelog entries today.]]></description>
		<content:encoded><![CDATA[<p>The 2.4.1 version did not pass an improved WordPress/extend review process. While the 2.4.1 code works with the latest WordPress, the review pointed out many possible improvements and we expect a cleaned up new version to be re-submitted for approval soon, along with a couple of new surprise features.</p>
<p>You can see the review&#8217;s specific objections in this ticket: <a href="https://code.google.com/p/simplish/issues/detail?id=30" rel="nofollow">https://code.google.com/p/simplish/issues/detail?id=30</a></p>
<p>And the work since on those issues and other improvements in the many changelog entries today.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Simplish version 2.4 by Josh</title>
		<link>http://simplish.pomfolio.com/dev/2010/06/17/simplish-24/comment-page-1/#comment-223</link>
		<dc:creator>Josh</dc:creator>
		<pubDate>Thu, 05 Aug 2010 03:11:07 +0000</pubDate>
		<guid isPermaLink="false">http://simplish.pomfolio.com/?p=308#comment-223</guid>
		<description><![CDATA[You probably need to modify the &lt;code&gt;$content_width&lt;/code&gt; value set in &lt;code&gt;simplish/functions.php&lt;/code&gt; on line 5. See http://www.bloggingteacher.com/setting-max-image-size-for-your-wordpress-themes for a quick explanation.

You can use WordPress&#039;s &quot;child themes&quot; features to keep your own changes like these separated from the base theme code. See http://codex.wordpress.org/Child_Themes for the official documentation, or a tutorial at http://op111.net/53 .]]></description>
		<content:encoded><![CDATA[<p>You probably need to modify the <code>$content_width</code> value set in <code>simplish/functions.php</code> on line 5. See <a href="http://www.bloggingteacher.com/setting-max-image-size-for-your-wordpress-themes" rel="nofollow">http://www.bloggingteacher.com/setting-max-image-size-for-your-wordpress-themes</a> for a quick explanation.</p>
<p>You can use WordPress&#8217;s &#8220;child themes&#8221; features to keep your own changes like these separated from the base theme code. See <a href="http://codex.wordpress.org/Child_Themes" rel="nofollow">http://codex.wordpress.org/Child_Themes</a> for the official documentation, or a tutorial at <a href="http://op111.net/53" rel="nofollow">http://op111.net/53</a> .</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Simplish version 2.4 by Jack</title>
		<link>http://simplish.pomfolio.com/dev/2010/06/17/simplish-24/comment-page-1/#comment-222</link>
		<dc:creator>Jack</dc:creator>
		<pubDate>Thu, 05 Aug 2010 01:00:04 +0000</pubDate>
		<guid isPermaLink="false">http://simplish.pomfolio.com/?p=308#comment-222</guid>
		<description><![CDATA[Hi, I posted a large image on one of my pages, and something automatically scaled it down to fit.  Then I deleted the sidebar code from all the pages in the theme editor, but the image still stays how small it is. Full size, the image should fit in the new page (without the sidebar).   I&#039;ve tried deleting the cache. I&#039;ve tried deleting and re-uploading the picture. The sidebar is not there. I&#039;ve exhausted all the options I know of...what should I do?]]></description>
		<content:encoded><![CDATA[<p>Hi, I posted a large image on one of my pages, and something automatically scaled it down to fit.  Then I deleted the sidebar code from all the pages in the theme editor, but the image still stays how small it is. Full size, the image should fit in the new page (without the sidebar).   I&#8217;ve tried deleting the cache. I&#8217;ve tried deleting and re-uploading the picture. The sidebar is not there. I&#8217;ve exhausted all the options I know of&#8230;what should I do?</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Simplish version 2.4 by josh</title>
		<link>http://simplish.pomfolio.com/dev/2010/06/17/simplish-24/comment-page-1/#comment-213</link>
		<dc:creator>josh</dc:creator>
		<pubDate>Fri, 18 Jun 2010 07:29:08 +0000</pubDate>
		<guid isPermaLink="false">http://simplish.pomfolio.com/?p=308#comment-213</guid>
		<description><![CDATA[Seems reasonable. I&#039;ve filed two new enhancement tickets:
http://code.google.com/p/simplish/issues/detail?id=24
http://code.google.com/p/simplish/issues/detail?id=25

And thanks as always for the astute input.]]></description>
		<content:encoded><![CDATA[<p>Seems reasonable. I&#8217;ve filed two new enhancement tickets:<br />
<a href="http://code.google.com/p/simplish/issues/detail?id=24" rel="nofollow">http://code.google.com/p/simplish/issues/detail?id=24</a><br />
<a href="http://code.google.com/p/simplish/issues/detail?id=25" rel="nofollow">http://code.google.com/p/simplish/issues/detail?id=25</a></p>
<p>And thanks as always for the astute input.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Simplish version 2.4 by demetris</title>
		<link>http://simplish.pomfolio.com/dev/2010/06/17/simplish-24/comment-page-1/#comment-212</link>
		<dc:creator>demetris</dc:creator>
		<pubDate>Fri, 18 Jun 2010 06:46:29 +0000</pubDate>
		<guid isPermaLink="false">http://simplish.pomfolio.com/?p=308#comment-212</guid>
		<description><![CDATA[When I saw “Support new custom menus”, I thought for a moment you added an horizontal navigation menu to Simplish! :-o

You people are fast!  Congratulations!

If I may add two little suggestions for a future release:

1.  Change the charset declaration to the hypercompact style recommended for HTML5.  See:  http://core.trac.wordpress.org/ticket/12483

2.  Add ARIA landmark roles.  They are perfectly valid HTML5, very easy to incorporate, and recommended by the accessibility people.  See again a WordPress trac ticket:  http://core.trac.wordpress.org/ticket/13055]]></description>
		<content:encoded><![CDATA[<p>When I saw “Support new custom menus”, I thought for a moment you added an horizontal navigation menu to Simplish! :-o</p>
<p>You people are fast!  Congratulations!</p>
<p>If I may add two little suggestions for a future release:</p>
<p>1.  Change the charset declaration to the hypercompact style recommended for HTML5.  See:  <a href="http://core.trac.wordpress.org/ticket/12483" rel="nofollow">http://core.trac.wordpress.org/ticket/12483</a></p>
<p>2.  Add ARIA landmark roles.  They are perfectly valid HTML5, very easy to incorporate, and recommended by the accessibility people.  See again a WordPress trac ticket:  <a href="http://core.trac.wordpress.org/ticket/13055" rel="nofollow">http://core.trac.wordpress.org/ticket/13055</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Simplish version 2.3 by Next Simplish &#8211; Simplish</title>
		<link>http://simplish.pomfolio.com/dev/2010/05/13/simplish-23/comment-page-1/#comment-178</link>
		<dc:creator>Next Simplish &#8211; Simplish</dc:creator>
		<pubDate>Sun, 23 May 2010 12:32:53 +0000</pubDate>
		<guid isPermaLink="false">http://simplish.pomfolio.com/?p=244#comment-178</guid>
		<description><![CDATA[[...] Simplish 2.3 continues to be the official release for stable WordPress (v2.9.2). [...]]]></description>
		<content:encoded><![CDATA[<p>[...] Simplish 2.3 continues to be the official release for stable WordPress (v2.9.2). [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on New Belarusian translation by Utopian</title>
		<link>http://simplish.pomfolio.com/dev/2010/04/20/new-belarusian-translation/comment-page-1/#comment-171</link>
		<dc:creator>Utopian</dc:creator>
		<pubDate>Sun, 02 May 2010 09:48:57 +0000</pubDate>
		<guid isPermaLink="false">http://simplish.pomfolio.com/?p=239#comment-171</guid>
		<description><![CDATA[The be_BY localization files have now been &lt;a href=&quot;http://code.google.com/p/simplish/source/detail?r=8d0e20f499d3fcb55e507b413d0103be83af9f79&quot; rel=&quot;nofollow&quot;&gt;committed to the source repository&lt;/a&gt; , available via &lt;code&gt;hg pull -u&lt;/code&gt;, etc.]]></description>
		<content:encoded><![CDATA[<p>The be_BY localization files have now been <a href="http://code.google.com/p/simplish/source/detail?r=8d0e20f499d3fcb55e507b413d0103be83af9f79" rel="nofollow">committed to the source repository</a> , available via <code>hg pull -u</code>, etc.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
