[Libreoffice-bugs] [Bug 98507] Formatting: Character format 'spills' forward to next line in MS .doc format on fileload of Microsoft

https://bugs.documentfoundation.org/show_bug.cgi?id=98507 Doug changed: What|Removed |Added Resolution|--- |WORKSFORME Status|NEW

[Libreoffice-bugs] [Bug 98507] Formatting: Character format 'spills' forward to next line in MS .doc format on fileload of Microsoft

https://bugs.documentfoundation.org/show_bug.cgi?id=98507 --- Comment #5 from QA Administrators --- Dear Doug, 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

[Libreoffice-bugs] [Bug 98507] Formatting: Character format 'spills' forward to next line in MS .doc format on fileload of Microsoft

https://bugs.documentfoundation.org/show_bug.cgi?id=98507 --- Comment #4 from QA Administrators --- ** 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

[Libreoffice-bugs] [Bug 98507] Formatting: Character format 'spills' forward to next line in MS .doc format on fileload of Microsoft

https://bugs.documentfoundation.org/show_bug.cgi?id=98507 --- Comment #3 from Buovjaga --- Created attachment 123544 --> https://bugs.documentfoundation.org/attachment.cgi?id=123544=edit DOC for testing -- You are receiving this mail because: You are the assignee for

[Libreoffice-bugs] [Bug 98507] Formatting: Character format 'spills' forward to next line in MS .doc format on fileload of Microsoft

https://bugs.documentfoundation.org/show_bug.cgi?id=98507 Buovjaga changed: What|Removed |Added Status|UNCONFIRMED |NEW

[Libreoffice-bugs] [Bug 98507] Formatting: Character format 'spills' forward to next line in MS .doc format on fileload of Microsoft

https://bugs.documentfoundation.org/show_bug.cgi?id=98507 --- Comment #1 from Doug --- I have just compiled and tested Writer for LibreOffice 5.0.5.2 and get the same bug. I have also discovered a potential workaround, though I worry about file corruption. WORKAROUND-ISH: