On Mon, Aug 15, 2011 at 07:38:07PM +0200, Philippe Verdy wrote: > 2011/8/13 mmarx <[email protected]>: > >>> I attach a Garshuni document from > >>> Beit al-Qammar showing Arab vowel > >>> marks -- just as the Syriac communmties > >>> are using Syriac vowel marks in Arabic > >>> script text -- and (in the second line > >>> on the left) wasla above olaph. > >>> > >>> So whatever the status of wasla mark > >>> will be fore Arabic, for Syriac/Garshuni > >>> it is need as a normal mark in normal text. > > > >> Unicode cannot encode a combining Wasla (because of various stability > >> policies), so if Syriac needs a Wasla to be shown only over a letter > >> or two, one needs to propose precomposed characters for them. Just > >> like the existing Arabic Alef-Wasla. > > Why not? If the character is new, it can perfectly be encoded with > whatever character property is needed, including with a non-zero > combining class, if it fits. The stability policy aboud combining
But as soon as you have a combining wasla in the Unicode you would have to change the decomposition mappings for Alef-Walsa (because from that point on you would have two possibilities how to encode this combination). However, If a special "Syriac Wasla" was encoded as a combining character than no problems would arise for the Arabic script. P.T. -- Petr Tomasek <http://www.etf.cuni.cz/~tomasek> Jabber: [email protected] ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ EA 355:001 DU DU DU DU EA 355:002 TU TU TU TU EA 355:003 NU NU NU NU NU NU NU EA 355:004 NA NA NA NA NA ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
