otfautohint: Consider using Unicode mappings and substitutions (or other heuristics) for parameter configuration

[skef]

As it stands psautohint makes font-wide choices, such as whether to attempt flex hints, based on heuristics that may not be reliable going forward, such as

    def isCID(self):
        return hasattr(self.topDict, "FDSelect")

in otfFont.py.

To the extent that CJK glyphs need different parameters it would be preferable to make that determination on a glyph level, either by looking at the code point or by analyzing properties of the path itself. That way in a primarily CJK font with some LGC glyphs the latter could be hinted appropriately, and vice-versa.

[skef]

Actually, if we move users towards using separate FDArray entries then parameterizing on the FDArray may be a good solution to this problem.