Rosettatype’s avatarRosettatype’s Twitter Archive—№ 4,106

  1. …in reply to @LudwigType
    @LudwigType Thanks! We will provide a flag/toggle to turn that behviour off.
    1. …in reply to @rosettatype
      @LudwigType It works better now. Here is some context, (as you know) there are two ways how to support mark-character combinations: a) through precomposed character combination with assigned unicode, b) through combination of base character, mark, and automated mark positioning (GPOS/GSUB).
      1. …in reply to @rosettatype
        @LudwigType From the perspective of language representation both are equal, although each has its own merits in type design and font production. Our original solution was too strict and required both. …
        1. …in reply to @rosettatype
          @LudwigType The current solution in the web app, requires combining marks (b) only if they are needed to build unencoded character-mark(s) combinationa that are listed in the base character set. I believe this should address your issues. The CLI provides further flexibility.