[
Lists Home |
Date Index |
Thread Index
]
> --text follows this line--
> The advantages of unified framework are inmense. For instance, instead
> using SVG for graphics and p-MathML for mathematics one prefer an all SVG
> approach.
hmm, perhaps, but now, today, If you use MathML you can just "cut and
paste" mathematical expressions from popular browsers (IE, firefox, in
particular) and drop the expressions into popular mathmatical packages,
(maple, mathematica) and have the expressions understood as
mathematics. The SVG may (see below) render OK but as far as any further
processing is concerned is likely to be essentially the same as an
image. Of course a browser that has SVG rendering capability (whether as
part of the core code or as a plugin of some sort) may use SVG
internally to render all sorts of things, including MathML, but that
doesn't negate the benefits of serving the Math-specific markup to the
client. The document author doen'st need to know what rendering
technology will be used to read the document. The document might last
1000 years, it's unlikely that the processing pipeline used to render it
will last that long.
> In that case any SVG browser can render math without need for
> native supprting MathML.
SVG may render OK at a particular window size but it's hard to see
how automatic line breaking would work in that case (as it happens today
in a limited extent in mozilla) given an SVG encoding of a particular
layout. SVG's very good at what it's good for, but it isn't designed for, and
isn't particularly good at, expressing an inline mathematical expression
that has to take part in the paragraph flow and line breaking of the
surrounding text.
David
|
