Re: Ligatures For Indic languages

From: Manik Mahajan (manik.mahajan@mediatek.com)
Date: Thu May 29 2008 - 23:33:05 CDT

  • Next message: Mahesh T. Pai: "Re: Ligatures For Indic languages"

    In case of different vendors are involved ,all the characters which formed
    the cluster( the logical buffer ) are needed to be passed on the
    communication channel,which then on the receiver end are converted into
    ligature in the proprietary range of that vendor.
    If present in Unicode ,that character itself can be transferred .

    A+B+C = D

    if D in Unicode we can send D else we need to send A+B+C which will be
    decoded at receiver to ,say E which represents the glyph D in its
    Proprietary range .

    Manik Mahajan

                                                                               
                 "John H. Jenkins"
                 <jenkins@apple.co
                 m> To
                 "John H. Jenkins" Unicode Mailing List
                 <jenkins@apple.co <unicode@unicode.org>
                 m> cc
                 Sent by:
                 unicode-bounce@un Subject
                 icode.org Re: Ligatures For Indic languages
                                                                               
                                                                               
                 29/05/2008 22:48
                                                                               
                                                                               
                                                                               

    On May 29, 2008, at 10:16 AM, Manik Mahajan wrote:

    > There is almost no Unicode for Indic Ligatures whereas Ligatures for
    > Arabic Languages are Part of Unicode ,Is there any special reason
    > for this?
    >

    Ligatures for Arabic (and Latin and Aramaic) are included as
    compatibility characters and the expectation is that they should not
    be used in actual texts. Unicode expects that ligatures will be
    formed by the display engine and should not be explicitly encoded
    except where necessary for reasons such as round-trip compatibility,
    and even then only as compatibility characters.

    =====
    John H. Jenkins
    jenkins@apple.com

    ************* Email Confidentiality Notice ********************
    The information contained in this e-mail message (including any attachments) may be confidential, proprietary, privileged, or otherwise exempt from disclosure under applicable laws. It is intended to be conveyed only to the designated recipient(s). Any use, dissemination, distribution, printing, retaining or copying of this e-mail (including its attachments) by unintended recipient(s) is strictly prohibited and may be unlawful. If you are not an intended recipient of this e-mail, or believe that you have received this e-mail in error, please notify the sender immediately (by replying to this e-mail), delete any and all copies of this e-mail (including any attachments) from your system, and do not disclose the content of this e-mail to any other person. Thank you!



    This archive was generated by hypermail 2.1.5 : Thu May 29 2008 - 23:35:29 CDT