dadap / piqad-tools Goto Github PK

It seems with the iOS 13 update that the behavior for selecting glyphs when the selected font doesn't contain those glyphs has changed. In previous iOS versions, text containing unicode pIqaD characters would be displayed using the glyphs provided by the pIqaD qolqoS font recommended here: https://dadap.github.io/pIqaD-tools/input-methods/iOS/install-font.html

The behavior of using the glyphs from the pIqaD font seemed to occur regardless of whether a pIqaD font was explicitly used. (A notable exception is the Klingon empire symbol at U+F8FF  which displays as an Apple logo unless a pIqaD font is explicitly selected.)

With iOS 13, it appears that when a pIqaD font is not explicitly selected, only certain pIqaD characters appear. Notably, it seems that if a string of text begins with one of a few pIqaD characters, the following text will be rendered as pIqaD even if that text would not appear as pIqaD in isolation. The characters for which this appears to be true include , , , , and . Furthermore, the kerning now seems totally off when not explicitly using a pIqaD font whereas previously the kerning was fine for implicit pIqaD text.

While explicitly setting the font to a pIqaD one should be okay for apps where this is possible (e.g. Pages, websites with pIqaD text input fields if they explicitly set a pIqaD font, the text area in the ipIqaD app itself), for a great number of important apps it's not possible to set the font (e.g. iMessage, Notes, Mail, just about all messaging apps), which makes ipIqaD much less useful for day to day typing.