<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:iweb="http://www.apple.com/iweb" version="2.0">
  <channel>
    <title>Bug Blog</title>
    <link>http://www.benspratling.com/biblexpress/Bug_Blog/Bug_Blog.html</link>
    <description>This is a blog about bugs in BibleXpress.  This is where you’ll find the latest information about what we know doesn’t work, if we’ve fixed it, what update it’ll be fixed in, and what you can do in the meantime.</description>
    <generator>iWeb 2.0.4</generator>
    <image>
      <url>http://www.benspratling.com/biblexpress/Bug_Blog/Bug_Blog_files/BibleXpress%20super%20artwork.jpg</url>
      <title>Bug Blog</title>
      <link>http://www.benspratling.com/biblexpress/Bug_Blog/Bug_Blog.html</link>
    </image>
    <item>
      <title>Bugs in 1.4</title>
      <link>http://www.benspratling.com/biblexpress/Bug_Blog/Entries/2009/1/4_Bugs_in_1.4.html</link>
      <guid isPermaLink="false">2f3074ab-f15f-4319-b4d2-3c9905ebd7c6</guid>
      <pubDate>Sun, 4 Jan 2009 17:46:32 -0600</pubDate>
      <description>Some Psalms display blank in KJV, or cause a crash.&lt;br/&gt;Index search results to chapters over 127 will cause a crash when attempting to display them.&lt;br/&gt;The bugs have been found fixed and uploaded to Apple, in version 1.4.1.&lt;br/&gt;-Ben</description>
    </item>
    <item>
      <title>Bug fix 1.3.1 uploaded</title>
      <link>http://www.benspratling.com/biblexpress/Bug_Blog/Entries/2008/11/10_Bug_fix_1.3.1_uploaded.html</link>
      <guid isPermaLink="false">3c1f13c4-d3de-44a2-b37e-975ced7061ac</guid>
      <pubDate>Mon, 10 Nov 2008 15:58:53 -0600</pubDate>
      <description>This morning I uploaded bug fix 1.3.1 which corrects the problems with text formatting missing in the NASB, LBLA, and NRSV.  It does not however, fix the smaller problems of some incidental errors in text formatting.  I had intended to solve those this week and release a 1.3.5 that had all those bugs fixed, but the need to place most of the text formatting back in those two translations took precedence.&lt;br/&gt;    Besides, it means y’all get the new features from 1.3.5 a week early :)&lt;br/&gt;&lt;br/&gt;It will probably take about a week for 1.3.1 to become available, so you might see it around Friday or Saturday.</description>
    </item>
    <item>
      <title>Missing formatting in some translations</title>
      <link>http://www.benspratling.com/biblexpress/Bug_Blog/Entries/2008/11/7_Missing_formatting_in_NASB_in_1.3.html</link>
      <guid isPermaLink="false">1b704fc7-cf7d-478d-b53b-274050e5cfa2</guid>
      <pubDate>Fri, 7 Nov 2008 22:02:58 -0600</pubDate>
      <description>The formatting attributes such as red letters, small caps, and footnote superscripts are mysteriously missing from some translations in version 1.3.  Even ones that were present during testing...  The error is in the data files.  I’m furiously working on a fix right now.</description>
    </item>
    <item>
      <title>Bookmark freeze bug</title>
      <link>http://www.benspratling.com/biblexpress/Bug_Blog/Entries/2008/10/7_Bookmark_freeze_bug.html</link>
      <guid isPermaLink="false">9a60a13e-9fc9-4f5e-9441-df16586a7dd7</guid>
      <pubDate>Tue, 7 Oct 2008 10:56:48 -0500</pubDate>
      <description>There is a bug that sometimes causes importing bookmarks with verse notes to fail and the application to freeze.  It is not known if this bug crept in at version 1.2.1 or 1.2.2.&lt;br/&gt;The bug has been patched in update 1.2.3 and I’m attempting to upload it to Apple right now.&lt;br/&gt;In addition, I made some speed improvements so importing a large number of bookmarks should go much faster.</description>
    </item>
    <item>
      <title>Some formatting in NASB is not correct</title>
      <link>http://www.benspratling.com/biblexpress/Bug_Blog/Entries/2008/9/17_Some_formatting_in_NASB_is_not_correct.html</link>
      <guid isPermaLink="false">e425cbf8-56d3-448c-8ad7-5813487e867a</guid>
      <pubDate>Wed, 17 Sep 2008 14:06:43 -0500</pubDate>
      <description>Howdy.  Some formatting in the NASB, such as italics, is not 100% correct.  There are instances where the formatting markers interfere with each other.  The problem seems to be a conflict between the markers used to mark italics in the original NASB data files during the data format transformation process.</description>
    </item>
  </channel>
</rss>
