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

A proper Unicode Font setting #10510

Closed
ndrogers opened this issue Jun 24, 2021 · 4 comments
Closed

A proper Unicode Font setting #10510

ndrogers opened this issue Jun 24, 2021 · 4 comments
Labels
Issue-Feature Complex enough to require an in depth planning process and actual budgeted, scheduled work. Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing.

Comments

@ndrogers
Copy link

ndrogers commented Jun 24, 2021

Description of the new feature/enhancement

I often work with unicode, and as anyone who uses unicode can attest, there aren't many fonts that support really nice unicode glyphs. I have seen the feature request for supporting multiple fonts, as Visual Studio Code does, which allows the user to specify a list of fonts. When a glyph is missing from the first font, VSCode allows missing characters to be rendered using subsequent fonts in the font-family. This feature request has been sitting around for a good few years without movement.

Instead of waiting for that feature to never be implemented, I had an alternative idea that might be an easier fix. I want a second font property in the settings. When there is no glyph available in the primaryFont, the unicodeFont will be used to render the missing glyph.

//settings.json
{

    ...,
    "PrimaryFont": "My Favorite Monospace Font",
    "UnicodeFont": "My Nice Unicode Font",
    ...
}

Alternative approach

You could very well just give me a hotkey to toggle between a primaryFont and secondaryFont so that I can switch when I need to, instead of constantly having to keep my settings file open and manually switch between them.

@ndrogers ndrogers added the Issue-Feature Complex enough to require an in depth planning process and actual budgeted, scheduled work. label Jun 24, 2021
@ghost ghost added Needs-Tag-Fix Doesn't match tag requirements Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting labels Jun 24, 2021
@SamHasler
Copy link

I think it would be better if Windows made configuring font linking easier. Then these fonts would be available to all editors / terminals.

in font linking (also called “composite fonts”) it is possible to link one or more fonts (called "linked fonts") to another font (called the "base font"). Once you link fonts, you can use the base font to display code points that do not exist in the base font, but that do exist in one of the linked fonts.

I've created an issue for it in Microsoft Power Toys repo:
microsoft/PowerToys#11933

@WSLUser
Copy link
Contributor

WSLUser commented Jul 6, 2021

You may enjoy #10525 when it's merged.

@zadjii-msft
Copy link
Member

This sounds like

/dup #1790
/dup #2664

@ghost
Copy link

ghost commented Jul 6, 2021

Hi! We've identified this issue as a duplicate of another one that already exists on this Issue Tracker. This specific instance is being closed in favor of tracking the concern over on the referenced thread. Thanks for your report!

@ghost ghost closed this as completed Jul 6, 2021
@ghost ghost added Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing. and removed Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting Needs-Tag-Fix Doesn't match tag requirements labels Jul 6, 2021
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Issue-Feature Complex enough to require an in depth planning process and actual budgeted, scheduled work. Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing.
Projects
None yet
Development

No branches or pull requests

4 participants