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 322096 - CTRL+Shift+Enter functions don't convert
CTRL+Shift+Enter functions don't convert
Status: RESOLVED OBSOLETE
Product: Gnumeric
Classification: Applications
Component: import/export MS Excel (tm)
git master
Other All
: Normal normal
: ---
Assigned To: Jody Goldberg
Jody Goldberg
: 404829 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2005-11-22 04:49 UTC by Titus Winters
Modified: 2018-05-22 13:13 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Titus Winters 2005-11-22 04:49:46 UTC
Please describe the problem:
It looks like there is some incompatibility between Excel and Gnumeric when
using (at least some forms of) the CTRL+Shift+Enter functions.  Such functions
will work properly in Gnumeric, but when converting / exporting back to Excel
they will only show up as #VALUE.  Re-accepting the equation by selecting the
cell(s) in Excel and hitting CTRL+Shift+Enter again fixes it.  

Fairly minor, but some gnumeric related applications I've been developing would
definitely benefit if this didn't happen.

Steps to reproduce:
1. Download http://www.cs.ucr.edu/~titus/matrix_test.xls 
2. View in Excel, notice cells are properly formatted.
3. Convert to and from gnumeric (ssconvert to gnumeric, ssconvert to xls)
4. View in Excel, notice cells are improperly displayed.


Actual results:
These matrix formula cells render only as #VALUE.

Expected results:
The correct value should still be displayed.

Does this happen every time?
Yes.

Other information:
Comment 1 Jody Goldberg 2005-12-26 17:50:32 UTC
confirmed.
I've got a simple patch that can be back ported, but I'd like to do some research today to confirm that this will not cause other problems.
Comment 2 Morten Welinder 2007-03-06 00:08:05 UTC
It appears that this was fixed some time ago.

This problem has been fixed in the development version. The fix will be available in the next major software release. Thank you for your bug report.
Comment 3 Jody Goldberg 2007-03-06 19:15:09 UTC
Unfortunately this has not been fixed.  The algorithm for selecting which class of op code to use is undocumented and we're still working to improve things.
Comment 4 Andreas J. Guelzow 2009-08-27 04:50:04 UTC
How does this report differ from bug 404829?
Comment 5 Jody Goldberg 2009-08-27 05:06:36 UTC
*** Bug 404829 has been marked as a duplicate of this bug. ***
Comment 6 GNOME Infrastructure Team 2018-05-22 13:13:00 UTC
-- GitLab Migration Automatic Message --

This bug has been migrated to GNOME's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.gnome.org/GNOME/gnumeric/issues/45.