Description: In this file all the special character like "space" and "(" are displayed with code like "_x0020_" and "_x0028_" In MSO the file is displayed OK. There's no way in LO to fix the problem (i dont't think find & replace is a useful way) but if you open the file in mso2013 and you do any change and save (even deleting an empty line) the file is ok both in lo and mso. This file is created by an automation in SAS Enterprise Guide. Steps to Reproduce: just open the file with lo Actual Results: all the special character like "space" and "(" are displayed with code like "_x0020_" and "_x0028_" Expected Results: special character should be displayed correctly Reproducible: Always User Profile Reset: Yes Additional Info: User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/54.0.2840.71 Safari/537.36
Created attachment 128641 [details] xlsx file for test
Created attachment 128642 [details] screenshot of what is displayed in lo
Created attachment 128643 [details] screenshot of what is displayed in MSO2013/16
Confirmed in Version: 5.3.0.0.alpha1 Build ID: f4ca1573fcf445164c068c1046ab5d084e1b005f CPU Threads: 4; OS Version: Linux 4.2; UI Render: default; VCL: gtk2; Locale: ca-ES (ca_ES.UTF-8); Calc: group and LibreOffice 3.3.0 OOO330m19 (Build:6) tag libreoffice-3.3.0.4
This document seems to encode also non-alphanumeric characters with a method that is meant to represent not allowed XML characters. MS-Excel does that for control characters below 0x20 but there's absolutely no need to use that as it is done here. For further details see also https://bugs.documentfoundation.org/show_bug.cgi?id=80149#c5 However, the generator that created this document first hand should not write this encoded form. *** This bug has been marked as a duplicate of bug 80149 ***