Skip to content
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

Closed
bedriczwaleta opened this issue Feb 21, 2021 · 17 comments
Closed

Character addition request. #419

bedriczwaleta opened this issue Feb 21, 2021 · 17 comments

Comments

@bedriczwaleta
Copy link

bedriczwaleta commented Feb 21, 2021

This font does not contain Arabic (namely Pashto).
The bitcoin sign is missing, ḂḃḊḋḞḟṀṁṖṗṠṡṪṫ is missing as well.
No more to explain, I'm bored.

@aaronbell
Copy link
Collaborator

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 (̇, uni0307).

@bedriczwaleta
Copy link
Author

bedriczwaleta commented Feb 21, 2021

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.

@aaronbell
Copy link
Collaborator

Sorry, your comment makes no sense.

@bedriczwaleta
Copy link
Author

What does that means? I plan Bitcoin, Pashto, Hebrew but not Yiddish, Thai, to make Cascadia multilingual. You think that's misinformation.

@aaronbell
Copy link
Collaborator

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:

I would like to use Cascadia Code for Arabic (Pashto) and Hebrew applications but noticed that the font doesn’t support Arabic. Could that be added? It would also be useful to add ḂḃḊḋḞḟṀṁṖṗṠṡṪṫ, as those glyphs are used for Hebrew romanization. And the Bitcoin symbol too, please. Thank you!

As I stated previously, issue #84 covers the addition of Arabic, and I will consider the other requests. Thanks for submitting an issue.

@aaronbell
Copy link
Collaborator

In the ISO 259 Romanization of Hebrew, the overdot is used to transcribe the dagesh: ⟨ḃ ḋ ġ ḣ ṁ ṅ ṙ ṡ ṥ ṧ ṩ ṫ⟩; ⟨ẇ⟩ transcribes the shuruk.

🤷‍♂️

@bedriczwaleta
Copy link
Author

No. That is old Irish.

@aaronbell
Copy link
Collaborator

If you would like to file a bug to support ISO subset1 and 2 please do so. Thanks.

@bedriczwaleta
Copy link
Author

No. Just no. This is Pashto

ابپتټثجځچڅحخدډذرړزژږسشښصضطظعغفقکګلمنڼوهیېيۍئےءَُِٙـ،؛؟۹۸۷۶۵۴۳۲۱۰, ﴾﴿ﷲ﷼, but also you need more Presntation forms A and B. and
(sorry if I put duplicates in the diacs, Ẓẓ is needed as well.)

This was referenced Feb 21, 2021
@aaronbell
Copy link
Collaborator

I have created three new issues to better track the separate character addition requests by @bedriczwaleta. As such, am closing this thread. Thanks.

@bedriczwaleta
Copy link
Author

If you want to know, Subset1 was made by @yg8ijvjvjv for his monospaced fonts as a requirement

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants
@aaronbell @bedriczwaleta and others