https://bugs.documentfoundation.org/show_bug.cgi?id=95984
Markus Mohrhard <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |NOTABUG --- Comment #8 from Markus Mohrhard <[email protected]> --- (In reply to Milos Sramek from comment #6) > Hi, > > I see now, the file is not OK. I have not noticed that before.Thanks for > noticing that. > > I think, however, that LO should not react by hanging for a long time, but > instead it should react in a meaningful way. Otherwise it looks like a bug > in LO Well it is a broken document. This is clearly not a bug in LibreOffice. We somehow try to make sense of the content of the document. > > The best way how to deal with that would be to warn the user by a message, > e.g. "Unbalanced delimiter on line XXX" and exit - so that he or she knows > that the data is corrupt. This is not known until the whole document has been imported. > > A not so good solution would be to ignore the problem, but still to start a > new record once line end is reached. This is the approach used in LO prior > to 3.6 and in MSO. This look pretty, but the user doers not know that the > data is corrupt. Obviously this is wrong. The newline inside of a quoted part is a normal newline that is transferred to the cell content. > > It would also be good to have a third option in text delimiter setting: None -- You are receiving this mail because: You are the assignee for the bug.
_______________________________________________ Libreoffice-bugs mailing list [email protected] https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
