{"id":1065,"date":"2008-12-12T16:47:16","date_gmt":"2008-12-13T00:47:16","guid":{"rendered":"http:\/\/www.oeconomist.com\/blogs\/daniel\/?p=1065"},"modified":"2009-11-22T04:05:56","modified_gmt":"2009-11-22T12:05:56","slug":"coding-deficit","status":"publish","type":"post","link":"https:\/\/www.oeconomist.com\/blogs\/daniel\/?p=1065","title":{"rendered":"Coding Deficit"},"content":{"rendered":"<p><a href=\"http:\/\/wordpress.org\/development\/2008\/12\/coltrane\/\">WordPress version 2.7 has been released.<\/a><\/p> <p><a href=\"http:\/\/trac.wordpress.org\/ticket\/6870\">About eight months ago, when 2.51 was new, I reported a <em>bug<\/em> that had been giving me grief, a mishandling of the <abbr title=\"HyperText Mark-up Language\">HTML<\/abbr> <q><code>&lt;q&gt;<\/code><\/q> element.<\/a>  WordPress.org automatically set the target of fixing this bug by version 2.7 &mdash; which, frankly, to me seemed rather <em>unambitious<\/em>.  It's <em>one<\/em> thing not to expect to fix a <em>bug<\/em> in the very next bug-fix release, quite another to put it off for <em>two<\/em> minor versions.<\/p> <p>In any case, I've been looking forward to version 2.7.  Now it's out&#8230; &#8230;and the bug is not fixed.  In fact, I've learned that <a href=\"http:\/\/trac.wordpress.org\/ticket\/6870\">about two months ago, the target was changed to fixing the bug by version 2.<em>9<\/em>, another <em>two<\/em> minor versions away<\/a>.  And there seems no assurance that, about half-a-year from now, <em>that<\/em> target won't be reset to version 3.1.<\/p>","protected":false},"excerpt":{"rendered":"WordPress version 2.7 has been released. About eight months ago, when 2.51 was new, I reported a bug that had been giving me grief, a mishandling of the HTML &lt;q&gt; element. WordPress.org automatically set the target of fixing this bug by version 2.7 &mdash; which, frankly, to me seemed rather unambitious. It's one thing not [&hellip;]","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_bbp_topic_count":0,"_bbp_reply_count":0,"_bbp_total_topic_count":0,"_bbp_total_reply_count":0,"_bbp_voice_count":0,"_bbp_anonymous_reply_count":0,"_bbp_topic_count_hidden":0,"_bbp_reply_count_hidden":0,"_bbp_forum_subforum_count":0,"footnotes":""},"categories":[7,6,69,5,4],"tags":[51,145,146,459,13],"class_list":["post-1065","post","type-post","status-publish","format-standard","hentry","category-blog-meta","category-commentary","category-information-technology","category-personal","category-public","tag-blogs","tag-bugs","tag-html","tag-software","tag-wordpress"],"_links":{"self":[{"href":"https:\/\/www.oeconomist.com\/blogs\/daniel\/index.php?rest_route=\/wp\/v2\/posts\/1065","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.oeconomist.com\/blogs\/daniel\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.oeconomist.com\/blogs\/daniel\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.oeconomist.com\/blogs\/daniel\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.oeconomist.com\/blogs\/daniel\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=1065"}],"version-history":[{"count":0,"href":"https:\/\/www.oeconomist.com\/blogs\/daniel\/index.php?rest_route=\/wp\/v2\/posts\/1065\/revisions"}],"wp:attachment":[{"href":"https:\/\/www.oeconomist.com\/blogs\/daniel\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=1065"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.oeconomist.com\/blogs\/daniel\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=1065"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.oeconomist.com\/blogs\/daniel\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=1065"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}