https://bugs.documentfoundation.org/show_bug.cgi?id=89683
--- Comment #27 from Turtle <tur...@think-electric.com> --- (In reply to Mike Kaganski from comment #25) > (In reply to Turtle from comment #24) > > Unfortunately, your post gives nothing new to the discussion already > happened here. It is a common place that there's a RFC (which is, btw, just > a memo to summarize some existing and most common elements of the huge > variety of existing (and pre-existing) CSV flavors). It is known that some > people open CSVs when already work with text files. > > FTR: the correct code pointer is not comment 1, but comment 4 (so it is > PlainTextFilterDetect::detect which needs to be changed, it this request is > implemented). > > Let me summarize the arguments. > > 1. In favor of the change: > > 1.1. CSV is a tabular format, and it is exceptionally rare to want to open > it in Writer, in which case, there is a mechanism to explicitly choose the > filter. > 1.2. Opening it differently depending on the currently active document may > be seen as unexpected and counter-intuitive- by people who are well-aware > that LibreOffice is a monolithic application. > 1.3. Writer is not a text editor anyway; so it not suited to edit plain text > documents - if so wanted, users would use notepad/gedit for such a task. > 1.4. The extensions like CSV, TSV, XLS (also often used in CSVs) is usually > given explicitly to automatize opening in the spreadsheet application. > > 2. In favor of the current behavior: > > 2.1. Exactly contrary to 1.2, for people who are used to the concept that > each module is "separate" (e.g., coming from MS Office), the behavior that > when a file is opened using Writer menu, it would be opened in Calc, would > be counter-intuitive; such people would rather open CSVs not from Writer > menu, but e.g. from file browser. Current behavior is consistent with, say, > what Word does. Opening a file depending on its extension is usually not > done from another application's recent list or file open dialog. Again, file > browser (or OS-provided recent files list) is used for such a task. > 2.2. There is an "easy" way to customize behavior using extension provided > in comment 18. (Only for those who reads this issue here.) > 2.3. Current behavior allows to use command line's "--writer" together with > the file name, to tell which module to use, and avoid specifying the exact > filter name. > > Personally I do not see a compelling reason for the change. Thanks for the summary, I agree with all points other than 2.1. While I have been exclusively a openoffice then libreoffice user since 2002 (21 years) so I can't say I have any experience with Microsoft word, I did just now try to reproduce 2.1 by signing up for a free trial version of word and opening a CSV file it opens with excel. I would also change 1.1 to Opening a CSV into calc from writer would be part of a normal supported work flow. In the work flow scenario where a user opens writer and is typing a document such as a letter, it would be logical for a user to refer to a CSV spreadsheet, such as to copy and paste a few numbers from a downloaded data file, then close the csv and continue composing in writer. It makes no logical sense to open a CSV into writer and use it as a text editor and should not be a supported work flow, other than with an extension. Also add: 1.5 When in calc if one needs to open a .txt file and refer to it, the text file should be opened with writer. As text/plain is not a spreadsheet format. Thanks again for your consideration. -- You are receiving this mail because: You are the assignee for the bug.
