Created attachment 121263 [details] The test .ods file Unicode ExtB+ chars are not well handled in Calc. The original text of test files is "大黃䗪蟲丸狐𧌒䒜𧀬". See attachments for detail.
Created attachment 121264 [details] Fig 1. Badly displayed when exported to PDF
Created attachment 121265 [details] Fig 2. Badly displayed when saved as .xlsx or .xls
Created attachment 121266 [details] Fig 3. Badly displayed when saved as .html
I get the paste error, but they don't display correctly after save + reload. Win 7 Pro 64-bit, Version: 5.0.3.2 (x64) Build ID: e5f16313668ac592c1bfb310f4390624e3dbfb75 Locale: fi-FI (fi_FI) Version: 5.2.0.0.alpha0+ Build ID: 014633f83e44ae8ba33087b6f38e8e253e281969 CPU Threads: 4; OS Version: Windows 6.1; UI Render: default; TinderBox: Win-x86@62-merge-TDF, Branch:MASTER, Time: 2015-12-15_06:21:44 Locale: fi-FI (fi_FI) 4.3.0.1
** Please read this message in its entirety before responding ** 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 on a currently supported version of LibreOffice (5.1.6 or 5.2.3 https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the version of LibreOffice and your operating system, and any changes you see in the bug behavior If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a short comment that includes your version of LibreOffice and Operating System 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) http://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: http://webchat.freenode.net/?channels=libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug-20170103
This bug still presents on LibreOffice 5.2.3.3/Windows 7 SP1!!!
** Please read this message in its entirety before responding ** 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 http://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
The situation is even worse on Libre Office 6.1.3.2 (x64). When I attempt to read the test .ods file LO becomes non-responsive and crashes!!! Then I attempt to open a new file and paste "大黃䗪蟲丸狐𧌒䒜𧀬" in a field, LO also becomes non-responsive and crashes!!!
(In reply to Danny Lin from comment #8) > The situation is even worse on Libre Office 6.1.3.2 (x64). When I attempt to > read the test .ods file LO becomes non-responsive and crashes!!! Then I > attempt to open a new file and paste "大黃䗪蟲丸狐𧌒䒜𧀬" in a field, LO also > becomes non-responsive and crashes!!! No such problem for me. Btw. what is the font used in the original file? Does it only come with Windows? Arch Linux 64-bit Version: 6.1.3.2 Build ID: 6.1.3-2 CPU threads: 8; OS: Linux 4.19; UI render: default; VCL: gtk3_kde5; Locale: fi-FI (fi_FI.UTF-8); Calc: group threaded Version: 6.3.0.0.alpha0+ (x64) Build ID: ffa5b8a82eab18041bbee4d6914892b82c7801d3 CPU threads: 4; OS: Windows 10.0; UI render: default; VCL: win; TinderBox: Win-x86_64@42, Branch:master, Time: 2018-12-19_03:24:54 Locale: fi-FI (fi_FI); UI-Language: en-US Calc: threaded
(In reply to Buovjaga from comment #9) > (In reply to Danny Lin from comment #8) > > The situation is even worse on Libre Office 6.1.3.2 (x64). When I attempt to > > read the test .ods file LO becomes non-responsive and crashes!!! Then I > > attempt to open a new file and paste "大黃䗪蟲丸狐𧌒䒜𧀬" in a field, LO also > > becomes non-responsive and crashes!!! > > No such problem for me. > > Btw. what is the font used in the original file? Does it only come with > Windows? > > Arch Linux 64-bit > Version: 6.1.3.2 > Build ID: 6.1.3-2 > CPU threads: 8; OS: Linux 4.19; UI render: default; VCL: gtk3_kde5; > Locale: fi-FI (fi_FI.UTF-8); Calc: group threaded > > Version: 6.3.0.0.alpha0+ (x64) > Build ID: ffa5b8a82eab18041bbee4d6914892b82c7801d3 > CPU threads: 4; OS: Windows 10.0; UI render: default; VCL: win; > TinderBox: Win-x86_64@42, Branch:master, Time: 2018-12-19_03:24:54 > Locale: fi-FI (fi_FI); UI-Language: en-US > Calc: threaded Yes, as the "hardward" field stated, this issue happens on Windows. The font in the file is "新細明體" (which does not have the Ext-B chars), but LO shouldn't get crash due to unsuppported chars in the specified font.
(In reply to Danny Lin from comment #10) > Yes, as the "hardward" field stated, this issue happens on Windows. The font > in the file is "新細明體" (which does not have the Ext-B chars), but LO > shouldn't get crash due to unsuppported chars in the specified font. Yep, in my comment you can see I tested also on Windows. So is this font shipped with Chinese version of Windows only or can we download it somewhere for free?
(In reply to Buovjaga from comment #11) > (In reply to Danny Lin from comment #10) > > Yes, as the "hardward" field stated, this issue happens on Windows. The font > > in the file is "新細明體" (which does not have the Ext-B chars), but LO > > shouldn't get crash due to unsuppported chars in the specified font. > > Yep, in my comment you can see I tested also on Windows. So is this font > shipped with Chinese version of Windows only or can we download it somewhere > for free? It's a very widely used font provided in the Chinese version of Windows.
Hi, I'm closing this issue because multiple test cases have been included in this issue. Each test case has its own test file and steps to reproduce. Reporting several test cases together makes it hard to communicate the status of the issue . I'm sure some of the test cases in this issue have been fixed. Please feel free to report each test case as a separate issue. Thanks.