Created attachment 162255 [details] Edited horror novel Also, in the same documents, large chunks of text are marked as having been inserted that were there originally and were not edited. Happening in .rtf, .doc, and .docx. The number-preceding-italics and fake-insert problems have been happening for a long time, but the latest file now also has uncuttable question marks preceding every title/heading … which DO paste into InDesign! Attaching latest file with the problems.
Hello, I've tried to reproduce the bug you had reported, but it works for me. First, I opened an empty document with Track Changer on. Next, I added a few titles and headers and then saved the file as .doc and .docx. When I reopened the files, there were no extra question marks added in the document. Please let us know if these continue to be issues. Thank you.
This is a bit problematic to analyse without having a known good state. The known good document should also preferably be in .odt format. The number strings are not random upon reopen, but can be seen if opening the file in a text editor. I investigated the question marks by removing markup from a line in a text editor. At least I found out that the question mark disappears, if I remove \ls2 \ According to the spec, ls means: \ls Should exactly match the ls for one of the list overrides in the List Override table. \ls The (1-based) index of this \listoverride in the \listoverride table. This value should never be zero inside a \listoverride, and must be unique for all \listoverrides within a document. The valid values are from 1 to 2000. http://www.biblioscape.com/rtf15_spec.htm We have to focus on a single issue per report in any case. Are you able to create an .odt file, which works fine, but then exhibits one of the problems when saved to .rtf?
Set to NEEDINFO. Change back to UNCONFIRMED after you have provided the document.
Created attachment 163300 [details] Example file for time being
Created attachment 163302 [details] Another alternative
(In reply to Buovjaga from comment #2) > This is a bit problematic to analyse without having a known good state. The > known good document should also preferably be in .odt format. > > The number strings are not random upon reopen, but can be seen if opening > the file in a text editor. > > I investigated the question marks by removing markup from a line in a text > editor. At least I found out that the question mark disappears, if I remove > \ls2 \ > > According to the spec, ls means: > > \ls Should exactly match the ls for one of the list overrides in the List > Override table. > > \ls The (1-based) index of this \listoverride in the \listoverride table. > This value should never be zero inside a \listoverride, and must be unique > for all \listoverrides within a document. The valid values are from 1 to > 2000. > > http://www.biblioscape.com/rtf15_spec.htm > > We have to focus on a single issue per report in any case. > > Are you able to create an .odt file, which works fine, but then exhibits one > of the problems when saved to .rtf? I don't generally have problems with documents I've created from scratch. These problems occur with documents I'm sent to edit for my work. These are usually compilations of Word files, sometimes generated from OCR, often subsequently saved as .rtf. But the problems don't appear until after I've used Record Changes in LibreOffice. I'm not sure what you mean about opening the file with a text editor and making the changes you propose; while I've worked with HTML, I've never worked with the background code for Word or LibreOffice documents.
Is it possible the upload a 'fine' document (so not broken in advance) Ideally with some steps to generate a broken file.. but original file it least give some pointers
Dear demiurge, 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
I'm not able to create a document that causes problems. I'm assuming these errors stem from platform/software conflicts. It's frustrating because these errors (insertion of number strings preceding italics) only occur in files after I've proofread them. Obviously, this is causing trouble with my employment. No, it's not a virus or malware at my end.
(In reply to demiurge from comment #9) > I'm not able to create a document that causes problems. I'm assuming these > errors stem from platform/software conflicts. It's frustrating because these > errors (insertion of number strings preceding italics) only occur in files > after I've proofread them. Obviously, this is causing trouble with my > employment. No, it's not a virus or malware at my end. Already updated to the latest version? Ideally 7.1 but 7.0 would do. there where improvements which could have an positive impact
Hello Demiurge, a new major release of LibreOffice is available since this bug was reported. Could you please try to reproduce it with the latest version of LibreOffice from https://www.libreoffice.org/download/libreoffice-fresh/ ? I have set the bug's status to 'NEEDINFO'. Please change it back to 'UNCONFIRMED' if the bug is still present in the latest version.
Dear demiurge, Please read this message in its entirety before proceeding. Your bug report is being closed as INSUFFICIENTDATA due to inactivity and a lack of information which is needed in order to accurately reproduce and confirm the problem. We encourage you to retest your bug against the latest release. If the issue is still present in the latest stable release, we need the following information (please ignore any that you've already provided): a) Provide details of your system including your operating system and the latest version of LibreOffice that you have confirmed the bug to be present b) Provide easy to reproduce steps – the simpler the better c) Provide any test case(s) which will help us confirm the problem d) Provide screenshots of the problem if you think it might help e) Read all comments and provide any requested information Once all of this is done, please set the bug back to UNCONFIRMED and we will attempt to reproduce the issue. Please do not: a) respond via email b) update the version field in the bug or any of the other details on the top section of our bug tracker Warm Regards, QA Team MassPing-NeedInfo-FollowUp