Last modified: 2006-10-24 10:04:44 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 4893 - allow rendering of &#xnnn; or &#nnnn;
allow rendering of &#xnnn; or &#nnnn;
Product: MediaWiki
Classification: Unclassified
Parser (Other open bugs)
All All
: Normal enhancement (vote)
: ---
Assigned To: Nobody - You can work on this!
Depends on:
  Show dependency treegraph
Reported: 2006-02-06 16:16 UTC by Tobias Schmidbauer
Modified: 2006-10-24 10:04 UTC (History)
0 users

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


Description Tobias Schmidbauer 2006-02-06 16:16:58 UTC
I'm a editor of the German wikipedia. On the english WP you normally write a
  between value and unit symbol; In our typography it's common to have a
thin space in those cases. On computer this would be the "NARROW NO-BREAK SPACE"
(U+202F). But you can't write   or   in a wiki. Construcions like
these are cut out of by the software.
The only solution is to write an UTF-8 character. But then other editors just
see a space and don't understand.
Comment 1 Brion Vibber 2006-02-06 21:19:52 UTC
Sure, you can write that. Provide details about what doesn't work and reopen if you 
actually have problems with it.
Comment 2 Tobias Schmidbauer 2006-02-07 10:26:56 UTC
Ah sorry, that's my browser who doesn't show the characters neither on the page
nor in the sourcecode. Could someone please delete this bug?

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