| Summary: | text in Writer copying to Impress shows in wrong encoding on Windows | ||
|---|---|---|---|
| Product: | LibreOffice | Reporter: | Cheng-Chia Tseng <pswo10680> |
| Component: | Impress | Assignee: | Not Assigned <libreoffice-bugs> |
| Status: | RESOLVED WORKSFORME | ||
| Severity: | normal | CC: | sasha.libreoffice |
| Priority: | medium | ||
| Version: | 4.0.1.2 release | ||
| Hardware: | All | ||
| OS: | Windows (All) | ||
| See Also: | https://bugs.freedesktop.org/show_bug.cgi?id=37859 | ||
| Whiteboard: | |||
| Crash report or crash signature: | Regression By: | ||
|
Description
Cheng-Chia Tseng
2011-08-06 19:55:22 UTC
On windows XP 32bit LibO 3.4 russian language this problem also exist. But what it interesting: when I copy text from Writer by Ctrl+V and paste it in Calc, this problem disappears until next start of LibreOffice. (into Calc it pastes as OLE object). [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 The bug still lives in Dev 3.5. not reproducible with LO 4.0.1.2 (Win7 Home, 64bit) Does this issue still persist for you with the latest release of LO? @Sasha: Do you also still have this problem or is it in the meantime already resolved so that we can close it? Not reproducible in 4.0.0 and 4.0.1 on Win XP 32 bit with Cyrillic characters @ Cheng-Chia Tseng Please, verify with Chinese characters Sorry for being late to test. :P 4.0 and 4.1 on XP 32-bit tested, not reporducible with Chinese. Maybe we can close this one now. :) As we don't know what fixes this issue, I set it to Resolved as Invalid. If it is not appropriate, then please correct it freely. |