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

Fallback fonts on SDL2 #338

Closed
laurence-flwls opened this issue Feb 14, 2024 · 4 comments
Closed

Fallback fonts on SDL2 #338

laurence-flwls opened this issue Feb 14, 2024 · 4 comments

Comments

@laurence-flwls
Copy link

laurence-flwls commented Feb 14, 2024

Hi, I'm creating a terminal emulator in SDL2 and finding a lot of characters aren't present in a particular type-face (examples below).

I'd like to be able to define fallback fonts to cover instances were glyphs aren't available in the default type face.

After a bit of searching online, the only reference to this issue I could find was a Github issue from 2019 which sounded like a fix was soon to be merged. However, unless I've missed something obvious in the docs, I cannot find how implement that.

eg:
my terminal emulator (SDL2) vs iTerm2 -- under the DEC Special graphics and line drawing heading:

image
image

@slouken
Copy link
Collaborator

slouken commented Feb 14, 2024

Could you link the GitHub issue you found? I'm not seeing it.

@laurence-flwls
Copy link
Author

@slouken my apologies, it wasn't an official SDL repo: grimfang4/SDL_FontCache#29

@laurence-flwls
Copy link
Author

So if we ignore the unrelated project, what would be the recommended way to solve my problem here? Because it's a text heavy application, a performant way to validate the glyphs would be preferable.

There is another curveball here though, I'm writing this terminal emulator in Go (golang). I do have some experience in C and older versions of C++ too so I can work my way through a C solution and port it to Go if needed. The only reason I favour Go these days is because it's faster (for me at least) to prototype code.

@slouken
Copy link
Collaborator

slouken commented Jun 10, 2024

Duplicate of #362, which has better repro steps.

@slouken slouken closed this as not planned Won't fix, can't repro, duplicate, stale Jun 10, 2024
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

2 participants