[Sorry for my poor English] When open the attachment with LibO, the DBCS became unreadable. HexBrowser consider it as "BIFF5/7/8 MS Excel 9x/2000/XP Worksheet". ASCII (“细”) -> CF B8 。 LibO : CF -> Ï ，B8 -> ¸ 。 ASCII (“粒”) -> C1 A3 。 LibO : C1 -> Á ，A3 -> £ 。 So, "细粒" becomes "ϸÁ£"，that's too bad... Can anybody help me? Thanks!!!!!! [Sorry for my poor English]
Created attachment 44347 [details] decode error?
Created attachment 44348 [details] this one is "BIFF2 MS Excel 2.1 Worksheet"
Hi Kong Nan, Is there a source info how did you generate the fils. It looks MS Office 2007 doesn't understand the characters either. Hi Kohei, Any ideas of this? Thanks!
[Sorry for my poor English] Oh, excel2003/2007 can show these files properly. In excel2003's "save-as" dialog, the file type is "Excel 2.1 Worksheet". Fakexls3.xls was generated with "RuiMei laboratory information system". http://ruimei.com.cn/cases_more.asp?id=1113 1.xls was uploaded from OOo community forum. http://user.services.openoffice.org/zh/forum/viewtopic.php?f=7&t=998 [Sorry for my poor English , and 我己给您发了中文邮件 ]
Here are some more example of .xls files that can't be opened correctly. You can not move around in the spreadsheets: http://www.aftonbladet.se/nyheter/article13180899.ab
[This is an automated message.] This bug was filed before the changes to Bugzilla on 2011-10-16. Thus it started right out as NEW without ever being explicitly confirmed. The bug is changed to state NEEDINFO for this reason. To move this bug from NEEDINFO back to NEW please check if the bug still persists with the 3.5.0 beta1 or beta2 prereleases. Details on how to test the 3.5.0 beta1 can be found at: http://wiki.documentfoundation.org/QA/BugHunting_Session_3.5.0.-1 more detail on this bulk operation: http://nabble.documentfoundation.org/RFC-Operation-Spamzilla-tp3607474p3607474.html
Bug still exists. Tested with LOdev 3.5.0beta2.
Still reproducable on Ubuntu 13.10 x64, LibreOffice Version: 4.2.0.1 Build ID: 420m0(Build:1) Best regards, Zeki
孔南 or Zeki, can you please post exact reproduce steps and write down what exactly to look for?
When I open the attached files with Excel 2010 SP2 I get *exactly* the same results as in LO. So the problem is in those files. Closing as NOTOURBUG.
File is opened fine with Excel 97. Cell contain stuff like this: 粉砂质泥岩岩 浅灰色3井岩 马103井岩
Looks like this was confirmed by Urmas - moving to NEW as REOPENED is only if the bug is assigned to someone which this one is not.
*** Bug 94382 has been marked as a duplicate of this bug. ***
*** Bug 96330 has been marked as a duplicate of this bug. ***
Added keyword filter:xls
Maxim Monastirsky committed a patch related to this issue. It has been pushed to "master": http://cgit.freedesktop.org/libreoffice/core/commit/?id=4f1ce46b8d65360436e09750242101b566e6186c tdf#35208 Allow choosing encoding for old Excel files It will be available in 5.2.0. The patch should be included in the daily builds available at http://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: http://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback.
Solved by introducing a new "Microsoft Excel - Choose Encoding" entry in the file picker, which will open a window with encoding list to choose from.
*** Bug 90210 has been marked as a duplicate of this bug. ***
The patch is going to be reverted, so back to NEW.
Maxim Monastirsky committed a patch related to this issue. It has been pushed to "master": http://cgit.freedesktop.org/libreoffice/core/commit/?id=373ef6eeb026a03b2198c3517d23daf282189702 Revert "tdf#35208 Allow choosing encoding for old Excel files" It will be available in 5.2.0. The patch should be included in the daily builds available at http://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: http://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback.
The early versions of Microsoft Office save their document as ANSII. maybe they check stealthy that is ANSII or not ,but ...... yes they save them as the ANSII. So when you check what codepage that it is, you maybe get the Null value sometime. and if you set the null to the some codepage internal ,you will get the error at somewhere. So we will need change it manually way to fix ,when we got the error.
Bug still exist Version: 5.2.2.2 Build ID: 8f96e87c890bf8fa77463cd4b640a2312823f3ad CPU Threads: 4; OS Version: Linux 4.4; UI Render: default; Locale: zh-CN (zh_CN.UTF-8); Calc: group
bug still seems to be existing see comment (3) on tdf#111406
** 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
(In reply to QA Administrators from comment #24) Bug still exists in the most recent versions.
Dear 孔南, 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
A reverse bibisect using repo https://go.suokunlong.cn:88/cgit/lo/bibisect-linux-64-7.1-CN/ has identified the following range: 75edcfc0569ca76fa22db451fd61138e52870a62..ac0112ecefd64094b150390fc36f9f56d19a4d87 and then point to the following commit which had fixed this bug: author Mike Kaganski <mike.kaganski@collabora.com> 2020-05-07 09:26:42 +0300 committer Mike Kaganski <mike.kaganski@collabora.com> 2020-05-07 12:23:40 +0200 commit ac0112ecefd64094b150390fc36f9f56d19a4d87 (patch) tdf#132796: use LO language settings to set default XLS language Reverse bibisect log: $ git bisect log # bad: [2ed31df5900ee5d392affe07497c37d6b578af99] 2020-05-30 20:49:16 +0200 80c9fae6aa8638e192e5b622d12305b304890b43 # good: [d7a13672346cb2c99df3ff6fba47ef6c73d853e0] 2019-11-13 16:51:24 +0100 9bc848cf0d301aa57eabcffa101a1cf87bad6470 git bisect start 'master' 'oldest' # good: [a402e0e4f0191597c5715d69257e5b8f2aea612d] 2020-03-10 09:26:19 +0100 edf13fe1247e7ef411a9ff5435385573fad01f56 git bisect good a402e0e4f0191597c5715d69257e5b8f2aea612d # good: [cc1dcc2c749e84c163897145b461dc6c7ae3d689] 2020-04-23 20:36:26 +0200 92b7e0fd668f580ca573284e8f36794c72ba62df git bisect good cc1dcc2c749e84c163897145b461dc6c7ae3d689 # bad: [f63bc8a6e3336816bd8ffa52fce14b552119bd47] 2020-05-11 14:34:48 +0200 da1de29f8410d352884688bd76bd07ca1c8f6ecd git bisect bad f63bc8a6e3336816bd8ffa52fce14b552119bd47 # good: [ebc91118295b44c285d864d09ac528d896915083] 2020-05-05 05:10:47 +0200 f14691683900f6b28737be8c599e1ee4e8386e14 git bisect good ebc91118295b44c285d864d09ac528d896915083 # bad: [74941347ed2b75f89a2a764aee7ffb4c09f0d5fe] 2020-05-08 14:51:19 +0200 80d44afd085c5f35e9f4698679885087318fc65d git bisect bad 74941347ed2b75f89a2a764aee7ffb4c09f0d5fe # good: [5a300d2afcc2967ff0f32902346d8ddbaebfae34] 2020-05-06 18:39:59 +0200 65b7873aab5deec7157328047e869a6385e0a74a git bisect good 5a300d2afcc2967ff0f32902346d8ddbaebfae34 # bad: [161df2d2d15fe522d4e1b96644d42c6199f310c8] 2020-05-07 15:34:53 +0200 58c87f8261abf4f1528a43dc501e956cb9c1d2f2 git bisect bad 161df2d2d15fe522d4e1b96644d42c6199f310c8 # good: [31ef17c106f7de30d11812a353521eec3d649d51] 2020-05-07 07:08:44 +0200 d7edac51367fe92c2659afdfd6e4d7c771dc5229 git bisect good 31ef17c106f7de30d11812a353521eec3d649d51 # good: [9b11df227bf5233730a3aae7b7e176662ad16182] 2020-05-07 10:58:53 +0200 75edcfc0569ca76fa22db451fd61138e52870a62 git bisect good 9b11df227bf5233730a3aae7b7e176662ad16182 # bad: [62772e502e6d857198bb05dc64973ec95a19b72f] 2020-05-07 15:21:21 +0200 403776b17706107001d49cf5eed3c4415c4d8b9d git bisect bad 62772e502e6d857198bb05dc64973ec95a19b72f # bad: [d92d1063a594b80d28ffbefb0e55aad74a15fdcd] 2020-05-07 12:23:40 +0200 ac0112ecefd64094b150390fc36f9f56d19a4d87 git bisect bad d92d1063a594b80d28ffbefb0e55aad74a15fdcd # first bad commit: [d92d1063a594b80d28ffbefb0e55aad74a15fdcd] 2020-05-07 12:23:40 +0200 ac0112ecefd64094b150390fc36f9f56d19a4d87 Mark as duplicate of bug 132796. *** This bug has been marked as a duplicate of bug 132796 ***