Replies: 2 comments
-
That's cool, playing round with font encodings can be fun, and educational. I hope your project brings joy! etc ;-) Eliminating the dict structure and all 'extras' will certainly help for a dedicated project! Have you tried the memory tests I used here? I'd be curious to see the results. I'm wondering why you didnt wrap the whole tuple as a For the fonts I'm publishing I need to keep backwards compatibility with the original format, so externals like REVERSE are needed. For instance min and max ch are used in my glyph dumper. They add very little extra to memory use. It's the dict{} that eats RAM ;-) The other thing I note is that you are assuming a linear block of characters; this is true in many use cases, but not all. By using a dict I can encode just the characters needed, even when they are spread out in the charset. This was why I chose a dict{} over a simple list[] or tuple() and a index offset. |
Beta Was this translation helpful? Give feedback.
-
@HLammers The functions are provided to be consistent with fonts produced by font-to-py and compatibility with nano-gui and micro-gu. They use minimal RAM. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Hi @easytarget,
Thank you for your awesome work! I’m using a highly adjusted version of your code in a project of mine (not yet published) and I’d like to share how I imporved the size of the font file when loaded to memory:
This is an example:
Beta Was this translation helpful? Give feedback.
All reactions