3) Upgrade to the latest version of Spreadsheet::ParseExcel (or at least test on a system with an upgraded version). The issue you are reporting may already have been fixed.

4) Create a small example program that demonstrates your problem. The program should be as small as possible. A few lines of codes are worth tens of lines of text when trying to describe a bug.

5) Supply an Excel file that demonstrates the problem. This is very important. If the file is big, or contains confidential information, try to reduce it down to the smallest Excel file that represents the issue. If you don't wish to post a file here then send it to me directly: jmcnamara@cpan.org

6) Say if the test file was created by Excel, OpenOffice, Gnumeric or something else. Say which version of that application you used.

7) If you are submitting a patch you should check with the maintainer whether the issue has already been patched or if a fix is in the works. Patches should be accompanied by test cases.

This is not a problem in SaveParser, but in Spreadsheet::WriteExcel. The '5.14' is making it to Spreadsheet::WriteExcel::Worksheet::_store_colinfo(), but it goes through some conversions to pixels and then to 'users units' and ends up as '1462' which shows as '5' in the spreadsheet. Adding 20 to this gives the correct '5.14' in the spreadsheet, but I'm not familiar enough with the conversion to know what's supposed to happen there. Will open a ticket on WriteExcel after checking to see if the issue is fixed already there, but am rejecting here.