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 66808 - Text file import breaks on unknown characters
Text file import breaks on unknown characters
Status: RESOLVED FIXED
Product: Gnumeric
Classification: Applications
Component: import/export Text
git master
Other All
: Low enhancement
: ---
Assigned To: Andreas J. Guelzow
Andreas J. Guelzow
Depends on:
Blocks:
 
 
Reported: 2001-12-12 17:01 UTC by abs
Modified: 2004-12-22 21:47 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description abs 2001-12-12 17:01:17 UTC
The text file import will ignore any data in a file after a NULL byte is
encountered, plus if any character not in the current locale is found it
will refuse to load the file. In the latter case an option to ignore the
issue and continue would be ideal, and indicating the line number would
help a little.
Comment 1 Jody Goldberg 2001-12-12 18:18:05 UTC
We are currently in a hard freeze with a 1.0 release pending in the next couple
of weeks.  There are several known issues like this in the importer that we'll
address after porting to gnome2 and switching to utf8 internals.
Comment 2 Andreas J. Guelzow 2003-05-06 00:10:31 UTC
What is the usefulness of being able to import files that have null
bytes in them.

I understand the need to be able to import files that have been
created in any encoding, but are you suggesting that gnumeric ought to
import some arbitrary byte files as strings?

Comment 3 abs 2003-05-06 09:14:02 UTC
The case in point were CSV files with characters not in the current
locale, and in one case with a null byte. 
Comment 4 Andreas J. Guelzow 2003-05-06 12:56:01 UTC
- CSV files with characters not in the current
locale

I am in the process of fixing this in cvs head. (In fact it has
already been fixed for csv/tsv non-configurable import: you can choose
the encoding of the imported file.)

- in one case with a null byte

Since I am not aware of any encoding with characters with a leading
null byte, this should be a case of multi byte characters with a
second or later byte being null. In this case it will be  or has been
fixed as part of the first item.
Comment 5 Andreas J. Guelzow 2003-05-08 03:37:21 UTC
text import in cvs head now provides the possibility of selecting the
encoding of the to be imported file. This should fix this problem.