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

TTF cache support #691

Open
bluewaysw opened this issue Oct 31, 2024 · 2 comments
Open

TTF cache support #691

bluewaysw opened this issue Oct 31, 2024 · 2 comments

Comments

@bluewaysw
Copy link
Owner

Building a cache that keeps already computed table for the fonts to be reused later. This will speed up the operation, especially on low end systems.

bluewaysw pushed a commit that referenced this issue Nov 10, 2024
(Kerning on and optimized and fixed)
@bluewaysw
Copy link
Owner Author

To make the cache approach more efficient Iadjusted the threshold for using available kerning information.

The current implementation uses KERN_VALUE_DIVIDENT 100 which translated to "starting at 1% character width of kerning information it is consided for geos rendering".

The following experiments lead to "DIVIDENT -> kern entry count used" for the "Nimbus Sans" font.

100 -> 0x567
40 -> 0x2a5
36 -> 0x278
34 -> 0x261
30 -> 0x1e7

I decided to go with 30, pre-installed cache has been computing using this threshold.

@bluewaysw
Copy link
Owner Author

The preinstalled cache is build (using an GeoWrite document containing all relevant glyphs) for all pre-installed font and styles with the following sizes: 10, 12, 14, 18 (as those are the sizes that are delived as bitmap variants for the original nimbus FNT font files)

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

No branches or pull requests

1 participant