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 658982 - Character misinterpretation
Character misinterpretation
Status: RESOLVED FIXED
Product: Gnumeric
Classification: Applications
Component: import/export Text
git master
Other Linux
: Normal normal
: ---
Assigned To: Morten Welinder
Jody Goldberg
Depends on:
Blocks:
 
 
Reported: 2011-09-13 19:01 UTC by Andreas J. Guelzow
Modified: 2011-09-13 20:17 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
smaller sample file (68 bytes, text/csv)
2011-09-13 19:29 UTC, Andreas J. Guelzow
Details

Description Andreas J. Guelzow 2011-09-13 19:01:36 UTC
Opening the sample file attached to 658916 using the csv importer works fine. On the otehr hand importing the same file using the configurable text importer and all automatic settings causes problems in A4. A small sequence of characters there is incorrect. In fact, if one tries to import the file several times one gets slightly different results in A4 each time.
Comment 1 Andreas J. Guelzow 2011-09-13 19:29:06 UTC
Created attachment 196430 [details]
smaller sample file
Comment 2 Morten Welinder 2011-09-13 19:53:32 UTC
I get a segfault, :-(  Sometimes, that is.

  • #0 __stpcpy_sse2
    from /lib64/libc.so.6
  • #1 g_strconcat
    from /lib64/libglib-2.0.so.0
  • #2 format_match_datetime
    at number-match.c line 830
  • #3 format_match
    at number-match.c line 1257
  • #4 stf_cell_set_text
    at stf-parse.c line 1206
  • #5 stf_parse_sheet
    at stf-parse.c line 1310

Comment 3 Morten Welinder 2011-09-13 19:56:40 UTC
Valgrind is complaining over itself and isn't useful here.

However, I believe that "fmt" as acquired on number-match.c:819 must be
ref'd if we want "time_format" to remain valid after line 822.  Or else
we must g_strdup "time_format".
Comment 4 Morten Welinder 2011-09-13 20:00:36 UTC
That problem is now fixed.  Please see if you still have the original
problem.