When applying a document heading style to a text span which has multiple rows then it becomes automatically also a bullets and numbering attribute, which is unuseful and has to be removed manually again in order to correct the wrong indents after the first row of this new heading.
Can you explain this with a attachment ? Is the problem not simply linked to autocorrect settings ? What if you UNCHECK all the settings on Tools -autocorrect - <Options tab> Yves
Hi Yves, yes I want to support you with more information. I am in the trouble that it passed some time meanwhile. When I reported you this bug I developed a tool which imports ODT document content into a program. The steps are the following: 1. Change the heading style of a selected text which covers multiple rows in an ODT document. 2. Then parse the XML nodes of this text span and there will we a numbering / bullet list. This might not appear on the UI but in the created XML content. Many greetings, Thomas On Dec 17, 2012, at 11:38 AM, bugzilla-daemon@freedesktop.org<mailto:bugzilla-daemon@freedesktop.org> wrote: ydutrieux@gmail.com<mailto:ydutrieux@gmail.com> changed bug 50787<https://bugs.freedesktop.org/show_bug.cgi?id=50787> What Removed Added Status UNCONFIRMED NEEDINFO Ever confirmed 1 Comment # 1<https://bugs.freedesktop.org/show_bug.cgi?id=50787#c1> on bug 50787<https://bugs.freedesktop.org/show_bug.cgi?id=50787> from ydutrieux@gmail.com<mailto:ydutrieux@gmail.com> Can you explain this with a attachment ? Is the problem not simply linked to autocorrect settings ? What if you UNCHECK all the settings on Tools -autocorrect - <Options tab> Yves ________________________________ You are receiving this mail because: * You reported the bug.
Dear Bug Submitter, 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 INVALID due to lack of needed information. For more information about our NEEDINFO policy please read the wiki located here: https://wiki.documentfoundation.org/QA/FDO/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
Dear Bug Submitter, Please read this message in its entirety before proceeding. Your bug report is being closed as INVALID 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 FDO