After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 537099 - original titles are being truncated when saved using Gnumeric
original titles are being truncated when saved using Gnumeric
Status: RESOLVED DUPLICATE of bug 535083
Product: Gnumeric
Classification: Applications
Component: General
1.9.x
Other All
: Normal minor
: ---
Assigned To: Jody Goldberg
Jody Goldberg
Depends on:
Blocks:
 
 
Reported: 2008-06-07 11:11 UTC by rob
Modified: 2008-06-07 12:15 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description rob 2008-06-07 11:11:42 UTC
Please describe the problem:
all my .xls were accessed and ran fine with this app but when saved the original titles were truncated to only 6 letters with a ~and a 1 after the 6 letters.

ie.  financial checks.xls  becomes financ~1.xls This is in windows xp sp1

Steps to reproduce:
1. create a spread sheet with excel and save with a title that has more than 1 word in it and greater than 6 characters in length

2. open the file using your app and make some changes to some of the cells and then save it.
3. 


Actual results:
The original title will be truncated using only the first 6 characters in the original title followed by ~1.xls

Expected results:
I would hope that the original title used when the file was created with Exel would remain unchanged when opened in your app and saved

Does this happen every time?
yes so far

Other information:
I would think that this should be an easy fix.  I have a lot of spread sheets and the longer titles are very helpful in understanding what each sheet is for.
Comment 1 Morten Welinder 2008-06-07 12:15:06 UTC
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.


*** This bug has been marked as a duplicate of 535083 ***