This is smart... provided that fonts also map the ZWJ (not all Arabic fonts map it, they often map only ZWNJ to disable joinings, assuming that there's no reason to force the joining in normal texts; some Arabic fonts do not even map ZWNJ as well).
Some Arabic fonts do not even map the joining types internally but depend on the engine to find the contextual forms by trying with the compatibility characters (so they are not suitable for anything else than basic Arabic). Le 31 mars 2012 10:39, Khaled Hosny <khaledho...@eglug.org> a écrit : > On Fri, Mar 30, 2012 at 07:37:53PM +0200, Andreas Prilop wrote: >> I come back to >> http://www.unicode.org/mail-arch/unicode-ml/y2012-m03/thread.html#11 >> >> A similar problem of showing non-joining, isolated Arabic glyphs >> can be seen in the attached file. Both Internet Explorer 8 and >> MS Word 2010 display isolated glyphs in some cases. >> >> I think a better idea is to have joining glyphs always even for >> different typefaces. At least the Unicode Standard should say >> what should happen when Arabic characters of different typefaces >> follow each other. > > OpenOffice/LibreOffice work around this by conditionally inserting ZWJ > when there is a font switch in the middle of the word and joining is > desired.
