Last modified: 2010-05-05 23:40:09 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 T25411, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 23411 - Spaces in the output of {{NUMBEROFARTICLES}} should not wrap
Spaces in the output of {{NUMBEROFARTICLES}} should not wrap
Status: RESOLVED INVALID
Product: MediaWiki
Classification: Unclassified
General/Unknown (Other open bugs)
unspecified
All All
: Normal enhancement (vote)
: ---
Assigned To: Nobody - You can work on this!
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2010-05-05 12:55 UTC by Helder
Modified: 2010-05-05 23:40 UTC (History)
2 users (show)

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


Attachments

Description Helder 2010-05-05 12:55:55 UTC
When the result of {{NUMBEROFARTICLES}} is something like "1 234" (with a space between two digits, 1 and 2), the number is wrapped and we get something like

/----------------------------------\
|Text text text text text text 1   |
|234 text text text text text...   |
\----------------------------------/
instead of

/----------------------------------\
|Text text text text text text     |
|1 234 text text text text text... |
\----------------------------------/

This is awful.

Maybe it should be used white-space:nowrap or   in the output... What do you think?

Helder
Comment 1 Svip 2010-05-05 12:58:15 UTC
I think you should do that yourself.  Making this magic word too clever would be widely a problem.

Make a no wrap template and wrap it around it.  Alternatively, but I doubt this will happen, create an additional magic word that does the same but with no wrapping.
Comment 2 Bawolff (Brian Wolff) 2010-05-05 23:40:09 UTC
Wouldn't it somewhat make sense to just make the number separator in separatorTransformTable be a non-breaking space (U+00A0) for the pt localization?

As far as i know, in general its considered bad to have a breaking space separate numbers.

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


Navigation
Links