Last modified: 2014-02-12 23:38:26 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 T19125, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 17125 - Correct rendering of ViewAPC for non-latin characters
Correct rendering of ViewAPC for non-latin characters
Status: NEW
Product: MediaWiki extensions
Classification: Unclassified
APC (Other open bugs)
unspecified
All All
: Normal normal with 1 vote (vote)
: ---
Assigned To: Nobody - You can work on this!
: i18n
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2009-01-23 06:51 UTC by fryed-peach
Modified: 2014-02-12 23:38 UTC (History)
2 users (show)

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


Attachments

Description fryed-peach 2009-01-23 06:51:45 UTC
<a href="http://www.mediawiki.org/wiki/Extension:APC">Extension:APC</a> doesn't properly generate a statics image in Japanese characters (probably other non-latin characters too). See http://translatewiki.net/wiki/File:ViewAPC.png for example. It is a partial screenshot of Special:ViewAPC (a special page showing APC statics) showing the bottom table titled "Detailed memory usage and fragmentation" ("メモリ使用および断片化の詳細" in Japanese) there. It shows some broken characters after arabic numerals the in statics image. Correctly, they would be "キロバイト" or some other Japanese text. Compare the text message below the image. Please display http://translatewiki.net/wiki/Special:ViewAPC in various language settings.

It will need a sophisticated way for drawing localized texts to images in MediaWiki.
Comment 1 Brion Vibber 2011-02-14 01:17:54 UTC
The basic problem is that the text-drawing routine used (imagestring()) only supports 8-bit fonts.

Unicode strings can be drawn with imagestringttf(), but a font file would need to be provided with sufficient coverage for whatever language(s) might be selected.

Best fix is probably to replace the server-side GD drawing with client-side drawing -- let the browser deal with the text -- or export to SVG and then run through the standard SVG transforms, letting whatever font configuration has been set up for SVG still happen there.

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


Navigation
Links