Created attachment 74624 [details] File as shown in MS Office 2013 (for reference) Polish diacritics characters in form button labels are lost when importing XLSX from MS Office 2013. I am attaching: - screenshot from MS Office 2013 - screenshot from LO 4.0.0 - test document After unzipping XLSX file, I can find content in xl/drawings/drawing1.xml. These diacritics characters sits there in plain view, encoded in UTF-8. I have no problem seeing them in vim. I can also create "push button" with label containing diacritic characters in LibreOffice Calc. I have no idea if this bug involves only Polish diacritic characters, all non-ASCII characters or some other subset of UTF-8. This problem is not related to font, because - as you can see- three different typefaces were used. I can confirm this behavior on LibreOffice 3.6.5, Debian GNU/Linux (amd64). Original screenshot was taken on LO 4.0.0, Windows 8 (arch unknown). Best regards Mirosław Zalewski
Created attachment 74625 [details] File as shown in LibreOffice 4.0.0
Created attachment 74626 [details] Testing XLSX file from MS Office 2013
Confirmed with master.
** 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 (4.4.0.3 or later): 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) Thank you for your help! -- The LibreOffice QA Team This NEW Message was generated on: 2015-02-19
Confirmed. Win 7 Pro 64-bit, LibO Version: 4.4.1.2 Build ID: 45e2de17089c24a1fa810c8f975a7171ba4cd432 Locale: fi_FI
** 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.0.5 or 5.1.2 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 your help! -- The LibreOffice QA Team This NEW Message was generated on: 2016-04-16
** 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.2.7 or 5.3.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-20170522
Repro with 6.0+. Looks like regression from 3.5.0, worked with 3.4.4.
** 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
Still reproducible. Version: 6.2.0.0.alpha1+ Build ID: 5d2ab49cbda1d7aea1019478abe0163e1f40a121 CPU threads: 4; OS: Linux 4.15; UI render: default; VCL: gtk3; Locale: de-DE (de_DE.UTF-8); Calc: threaded from today
Repro 6.3+. Regression from 3.5.0, worked with 3.4.4.
Already buggy in the oldest of bibisect-43all.
*** Bug 142164 has been marked as a duplicate of this bug. ***
Code pointer: https://opengrok.libreoffice.org/xref/core/sax/source/fastparser/fastparser.cxx?r=d203d3ae#1347
Very strange behaviour in https://opengrok.libreoffice.org/xref/core/sax/source/fastparser/fastparser.cxx?r=d203d3ae#489 When there are unicode characters in the lables of buttons, textboxes, etc., there is no pContext: XFastContextHandler * pContext( maContextStack.top().mxContext.get() );
Created attachment 182989 [details] The example file in current nightly This looks good now in Version: 7.5.0.0.alpha0+ (x64) / LibreOffice Community Build ID: 73911ed8d35294a9e15771d8aaa1e9121ef10309 CPU threads: 14; OS: Windows 10.0 Build 19044; UI render: Skia/Raster; VCL: win Locale: en-US (hu_HU); UI: en-US Calc: threaded presumably after: https://cgit.freedesktop.org/libreoffice/core/commit/?id=b320ef30977144c52de9b39bc4db0db540727c79 author Caolán McNamara <caolanm@redhat.com> 2022-10-11 15:10:43 +0100 committer Caolán McNamara <caolanm@redhat.com> 2022-10-11 20:34:05 +0200 vml whitespace-check mangled Částečně to ste n
backported to 7-4 with https://gerrit.libreoffice.org/c/core/+/141185
(In reply to Gabor Kelemen (allotropia) from comment #16) > presumably after: > > https://cgit.freedesktop.org/libreoffice/core/commit/ > ?id=b320ef30977144c52de9b39bc4db0db540727c79 > > author Caolán McNamara <caolanm@redhat.com> 2022-10-11 15:10:43 +0100 > committer Caolán McNamara <caolanm@redhat.com> 2022-10-11 20:34:05 +0200 > > vml whitespace-check mangled Částečně to ste n I do confirm the issue reappears if b320ef30977144c52de9b39bc4db0db540727c79 is reverted
Xisco Fauli committed a patch related to this issue. It has been pushed to "master": https://git.libreoffice.org/core/commit/369c7d2dc4b941d5b7699b03a3cfc03ad0e3b430 tdf#60673: sc_subsequent_filters_test2: Add unittest It will be available in 7.5.0. The patch should be included in the daily builds available at https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: https://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback.