ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Tobias Burnus <burnus@gmx.de>
Subject: RFC: ConTeXt/MathML: Alternative representations
Date: Mon, 12 Mar 2001 08:16:06 +0100	[thread overview]
Message-ID: <3AAC77B6.CF82940F@gmx.de> (raw)

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

i,

I would like to collect a list of needed alternative representations for
the MathML engine of ConTeXt. For a detail list have a look at the DVI
file. I mean things like "otherwiese" => (e.g. German) "sonst" and \grad
vs. \nabla. -----> For a detailed list see attachment (first draft).

Maybe this thread could also be used to track/collect some bugs or
misbehaviours of ConTeXt's MathML support.

Could someone who knows the American school books please try the
<menclose/> and tell me/us whether ConTeXt makes it correctly. I have a
vague fealing that the example in the MathML reference, sect.3.3.9 is
not very good. (Maybe send a .png to illustrate).

Another RFC: Which annotation encodings should ConTeXt support? TeX,
tex, ConTeXt, context, ...
I think presently only TeX is supported. (For hyperlinks etc. "ConTeXt"
would also be nice).

Bugs in ConTeXt:

- The \max\{ ·  \} should use a \left / \right before the braces, you
see why on page 35 of the mmlprimer.pdf

- (not MML): The column serparating lines in the TOC of mmlprimer are
one line too short. The column in the middle is one line longer than the
others this might cause this -- in my optinion -- misbehaviour.
Or how should this be handled, what is the typographs opinion?

Ciao from Bologna,

Tobias

PS: I seems that I will give a lecture on MathML at EuroTeX ;-)

[-- Attachment #2: mml-proposals.dvi --]
[-- Type: application/x-dvi, Size: 7428 bytes --]

                 reply	other threads:[~2001-03-12  7:16 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=3AAC77B6.CF82940F@gmx.de \
    --to=burnus@gmx.de \
    /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).