The summary of a text is edited in the user interface language, instead of the text body language, i.e. my user interface is in french, but when I write a text in portuguese and want to add the summary, the division terms ('title", "chapter"...) appear in frenche.
Thank you for reporting the bug. Unfortunately without clear steps to reproduce it, we cannot track down the origin of the problem. Please provide a clearer set of step-by-step instructions on how to reproduce the problem. I have set the bug's status to 'NEEDINFO'. Please change it back to 'UNCONFIRMED' once the steps are provided
Concern about the writer I use to write texts in different languages (english, portuguese, french), but my interface language is the same, i.e; french. If I want to build a summary with the titles and pages, I want it to be in the same language as the text: i.e. Chapter or Capitulo or Chapitre. Unfortunately, the language of the summary is always in the interface language, in french. I temperarily solved the problem by installing different versions of the the software with different interface languages.
There is no function to provide "summary of a text", or to "build a summary", and I don't think you mean the AutoAbstract feature[1]. A screen clip is most helpful here to identify the part of the GUI you are working with. For now I'll just guess that you are referring to constructing a "Table of Contents", setting index and style levels? If that is the case, you need to simply define additional styles [1] at each outline level for each language. Then apply correct style as needed for each element of the TOC. You are correct that a "default" set of styles provided will be by OS locale, or language of the Locale setting: as set in Tools -> Options -> Languages. =-ref-= [1] from the File -> Send -> Create AutoAbstact button [2] see the default list of styles used per level in the dialog "Table of Contents, Index, or Bibliograry" opened from main menu Insert -> Table of Contents and Index
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 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-20180129
Dear Bug Submitter, 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-20180302