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

Make it possible to choose between a font's stylistic sets #10557

Closed
JakobBruenker opened this issue Jul 4, 2021 · 4 comments
Closed

Make it possible to choose between a font's stylistic sets #10557

JakobBruenker opened this issue Jul 4, 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

@JakobBruenker
Copy link

JakobBruenker commented Jul 4, 2021

Description of the new feature/enhancement

OpenType fonts often have stylistic sets that allow users to choose specific alternate characters - for example, old-style numerals instead of lining figures. However, this requires support by the software the font is used with, which is already the case with many editors and terminal emulators.

It would be great if such support were added to Windows Terminal.

This could be a comma-separated option for "profiles" in settings.json, e.g.

    "profiles":
    {
        "defaults":
        {
            // Put settings here that you want to apply to all profiles.
            "fontFace":"Fira Code Retina"
            "stylisticSets":"ss01,ss03,zero,onum"
        },
<...>
    }
@JakobBruenker JakobBruenker added the Issue-Feature Complex enough to require an in depth planning process and actual budgeted, scheduled work. label Jul 4, 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 Jul 4, 2021
@DHowett
Copy link
Member

DHowett commented Jul 4, 2021

You are really going to like #10525!

@JakobBruenker
Copy link
Author

@DHowett Oh, nice, thank you

@zadjii-msft
Copy link
Member

/dup #1790

@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

3 participants