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

question: font rendering speed different between sarasa-gothic-ttf-0.8.2 and the latest 0.37.4 #305

Closed
asmwarrior opened this issue Oct 16, 2022 · 9 comments
Labels

Comments

@asmwarrior
Copy link

asmwarrior commented Oct 16, 2022

Hi, I just test several versions of the sarasa-gothic-ttf font release under Code::Blocks IDE under Win7 64bit, which renders the font in normal GDI mode.

The sarasa-gothic-ttf-0.8.2 version(released in year 2019), such as: sarasa-mono-sc-regular.ttf, the editor renders very fast
The latest release sarasa-gothic-ttf-0.37.4 with hinting version, the editor renders very slow, I can see the whole page get updated when I scroll the page. Though the un-hinted version renders fast, but the font shows badly because some lines of the font may be too trick.
I choose another version such as: sarasa-gothic-ttf-0.16.5(released around year 2021), it also renders very slow.

My question is:
What is the different between those release? I don't see much change logs of each release, but only a git tag about the version number.

The size of the font is also different, for example, the 0.8.2 version of sarasa-mono-sc-regular is about 34M, while the latest 0.37.4 release this same file is about 23M, so why the ttf size is smaller, but the render time get longer?

Thanks.

@asmwarrior
Copy link
Author

asmwarrior commented Oct 16, 2022

Another question is:

in the 0.8.2 release, there are two files named sarasa-monoT-sc-regular.ttf and sarasa-mono-sc-regular.ttf. While in the latest release, there is only one file named sarasa-mono-sc-regular.ttf. So, what is the difference between mono and monoT, thanks.

@github-actions
Copy link

This issue is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 15 days.

@github-actions github-actions bot added the stale label Dec 16, 2022
@asmwarrior
Copy link
Author

I think this is not stale, the issue just not get comment for about 15 days.

@github-actions github-actions bot removed the stale label Dec 17, 2022
@github-actions
Copy link

This issue is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 15 days.

@github-actions github-actions bot added the stale label Feb 15, 2023
@asmwarrior
Copy link
Author

I think this is not stale, the issue just not get comment for about several days.

@github-actions github-actions bot removed the stale label Feb 16, 2023
@github-actions
Copy link

This issue is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 15 days.

@github-actions github-actions bot added the stale label Apr 18, 2023
@asmwarrior
Copy link
Author

I think this is not stale, the issue just not get comment for about several days.

@be5invis
Copy link
Owner

I think one difference is that the newer versions use a more complex embedded instructions to reduce the size. As a result, it may take more time for glyphs' first rendering.

Resolve as by design.

@asmwarrior
Copy link
Author

I think one difference is that the newer versions use a more complex embedded instructions to reduce the size. As a result, it may take more time for glyphs' first rendering.

Resolve as by design.

Hi, be5invis, thanks for the explanation.

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

No branches or pull requests

2 participants