[Kst] [Bug 121049] Tabular data imported as 0

Nicolas Brisset nicolas.brisset at eurocopter.com
Tue Jan 31 12:54:42 CET 2006

------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

------- Additional Comments From nicolas.brisset eurocopter com  2006-01-31 12:54 -------
I remember this problem from the time I looked at ASCII configuration options (I even thought there was a comment in the code I wrote to warn about this, but it seems to be gone now...) 
The question is actually: is it wise to ignore the rest of a line just because there is somewhere a character listed in the comment indicators ? Couldn't we just ignore that particular column ? 
I'm also curious about fixed-width columns (like 16 characters): the way it used to be, the "bad" columns could just be ignored as the offset to read from can be computed directly and we don't have to parse the whole line... No time to check this now, though... However, it could be an alternative as it's pretty easy to reformat an ASCII file with fixed-width columns with awk/python/etc...

All in all, for the short term and considering other more important changes to be made, I'd say that making the default comment indicator only "#" would be the right way to go. I think ";" is very widely used (.csv files often have those) and should not be handled as a comment indicator :-)

More information about the Kst mailing list