Summary: | text editor's line is aligned to the right if there are more hebrew chars then english ones | ||
---|---|---|---|
Product: | [Applications] krusader | Reporter: | Nadav Kavalerchik <nadavkav> |
Component: | general | Assignee: | Shie Erlich <manson> |
Status: | RESOLVED DUPLICATE | ||
Severity: | normal | CC: | elcuco, kde-2011.08, matitiahu.allouche |
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | unspecified | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
Nadav Kavalerchik
2008-11-23 21:51:48 UTC
I agree, the first letter should determine directionality. I am almost certain that this is a dupe, though I cannot find the original bug. see this page : http://www.w3.org/International/tutorials/svg-tiny-bidi/Overview.en.php for the right way to implement the bidi algorithm. The Unicode Bidi Algorithm (UBA) states that, in the absence of a higher level protocol to specify the base direction of a piece of text, the first "strong" character (character with a clear left-to-right or right-to-left directionality) determines the base direction of the text. In most cases, left alignment is appropriate for text with a left-to-right base direction, and right alignment is appropriate for text with a right-to-left base direction, so that the first strong character is also an appropriate criterion to determine the alignment. Why is this filed as a Krusader bug? I could not get the Krusader CLI to align right at all, even with the appropriate option selected in Qt Config. For that matter, I cannot get Kate to right-align either. Mati, Dotan, This was done by design in KDE 4.1 - originally I designed katepart to choose the direction not by the first strong char, but by the most characters available. This is fixed in KDE 4.2, and it's a dup of 178594. This is not a bug in Qt4, but only in katepart. If you are using Ubuntu, please see also https://bugs.launchpad.net/ubuntu/+source/kde4libs/+bug/314016 Closing. *** This bug has been marked as a duplicate of bug 178594 *** |