search

microsoft / cascadia-code

This is a fun, new monospaced font that includes programming ligatures and is designed to enhance the modern look and feel of the Windows Terminal.
Other
25.9k stars 805 forks source link

【Feature Request】Consider to add support for phonetic symbols #374

Open byyxx128 opened 4 years ago

byyxx128 commented 4 years ago

Description of the new feature/enhancement (with images if possible)

It seems cascadia does not have a complete support for phonetic symbols. Sometimes I need to use phonetic symbols, but the different fonts make me uncomfortable.

Proposed technical implementation details (optional)

Please add support for phonetic symbols.

kenmcd commented 3 years ago

Just another user here ... You need to be more specific about exactly what symbols you want, and for what usage. The phrase "phonetic symbols" covers multiple Unicode blocks and a few hundred characters.

If you need just a few additional characters for a specific use, you may get a response. But it is unlikely that all the "phonetic symbols" would be added.

So please provide details and how it relates to the target use or goals of these fonts. Then you may have a better chance of getting the symbols added.

Phundrak commented 3 years ago

I think what byyxx128 meant was the addition of the glyphs from the International Phonetic Alphabet (IPA). Here is a render of a couple of tables found on this wikipedia page with the font from the ArchLinux package otf-cascadia-code version 2102.03-1 (the latest available when commenting, from the community repo) used under Emacs 28.0.50 (feature/native-comp branch): 2021-02-19-114227_1445x858_scrot

The relevant Wikipedia page for the IPA glyphs and their Unicode code can be found here.

I agree adding the entirety of the IPA would be a lot of work, which is why I believe the most important ones to add are the ones presented on this page (except for the arrows) as they are most common. The rest could be treated in decreasing orders of priority, with the IPA extensions at the lowest level in this issue. I would put this order of priority:

  1. characters 0251 through 01C3
    • early implementation of 02DE might also help with the generation of 025A and 025D
  2. characters 02C8 through 02DE
  3. characters 0325 through 0361

I don’t know how widespread the usage of IPA symbols in monospace fonts is, but in my usecase I write most of my linguistics documents in Emacs, so a monospaced font supporting IPA characters would be very, very nice to have, especially if they’d finally stop breaking character alignment.