Description: Skipping 0,0 (comma) when tabulator is too 'narrow' when importing *.txt data file (0,036 gives 36) 1. This is a part of my data set (*.txt tab separated values): Link to this file: https://ufile.io/f/7oehs or https://www.filehosting.org/file/details/973352/1%20-%20comma%20decimal.TXT Measured values X (mm) Fn (mN) Measured Fn (mN) Ft (mN) AE (%) Pd (nm) Profile (nm) Time (sec) 0,0015 30 32,0721 20,646 24,4323 2926,1563 247,1246 0,5213 0,006 30 31,0988 24,905 24,4262 2910,1531 287,8362 0,5744 0,0105 30 29,132 30,8598 24,5012 2896,7961 358,37 0,6285 0,015 30 31,7393 32,1116 24,5447 2968,1101 417,3061 0,6827 0,021 30 31,242 32,6437 24,6638 3001,9473 463,5856 0,7549 0,0255 30 31,6702 31,976 24,6346 2993,0344 498,3948 0,809 0,03 30 32,3578 31,0657 24,6293 2981,5125 515,8998 0,8632 0,036 30 32,7266 31,433 24,5747 2996,2732 521,0854 0,9353 (Pasting from this text does not roproduces a bug. Bug appears in attached file). 2. When importing that file some values (about 2%) without zero, comma and further zeros (0,000...). In this case values are entered as if there was not a decimal fraction but integer: eg. 0,036 --> 36 No mater if UTF-8 is choosen or other coding. Different languages also does not play any role. And no mater if 'Identify special numbers' is set. Microsoft Office recognizes this data set properly, and all versions of LibreOffice (7.1.4.2; 7.2.2.2; 7.2.4.1) and OpenOffice (4.1.11) I've tested on Windows have this issue. Further circumstances: 1. In import dialog numbers are separated and displayed correctly. 2. After loading data to spread sheet some data loses zeros and comma at the begining of line. Actual Results: When using comma decimal separator "," in some values zeros and commas are skipped. When using dot decimal separator "." every number are recognized properly. Expected Results: Software should recognize numbers separated by commas. Reproducible: Always User Profile Reset: No Additional Info: Version: 7.2.2.2 (x64) / LibreOffice Community Build ID: 02b2acce88a210515b4a5bb2e46cbfb63fe97d56 CPU threads: 8; OS: Windows 10.0 Build 19044; UI render: Skia/Raster; VCL: win Locale: pl-PL (pl_PL); UI: pl-PL Calc: threaded
Created attachment 177003 [details] Numerical data set with tab columns separator and comma as decimal separator
This is not a bug. You are importing the text using a locale that uses comma as thousand separator. That means that *when a text looks like 0 followed by comma followed by exactly three digits* - e.g., "0,036", it's recognized as number 0036. In other locales using different thousand separators, it could look like "0 036", or "0'036". Use a correct locale ("language" - see bug 138748 for the term ambiguity) when you import the data, to correctly treat comma as decimal separator; or mark the column as text, to avoid its interpretation altogether.
Thank you!