RE: menclose

John and Simon,

We at Design Science are coming up with a proposal that we'll post early
next week and, if generally approved, we'll implement it in MathPlayer 2.0
due in a few months and in our MathFlow product.

Paul

----------------------------------------------------------------
Paul Topping                     email: pault@dessci.com            
                                 phone: 562-433-0685            
Design Science, Inc.             http://www.dessci.com
"How Science Communicates"
MathType, WebEQ, MathPlayer, Equation Editor, TeXaide
----------------------------------------------------------------

> -----Original Message-----
> From: jpederse@wiley.com [mailto:jpederse@wiley.com] 
> Sent: Friday, August 08, 2003 8:04 AM
> To: Pepping, Simon (ELS)
> Cc: Neil Soiffer; Robert Miner; www-math@w3.org
> Subject: RE: menclose
> 
> 
> 
> 
> I'm waiting on this naming issue to be resolved so that we 
> can finish marking up a product. So the sooner it can be 
> decided, the better.  I agree with Simon's comment about the 
> repeated "s", and it would seem to make sense to stay 
> consistent with the existing values "longdiv", etc., so we 
> shouldn't start doing camel case upwardsStrike. Some shorter 
> non-compass names would be
> 
> upstrike   or  upcancel
> downstrike  or downcancel
> hstrike    or hcancel
> ulcorner
> urcorner
> llcorner
> lrcorner
> 
> But at this point I'd be very happy for someone just to lay 
> down the law so we can proceed.
> 
> John.
> 
> -----------------------------
> John Pedersen
> Content Systems,
> John Wiley & Sons, Inc.
> 
> 
> 
> 
>                                                               
>                                            
>                       "Pepping, Simon                         
>                                            
>                       (ELS)"                   To:       
> "'jpederse@wiley.com'" <jpederse@wiley.com>,    
>                       <S.Pepping@elsevi         Neil Soiffer 
> <NeilS@dessci.com>                          
>                       er.nl>                   cc:       
> Robert Miner <RobertM@dessci.com>,              
>                                                 
> www-math@w3.org                                          
>                       08/08/03 06:27 AM        Subject:  RE: 
> menclose                                    
>                                                               
>                                            
>                                                               
>                                            
> 
> 
> 
> 
> > > NESWstrike
> > > NWSEstrike
> > > WEstrike
> > > NEcorner
> > > SEcorner
> > > SWcorner
> > > NWcorner
> > >
> > upwardsstrike
> > downwardsstrike
> > horizontalstrike
> > verticalstrike
> > upperleft
> > upperright
> > lowerleft
> > lowerright
> 
> I find the latter set of names more intuitive than the 
> compass directions. I like them esp. for the corners and the 
> horizontal and vertical. I am less sure about upward and 
> downward, but I do believe that they are unambiguous.
> 
> verticalstrike does not work with menclose. It was not in 
> Robert's list.
> 
> I do prefer the longer variants, with strikeout and corner; 
> they describe the intention.
> 
> I do not like the double s in upwardsstrike; I will forget to 
> write it most of the time.
> 
> Regarding the earlier discussion about the DTD. I consider 
> the DTD as an approximation of the standard. When the text 
> lists three allowed values for the attribute, then that is 
> the MathML spec. So the current discusson is about an 
> extension of the spec.
> 
> Regards,
> Simon Pepping
> DTD Development and Maintenance
> Elsevier
> s.pepping@elsevier.com
> www.elsevier.com/locate/sgml
> 
> 
> > -----Original Message-----
> > From: jpederse@wiley.com [mailto:jpederse@wiley.com]
> > Sent: 07 August 2003 14:33
> > To: Neil Soiffer
> > Cc: Robert Miner; www-math@w3.org
> > Subject: Re: menclose
> >
> >
> >
> >
> > There is also precedent in the entity names for using 
> directions, for 
> > example nwarr and nearr in isoamsa.ent (nwarrow, nearrow in 
> > mmlalias.ent). Personally I think upwards/downwards for the 
> diagonal 
> > strokes could be slightly ambiguous (I know some Windows people who 
> > insist on calling \ a
> > forwards slash); using compass directions leaves no doubt.
> >
> > John.
> >
> > -----------------------------
> > John Pedersen
> > Content Systems,
> > John Wiley & Sons, Inc.
> 
> 
> 
> 
>

Received on Friday, 8 August 2003 21:13:50 UTC