ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: "Keith J. Schultz" <keithjschultz@web.de>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Epub format Was: Re:  Context to epub: itemize
Date: Tue, 17 Feb 2015 08:24:16 +0100	[thread overview]
Message-ID: <8BA925AF-1101-4DA2-84FC-D4747E47C5AB@web.de> (raw)
In-Reply-To: <D25EC8D1-35EF-4994-BE67-C06A3A51EDF3@axelkielhorn.de>


[-- Attachment #1.1: Type: text/plain, Size: 2139 bytes --]

Hi Axel, All,

You have mentioned that most current ebook readers can not display MathML.

Well, the problem lies in the epub guidelines for the readers.

The problem is even worse. many readers do not even implement the full HTML5
standard. though that is the standard used in the latest epub stadnard.
The fact is to be considered epub readers the do not have to, it is a problem
of the epub reader definition.

The problem is what should ConTeXt output?
Should it output code that implements according to the full epub standard 
OR JUST 
what is handled by most epub readers!

IMHO : ConTeXt should not output XHMTL for epub, but HMTL5.
Yes, yes, I know XHMTL is part of HMTL5.

Another question for me is if ConTeXt should also output code for
the iBooks epub format, (Basicaly epub, but some extras).
There are thing you can do in/with ConTeXt that would work with iBooks
that do not in „ordinary“ epub books.

Then, there is the Kindle format one might want to consider!

Another, question which needs investigation is if the ConTeXt output for epub,
also, implementing the fallbacks for missing features which is required?

Just some added thoughts.

Basically, you can only expect ConTeXts epub output to be a starting point that
then has to be tweak.

regards
	Keith.

> Am 17.02.2015 um 07:11 schrieb Axel Kielhorn <tex@axelkielhorn.de>:
> 
> [...]
> Yes I know.
> Let me rephrase the question:
> 
> Should the symbols used in epub be identical to those used in the pdf or should the css determine the look of the symbols?
> Especially when one considers that most current ebook readers can't display MathML.
> 
> Even if I substitute the Symbols:
> 
> \definesymbol[uni1][•]
> \definesymbol[uni2][–]
> \definesymbol[uni3][*]
> \definesymbol[uni4][·]
> 
> \setupitemgroup [itemize] [1] [symbol=uni1]
> \setupitemgroup [itemize] [2] [symbol=uni2]
> \setupitemgroup [itemize] [3] [symbol=uni3]
> \setupitemgroup [itemize] [4] [symbol=uni4]
> 
> I get a result that neither ADE nor Calibre interprets as a list.
> (Wrapping it in <ul> </ul> doesn't help.) 
> 


[-- Attachment #1.2: Type: text/html, Size: 16404 bytes --]

[-- Attachment #2: Type: text/plain, Size: 485 bytes --]

___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!

maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : http://www.pragma-ade.nl / http://tex.aanhet.net
archive  : http://foundry.supelec.fr/projects/contextrev/
wiki     : http://contextgarden.net
___________________________________________________________________________________

  reply	other threads:[~2015-02-17  7:24 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-16 16:17 Axel Kielhorn
2015-02-16 18:55 ` Hans Hagen
2015-02-17  6:11   ` Axel Kielhorn
2015-02-17  7:24     ` Keith J. Schultz [this message]
2015-02-17 20:16       ` Epub format Was: " Hans Hagen
2015-02-17 21:01         ` Keith Schultz
2015-02-18 16:54           ` Hans Hagen
2015-02-19  9:27             ` Keith Schultz
2015-02-17 22:37         ` Aditya Mahajan
2015-02-18  8:14           ` Henning Hraban Ramm
2015-02-18 14:10             ` Keith J. Schultz
2015-02-18 14:21               ` Henning Hraban Ramm
2015-02-18 16:44               ` Hans Hagen
2015-02-18 16:55           ` Hans Hagen

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=8BA925AF-1101-4DA2-84FC-D4747E47C5AB@web.de \
    --to=keithjschultz@web.de \
    --cc=ntg-context@ntg.nl \
    /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).