- From: Liddy Nevile <liddy@sunriseresearch.org>
- Date: Fri, 10 Sep 2004 07:26:04 +1000
- To: Robert Miner <RobertM@dessci.com>
- Cc: www-math@w3.org
Robert - excellent! Thanks for your help... Liddy On Friday, September 10, 2004, at 12:12 AM, Robert Miner wrote: > > Hi Liddy, > > Bruce Miller is correct that MathType currently is limited to a single > choice of mi, mn, or mo for notations like '...' and ','. The > translator mechanism that generates MathML from MathType's internal > format has a pretty limited ability to choose the markup based on > surrounding context. > > However, you can easily change what it does generate. There is a file > called MathML2Base.tdl that define the MathML translator rules. > Typically it is located in > > C:\Program Files\MathType\Translators > > The translator definition language is fully described in the MathType > SDK docs, which you can download from > > http://www.dessci.com/en/reference/sdk/ > > However, the ellipsis change is simple. The ellipsis character is > 0x2026; Line 1271 is > > char/0x2010/0x2027/mathmode = "<(ns)mo>&$#x(CharHex);</(ns)mo>"; // > range: General Punctuation > > which says to translate any character is the range 0x2010 to 0x2027 as > an mo. If you break up that range as > > char/0x2010/0x2025/mathmode = "<(ns)mo>&$#x(CharHex);</(ns)mo>"; // > range: General Punctuation > char/0x2026/mathmode = "<(ns)mi>&$#x(CharHex);</(ns)mi>"; > char/0x2027/mathmode = "<(ns)mo>&$#x(CharHex);</(ns)mo>"; > > then you will get <mi>&0x2026;</mi> for your ellipsis, and mo's for > the rest. > > On the topic of mo's directly in mrows or mfenced, I personally prefer > mo's. > > --Robert > > ------------------------------------------------------------------ > Dr. Robert Miner RobertM@dessci.com > W3C Math Interest Group Co-Chair 651-223-2883 > Design Science, Inc. "How Science Communicates" www.dessci.com > ------------------------------------------------------------------ > > > > > > >
Received on Thursday, 9 September 2004 21:26:17 UTC