Created attachment 97861 [details] bullet list font styles are not correct I downloaded the .docx file found at < http://download.microsoft.com/documents/rus/microsoft4you/How_to_license_the_operating_system_Windows_8_new.docx > and opened it in Kingsoft Writer 9.1.0.4280 < http://wps-community.org/download.html > and then saved it as a rtf file. Then i opened the saved file in LibO and on all pages that contain bullet list items, the text isnt correct as the import of styles isnt correct. It should also be noted that number list numbers, which is present on page 3, appear like '10!br0ken!!' rather than '1.'. Tested in LibO 4.1+. Earlier versions are not able to open it.
Created attachment 97862 [details] list of applied styles
Created attachment 97863 [details] rtf file created with kingsoft writer
Wow, this looks bad. Tested using Windows 8.1 with LibreOffice Version: 4.3.0.0.alpha1+ Build ID: f4a6837025a293312cbc43b9c527851362f11030 TinderBox: Win-x86@47-TDF, Branch:MASTER, Time: 2014-04-26_09:21:18 Looks like a RTF version produced using Word 2013 looks a bit better. So might be also some issues related to Kingsoft Writer. Kind regards, Joren
Nope not an issue related to kingsoft writer as i tested the rtf in word 2010 and it didnt have the same problems.
I've submitted another bug report for the broken numeric list character showing as '10!br0ken!!' issue. bug 78506.
(Win7 Ultimate 64bit) RTF import alters the paragraph style named "Default". User changes the font of the "Default" style. User saves document az RTF. Reopens: the font changes back to Times New Roman. Similar happens with line spacing (changes back to single from any other. Same with space below paragraph (changes back to 0) Background color behaves more erratic: it is remains changed (ie red) in the dialog, but the document does not display it. Other issues are to be invetigated. The preview of the recent docs at the initial Writer window is correct!
Migrating Whiteboard tags to Keywords: (filter:rtf)
** 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 (5.1.6 or 5.2.3 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 helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug-20170103
Created attachment 136572 [details] applied styles in 6.0 There are 7 styles currently being applied and the document does look close to the original so its a fix for me.