Last modified: 2010-05-15 16:03:22 UTC

Wikimedia Bugzilla is closed!

Wikimedia has migrated from Bugzilla to Phabricator. Bug reports should be created and updated in Wikimedia Phabricator instead. Please create an account in Phabricator and add your Bugzilla email address to it.
Wikimedia Bugzilla is read-only. If you try to edit or create any bug report in Bugzilla you will be shown an intentional error message.
In order to access the Phabricator task corresponding to a Bugzilla report, just remove "static-" from its URL.
You could still run searches in Bugzilla or access your list of votes but bug reports will obviously not be up-to-date in Bugzilla.
Bug 14108 - API should use WgOutputEncoding
API should use WgOutputEncoding
Status: RESOLVED INVALID
Product: MediaWiki
Classification: Unclassified
API (Other open bugs)
1.13.x
All All
: Normal enhancement (vote)
: ---
Assigned To: Roan Kattouw
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2008-05-13 16:03 UTC by Steve Sanbeg
Modified: 2010-05-15 16:03 UTC (History)
1 user (show)

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


Attachments

Description Steve Sanbeg 2008-05-13 16:03:17 UTC
Currently, the API just uses the web server's default encoding, while MediaWiki uses $wgOutputEncoding, which can cuase problems with frameworks that expect the whole wiki to use the same encoding.
Comment 1 Brion Vibber 2008-05-13 16:09:30 UTC
Should be always speaking UTF-8...

$wgOutputEncoding is pretty much obsolete, and probably should be removed. (There may need to be some checks to see what's interacting with the edit encoding, which I think is only being used for the Esperanto x-coding conversion.)
Comment 2 Steve Sanbeg 2008-05-13 16:24:45 UTC
Is there a recommended way to get the API to use UTF-8 then?  Like adding a heading line into LocalSettings.php or .htaccess?
Comment 3 Brion Vibber 2008-05-13 16:39:36 UTC
The charset is specified along with the Content-Type header in ApiFormatBase.php.

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


Navigation
Links