4 ms·

Windows user here. It's not particularly any prettier, and Calc doesn't open CSVs correctly anymore. So yeah, there's that. http://i.imgur.com/i1YuVXA.png http

• zuck9 12y ago
  Tried changing the encoding?
  • cheald 12y ago
    That did the trick. Flipped it to UTF-8 and it works now. I should have noticed that before, but then, I'm not sure why it's defaulting to UTF-16 for CSVs! I appreciate the UI work, but come on, the simple stuff can't break.
• chris_wot 12y ago
  Can you file a bug report and send over the file you are using?
  • cheald 12y ago
    Where should I file it?
    • chris_wot 12y ago
      https://bugs.documentfoundation.org/enter_bug.cgi https://bugs.documentfoundation.org/enter_bug.cgi So that's a UTF-8 file? Funny it's coming up with UTF-16...
      • cheald 12y ago
        Filed. https://bugs.documentfoundation.org/show_bug.cgi?id=88909 https://bugs.documentfoundation.org/show_bug.cgi?id=88909 It should just be a US-ASCII file, so yeah, UTF-8 works, while UTF-16 obviously wouldn't.
        • chris_wot 12y ago
          Cheers.
          • cheald 12y ago
            Thanks! Despite my complaining, I do use and love LibreOffice. Thanks for all your hard work!
• nkoren 12y ago
  Earlier this week I wasted 45 minutes trying to figure out why the software I've been writing was producing Chinese CSVs, before I finally thought to open them in some software other than LibreOffice. Thanks, Libre!
  • chris_wot 12y ago
    Did you change the encoding to UTF8? But it does look like our default option is now UTF-16, there's now a bug logged about this - https://bugs.documentfoundation.org/show_bug.cgi?id=88909 https://bugs.documentfoundation.org/show_bug.cgi?id=88909 Sorry that your experience wasn't great though :-(
    • nkoren 12y ago
      Yes, the encoding was UTF-8. No worries: I'm a developer too; I know these things happen. Given some of the regressions I've been dealing with recently, it was entirely believable that but was in my software -- otherwise I would have cross-checked with something else much earlier!
• berkut 12y ago
  Importing of CSVs is a joke in both OO and LibreOffice - I literally have to rename files to .csv to get them to interpret .txt (or other extensions) as comma-separated - there's no nice "Import" menu like Excel has had for decades. Even opening Calc first then using its menu to open a .txt opens the file in LibreOffice Writer! And then of course Gnome's (on Linux) file browsers no longer support renaming of files in the browsers, so you have to mess around elsewhere.
  • chris_wot 12y ago
    Have you considered filing a bug report?
  • stinky613 12y ago
    I had no idea that LibreOffice can't be forced to recognize that a .txt file is CSV; that sounds annoying. Watch out, though, for handling CSV files in Excel if you're using an encoding other than ANSI. Excel for Windows does not correctly write UTF-8 files[1] Excel for Mac lists 'UTF-8' as an import CSV encoding option but Excel for Mac does not import UTF-8 CSV files[2] [1]Response from MS employee: "Unfortunately, not all applications can encode files in UTF-8 by default, and Microsoft Excel is one of them." http://answers.microsoft.com/en-us/office/forum/office_2013_release-excel/how-can-i-save-a-csv-with-utf-8-encoding-using/12801501-c1e4-4a64-80d9-96b680b64cfe http://answers.microsoft.com/en-us/office/forum/office_2013_... [2]Response from MS employee: "Excel for Mac does not currently support UTF-8" -- despite UTF-8 being an option in Excel for Mac http://answers.microsoft.com/en-us/mac/forum/macoffice2011-macexcel/mac-excel-converts-utf-8-characters-to-underlines/7c4cdaa7-bfa3-41a2-8482-554ae235227b http://answers.microsoft.com/en-us/mac/forum/macoffice2011-m...
  • ac29 12y ago
    File a bug report, it works fine for me.