- From: Paul Topping <pault@dessci.com>
- Date: Wed, 20 Feb 2013 19:46:15 +0000
- To: Murray Sargent <murrays@exchange.microsoft.com>, Khaled Hosny <khaledhosny@eglug.org>
- CC: Neil Soiffer <neils@dessci.com>, Kent Karlsson <kent.karlsson14@telia.com>, David Carlisle <davidc@nag.co.uk>, "Daniel Marques" <dani@wiris.com>, "www-math@w3.org" <www-math@w3.org>
So this means that reversing a symbol to express a mathematical concept is unavailable to non-RTL text even though the fonts and the font rendering mechanism has the capability. Paul > -----Original Message----- > From: Murray Sargent [mailto:murrays@exchange.microsoft.com] > Sent: Wednesday, February 20, 2013 11:36 AM > To: Paul Topping; Khaled Hosny > Cc: Neil Soiffer; Kent Karlsson; David Carlisle; Daniel Marques; www- > math@w3.org > Subject: RE: Mirroring Unicode symbols in Arabian > > I meant that the codes for the mirrored integral, etc., are exactly the > same as the unmirrored symbols. The display software just mirrors them > in RTL math zones. If you use OpenType, you used the 'rtlm' feature or > shaping, as the characters warrant. This is the same thing as for > mirrored characters that have mirrored character counterparts. An open > paren is U+0028 whether it's mirrored or not. > > Murray > > -----Original Message----- > From: Paul Topping [mailto:pault@dessci.com] > Sent: Wednesday, February 20, 2013 11:31 AM > To: Murray Sargent; Khaled Hosny > Cc: Neil Soiffer; Kent Karlsson; David Carlisle; Daniel Marques; www- > math@w3.org > Subject: RE: Mirroring Unicode symbols in Arabian > > Not sure how this answers my question. > > Paul > > > -----Original Message----- > > From: Murray Sargent [mailto:murrays@exchange.microsoft.com] > > Sent: Wednesday, February 20, 2013 11:24 AM > > To: Paul Topping; Khaled Hosny > > Cc: Neil Soiffer; Kent Karlsson; David Carlisle; Daniel Marques; www- > > math@w3.org > > Subject: RE: Mirroring Unicode symbols in Arabian > > > > Mirrored glyphs are a display feature, not a semantic one. > > > > Murray > > > > Paul Topping asked, "If access to these characters requires use of > > this OpenType feature, does it imply that such characters will not be > > accessible from applications that simply process Unicode text strings > > (eg, web browsers and most other apps)?"
Received on Wednesday, 20 February 2013 19:46:48 UTC