Last modified: 2012-08-27 10:54:10 UTC
Created attachment 10086 [details] screenie for history page on my browser http://id.wikisource.org/w/index.php?title=Wikisource:Warung_kopi&curid=49&action=history&uselang=en There's script error when reverting a user with Arabic script username, even though the name itself shows correctly on his edit log. I assume this is a problem with my browser (FF 3), hence I mark it as trivial. But probably there's an underlying difference on the code for handling non-Latin characters between the two actions.
Edit: -okay for IE 6 and IE 9 -okay for Chrome 11 and a little bit funny on Chrome 17 -not displaying (!) on Safari 5.1.1 -extra bold on Opera 11 -okay for FF 10
Looks fine for me at the given link in both Safari 5.1.2 and FF 3.6.23 on MacOS 10.6.8.
Hi Benny! It's probably a Firefox 3 bug, but i'm wondering whether it happens only with Arabic or are other scripts affected, too. Can you try it with other scripts? For example, create the user "बेनि लिन" (that's "Benny Lin" in Devanagari), edit a sandbox using it, and then revert the edit.
Or probably it depends on a font that hasn't been installed in the particular machine? Because I checked on different Firefox 3.0 yesterday and it was fine. Just curious because obviously the two strings (on the contributor name, and on the revert summary) using different method of displaying Arabic character. Maybe its not Unicode? But I'll try your suggestion, Amir.
Created attachment 10235 [details] try with devanagri script
it's fine with Devanagri. Let's try Arabic or Hebrew, maybe it's because the RTL script.
I tried to reproduce this bug in FF 3.6(Windos XP SP2 and Ubuntu), FF 14(Windows 7), IE8(WIndows 7) Results http://crossbrowsertesting.com/users/34057/screenshots/z892a31276a2b6b2fc09/public and http://crossbrowsertesting.com/users/34057/screenshots/za33990113ec51befec7/public As you can see, script rendering error is not happening. It could be a bug in FF3, but no point in reporting it upstream since it is very very old. And as you pointed out it can be any configuration issue from the OS you tried. So I am closing it, thanks for reporting the issue.
