https://bugs.documentfoundation.org/show_bug.cgi?id=134154
--- Comment #13 from ady <[email protected]> --- The report is not as clear as the OP thinks. IIUC, the XLSX file is the "original" source of the info, and the CSV file is just an "extra" alternative. According to this, we should interpret that this is not an issue about importing CSV content into Calc (again, IIUC from prior OP's comments). If the XLSX file is the "original" source of info, it is yet not clear how this XLSX file was generated and by which tool. Was the data typed-in directly into an empty spreadsheet? Was the data somehow imported to an empty spreadsheet? If the latter, we would need to know the precise options that were used when importing the data. Before introducing the data (in whichever way that was done), was the spreadsheet formatted in any particular way (e.g. cells pre-formatted as Text, Number, Date, whatever)? Was it created in Calc? In Excel? In/by some other tool? Regarding point "2" in comment 0 (cells displayed on top of each other), this is typical behavior – it may or may not happen, sometimes depending on the specific version of Calc. Just modify the width of the respective columns. Regarding point "1" in comment 0, the appearance of the initial apostrophe depends on the exact way that the cells were formatted before typing-in the data, and/or the options used when importing the data. With attachment 162211 of comment 1, I don't even reproduce the "apostrophe problem"; but if I had, it would not imply that there is a bug in Calc. Moreover, Excel does it too. See, just as an example, the following forum post about Excel and the initial apostrophe when identifying data as Text while it looks as a number (and the user's intention could be either of those possibilities, or even a third one): <https://superuser.com/questions/1701039/why-does-excel-add-leading-apostrophes-to-some-of-my-text-cells> Not only I don't reproduce a bug (as described in comment 0) with attachment 162211 with a recent LO Dev 26.8 version; if I had, I would still consider it not-a-bug. -- You are receiving this mail because: You are the assignee for the bug.
