[frameworks-ktexteditor] [Bug 280645] [BiDi/Unicode] If the BiDi algorithms is too complicated to maintain, why not to support the simple one???
https://bugs.kde.org/show_bug.cgi?id=280645 --- Comment #11 from AvidSeeker --- Thank you for your work. I just tested the feature on kate 24.02.2 and it works. However, RTL and LTR text directions are mutually exclusive. It doesn't make sense to have it as a checkbox instead of a toggle. This makes the common operation of switching directions hard to reach. Compare this with how other programs implement it like Firefox where it is only a single shortcut that toggles the text direction: Ctrl+Shift+X. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-ktexteditor] [Bug 280645] [BiDi/Unicode] If the BiDi algorithms is too complicated to maintain, why not to support the simple one???
https://bugs.kde.org/show_bug.cgi?id=280645 Waqar Ahmed changed: What|Removed |Added CC||waqar@gmail.com Resolution|NOT A BUG |FIXED --- Comment #10 from Waqar Ahmed --- Fixed now. To force RTL direction, "View -> Force RTL Directino" To force LTR directino, disable dynamic wrapping. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-ktexteditor] [Bug 280645] [BiDi/Unicode] If the BiDi algorithms is too complicated to maintain, why not to support the simple one???
https://bugs.kde.org/show_bug.cgi?id=280645 AvidSeeker changed: What|Removed |Added CC||avidseek...@protonmail.com --- Comment #9 from AvidSeeker --- Relevant issue: https://bugs.kde.org/show_bug.cgi?id=468151 Possible merge: https://invent.kde.org/frameworks/ktexteditor/-/merge_requests/537 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-ktexteditor] [Bug 280645] [BiDi/Unicode] If the BiDi algorithms is too complicated to maintain, why not to support the simple one???
https://bugs.kde.org/show_bug.cgi?id=280645 Christoph Cullmann changed: What|Removed |Added Resolution|--- |NOT A BUG Status|REPORTED|RESOLVED --- Comment #8 from Christoph Cullmann --- Dear user, this wish list item is now closed, as it wasn't touched in the last year and no contributor stepped up to implement it. The Kate/KTextEditor team is small and we can just try to keep up with fixing bugs. Therefore wishes that show no activity for a years or more will be closed from now on to keep at least a bit overview about 'current' wishs of the users. If you want your feature to be implemented, please step up to provide some patch for it. If you think it is really needed, you can reopen your request, but keep in mind, if no new good arguments are made and no people get attracted to help out to implement it, it will expire in a year again. We have a nice website https://kate-editor.org that provides all the information needed to contribute, please make use of it. Patches can be handed in via https://phabricator.kde.org/differential/ Greetings Christoph Cullmann -- You are receiving this mail because: You are watching all bug changes.
[frameworks-ktexteditor] [Bug 280645] [BiDi/Unicode] If the BiDi algorithms is too complicated to maintain, why not to support the simple one???
https://bugs.kde.org/show_bug.cgi?id=280645 --- Comment #7 from Safa Alfulaij --- (In reply to Diego Iastrubni from comment #6) > Safa, that is not correct. In our current implementation, > direction=alignment. > > That said, I do see some scenarios in which "first strong character of > paragraph" fails as an algorithm. Here you are, some screenshots :) This is in Windows, but it's the exact same in ArchLinux (Kate 16.04.1, Qt 5.6, KF 5.22) Word-wrap on: http://i.imgur.com/3uxv2vK.png Word-wrap off: http://i.imgur.com/L8B8dDG.png And this is Windows notepad where alignment=direction: RTL text order active: http://i.imgur.com/76XnPma.png RTL text order inactive: http://i.imgur.com/1QaH4gw.png -- You are receiving this mail because: You are watching all bug changes.
[frameworks-ktexteditor] [Bug 280645] [BiDi/Unicode] If the BiDi algorithms is too complicated to maintain, why not to support the simple one???
https://bugs.kde.org/show_bug.cgi?id=280645 --- Comment #6 from Diego Iastrubni --- Safa, that is not correct. In our current implementation, direction=alignment. That said, I do see some scenarios in which "first strong character of paragraph" fails as an algorithm. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-ktexteditor] [Bug 280645] [BiDi/Unicode] If the BiDi algorithms is too complicated to maintain, why not to support the simple one???
https://bugs.kde.org/show_bug.cgi?id=280645 Safa Alfulaij changed: What|Removed |Added CC||safa1996alful...@gmail.com --- Comment #5 from Safa Alfulaij --- I don't see any use of making such a button. The current implementation of bidi text is quite fine. Word-wrap (off): All the text is aligned to left, while the direction of each is correct. RTL text have RTL direction, and LTR text have LTR direction. Word-wrap (on): Text is aligned depending on it's direction. So Arabic/Hebrew text is aligned to right, and English text is aligned to left. And the text direction of both is correct. To conclude: Direction-ality is reserved for both RTL and LTR text. Just the alignment differs and that's totally fine. -- You are receiving this mail because: You are watching all bug changes.
