public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: Paulo Ney de Souza <pauloney-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: "pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org"
	<pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Re: Maths in ebooks
Date: Thu, 15 Jan 2015 21:08:07 -0800	[thread overview]
Message-ID: <CAFVhNZNHxOtTmSrsOn=wp9Nvmz0L+Kd6+51Q7TOMJVNKZ=OW4w@mail.gmail.com> (raw)
In-Reply-To: <20150116021144.GW19197-j/q8TITqDDESy/uc2pLa89BPR1lH4CV8@public.gmane.org>

[-- Attachment #1: Type: text/plain, Size: 2600 bytes --]

On Thu, Jan 15, 2015 at 6:11 PM, Raniere Silva <raniere-Xhq86aZylhRTIXuwt5Zssw@public.gmane.org>
wrote:

>
> MathML rendering tools isn't as good as LaTeX. Firefox/Gecko has the best
> implementation so far. "Community WebKit" (e.g. used by [Epiphany]) and
> "Apple Webkit" (e.g. used by Safari) have some basic support to MathML
> but Chromium/Chrome don't have neither Internet Explorer.
>


I would like to add that even Firefox/Gecko having one of the best support
for MathML around -- it is still not enough! Under certain situations even
if you feed MathJax certain MathML code it will revert back to HTML+CSS
depending on the Firefox version of the user... because it know the
shortcomings of the browser.

Frédéric Wang has worked intensively in fixing the MathML display bugs in
Gecko and WebKit, and when the masters fold his code in -- we will have a
nicer MathML level display in HTML engines. Anyone interested should check
his blog:

          http://www.maths-informatique-jeux.com/blog/frederic/



> Most of the EPUB readers that support MathML use Gecko as rendering engine
> or
> MathJax that requires Javascript enabled.
>


And the ones that don't are almost all using Adobe Digital Editions for
rendering engine - one of the worst out there! I am writing a paper "On
determining the HTML rendering engine of ePub readers" (based on what they
do wrong with CSS) and this was a big surprise for me. It looks like things
are changing and Kobo started to move away from ADE, but overall the
industry is moving very slowly.


> However, I recently figured out that
> > ePub seems to support SVG as well and it is actually possible to turn
> LaTeX
> > into SVG output (see e.g. http://dvisvg.sourceforge.net/ and
> > http://svgkit.sourceforge.net/SVGLaTeX.html).
>
> That's true. Wikipedia does it.
>

The caveat being ... the support of SVG in browsers is roughly two years
ahead of support of SVG in ePub readers.


Paulo Ney

-- 
You received this message because you are subscribed to the Google Groups "pandoc-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
To post to this group, send email to pandoc-discuss-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
To view this discussion on the web visit https://groups.google.com/d/msgid/pandoc-discuss/CAFVhNZNHxOtTmSrsOn%3Dwp9Nvmz0L%2BKd6%2B51Q7TOMJVNKZ%3DOW4w%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[-- Attachment #2: Type: text/html, Size: 4079 bytes --]

  parent reply	other threads:[~2015-01-16  5:08 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-15  8:59 Thomas Arildsen
     [not found] ` <dfcf2e4b-b377-4d48-be9f-de82088e7832-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2015-01-15 17:51   ` Paulo Ney de Souza
     [not found]     ` <CAFVhNZPeDbtt+Tt3=8BYVX42XfFb=4RtaLGt29Ho-ik=QzeTSg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2015-01-15 21:29       ` Thomas Arildsen
     [not found]         ` <CAFQUsiZhZtAwzTDgUcpfOGkaP1gBSb5TRV+VeH0masuxq44QTA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2015-01-15 22:43           ` John MacFarlane
2015-01-15 20:30   ` John MacFarlane
     [not found]     ` <20150115203001.GA10846-nFAEphtLEs/fysO+viCLMa55KtNWUUjk@public.gmane.org>
2015-01-15 20:32       ` a
2015-01-15 21:24         ` Thomas Arildsen
     [not found]           ` <CAFQUsiZNNx=cMG9+Usrc5E=_sfN1Y7-3mF2Yv0OCmXdD4FJ0XA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2015-01-16  0:55             ` Beni Cherniavsky-Paskin
     [not found]               ` <CALJxei+TNrf+LGZTOQF_KKN+fYjBXxJyS51y1wYSyf2pQxQ19w-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2015-01-16  5:10                 ` Paulo Ney de Souza
2015-01-16  2:23             ` Raniere Silva
2015-01-16  2:17         ` Raniere Silva
     [not found]           ` <20150116021752.GX19197-j/q8TITqDDESy/uc2pLa89BPR1lH4CV8@public.gmane.org>
2015-01-16  5:24             ` Paulo Ney de Souza
2015-01-16  5:32         ` Paulo Ney de Souza
2015-01-15 21:24       ` Thomas Arildsen
     [not found]         ` <CAFQUsibyf8muK86Y5Ozj+9PfVBRgt-EAkjDAfU=4gy-wJ4e8mA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2015-01-16  6:13           ` Paulo Ney de Souza
2015-01-16  2:11   ` Raniere Silva
     [not found]     ` <20150116021144.GW19197-j/q8TITqDDESy/uc2pLa89BPR1lH4CV8@public.gmane.org>
2015-01-16  5:08       ` Paulo Ney de Souza [this message]
2015-01-16  6:13       ` John MacFarlane

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAFVhNZNHxOtTmSrsOn=wp9Nvmz0L+Kd6+51Q7TOMJVNKZ=OW4w@mail.gmail.com' \
    --to=pauloney-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
    --cc=pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).