https://bugs.documentfoundation.org/show_bug.cgi?id=155384
--- Comment #13 from ady <adylo811...@gmail.com> --- (In reply to Pierre Fortin from comment #12) > (In reply to ady from comment #10) > > So... rather than fixing what I consider a rookie coding error, the user is > expected to abandon work on a HUGE spreadsheet (often 14-15M rows) Let me clarify my comment then. There is indeed a problem. The fixed-width selection should not trim the second/last column. Additionally, the width of the last column should not strictly depend on some kind of scanning or look-up of the first few rows. The current result acts as if the second column's width was somehow selected/delimited, but the user didn't do that. The problem is that the last column's width is limited in the dialog and it seems it cannot be marked in any way in order for it to be wider. (At least the data is not completely lost.) Having said that, care should be taken if solving this issue, I could imagine some case in which someone complains in the opposite direction (e.g. the last column is too wide and contains unwanted characters, not seen in the dialog). It seems as if somehow some lookup is performed in order to hint about some columns' widths; when solving this problem, care should be taken not to delay the dialog too much (for instance if there are many columns and many rows). I am able to overcome the case by using the "Separated by" alternative when importing the first time the csv (no need to copy after the initial import), but, again, this is because the relevant column is not the _last_ one. So, clearly, there is some problem when importing, with the "last" column's width. -- You are receiving this mail because: You are the assignee for the bug.
