This is an enhancement request based on bug id 90202. It should be possible to edit the role mapping. Ideally this should be specified as part of the style defintions. More pragmatically it should be possible to specify an external file with the preferred mapping.
(In reply to p.abrahams@clara.co.uk from comment #0) > This is an enhancement request based on bug id 90202. > It should be possible to edit the role mapping. What's the difference between this issue and bug 90202? Status -> NEEDINFO
There is no real difference. I am new to submitting problems to bugzilla and I thought that bug 90202 was trying to clarify how the product worked and the new request was for a specific request for a change to the product. Having said that I have now found ways to produce the tags I want: - I can make a title style map to H1 by Go to Tools > Outline Numbering and change the settings so that: Level 1 Paragraph style is 'Title' (this maps Title to <H1>), Level 2 is 'Heading 1' (this maps Heading 1 to <H2>) etc. - I Can map content header to h2: Go to Format > Styles and Formatting and find 'Content Heading' in Organizer change 'Linked with' to 'Heading 1'. This makes the table of contents heading appear as a <H2>. So I think both bugs can be closed. However I have found a problem in the role mapping where there are entries such as /h1 /h1 which is cyclic and considered incorrect. I will open a new bug just for that.
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 This NEEDINFO message was generated on: 2015-10-14
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 our bug tracker Warm Regards, QA Team This INVALID Message was generated on: 2016-05-09