In program CALC I took some cells in a clipboard. In program Base I have inserted a clipboard on bookmark Tables. I have created the new table "Table 1", have opened it. There there is data from CALC. I have closed this table. For this table I have chosen from the context menu Copy and have inserted in CALC. In CALC there was data from BASE with an error in the text coding. I use Russian version LibreOffice, code page 1251.
Created attachment 48948 [details] it shows Adobe Captivate unpack, start libreoffice-calc-base.htm
Rainer, please check it.
Unfortunately base is not my forte, but let's see. Oleg's great movie might help. May be it's a problem with the not very mature LibO codepage detection? @Oleg: Can you please attach an additional test kit with source document and result? that would ease testing for a Base beginner like me.
Created attachment 49030 [details] Test data exchange calc->base->calc see video
[Reproducible] with "LibreOffice 3.4.1 - WIN7 Home Premium (64bit) German UI [OOO340m1 (Build:103)]" I did some further investigations, for that I saved reporter's CALC source column as a .csv (codepage 1251). When I want to get the same result like reporter saw with copy table / paste to CALC opening the .csv, I have to select a codepage "System" when I open .csv. That codepage is not available when I create the .csv Copy Base Table / Paste to Writer works without problems, the contents column looks at least very similar to the Base Table, but it's not identical Original Contents: бвгдеёжзиклмопрст Writer Result: бвгдеёжзиклмопрст Wrong CALC result: бâãäå¸æçèêëìîïðñò If my results are correct, copy Base Table / Paste to CALC wrongly changes Codepage to "System" - what ever that might mean. Because paste to WRITER works fine, I currently see that as a CALC problem, but I may be wrong. My be some further investigations by experts for Base and/or Base will be useful? @Oleg: Please contribute information concerning your - OS WIN Version and localization - LibO Localization @Kohei: Please feel free to reassign if it’s not your area or if provided information is not sufficient.
(In reply to comment #5) > [Reproducible] with "LibreOffice 3.4.1 - WIN7 Home Premium (64bit) German UI > [OOO340m1 (Build:103)]" > > I did some further investigations, for that I saved reporter's CALC source > column as a .csv (codepage 1251). When I want to get the same result like > reporter saw with copy table / paste to CALC opening the .csv, I have to select > a codepage "System" when I open .csv. That codepage is not available when I > create the .csv > > Copy Base Table / Paste to Writer works without problems, the contents column > looks at least very similar to the Base Table, but it's not identical > > Original Contents: бвгдеёжзиклмопрст > Writer Result: бвгдеёжзиклмопрст > Wrong CALC result: бâãäå¸æçèêëìîïðñò > > If my results are correct, copy Base Table / Paste to CALC wrongly changes > Codepage to "System" - what ever that might mean. > Because paste to WRITER works fine, I currently see that as a CALC problem, but > I may be wrong. > > My be some further investigations by experts for Base and/or Base will be > useful? > > @Oleg: > Please contribute information concerning your > - OS WIN Version and localization > - LibO Localization > > @Kohei: > Please feel free to reassign if it’s not your area or if provided information > is not sufficient. I have tried to work with MS Office. As a result I think that an error in BASE and WRITER. Both of them use the old agreement on text transformations. Only they understand each other. Investigations are not required any more
Since all new unconfirmed bugs start in state UNCONFIRMED now and old unconfirmed bugs were moved to NEEDINFO with a explanatory comment, all bugs promoted above those bug states to NEW and later are automatically confirmed making the CONFIRMED whiteboard status redundant. Thus it will be removed.
- OS WIN Version and localization: Windows 7 Enterprise SP1 Russian - LibO Localization: Russian
** 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.1 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) 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: 2015-04-18
(In reply to QA Administrators from comment #9) I tried to execute the test on LibreOffice 4.4.1. Error is preserved. My personal computer hat Microsoft Windows 7 SP1.
this bug is present at ja-jp, Win8.1 Pro, LibreOffice 5.1.3.2 x64
LibreOffice version is 5.0.5.2 on Wondows 7 corporate edition in this case works correctly
Since there is no specific commit fixing this issue, setting to WORKSFORME. FIXED is used only when a commit exists.
Created attachment 125681 [details] not solved it's not solved in ja-JP x64 either 5.0.6.3 nor 5.1.3.2
Correcting status to NEW.
*** Bug 106969 has been marked as a duplicate of this bug. ***
Jumping in from Bug 106969, on which I have provided test files. Summarizing, affected platforms are: - both Windows Xp and 10 - both 32 and 64 bit - LibreOffice still 5.2.6.2 - Locale Greek (el_GR), codepage 1253 I believe Interesting observations: - Dragging a Base table to an empty Calc worksheet does *not* reproduce the issue. Copying and pasting does - Copying and pasting affects the the transferred table data, but *not* the table field names (essentially, the first line of the resulting spreadsheet data). I have submitted test files *and* screenshots of how these files look on my platforms.
(In reply to Michail Pappas from comment #17) > I have submitted test files *and* screenshots of how these files look on my > platforms. ... on bug 106969.
@Eike : any idea why with drag and drop the code page is interpreted correctly, but not copy and paste (Ctrl-C/Ctrl-V or via Edit menu) ? Are different parts of the code responsible for interpreting the codepages ?
** 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
Any update with a recent LO version (eg 6.0.4 or 5.4.7 for conservative users)? Indeed, tdf#37859 seems a dup of this one.
Dear Bug Submitter, This bug has been in NEEDINFO status with no change for at least 6 months. Please provide the requested information as soon as possible and mark the bug as UNCONFIRMED. Due to regular bug tracker maintenance, if the bug is still in NEEDINFO status with no change in 30 days the QA team will close the bug as INSUFFICIENTDATA due to lack of needed information. For more information about our NEEDINFO policy please read the wiki located here: https://wiki.documentfoundation.org/QA/Bugzilla/Fields/Status/NEEDINFO If you have already provided the requested information, please mark the bug as UNCONFIRMED so that the QA team knows that the bug is ready to be confirmed. Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-NeedInfo-Ping-20181203
... > If the bug is present, please leave a comment that includes the information > from Help - About LibreOffice. ... Bug is present. Infomation About LibreOffice: Version: 6.1.3.2 (x64)
*** This bug has been marked as a duplicate of bug 126940 ***