Last modified: 2010-03-28 22:40:11 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 T24031, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 22031 - deactivate Unicode normalization via <foobar>bla</foobar>
deactivate Unicode normalization via <foobar>bla</foobar>
Product: MediaWiki
Classification: Unclassified
Page editing (Other open bugs)
All All
: Normal enhancement (vote)
: ---
Assigned To: Nobody - You can work on this!
Depends on:
Blocks: unicode
  Show dependency treegraph
Reported: 2010-01-06 11:47 UTC by lɛʁi לערי ריינהארט
Modified: 2010-03-28 22:40 UTC (History)
3 users (show)

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


Description lɛʁi לערי ריינהארט 2010-01-06 11:47:50 UTC
Dear friends,

In order to document systems which do not use / did not use Unicode normalization MediaWiki should provide a way do deactivate  Unicode normalization.

Please read the discussion at .

Best regards Reinhardt [[user:Gangleri]]
Comment 1 Conrad Irwin 2010-03-28 22:37:29 UTC
You can already  include un-normalised text using HTML entities, see [[wikt:Appendix:Unicode normalization]], or as you did with manual URL encoding.

I reckon most people who know why such things are broken will be able to work out the escapes, though a utility to help them wouldn't be bad. For any given text, it requires detailed knowledge of unicode and the context to identify the few cases where normalization is destructive.

Unicode normalization is done on input, so it's hard to imagine the tag method you propose working safely and efficiently.
Comment 2 Aryeh Gregor (not reading bugmail, please e-mail directly) 2010-03-28 22:40:11 UTC
Should we avoid Unicode normalization in URLs altogether?  It seems as though it's likely to cause this sort of problem.

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