It seems no to be foreseen that with Libre Office Writer one can make a comment into a text passage that already is marked up with another comment: a nested comment so to say. Visually it sometimes look like the comment #2 is embedded in the comment#1. But if you save the output and extract the zip and look into content.xml a comment#2 that you included into a comment#1 will not be shown and strange behavior can be seen. Faulty behavior becomes more explicit ones the ODT is reloaded: no nested comments visible. We would have needed this functionality of nesting one comment into another one for our W3C ITS2.0 Implemenation of Libre Office (more info on: http://www.init.de/en/libreofficeWriter). There we want to create and readout comments using the UNO API but now will use bookmarks to stick additional information to a text. Ways to reproduce: 1.) Create a new Writer Document 2.) Write some text 3.) Make a selection on text 4.) Insert an annotation #1 5.) Make a subselection on the large annotation 6.) Insert an annotation #2 7.) Make a subselection on the large annotation again 8.) Insert an annotation #3 9.) Save the Document to ODT / ODF (both buggy) 10.) Close Writer 11.) open content.xml with an editor and see comments not inserted properly or reopen ODT in a new libre office writer and see the missing comments Behaviour seen in LO 3.6.5 and 4.0.1 on Windows platform
Sure - we don't have conversational or nested comments; it's an enhancement we'd like - we're accepting patches of course :-)
We have now reply to a comment. Could you test with a newer version? Aslo is possible to select a part of the comment and to reply to that, taht part being cited inside. Version: 7.3.0.0.alpha0+ / LibreOffice Community Build ID: 5aa74aa1e6fac571f99146ebcb6adc9feb1459ad CPU threads: 4; OS: Linux 5.8; UI render: default; VCL: gtk3 Locale: ro-RO (ro_RO.UTF-8); UI: en-US TinderBox: Linux-rpm_deb-x86_64@86-TDF, Branch:master, Time: 2021-07-28_19:35:14 Calc: threaded
Dear init-bugzilla, 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
Dear init-bugzilla, 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