Created attachment 132345 [details] Test database Libreoffice on Windows 10 64-bit, also tested on Windows XP 32-bit, both on Greek locale and Greek versions of Libreoffice still 5.2.6.2 I have filed this as LibO Calc issue, since there was nothing general. Could be Java- or Base-related too. I wanted to export some database tables to spreadsheets. I have attached an example test.odb base, as well as a screenshot of what the single table of this database contains, as base.png. I copy the table (right-click on table name, from the table list abd select "copy". I create a new LibO calc document and select paste. The end result is shown in the attached calc.png file. Text fields are shown with gibberish characters. Two important remarks: 1) If you closely examine calc.png, you'll observe that the very first line, which contains the table field names, is displayed correctly in Greek. If instead of LibO calc I select an empty Libo write document to paste into, characters display just fine in Greek! 2) If you examine the ODS file screenshot, you'll see that column legends (that is, the base field names) are *correctly* displayed in Greek. But not the actual data, which seems quite puzzling to me!
Created attachment 132346 [details] Resulting spreadsheet with pasted info
Created attachment 132347 [details] Table content (from database), in Greek
Created attachment 132348 [details] Spreadheet content, Greek characters from 2nd row unreadable
Works for me on OSX 10.12.3 and Version: 5.2.6.2 Build ID: a3100ed2409ebf1c212f5048fbe377c281438fdc Threads CPU : 8; Version de l'OS :Mac OS X 10.12.3; UI Render : par défaut; Locale : fr-FR (fr_FR.UTF-8); Calc: group see enclosed screenshot Is this a Win only problem ?
Created attachment 132362 [details] Screenshot of Greek char representation after copying to Calc
For the test, I tried both Copy/Paste via the menu / keyboard shortcuts, and drag and drop from Base to Calc.
(In reply to Alex Thurgood from comment #4) > Is this a Win only problem ? Beats me, perhaps someone with a different (or Greek) locale on Windows can add to this issue his/her own findings. And, BTW, I saw that you've changed the issue subject; it is not a Windows 10-only issue, it also affects my Windows XP installations.
(In reply to Alex Thurgood from comment #6) > For the test, I tried both Copy/Paste via the menu / keyboard shortcuts, and > drag and drop from Base to Calc. I was not aware that it was possible to copy/paste here with drag and drop. Results: * With drag and drop to empty Calc: SUCCESS * With copy from base and normal paste to empty Calc: FAIL * With copy from base and special paste (either RTF or HTML) to empty Calc: FAIL
(In reply to Michail Pappas from comment #8) > I was not aware that it was possible to copy/paste here with drag and drop. > Results: > > * With drag and drop to empty Calc: SUCCESS > * With copy from base and normal paste to empty Calc: FAIL > * With copy from base and special paste (either RTF or HTML) to empty Calc: > FAIL This rings a bell, as in, I think it has been reported already, so possible duplicate, but would need to check.
(In reply to Alex Thurgood from comment #9) > This rings a bell, as in, I think it has been reported already, so possible > duplicate, but would need to check. I see, I was not able to find something when searching. OT a bit, but since the bug affects 32-bit Windows (XP) as well, should perhaps Hardware be set to "All" instead of "x86-64 (AMD64)"?
Possible DUP of bug 39124 ?
(In reply to Alex Thurgood from comment #11) > Possible DUP of bug 39124 ? I believe so, from what I've read there. So, how does one proceed? Close this one as a DUP and proceed there?
Yep, don't worry, I'll do it. *** This bug has been marked as a duplicate of bug 39124 ***
(In reply to Michail Pappas from comment #12) > (In reply to Alex Thurgood from comment #11) > > Possible DUP of bug 39124 ? > > I believe so, from what I've read there. > > So, how does one proceed? Close this one as a DUP and proceed there? It would be a good idea to add your findings re 5262 to bug 39124 too, as the report keeps getting automatic queries to set to WFM or resolved, when quite clearly it isn't (at least not for JP or GR).
(In reply to Alex Thurgood from comment #14) > It would be a good idea to add your findings re 5262 to bug 39124 too, as > the report keeps getting automatic queries to set to WFM or resolved, when > quite clearly it isn't (at least not for JP or GR). Done! If you think I should add something more, I'd be happy to do so, just let me know what to add.