Right, by using the TTX tool to dump the OpenType GPOS table I have been able to confirm that Ezra SIL has two positioning rules that apply in this situation. (the line below, patah, is a bit different in Ezra and Times New Roman in the image above, that's normal, it's a patah furtive and the typography varies for that) Just in case, the sequence לְנֹ֔חַ is letter: lamed 05DC, dots below: sheva 05B0, letter: nun 05E0, single dot: holam 05B9, double dot: zaqef qatan 0594, letter: het 05D7, and line below: patah 05B7. This is what Chrome does, and it is also done in real time by Wordpad: typing the het immediately changes the holam and zaqef qatan. ![]() The לְנֹ֔חַ case actually shows that rules need to be applied several glyphs before: when the last letter is typed (het ח), as the image on this post shows the placements of the TWO preceding glyphs (single dot = holam and double dot = zaqef qatan) change. So I think that after Prince has processed the alef, it should apply a rule to the preceding glyph (the holam) maybe in relation with the glyph even before that (the yod). This may account for why Ezra SIL is supposed to be more precise (as a font specifically designed for Classical Hebrew), because there are cases where the next glyph changes the typography of the preceding one and even preceding ones. So both fonts appear to differ in the order of applying the rules: Ezra SIL applies the rule only after (or if) the next, expected letter is typed/present/processed, whereas Times New Roman applies all rules (in this case) immediately. But just yod+holam makes no sense on its own, so Ezra SIL is expecting another letter just afterwards, and when I type this expected next letter, alef, Ezra SIL moves the holam to the left and both fonts end up giving the same correct result. There is a different behavior in Ezra compared to Times New Roman, which is exactly the same thing happening in the previous post when removing the last letter of לְנֹ֔חַ:Īs shown in the image, if I type yod then holam in Wordpad (without typing the alef for now), the holam appears just above yod in Ezra SIL (wrong for now) whereas the holam appears up left to yod in Times New Roman (already right). ![]() For some reason this issue does not come up with Arial, but does with Ezra SIL/Ezra SIL SR, with Shlomo and with SBL Hebrew, all widely used and standard fonts specialized for Classical Hebrew.ĮDIT: If it's any help, the standard keyboard layout to type all these letters and marks is Biblical Hebrew (Tiro). The exact same behavior happens while typing in Wordpad. So the normal, non-overlapping positioning rule is apparently dependent on the next letter being present, and Prince apparently does not apply that rule at all, whether the next letter is present or not. It seems to be an issue with some positioning rules applied after the symbols have been drawn on the letter, because for example with the third word of the image above לְנֹ֔חַ, the double dots and the single dot normally do not overlap (as in the image above, Chrome version), but if I edit the HTML file and remove the last letter of לְנֹ֔חַ, ie replace it with לְנֹ֔, then the double dots and single dot do overlap, exactly in the same way as in the image above, Prince version. ![]() ![]() The Shlomo fonts above are derived from and very similar to Ezra SIL.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |