The 24.0.8 update displays more information about potential problems with (loading) text files:
-
If invalid utf8 sequences are found in .txt/.csv files (which typically occurs when this is an ansi/iso text file that doesn’t use utf8 encoding), GS-Calc will now display the incorrect byte
in the hex format along with the surrounding text. -
If some data cells/fields in a given text file exceed the 1K cell size limit, GS-Calc now displays information where the first text cell is that was split into subsequent sheet cells and how many additional cells were generated due to the overflowing data (whereas in previous versions GS-Calc displays only general info that some splitting occurred).
-
Users can now choose whether over-1K cells should be split into subsequent cells or truncated.
-
In both the above solutions the truncated or split cells are displayed in red and you can easily browse them using the “Format > Cell Style Palette” then “Find Next/Previous” to walk through cells formatted with that red font.
Bug fixes:
-
If the above splitting 1K occurs exactly in the middle of some UTF8 sequence of 3-4 bytes, in the previous versions characters in both these parts were displayed incorrectly at these positions. (This could also generate error messages if you tried to Find/Replace that cell using regular expressions.
-
When opening UTF16 file the first character is skipped.
-
Due to the system library version mismatch, in the latest (previous) update Python UDF functions were inactive.
-
The included “sample.gsc” file contained charts created in an old GS-Calc version and to complete the conversion, if they were resized, one had to click the “max” button in the main chart dialog box.