https://bugs.documentfoundation.org/show_bug.cgi?id=164250
--- Comment #8 from Eyal Rozenberg <[email protected]> --- (In reply to Mike Kaganski from comment #7) It's not that users are actively _trying_ to enable expanded/full support, and failing. The problem is that they're not trying (or at least, not trying what would actually works). So, is this a (meta-)bug about discoverability? Partially. Broadly speaking, there are two approaches to getting RTL-CTL/CJK clicked when it needs to be: * Do this automatically for the user (e.g. in some circumstances) * Make it more likely the user does it themselves Different blockers (or related bugs) improve things in one of these avenues About the "it is often the case" claim - I spoke about this in the design meeting, but the minutes are very succinct and bottom-line-ish. Let me elaborate a little: Looking at a LibreOffice module, there is nothing to lead one to believe that there may be "better RTL support", that's just disabled. You can open a document with RTL content, it will be rendered RTL, and you can insert RTL and LTR as you please. You would notice, at some point, that you can't change the RTL text's font - but again, nothing will lead you to think "oh, I just haven't told my app to _really_ support RTL". It's not like how some apps have a choice between "simple mode" and "advanced mode" when you start them up. But, one would ask, isn't RTL-CTL support enabled by default if you download a version localized for Arabic, or Farsi, or Hebrew etc.? ... Well, the thing is, it is often the case that that's not the version people have installed. Why? * Many RTL language speakers/writers prefer English UI for their OS and applications - because they're used to it, because of collaboration with others on the same machine, because it then feels weird to use the English UI when you're on some public computer, because the translation is not really there yet, etc. So, they are likely to download the "default", or English-language, LibreOffice - either by explicit choice or by the locale choice of their browser when they visit the download page. * The "default version" that gets installed if you use a package manager is typicdally not your country-localized one. This is true both for GNU/Linux distributions and for Windows package managers like WinGet or Chocolatey. -- You are receiving this mail because: You are the assignee for the bug.
