steps to reproduce: 1. open new libre office writer file by right-clicking in windows explorer, then ->new ->opendocument text. remark: in this case, the user defined .ott-file, that is used when openig a new document via -> file -> new -> textdocument (or ctrl n) is not used, but some very default opentext template with no user defined paragraph templates. 2. check, that -> extras -> autocorrection -> options for German is in standard setting. i.e. U201E set as opening quotation mark. 3. type quotation mark expected behaviour: U201E appears actual behaviour: U201C appears remark: this is the character for the closing quotation mark.
Could you verify that the language of the paragraph is actually set to German--the U+201C opening double quote is default for English. And where closing quote would be U+201D--what is the closing double quote you are receiving? The language of the current paragraph should be picked up from locale, as set in Tools -> Options -> Language Settings -> Languages If your profile has gone wonky, maybe back it up and use a clean profile. Or give the "safe mode" a try--either should pick up your OS locale.
Dear Dominik Lenné, 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 Dominik Lenné, 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
Hi, I found, that the language of the paragraph was "english/usa". When switching it to "german", the behaviour is as expected. When I opened a document via - file - open new document the user defined template is used, the paragraph language is "standard" and the behaviour is as expected. table of double quotes i get (all starting with u201) opening closing en/usa c d standard/ger e c OS: w10 actual LO version: 6.3.2.2 system language: german So, when opening a new file via - explorer - context menu - new - opendocument text the local language setting is not beeing recognized and used for the first paragraph. hth ---
(In reply to Dominik Lenné from comment #4) > So, when opening a new file via - explorer - context menu - new - > opendocument text the local language setting is not beeing recognized and > used for the first paragraph. As far as I understand your comment, this is another issue. So please file a new bug report for that. If - as you mentioned - quotation marks works as expected we can close this bug report as RESOLVED NOTABUG. Please feel free to change it again to UNCONFIRMED with a short reasoning, if you don't agree.
I found bug 90286 which is very similar and added behaviour description there. So any further work is with 90286.