I noticed this was mentioned a while back but it seems as if it wasn't addressed. I just downloaded a copy of the spreadsheet and it still shows the Runed Cardinals as 25sp instead of 23. It also shows the same for the Runed Stormjewel.

There are no plans for me personally making a version of this operational for openoffice. This is mostly due to time constraints.

Looks like the database has been updated. In free time when not feeling lazy i am writing a program for automation the getting the information on items, so soon™ might be able to tell what items are still missing.
Edit. My item parser works in such way: one manually gets html text with items, manually truncates info from it, with winword replaces some text with line breaks, saves result in text file, and only than treats the file to program. Having commas in unexpected places(e.g., item name) doesn't help writing. Getting all ways to get the item isn't easy when item can be obtained in various ways.
Edit2.items2_for_excel.zip is now testable. As always, usage of executables is on your own risk. How to use it: open Items - World of Warcraft in your favorite browser, choose the slot, click apply filter, click view source, select all, paste in notepad, save it. Double click the program, input the file name, and 3 new files should appear. The ones you would like to see, end with 1.txt and 2.txt. Open them with Excel and watch the result. The program shouldn't work with trinkets(one still may try to get the correct link).

That would be really handy! If/when you get it up and running give me a jingle. On another note, currently I'm planning out the rewrite of the sheet and plan on making two versions. One will be for WotLK and the other for Cata; hopefully this will make the transition between expansions effortless.

Yeah, adding loot to the Gearlist will error out the calculation, because the lists that the gear and buffs sheet uses are separated from the gearlist itself due to how vlookup works. Thus when the gearlist puts that item into the gear setup, it will cause all the vlookup functions to spit reference errors everywhere and cascades down everything eventually causing the vba code to error. This is one of the big things I'm going to work on in my rewrite, that and some kind of automated method for updating the databases.

Sorry to bug you but any ETA on 3.3? I'm curious how HT is weighing in against Nourish these days.

When Pain has one ready to work with 3.3 a new thread will be started. Since it's currently out of date I'm going to lock this so we don't end up with a bunch of folks posting for update status.