Re: Medievalist ligature character in the PUA

From: Andrew West (andrewcwest@gmail.com)
Date: Tue Dec 01 2009 - 16:45:34 CST

  • Next message: Doug Ewell: "Re: Medievalist ligature character in the PUA"

    2009/12/1 Wolfgang Schmidle <wschmidle@mpiwg-berlin.mpg.de>:
    >
    > Consequently, in a font that contains the ligature glyph at e.g. U+E8BF, the
    > sequence q+200D+A76B should ideally be displayed by the same glyph as the
    > single codepoint E8BF, i.e. a rendering mechanism for this font should
    > replace q+200D+A76B by E8BF. Normal fonts would display the sequence as qꝫ
    > instead of the ligature.

    Yes, although some fonts might display a box between the q and ꝫ.

    > Is there no implemented rendering mechanism for 200D in the Latin alphabet?
    > Or is 200D not meant for cases like these? Is there another way to avoid the
    > PUA codepoint?

    The individual ligatures have to be pre-implemented in the font, so if
    you want q+200D+A76B to display as a ligature you either have to
    create a font yourself and add the appropriate OpenType features, or
    else nag a font developer to put it in their font for you. In
    principle this mechanism does work with Latin text. For example, the
    Code2000 font implements a number of common ligatures which are
    triggered by means of ZWJ, e.g. <s+ZWJ+t> produces the "st" ligature.
    An alternative implementation might automatically generate an "st"
    ligature whenever "t" follows "s" unless broken by ZWNJ.

    Andrew



    This archive was generated by hypermail 2.1.5 : Tue Dec 01 2009 - 16:47:59 CST