Last modified: 2013-09-23 11:42:59 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 10891 - Change the - char from 'ndash' to 'minus'
Change the - char from 'ndash' to 'minus'
Status: RESOLVED WONTFIX
Product: MediaWiki extensions
Classification: Unclassified
CategoryTree (Other open bugs)
unspecified
All All
: Lowest trivial (vote)
: ---
Assigned To: Nobody - You can work on this!
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2007-08-12 14:05 UTC by Josh Lee
Modified: 2013-09-23 11:42 UTC (History)
2 users (show)

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


Attachments

Description Josh Lee 2007-08-12 14:05:38 UTC
When you expand a category, the symbol changes from '+' to '–'. This is visually unappealing because the characters have different widths. The minus sign, however, has the same width as the plus sign. Line 26 of CategoryTree.js should be changed to:

      lnk.innerHTML= '−';

to accomodate this.
Comment 1 Danny B. 2007-08-13 04:30:19 UTC
I'd rather suggest the normal "-" sign (U+002D) since the − (U+2212) doesn't have to be rendered properly in user agents using poor fonts while "-" is ASCII and will be rendered properly everytime.
Comment 2 Josh Lee 2007-08-13 12:22:25 UTC
That would work only if a monospace font were used.
Comment 3 Brion Vibber 2007-08-25 13:28:25 UTC
My very unscientific testing (one data point, Firefox 2.0 on Mac :) showed that −, −, and - all have a much shorter width from + in the default display, while – is slightly different but very close -- I have to zoom in a lot to see the difference.

So if it's just going to get worse from using −, I don't see a big benefit here.
Comment 4 Danny B. 2007-08-26 00:13:21 UTC
Any reason why we couldn't use monospace font for [+] and [-] ?
Comment 5 Brion Vibber 2007-08-27 18:06:59 UTC
Should work. :)
Comment 6 Aryeh Gregor (not reading bugmail, please e-mail directly) 2007-08-27 18:15:55 UTC
(In reply to comment #3)
> My very unscientific testing (one data point, Firefox 2.0 on Mac :) showed that
> −, −, and - all have a much shorter width from + in the default
> display, while – is slightly different but very close -- I have to zoom
> in a lot to see the difference.

Could you be using a font that doesn't contain −?  AFAIK it's generally assumed that + and − are to be the same width, and in my experience that's always been true (but Unicode doesn't seem to specify it).  Does any single font actually contain radically different-width plus and minus, and if so, what were its creators smoking?

Not that this should really be a big factor in changing the status quo, if current browsers aren't rendering it properly, since pretty much everyone renders – as very close to the width of +.  I'll change to LATER, it would be nice if this could be fixed eventually (when things aren't rendered so stupidly, one would hope).
Comment 7 Andre Klapper 2012-12-19 11:28:28 UTC
[Removing RESOLVED LATER as discussed in http://lists.wikimedia.org/pipermail/wikitech-l/2012-November/064240.html . Reopening and setting priority to "Lowest". For future reference, please use either RESOLVED WONTFIX (for issues that will not be fixed), or simply set lowest priority. Thanks a lot!]
Comment 8 This, that and the other (TTO) 2013-09-23 11:42:59 UTC
(In reply to comment #7)
> [Removing RESOLVED LATER as discussed in
> http://lists.wikimedia.org/pipermail/wikitech-l/2012-November/064240.html .
> Reopening and setting priority to "Lowest". For future reference, please use
> either RESOLVED WONTFIX (for issues that will not be fixed), or simply set
> lowest priority. Thanks a lot!]

No need to fix this one.

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


Navigation
Links