BookSmart

Spellchecker Stuck

Using Blurb 1.8.1 the spellchecker can’t check more than one page without getting stuck.  Launching the spellchecker for the entire book also does not function correctly.  If I launch it, Booksmart goes to the first page of my book but does not launch the spellcheck window.  I have to select the spellchecker from the menu again to get it to launch.  Then, after checking the first page, it gets stuck transitioning to the next page.  Booksmart moves to the next page but the spellcheck window sticks on the last "mispelling" it identified on the previous page and none of the buttons in the dialog box do anything except the "Done" one.  This has basically halted my book production, as it is now impossible to spellcheck the books prior to uploading. 

There definetly needs to be some more testing before these versions are released if critical functionality like the spellchecker doesnt work on launch.  Add to that all the other issues with 1.8 and it seems this version was rushed.

Replytopic_b_normal
Posted by
cdenslow
Aug 29, 2007 1:38am PDT
Permalink
cdenslow
 

Remember, Blurb is relatively a new company. So, the BookSmart is still in beta stage. And, in fact, it is continuing to improve. As I understand that Blurb software engineering team are currently working on next version of BookSmart. However, I do not know when it will be officially released, though. I assume sometime in autumn, I believe.

However, you are strongly encouraged to submit a feedback or suggestion through Blurb contact form to address software enhancement feature.

Hope that helps.

Posted by
brianbonitz
Aug 29, 2007 12:00pm PDT
Permalink
brianbonitz
 

Being a "new company" is not a valid excuse for shoddy testing practices.  It’s also kind of ridiculous for them to continually claim an application is beta when its at version 1.8.  Seems to me this is a cop out. I know I wouldn’t be able to get away with that in software I develop. 

 I will give blurb credit though, they got back to my support request on this very quickly and confirmed it was a bug (duh!).  They also claim it will be fixed in version 1.9, probably due out in a couple of weeks.  Of course, this will be too late to get my book done when it needs to be though.  If I had not invested significant time in doing blurb books, I would be moving to another provider.  This is an inexcusable bug.  It should have been caught in testing prior to release.  Since Blurb provides no path backwards to old releases, there is really no option except to stop work. 

I hope Blurb clears this up soon, this is two out of the last three versions that have had really bad issues of one kind or another and its getting really frustrating to put a lot of work into books only to have uneccessary roadblocks appear.  After all, Blurb doesn’t see a dime until I print something, so it would be in their best interests to actually enable that to happen.  I think they need to seriously consider doing limited external betas of the pre-release versions to start catching more of these issues because it seems like the book makers are better at finding the issues than the dev team is at this point.

  

Posted by
cdenslow
Aug 29, 2007 1:25pm PDT
Permalink
cdenslow