RE: Whitespace handling following inline math

Hi Mike,

I think you are also safe if you strip out all the whitespace between
MathML elements.  We do this with some of our own XSL stylesheets, and
it also seems to work around the problem without running the risk of
nbsp's causing some unexpected side effects.

I also sadly note that although we have reported this "feature" of
Internet Explorer to Microsoft through multiple channels, they have (so
far) declined to fix it in IE7.  I speculate they regard it as critical
for backward compatibility.

--Robert

Robert Miner
Director, New Product Development

Design Science, Inc.
140 Pine Avenue, 4th Floor
Long Beach, California  90802
USA
Tel:  (651) 223-2883
Fax:  (651) 292-0014
robertm@dessci.com
www.dessci.com
~ Makers of MathType, MathFlow, MathPlayer, WebEQ, Equation Editor,
TexAide ~

 

> -----Original Message-----
> From: www-math-request@w3.org 
> [mailto:www-math-request@w3.org] On Behalf Of Waters, 
> Michael, Springer US
> Sent: Wednesday, August 30, 2006 12:25 PM
> To: David Carlisle
> Cc: www-math@w3.org
> Subject: RE: Whitespace handling following inline math
> 
> 
> >yes they know about that one, see
> >http://www.dessci.com/en/support/mathplayer/tsn106.htm
> >item 5
> >Internet Explorer Bugs & Limitations
> >IE sometimes removes space following the </math> tag. It 
> seems to do so
> >when there is no start tag on the same line. Here is a test page that
> >demonstrates the problem. 
> >
> >what I do is just make sure that the space after math is a 
> #160 rather
> >than a #32 (by inserting a suitable rule in the stylesheet that's
> >generating the pages) not ideal but it works.
> >
> >I do this while generating the pages, if you are using 
> pmathml.xsl you
> >could add a template to that stylesheet to change a space following a
> >math at rendering time.
> >
> 
> 
> Yes, I thought that might be the case.
> 
> In a re-posting of my original message [some www-math 
> subscription problems and an overly long delay in 
> distribution led me to believe that my message was not 
> received], I also noticed the behavior of #160. I'm somewhat 
> concerned about the nonbreaking nature of #160, which might 
> lead to some occasional unsightly situations where the inline 
> math and the following word are rather long. But this is 
> better than losing the space after inline math in all cases.
> 
> AS you say, "not ideal but it works."
> 
> Thanks for the link to the bug page.
> 
> Mike
> 
> 
>

Received on Wednesday, 30 August 2006 19:16:57 UTC