Last modified: 2005-07-23 04:36:21 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 2344 - charinsert should enter UTF-8 on UTF-8 wikis
charinsert should enter UTF-8 on UTF-8 wikis
Product: MediaWiki extensions
Classification: Unclassified
CharInsert (Other open bugs)
All All
: Normal normal (vote)
: ---
Assigned To: Nobody - You can work on this!
Depends on:
  Show dependency treegraph
Reported: 2005-06-07 02:39 UTC by Andrew Dunbar
Modified: 2005-07-23 04:36 UTC (History)
0 users

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


Description Andrew Dunbar 2005-06-07 02:39:44 UTC
Currently the charinsert extension enters HTML entities for all wikis. But UTF-8 
wikis prefer all input to be in UTF-8. Certainly the English Wiktionary does. Another 
problem is that searching does not treat HTML entites and UTF-8 plain text the same, 
even with the new search engine.
Comment 1 Zigger 2005-06-07 03:31:24 UTC
The search discrepancy should be a separate report.
Comment 2 Andrew Dunbar 2005-06-07 04:02:45 UTC
Bug 1036: "Search doesn't handle special characters correctly" already covers the search 
discrepancy I mention though it's not very detailed and hasn't received any attention.
Comment 3 Brion Vibber 2005-06-07 05:27:35 UTC
Charinsert inserts UTF-8 characters if that's what you give it.

Resolving as WORKSFORME.
Comment 4 Andrew Dunbar 2005-07-23 04:36:21 UTC
Yes it was my mistake. There was no such problem.

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