Description: I am a Persian/Farsi user, and I usually work with Persian/Farsi language documents. Because of this, I use "Persian" locale in Libreoffice. Now that I want to create an English language document, I change the keyboard into English, and change the paragraph to left-to-right, and start typing. When I closely look at the status bar, I see Persian in the language section of the status bar, and I should type at least one character to see Englih language there. This may not seem to create problems at first, but actually it does. When I want to write quotation mark, it uses the Persian/Farsi quotation mark, and not the correct English one. Steps to Reproduce: 1. Set locale to Persian in Options > Language Settings > Languages > Locale setting 2. Change the paragraph to LTR 3. Start typing something with single or double quotation mark like: "Test" or 'Test' Actual Results: You will see that the first quotation mark is shown as « which is wrong. Expected Results: You should see the correct English quotation marks, double quotation mark " or single quotation mark '. Reproducible: Always User Profile Reset: No Additional Info: This seems to be created in LibreOffice 5.3, which fixed a lot of text rendering issues. The locale prolbems are not confined to this. Translating numerals into appropriate shapes according to the context is also wrong in LibreOffice 5.3. If you set locale to Persian, you will see all the numerals are Hindi in a completely English and LTR Impress document. User-Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:51.0) Gecko/20100101 Firefox/51.0
Created attachment 131615 [details] An examle of wrong output with double and single quotation mark.
And selecting 'English' as font language for character?, or with double-click on the status bar language to select English?
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-20170929
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-20171030
Can repo it with arabic locale. It treats the first single or double quotes as if it in the ctl language and the second quote after typing an english word as latin language. Version: 6.0.0.0.alpha1+ Build ID: 43d6b11a5c1dda0cc2c1e06c768eece25051a56c CPU threads: 2; OS: Linux 4.4; UI render: default; VCL: gtk2; Locale: ar-AE (en_US.UTF-8); Calc: group
Created attachment 137380 [details] sample
Isn't this a Unicode implementation issue? Don't these transitions between language scripts depend on our ICU library handling? But they still need additional boundary logic--otherwise as here where Unicode usage is not defined to a script, i.e. punctuation, symbols, numbers we get this type of issue at script transition(s). Is there a better way to detect/toggle word boundaries? =-ref-= [1] http://unicode.org/reports/tr29/#Word_Boundaries
related: Bug 66791: FORMATTING: Incorrect application of "Asian text font"
(In reply to V Stuart Foote from comment #7) > Isn't this a Unicode implementation issue? AFAIK, no. The itemization of text into Western/CTL/Asian (or only three categories) is done by Writer and/or other LibreOffice internal code. My guess is that is is just using the default languages for common characters and then it does not look back when it sees the first script-specific character.
Still happens in: Version: 6.0.0.0.alpha1+ Build ID: 9050854c35c389466923f0224a36572d36cd471a CPU threads: 8; OS: Linux 4.9; UI render: default; VCL: gtk3; Locale: en-US (en_US.utf8); Calc: group OS: Debian 64bit Stretch (Debian 9.2, with some backported packages)
** Please read this message in its entirety before responding ** 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 http://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://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug
Confirmed on Version: 6.3.0.0.alpha0+ Build ID: 98630a0bd49bd80652145a21e4e0d0ded792b36b CPU threads: 4; OS: Linux 4.4; UI render: default; VCL: gtk3; TinderBox: Linux-rpm_deb-x86_64@86-TDF, Branch:master, Time: 2019-05-04_04:44:35 Locale: tr-TR (tr_TR.UTF-8); UI-Language: en-US Calc: threaded
Does ODF 1.3 got solution for this?
This is still reproduce in Version: 7.2.0.1 (x64) / LibreOffice Community Build ID: 32efc3b7f3a71cfa6a7fa3f6c208333df48656cc CPU threads: 4; OS: Windows 10.0 Build 19043; UI render: Skia/Raster; VCL: win Locale: zh-CN (zh_CN); UI: zh-CN Calc: threaded
Still reproducible with the latest LO 7.5 master: Version: 7.5.0.0.alpha0+ / LibreOffice Community Build ID: 947a6455d23bff290319313734c8c30e8f495773 CPU threads: 8; OS: Linux 5.15; UI render: default; VCL: gtk3 Locale: fa-IR (en_US.UTF-8); UI: en-US Calc: threaded
I _can't_ reproduce this with: Version: 7.6.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: ad387d5b984c6666906505d25685065f710ed55d CPU threads: 4; OS: Linux 6.1; UI render: default; VCL: gtk3 Locale: fa-IR (en_IL); UI: en-US Calc: threaded but then, I never reproduced this before. I suspect perhaps the reproduction instructions are partial? Perhaps auto-correct needs to be on?
Still reproducible with the latest LO 7.6 dev master: Version: 7.6.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: 72959cc2b36749a779b56522f27e290731187043 CPU threads: 4; OS: Windows 10.0 Build 19045; UI render: Skia/Raster; VCL: win Locale: fa-IR (fa_IR); UI: en-US Calc: threaded You can reproduce it with a few steps: 1. Create a new Writer document. 2. Go to "Tools > Options > Language Settings > Languages > Default Language for Documents > Complex text layout". Set the combo box to "Persian". 3. Make the paragraph LTR using "left ctrl+ left shift" 4. Type -> "test" (including the double quotes). You will get «Test" and this is wrong.
(In reply to Hossein from comment #17) > You will get «Test" and this is wrong. I followed your instructions, and got "test". No change of quotes.
I uncommented fa_IR in my /etc/locale.gen and ran sudo locale-gen Then I launched LibreOffice with LC_ALL=fa_IR.UTF-8 libreoffice I could reproduce the issue. Arch Linux 64-bit, X11 Version: 7.5.0.3 (X86_64) / LibreOffice Community Build ID: 50(Build:3) CPU threads: 8; OS: Linux 6.1; UI render: default; VCL: kf5 (cairo+xcb) Locale: fi-FI (fi_FI.UTF-8); UI: en-US 7.5.0-1 Calc: threaded
(In reply to Buovjaga from comment #19) > Arch Linux 64-bit, X11 > Version: 7.5.0.3 (X86_64) / LibreOffice Community > Build ID: 50(Build:3) > CPU threads: 8; OS: Linux 6.1; UI render: default; VCL: kf5 (cairo+xcb) > Locale: fi-FI (fi_FI.UTF-8); UI: en-US > 7.5.0-1 > Calc: threaded Ignore the locale here, this is just my boilerplate version paste.
I believe LibreOffice could implement smart rules to assign font face, font size, text direction, etc. for such punctuations.