Last modified: 2011-08-15 20:45:42 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T32370, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 30370 - Unicode wrong siplay in summaries
Unicode wrong siplay in summaries
Status: RESOLVED WORKSFORME
Product: MediaWiki
Classification: Unclassified
Interface (Other open bugs)
1.17.x
All All
: Unprioritized normal (vote)
: ---
Assigned To: Nobody - You can work on this!
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2011-08-14 19:23 UTC by Arno Lagrange
Modified: 2011-08-15 20:45 UTC (History)
0 users

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Attachments

Description Arno Lagrange 2011-08-14 19:23:56 UTC
When some unicode stuff is put in summary, in history pages or Recent changes, it is wrong displaid

Example : 
http://eo.wikipedia.org/w/index.php?title=Uzanto:%D9%85%D8%AD%D9%85%D8%AF_%D8%A7%D9%84%D8%AC%D8%AF%D8%A7%D9%88%D9%8A&action=history
History of "eo:Uzanto:محمد الجداوي"

While copiing pasting we get a good result:
(ar:مستخدم:محمد الجداوي) 
(arz:مستخدم:Mohamed ElGedawy) 
(ar:مستخدم:محمد الجداوي en:User:محمد الجداوي)

in the history page appear squares and greek letters but not the arabic. It is confusing. 

Screen capture: http://arnolag.free.fr/Vikipedio/Unicodewrongdisplay.png
Comment 1 Brion Vibber 2011-08-15 17:27:31 UTC
Looks fine here, this is probably just your browser's or system's text rendering system having a bug and picking the wrong glyphs for the Arabic text.

Presence of Esperanto accented chars in the screenshot confirms it shouldn't be an encoding bug; the whole page should either come through or not.
Comment 2 Arno Lagrange 2011-08-15 20:45:42 UTC
Yes I have the bug with firefox and not with Google chrome, but I don't how I could fix that.

Note You need to log in before you can comment on or make changes to this bug.


Navigation
Links