Created attachment 151486 [details] Test XLS file Calc shows messy code when open the attached xls file. This file was from an Financial Accounting ERP system, with confidential information removed in MS Excel. The expected cell values are in Simplified Chinese chars, so you need to install at least one Chinese fonts (e.g., Source Han Sans CJK SC or Noto Sans CJK SC).
Created attachment 151487 [details] Expected result screenshot (in MS Excel)
Created attachment 151488 [details] Bug result in Calc The cell values are in messy code. However, I noticed that the name of the tab is showing correct Chinese chars.
Looks like a wrong text encoding was used during import. It may already help to save the file in Excel as .xlsx instead of .xls, the binary .xls file format is notoriously known for not properly indicating which encoding is used for stored strings, especially if written by 3rd party software and not Excel, but even then..
Created attachment 151492 [details] Bug xls resaved as xlsx in Excel > It may already help to save the file in Excel as .xlsx instead of .xls See attached. The resaved xlsx file can be open in Calc without any problem.
Also reproduced in Version 4.1.0.0.alpha0+ (Build ID: efca6f15609322f62a35619619a6d5fe5c9bd5a)
Dear Kevin Suo, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug
Same results for Big5 (MS Codepage 950) files.
Everything is fine now. Tested with Version: 7.6.0.0.alpha1+ (X86_64) / LibreOffice Community Build ID: fc4f7db59152f606b6aa88cf32197700959d0f8b CPU threads: 16; OS: Linux 5.19; UI render: default; VCL: gtk3 Locale: ro-RO (ro_RO.UTF-8); UI: en-US Calc: threaded Please retest with 7.6, and if you can reproduce this bug, please change the status to New.