Single and double quotation marks are different for different written languages. Consequently, these are supposed to have per-language settings in Tools - under the "localized settings". However, if I go there, I see a grayed-out label and drop-down box at the top of the dialog: Replacements and exceptions for language [ Hebrew V] why is this grayed out? I believe it should not be.
Language selection is greyed out in the following tabs: Options | Localised Options | Word Completion. You can change language selection in the following tabs: Replace | Exceptions. I couldn't find any information in LO help. I don't see a reason for this and so I would call it a bug. But let's ask design-team.
(In reply to Eyal Rozenberg from comment #0) > why is this grayed out? I believe it should not be. I understand this as localized options are applied in all situations. The first option, space before punctuation in French, is a localized option for French text - but set globally. It's in fact a bit confusing for the double quotes as "Lorem" becomes „Lorem“ for German and “Lorem” for English although the autocorrect option is always the same (start quote = double low-9 quotation mark, U+201E).
(In reply to Dieter from comment #1) > Language selection is greyed out in the following tabs: Options | Localised > Options | Word Completion. > You can change language selection in the following tabs: Replace | > Exceptions. I couldn't find any information in LO help. I don't see a reason > for this and so I would call it a bug. But let's ask design-team. If language setting is only relevant for Replace and Exceptions tab it should be removed in other tabs.
Custom quotation marks are stored without language information in registrymodifications.xcu. And if you add language information there, it is not recognized. We had the discussion already in bug 31609 and bug 70443. I agree, it should be possible to set the quotation marks specific for a language. Especially, it should be possible e.g. to set angled quotation marks for German and keep the default replacement for other languages. I think it is a valid enhancement request.
Bug 31609 is resolved worksforme, obviously we have it properly defined in the registry. Why do you need to overwrite it? And I wonder what the options "Single/Double Quotes" are good for.
(In reply to Heiko Tietze from comment #5) > Bug 31609 is resolved worksforme, obviously we have it properly defined in > the registry. Why do you need to overwrite it? 1. It's not about me - overriding is supported, so it had been decided people need the override. 2. In Hebrew, there isn't a strong consensus on the default, and, in fact, some believe that the most common choice of opening and closing quotes is actually broken and needs to be (and can be) corrected.
Definitely a valid request. Currently, this is *either* "use built-in defaults per language for substitution for all languages", *or* "use the defined characters irrespective of current language". Having an ability to use "use built-in defaults for all languages, except for this (having manually defined substitution A) and that (having manually defined substitution B)" is a valid idea. (In reply to Heiko Tietze from comment #5) > I wonder what the options "Single/Double Quotes" are good for. Please note that https://en.wikipedia.org/wiki/Quotation_mark talks about both single and double quotation marks. The need to use a proper character for this punctuation is obvious from the very fact of its existence. Note that in other languages, it could be useful to have other two, or even *three*, different pairs of symbols (useful in nesting, or otherwise different semantically).
*** Bug 156021 has been marked as a duplicate of this bug. ***
*** Bug 156220 has been marked as a duplicate of this bug. ***
same in OOo 3.3, so inherited.
Dear Eyal Rozenberg, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug
Problem still present on Version: 25.2.4.3 (X86_64) / LibreOffice Community Build ID: 33e196637044ead23f5c3226cde09b47731f7e27 CPU threads: 8; OS: Linux 6.4; UI render: default; VCL: kf5 (cairo+xcb) Locale: es-ES (es_ES.UTF-8); UI: es-ES Calc: threaded
Still the same on: Version: 26.2.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: 7ef1c437f30b0869a5b9fa33809bac2c6665ace3 CPU threads: 4; OS: Linux 6.12; UI render: default; VCL: gtk3 Locale: en-IL (en_IL); UI: en-US
Still a problem when one uses libreoffice in multiple languages :(