Re: Newbie Q: How to control <mover> height?

>          
>
>     There are various options to control layout in MathML but it's not
>     always a good option to use them:
>     http://www.w3.org/TR/MathML3/chapter3.html#presm.warnfinetuning
>
>
> Thanks for the link, this will be very helpful, as I'm finding it 
> easier to get what I'm after writing my own mark-up (as opposed to 
> using the graphical tools). 
>
Actually, my point was that "fine-tuning of presentation" should not be 
used, unless you have a good reason to do so. I did not recommend you to 
read the MathML spec, that is rather written for implementers. Ideally, 
people should use generators / graphical tools rather than trying to 
directly write the verbose MathML code. As indicated in the introduction:

"While MathML is human-readable, in all but the simplest cases, authors 
use equation editors, conversion programs, and other specialized 
software tools to generate MathML. Several versions of such MathML tools 
exist, and more, both freely available software and commercial products, 
are under development. "
>
>  
>
>     I think the code generated by Amaya is correct and it's probably
>     the rendering engine that should be improved in that case, so you
>     don't need to add a "hack" in the MathML code. In Firefox, the
>     result is OK. See attachment.
>
>
> Yes it is (in part because you're using an overline character as the 
> overline - doh! why didn't I think of that?)  However, your code looks 
> fine in my Firefox window, but FF isn't rendering any of my MathML 
> even close to correct (I can post a screen shot and my source if that 
> will help).  I compared your source to mine and there were differences 
> between their "pre-headers" and their heads, so I changed mine to 
> yours, but no improvement
I've simply created a new html document with Amaya and clicked on the 
"complex conjugate" button in the MathML panel (so that I needed not go 
through the pain of finding which markup/characters should be used). I 
suspect your problem to be that Firefox does not parse your document as 
XML. Just try to use the ".xhtml" extension instead. If you put your 
document on the Web, you will probably need to serve it as 
"application/xhtml+xml".
> (for some obscure reason, doing so, in Amaya, "broke" all my 
> non-breaking spaces in the body, at which point Amaya complained and 
> wouldn't render anything after the first broken nbs; so I had to go 
> back and repair those, and then Amaya rendered the source - incl. the 
> new pre-head and head - fine, but upon refreshing in Firefox, I still 
> saw the same old text w/out formatting).
Yes, I've already seen this problem too. I think it should be reported 
to the bug tracker.

Received on Sunday, 29 November 2009 21:51:27 UTC