VaultAusir
commented
6 months ago Another good example of the ligature:
Source:
Open VaultAusir opened 8 months ago
VaultAusir
commented
6 months ago Another good example of the ligature:
Source:
simoncozens
commented
5 months ago Thanks for this report; as with the point, this will require additional drawing.
Title
No support for U+FB4F (Hebrew Ligature Alef Lamed)
Font
NotoRashiHebrew-VariableFont_wght.ttf
Where the font came from, and when
Site: https://fonts.google.com/noto/specimen/Noto+Rashi+Hebrew Date: 2024-02-04 (preferred format)
Font Version
Version 1.006
OS name and version
macOS 14.2 (but happens on every system)
Issue
The font is missing a character historically found in various texts in Ladino (Judeo-Spanish), a language where the Rashi script is used as a standard, such as Me'am Lo'ez, making it impossible to properly transcribe them.
U+FB4F (Hebrew Ligature Alef Lamed)
Character data
The character U+FB4F (Hebrew Ligature Alef Lamed) is not supported, despite being a character found in many historical texts in Ladino (Judeo-Spanish) in the Rashi script.
Screenshot
Example of a word with the character defaulting to fallback font instead when it is used (screenshot of Pages app):
Historical text in Rashi script (Me'am Lo'ez) with the same word (ﭏישארלו), using this ligature highlighted:
Another example of the same character from the same text, can be used as reference for the glyph, as this is how the character was historically portrayed in Rashi script (in the word ﭏמה):
Some other Rashi fonts use different shapes for this ligature, but one more close to the historical one, as above, is recommended.