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

Some ligature don't work in Visual Studio 2017 #422

Closed
davidtme opened this issue May 18, 2017 · 11 comments
Closed

Some ligature don't work in Visual Studio 2017 #422

davidtme opened this issue May 18, 2017 · 11 comments

Comments

@davidtme
Copy link

Most are ok but seems ones with a dash (-) don't

image

@dhouck
Copy link

dhouck commented May 18, 2017

This is a duplicate of #32, #43, #99, #157, #196, #220, #259, #273, and #395.

Of those, #259 has the best information. This is a bug in the editor used in Visual Studio. Microsoft knows about the issue but has not yet addressed it. There is nothing a font can do to fix it.

At this point, I’m starting to think the real issue for the font is that we could document this better so people know before downloading.

@kizerkizer
Copy link

Is this still an issue in the latest VS?

@Gaztin
Copy link

Gaztin commented Nov 22, 2019

Is this still an issue in the latest VS?

Yes this is still an issue in VS 2019 as of version 16.3.10

@Charlie-zzy
Copy link

VS 2019 version 16.3.2 find this issue as well

@stogle
Copy link

stogle commented Feb 21, 2020

This is a duplicate of #32, #43, #99, #157, #196, #220, #259, #273, and #395.

Of those, #259 has the best information. This is a bug in the editor used in Visual Studio. Microsoft knows about the issue but has not yet addressed it. There is nothing a font can do to fix it.

They're now tracking this at dotnet/wpf#109

@julian-a-avar-c
Copy link

VS 2022 version 17.0.4, still an issue

@flundstrom2
Copy link

VS 2022 Version 17.0.5, also issue.

@smile-zyk
Copy link

VS 2022 Version 17.3.5, also issue.

@NPEX42
Copy link

NPEX42 commented Jan 28, 2023

VS 2022 v17.4.4, Still an issue

@Stehsaer
Copy link

VS 2022 v17.7.2, issue still not addressed
:-(

@wopian
Copy link
Contributor

wopian commented Aug 25, 2023

This is a VS issue that Fira Code would have no way of fixing itself - you can follow the (lack of) progress here: dotnet/wpf#109

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

No branches or pull requests