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

[Bug]: Italicized :: seems off on Windows #273

Open
bebraw opened this issue May 7, 2024 · 7 comments
Open

[Bug]: Italicized :: seems off on Windows #273

bebraw opened this issue May 7, 2024 · 7 comments
Assignees
Labels
bug Something isn't working regression

Comments

@bebraw
Copy link
Contributor

bebraw commented May 7, 2024

Edition

Basic (Personal)

What version are you using?

2.015

What type of weights are you using?

Default (non-customized)

Operating system

Windows

Program

JetBrains IDE

Display resolution

No response

What happened?

Below:

image-1
image

Test input: input::placeholder

@bebraw bebraw added the bug Something isn't working label May 7, 2024
@MarcusSterz
Copy link

Can you describe the problem?

@bebraw
Copy link
Contributor Author

bebraw commented May 7, 2024

@MarcusSterz See how :: renders in the screenshots. It's somehow doing : and a dot in the middle. For upright, it's rendering correctly.

@MarcusSterz
Copy link

OK, looks like the path order got messed up. Weird, I don’t recall touching this ligature lately...
Will look into it.

@MarcusSterz
Copy link

So it’s a double colon ligature (white space), right? Looks OK in the specimen section.

@bebraw
Copy link
Contributor Author

bebraw commented May 7, 2024

@MarcusSterz Yeah, that's the weird thing. I wasn't able to reproduce it at the website either (MacOS, though). I wonder if it could be specific to Windows somehow.

@MarcusSterz
Copy link

MarcusSterz commented May 15, 2024

I looked into the Glyphs file. There is no indication for a wrong path that would explain this effect.

Bildschirmfoto 2024-05-15 um 11 44 47

@bebraw
Copy link
Contributor Author

bebraw commented May 24, 2024

I think we might have fixed this in 2.015. Here's a render from WebStorm on Windows 11:

Screenshot 2024-05-24 at 10 57 38

I sent a query to the user to confirm.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working regression
Projects
None yet
Development

No branches or pull requests

2 participants