Pamudpod getting put in a different run
davelab6 opened this issue · comments
Hi @davelab6 . Thanks for reporting.
It's another issue similar to the one described on pages 14 and 15 of the manual.
The issue is that the pamudpod has as its Unicode script hano: that is, Hanuno'o. So, it's getting put in a different run. In reality, pamudpod should have the same script tag as PHILIPPINE PUNCTUATION DOUBLE DANDA (U+1736). That is to say, it should have class Po and script Zyyy,
Hopefully you can appreciate, there's nothing I can do in my font to fix this.
The unfortunate reality is, Tagalog has been pretty neglected by Unicode for far too long, and my ra proposal doesn't go far enough. Thank you for reminding me of this issue, I will write another proposal. It can be a short one given the simplicity of the issue.
I will ask them to either change the pamudpod (U+1734)'s script to Zyyy and type to Po, or to create a new character, PHILIPPINE PUNCTUATION PAMUDPOD.
See also notofonts/noto-cjk#172 (comment), I was serious about this. These issues with script mismatches and unencoded characters which are in the pipeline are a drag and the Chrome team should seriously consider copying Mozilla.
For now you can uncheck pamudpod option. Lots of documents use it though...like I said, Unicode has neglected Tagalog. But, the virama have the same function. Just, Filipinos like Norman de los Santos and others prefer the pamudpod because it's native; the virama are a Spanish invention, they are Christian as well, in the sign of a cross; some people make them X's (the font supports this, salt) to get around that, but of course pamudpod is still preferred.