GNOME Bugzilla – Bug 508796
Song header has wrong direction in RTL languages
Last modified: 2010-03-07 07:26:29 UTC
The song header (below the controls) has the wrong direction when in an RTL language such as Arabic, and when the song tags are latin characters. A song name with latin characters will cause the text to be flipped, which is wrong. To remedy this, test for the direction and insert RLM at the start of the text. I will attach a patch that does this.
Created attachment 102602 [details] [review] Fix song header when in RTL
Hmm, just for your information, in the patch there is an RLM character being appended between those "".
It would be a good idea to escape the RLM character. Otherwise, the code is likely to be deleted because it doesn't appear to do anything, or get corrupted because someone used a stupid text editor, or it might choke a less capable c compiler, or...
Created attachment 102672 [details] [review] Updated Here is a better patch, using a clearer representation or RLM.
Since this does seem to make a definite improvement, I've committed it. It's not perfect, though; I'll attach an image that shows the problem I'm talking about.
Created attachment 102703 [details] Brackets in the embedded left-to-right strings aren't handled correctly.
Jonathan, unfortunately, currently that is unfixable without text analysis that probably does not belong to rhythmbox. It's unpredictable what the user will have there. Since she is running an RTL version, bets are her songs are tagged in her language. If they are not, problem happens. I'm CC'ing Behdad, may be there is a way to handle this?
See bug 413263 and bug 413266 where I have problems with brackets handling as well. Works fine in Mozilla, but not with Pango.
Can someone attach a shot of the problem before the patch? The best fix is to use different labels for the label and the song detail, so each gets its own, correct, direction. There are other fixes possible too. I need to see what the original problem was though.
This was fixed in bug 610753. *** This bug has been marked as a duplicate of bug 610753 ***