Page MenuHomePhabricator

Incorrect symbols MathML in chromiun
Closed, ResolvedPublic

Description

image1 Firefox (MathML)

math \Coppa, \coppa, \Koppa, \koppa, \Stigma, \stigma, \S, \P
in

in Firefox (MathML):
Ϙ , ϙ , Ϟ , ϟ , Ϛ , ϛ , § , ¶
see image1

in Firefox & Chromium with settings "PNG images" (or when not loggin):
see image2

in Chromium (MathML):

see image3


Version: unspecified
Severity: normal

Attached:

Снимок_экрана_от_2014-11-08_14:07:16.png (159×306 px, 15 KB)

Details

Reference
bz73173

Event Timeline

bzimport raised the priority of this task from to Needs Triage.Nov 22 2014, 3:59 AM
bzimport set Reference to bz73173.
bzimport added a subscriber: Unknown Object (MLST).

Created attachment 17080
image2 Firefox/Chromium (PNG)

Attached:

Снимок_экрана_от_2014-11-08_16:56:36.png (244×354 px, 33 KB)

Created attachment 17081
image3 Chromium(MathML)

Attached:

Снимок_экрана_от_2014-11-08_17:00:24.png (250×349 px, 31 KB)

I'm assuming this is due to the use of the MathJax fonts for the SVG conversion, so I'm moving this to Mathoid.

I can reproduce this; see https://en.wikipedia.org/wiki/User:Pkra/sandbox.

However, I don't think it's the MathJax fonts. MathJax will always fallback to regular Unicode text when it encounters a character that the fonts do not cover.

You can see that this works in the SVG generated by MathJax at https://en.wikipedia.org/w/index.php?title=Special:MathShowImage&hash=e9393d9bafb58f58b1a47a1c908d2b01&mode=5.

This looks like another problem related to embedding the SVG in the page.

PS: It works fine on IE11. Perhaps it's a bug in Chrome.

OK, well so server-side it's a problem with the MathJax fonts (for not having the appropriate glyphs to do proper SVG conversion) and client-side it's a problem with the config (for lacking fonts to display the <text> fallback). So we can either fix that by changing the font server-side or by adding Web fonts client-side.

So we can either fix that by changing the font server-side

Yes.

or by adding Web fonts client-side.

I don't think that will help. It looks like a Chrome bug.

Physikerwelt claimed this task.