ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Hans Hagen <pragma@wxs.nl>
Subject: Re: mml
Date: Thu, 30 Mar 2006 21:09:40 +0200	[thread overview]
Message-ID: <442C2CF4.5080008@wxs.nl> (raw)
In-Reply-To: <442C2010.3090909@elvenkind.com>

Taco Hoekwater wrote:
> nico wrote:
>   
>> So, the behaviour should not be different when using an entity name and  
>> the corresponding unicode value. Imagine some XML tool processing an  
>> original XML mathml code containing an entity name, and simply expanding  
>> the entity according the MathML DTD. I think that processing the original  
>> and the expanded code should give the same result.
>>     
>
> I just reread that bit, and you are right (of course you knew
> that already, sorry).
>
> Unfortunately, the use of bare character entities makes it quite a
> bit harder to implement mathml. Essentially, the top-level mathml
> element would have to redefine (and remember, for embedded non-mathml)
> lots and lots of 'normal' tex stuff.
>   
indeed (preprocessing such an xml doc makes sense then)

somehow i got the impression that many of those standards are not written with an implementation in mind 

Hans 


-----------------------------------------------------------------
                                          Hans Hagen | PRAGMA ADE
              Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
     tel: 038 477 53 69 | fax: 038 477 53 74 | www.pragma-ade.com
                                             | www.pragma-pod.nl
-----------------------------------------------------------------

  reply	other threads:[~2006-03-30 19:09 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <441F2177.9060005@wxs.nl>
     [not found] ` <ops6r30uv79niby6@localhost>
     [not found]   ` <44208780.8000804@wxs.nl>
     [not found]     ` <ops6sfujps9niby6@localhost>
     [not found]       ` <44212554.4090707@wxs.nl>
     [not found]         ` <ops6v5wkph9niby6@localhost>
     [not found]           ` <4423B5A0.9060408@wxs.nl>
     [not found]             ` <ops6x0heh39niby6@localhost>
     [not found]               ` <4425381B.20900@wxs.nl>
     [not found]                 ` <ops6zi0ytn9niby6@localhost>
     [not found]                   ` <4426D571.5070302@wxs.nl>
     [not found]                     ` <ops61keb1k9niby6@localhost>
     [not found]                       ` <4427D9D7.7020306@wxs.nl>
     [not found]                         ` <ops63at5uy9niby6@localhost>
     [not found]                           ` <4429022A.2040302@wxs.nl>
     [not found]                             ` <ops6489a1j9niby6@localhost>
2006-03-29 14:14                               ` mml Hans Hagen
2006-03-30  8:18                                 ` mml Taco Hoekwater
2006-03-30 17:44                                   ` mml nico
2006-03-30 18:14                                     ` mml Taco Hoekwater
2006-03-30 19:09                                       ` Hans Hagen [this message]
2006-03-30 21:02                                     ` mml Hans Hagen
2006-03-30 22:54                                       ` mml nico

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=442C2CF4.5080008@wxs.nl \
    --to=pragma@wxs.nl \
    --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).