The Ruby Spreadsheet

January 15, 2009

Spreadsheet 0.6.3 released

Filed under: Release, Spreadsheet — zdavatz @ 9:34 am

0.6.3 / 2009-01-14

* 1 Bugfix

* Fixes the issue reported by Corey Martella in as well as other issues engendered by the decision to always shorten Rows to the last non-nil value.

* 2 minor enhancements

* Added bin/xlsopcodes, a tool for examining Excel files

* Documents created by Spreadsheet can now be Printed in Excel and Excel-Viewer. This issue was reported by Spencer Turner in / 2008-12-18

* 1 Bugfix

* Using Spreadsheet together with ‘jcode’ could lead to broken Excel-Files Thanks to Eugene Mikhailov for tracking this one down in:


January 10, 2009

I get an error when trying to open a file with spreadsheet

Filed under: Ruby, Spreadsheet — Tags: , , — zdavatz @ 2:52 pm

Mike Potter reported that he gets an error when he try’s to open a file a file with Ruby Spreadsheet.

This is due to still having the old ParseExcel installed. You must manually uninstall that (gem uninstall parseexcel), otherwise you will run into all sorts of errors.

highlight cells and print them

Filed under: Ruby — Tags: , , , , , — zdavatz @ 2:48 pm

Another Bug-Report that came in before Christmas:

Spencer Turner reports that he can successfully write a file which can be read, in Excel, however, when he highlights cells and try’s to print them, Excel (OfficeXP on Windows XP) says it cannot find any data.

Looking at the file created in a Raw Text editor,  he does not see any BIFF text added. Once he saves it again from OpenOffice, it is there.

Update: This Bug has been solved here:;a=commitdiff;h=dc508a787f33e00dd1ca6efb88c1b4c36b08f71a

January 9, 2009

Cell all the cells of a column except the first

Filed under: Spreadsheet — Tags: , — zdavatz @ 9:21 am

Happy New Year to all of you!

We are working on the next version of Spreadsheet and squashing some bugs in the mean time. This Bug-Report comes from Corey Martella

This seems to be a Symptom of the underlying problem.

We anticipated the decision that fields that the client set to ‘nil’ (nothing) would completely be deleted from the spreadsheet. But it turns out that like that some formatting is being lost. When thinking about it, we noticed that this behavior could also be inconvenient for other cases, i.e. when a row is completed in two separate steps but after the first step ‘nil’-values still would exist at the end of the data.  Then the following fields would all be moved to the left.

Basically the goal still is to filter out empty and unformatted cells; but this has to happen later, when the file is being written.

The problem has been solved here:;a=commit;h=52755ad76fdda151564b689107ca2fbb80af3b78

Blog at