-
Notifications
You must be signed in to change notification settings - Fork 804
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Character addition request. #419
Comments
Sorry you're bored. We already have a bug related to Arabic. The bitcoin glyph is one I will consider adding, as are the dot above glyphs, but you can work around those for now by using the dotabove combining mark ( |
But 84 is not as long, and too unexplained, in its early development. Also U+0659 is required in the future... I do think. 84 is just nothing. |
Sorry, your comment makes no sense. |
What does that means? I plan Bitcoin, Pashto, Hebrew but not Yiddish, Thai, to make Cascadia multilingual. You think that's misinformation. |
Thanks for helping @yg8ijvjvjv, though based on researching those specific glyphs, the request is likely more in relation to Hebrew romanization than alignment with ISO standards. Given the above, let me rephrase the feature request:
As I stated previously, issue #84 covers the addition of Arabic, and I will consider the other requests. Thanks for submitting an issue. |
🤷♂️ |
No. That is old Irish. |
If you would like to file a bug to support ISO subset1 and 2 please do so. Thanks. |
No. Just no. This is Pashto ابپتټثجځچڅحخدډذرړزژږسشښصضطظعغفقکګلمنڼوهیېيۍئےءَُِٙـ،؛؟۹۸۷۶۵۴۳۲۱۰, ﴾﴿ﷲ﷼, but also you need more Presntation forms A and B. and |
I have created three new issues to better track the separate character addition requests by @bedriczwaleta. As such, am closing this thread. Thanks. |
If you want to know, Subset1 was made by @yg8ijvjvjv for his monospaced fonts as a requirement |
This font does not contain Arabic (namely Pashto).
The bitcoin sign is missing, ḂḃḊḋḞḟṀṁṖṗṠṡṪṫ is missing as well.
No more to explain, I'm bored.
The text was updated successfully, but these errors were encountered: