[Libreoffice-ux-advise] [Bug 148257] Missing/unexposed ability to explicitly set the "language group" of a piece of text
https://bugs.documentfoundation.org/show_bug.cgi?id=148257 Heiko Tietze changed: What|Removed |Added CC|libreoffice-ux-advise@lists |heiko.tietze@documentfounda |.freedesktop.org|tion.org Keywords|needsUXEval |needsDevAdvice --- Comment #10 from Heiko Tietze --- (In reply to Eyal Rozenberg from comment #6) > It's more than about a use-case, it's a matter of principle: > > * It does not make sense that setting a direction also sets the language. > * It does not make sense, and is not tolerable, that changing the direction > of a run of text changes its font. What bothers me in general on the ticket is using the language group for layouting. But I cannot judge on this topic since it affects basic development aspects. -- You are receiving this mail because: You are on the CC list for the bug.
[Libreoffice-ux-advise] [Bug 148257] Missing/unexposed ability to explicitly set the "language group" of a piece of text
https://bugs.documentfoundation.org/show_bug.cgi?id=148257 JO3EMC changed: What|Removed |Added See Also|https://bugs.documentfounda | |tion.org/show_bug.cgi?id=14 | |4003| --- Comment #9 from JO3EMC --- I'm sorry. In Bug 144003, the automatic recognition of language groups does not seem to be wrong. It seemed that the handling of punctuation marks was just strange. -- You are receiving this mail because: You are on the CC list for the bug.
[Libreoffice-ux-advise] [Bug 148257] Missing/unexposed ability to explicitly set the "language group" of a piece of text
https://bugs.documentfoundation.org/show_bug.cgi?id=148257 JO3EMC changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=14 ||4003 --- Comment #8 from JO3EMC --- After that, I noticed ... The Bug 144003 issue in Japanese may be related to this issue. In vertical writing (RTL), Japanese characters are automatically recognized in the wrong language group when Western characters are followed by punctuation marks. -- You are receiving this mail because: You are on the CC list for the bug.
[Libreoffice-ux-advise] [Bug 148257] Missing/unexposed ability to explicitly set the "language group" of a piece of text
https://bugs.documentfoundation.org/show_bug.cgi?id=148257 --- Comment #7 from JO3EMC --- As you may know, in the current Japanese language, LTR is the basis for horizontal writing. So, no matter what the automatic language group selection works, you usually don't have to worry about mixed character directions. Of course, sentences with a mixture of Western characters (mainly English ASCII characters) and Japanese characters are common. In such cases, it is natural that the Western characters are treated as Western instead of Japanese. The current automatic recognition of LibreOffice language groups seems to work well in the Japanese environment. So I don't think we'll often encounter cases where we have to manually change language groups individually. ASCII numerical characters are also automatically recognized as Western. In Japanese, that is OK. As discussed in Bug 146910 etc., there is some need to apply the same font to both Western and CJK language groups, but that is not the same as wanting to treat them all as the same language group. It is a need to recognize them as different language groups and to be able to easily apply the same font. There are also many needs to apply different fonts to each. So far, I've talked about the situation in Japanese that seems to be related to this issue, but I haven't fully understood this issue. I'm unfamiliar with CTL and RTL and can't figure out what's wrong and how you want it to work. Please pardon. -- You are receiving this mail because: You are on the CC list for the bug.
[Libreoffice-ux-advise] [Bug 148257] Missing/unexposed ability to explicitly set the "language group" of a piece of text
https://bugs.documentfoundation.org/show_bug.cgi?id=148257 --- Comment #6 from Eyal Rozenberg --- (In reply to Heiko Tietze from comment #5) > What exactly is the use case / scenario then? Besides convenience. I thought the title of the bug made it clear... It's more than about a use-case, it's a matter of principle: * It does not make sense that setting a direction also sets the language. * It does not make sense, and is not tolerable, that changing the direction of a run of text changes its font. In the attached document, the 12:35 should not appear in the CTL font. And at the very least, it should be easy to prevent that from happening, and easy to indicate it's in English rather than Hebrew (which would make it use the Western language group font). At the moment, it just can't be done: You can't say it's in English, and you can't set its font to the Western languages group font. (You could change the CTL font to the Western language font but that's a hack, not a solution.) (I'll also say that it's not obvious what the font selection logic for "None"-language text should be, but that also would be another bug.) -- You are receiving this mail because: You are on the CC list for the bug.
[Libreoffice-ux-advise] [Bug 148257] Missing/unexposed ability to explicitly set the "language group" of a piece of text
https://bugs.documentfoundation.org/show_bug.cgi?id=148257 --- Comment #5 from Heiko Tietze --- (In reply to Eyal Rozenberg from comment #3) > ...this bug is only about language+font selection What exactly is the use case / scenario then? Besides convenience. -- You are receiving this mail because: You are on the CC list for the bug.
[Libreoffice-ux-advise] [Bug 148257] Missing/unexposed ability to explicitly set the "language group" of a piece of text
https://bugs.documentfoundation.org/show_bug.cgi?id=148257 --- Comment #4 from Eyal Rozenberg --- Moreover, even if manually changing the language group to "none" helped, that wouldn't resolve the bug, because: * People would not easily figure out that's what they need to do. * No right-click menu UI for this. * There are parity issues with MS Office for .doc and .docx document importation. * Autocorrect cannot be assumed to be applied by default, and is anyway something optional, not to be relied on. -- You are receiving this mail because: You are on the CC list for the bug.
[Libreoffice-ux-advise] [Bug 148257] Missing/unexposed ability to explicitly set the "language group" of a piece of text
https://bugs.documentfoundation.org/show_bug.cgi?id=148257 --- Comment #3 from Eyal Rozenberg --- (In reply to Heiko Tietze from comment #2) > The only issue for me is when I select the number/date - as it is RTL I > cannot mark from left. ... but that would be a whole different bug page, about selection. That is annoying, actually; would you open a separate bug about it? Anyway, to be clear, this bug is only about language+font selection, and especially the font. > But changing the language to None (we have a section > in the status bar to quickly reach language options) does the trick. I don't think so. When I did this, it set the language in all groups to "none", but the font didn't change. Which means it probably didn't change the language-group selection either. > The language group is maybe only a virtual thing meaning just at the UI, > haven't check the ODF. Although the idea to get rid of it was rejected in > bug 146910 it was at least worth to discuss. Ok. But - I'm not taking a position on that matter here. -- You are receiving this mail because: You are on the CC list for the bug.
[Libreoffice-ux-advise] [Bug 148257] Missing/unexposed ability to explicitly set the "language group" of a piece of text
https://bugs.documentfoundation.org/show_bug.cgi?id=148257 Heiko Tietze changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=14 ||6928 Severity|normal |enhancement CC||frank...@goodhorse.idv.tw, ||jo3...@jarl.com, ||libreoffice-ux-advise@lists ||.freedesktop.org, ||naru...@gmail.com, ||shinji.en...@gmail.com --- Comment #2 from Heiko Tietze --- The only issue for me is when I select the number/date - as it is RTL I cannot mark from left. But changing the language to None (we have a section in the status bar to quickly reach language options) does the trick. The language group is maybe only a virtual thing meaning just at the UI, haven't check the ODF. Although the idea to get rid of it was rejected in bug 146910 it was at least worth to discuss. Possible solution to the number problem might be to add this to the AutoCorrect options as "[ ] Use 'None' for language in case of numbers". Wonder how CJK people deal with the problem. -- You are receiving this mail because: You are on the CC list for the bug.
