Last modified: 2011-03-13 18:04:54 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 6413 - Rendering <math> PNG image improvements
Rendering <math> PNG image improvements
Status: RESOLVED WONTFIX
Product: MediaWiki
Classification: Unclassified
Parser (Other open bugs)
unspecified
All All
: Lowest enhancement (vote)
: ---
Assigned To: Nobody - You can work on this!
http://meta.wikimedia.org/wiki/Help_t...
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2006-06-22 23:59 UTC by Mets501
Modified: 2011-03-13 18:04 UTC (History)
0 users

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


Attachments

Description Mets501 2006-06-22 23:59:32 UTC
I think it would be a great idea if we could implement some of Maynard Handley's
suggestions listed here:
http://meta.wikimedia.org/wiki/Help_talk:Displaying_a_formula#Maynard_Handley.27s_suggestions
. That would solve most of the problems of using <math> PNG images.  He includes
ways to make transparant PNG images, make font-sized PNG images, and fix the
vertical alignment.
Comment 1 Brion Vibber 2006-06-23 00:04:56 UTC
As discussed over the previous several years:
* Transparency is unsafe, as the foreground color won't match with
overridden background colors. This leads to illegible black-on-black
text, etc.

* Sizing with fonts is similarly infeasible as font size may vary
significantly, and it's far too slow to rerender the images even
if you could detect the font size properly in the browser.

Better math output will be achieved only with improved MathML support.
Comment 2 Aryeh Gregor (not reading bugmail, please e-mail directly) 2006-06-23 00:07:15 UTC
(In reply to comment #1)
> * Sizing with fonts is similarly infeasible as font size may vary
> significantly, and it's far too slow to rerender the images even
> if you could detect the font size properly in the browser.

The suggestion was to define image height/width inline with <img style="..."> in
CSS exes rather than leaving out the size or specifying it in pixels.  That
might work reasonably well, but would require testing on various platforms.
Comment 3 Brion Vibber 2006-06-23 00:07:47 UTC
That would also look horrible.
Comment 4 Mets501 2006-06-23 00:16:49 UTC
What about adding another command to TeX, such as "\small" that would render the images smaller.  Right now, 
it's not a huge problem, but my main concern is square roots.  Right now they display way too large for 
inline PNG and look too ugly in HTML.  Even a \smallrt (small root) command would help.
Comment 5 Aryeh Gregor (not reading bugmail, please e-mail directly) 2006-06-23 00:22:29 UTC
&sqrt;<span style="text-decoration: overline;">2</span> looks fine to me.  It
looks ugly, granted, so make a template.
Comment 6 Mets501 2006-06-23 00:43:11 UTC
Did you check that out on IE? It works perfectly in Firefox, but looks completely horrible in IE.
Comment 7 Aryeh Gregor (not reading bugmail, please e-mail directly) 2006-06-23 00:55:55 UTC
(In reply to comment #6)
> Did you check that out on IE? It works perfectly in Firefox, but looks
completely horrible in IE.

There's a gap of a couple of pixels, but provided you {{unicode}} it, it's more
"a bit annoying" than "completely horrible".  Example:
http://en.wikipedia.org/w/index.php?title=User:Simetrical/Sandbox&oldid=60093706
Comment 8 Mets501 2006-06-23 00:58:22 UTC
Oh yes, you're right.  If you {{unicode}} it is works fine.
I'm going to create a template right now called {{sqrt}}.

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


Navigation
Links