Last modified: 2012-04-16 09:15:53 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 26205 - narrow no-breaking space &nnbsp; missed
narrow no-breaking space &nnbsp; missed
Status: RESOLVED WONTFIX
Product: MediaWiki
Classification: Unclassified
Parser (Other open bugs)
unspecified
PC Windows 7
: Lowest enhancement (vote)
: ---
Assigned To: Nobody - You can work on this!
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2010-12-02 15:58 UTC by Juetho
Modified: 2012-04-16 09:15 UTC (History)
1 user (show)

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


Attachments

Description Juetho 2010-12-02 15:58:32 UTC
HTML offers   and &nnbsp; (narrow no-breaking space). Wiki offers   and   but   allows line breaking. Typographic rules say (in Germany, at least): One has to use a thin space to show tousands and a fixed space to combine value and unit: 123 456 km² Both spaces must be no-breakings.

Either   is extended to "no-break". Or &nnbsp; is installed.

Thank you!
Comment 1 Bawolff (Brian Wolff) 2010-12-02 22:52:54 UTC
>HTML offers   and &nnbsp;

Source? Wikipedia disagrees that &nnbsp; is a real entity in (x)html.


>Either   is extended to "no-break". Or &nnbsp; is installed.

We just generally offer what html does. Adding our own entities and translating them on the fly seems to be a bad idea because then it'd be confusing as to why &somethingRandom; works when it doesn't in html. Furthermore it'd be extremely confusing to have the parser replace   with a character other then what   represents in html.

Note: you can currently type this character using the entities   or   (or by directly typing it in. In firefrox, ctrl+shift+u + 202f  (thats a literal plus) types it in. If thats too hard to remember, why not create a template {{nnbsp}} containing the character.

I suggest wontfixing this.
Comment 2 Juetho 2010-12-03 08:22:15 UTC
Sorry, I misunderstood the de.wikipedia article "Geschütztes Leerzeichen". The abbreviation NNBSP doesn't concern to an html code like I meant.

I'ld better avoid a template {{nnbsp}} if wikimedia would contain a general solution.

I shall use   or a template further on. Sorry for unnecessary request.

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


Navigation
Links