Typicon support #58

Font

NotoMono-Regular.otf
NotoSans-Regular.ttf
NotoSerif-Regular.ttf

Where the font came from, and when

Site: https://github.com/googlefonts/noto-fonts/blob/bf20559450ec75aec7a646b208343540a4496262/phaseIII_only/unhinted/otf/NotoMono/NotoMono-Regular.otf
Site: https://github.com/googlefonts/noto-fonts/blob/bf20559450ec75aec7a646b208343540a4496262/phaseIII_only/hinted/ttf/NotoSans/NotoSans-Regular.ttf
Site: https://github.com/googlefonts/noto-fonts/blob/bf20559450ec75aec7a646b208343540a4496262/phaseIII_only/hinted/ttf/NotoSerif/NotoSerif-Regular.ttf
Date: 2020-08-01

Font version

Noto Mono: Version 2.004
Noto Sans: Version 2.003; ttfautohint (v1.8.2)
Noto Serif: Version 2.003; ttfautohint (v1.8.2)

Issue

The LGC fonts should support U+29DF DOUBLE-ENDED MULTIMAP. According to Unicode Technical Note notofonts/noto-fonts#41, U+29DF is used as a typicon symbol. It may be the base for combining typicon marks; e.g. ⟨⧟꙼̇⟩ for June 11 (а҃і), ⟨⧟꙼⟩ for July 7 (з҃), and ⟨⧟᷹⟩ for August 25 (к҃є). For such combinations to work, the base and the mark must be in the same font.

Character data

⧟꙼
U+29DF DOUBLE-ENDED MULTIMAP
U+A67C COMBINING CYRILLIC KAVYKA

Screenshot