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

File size savings over avar1 release, as a README badge #58

Open
davelab6 opened this issue Aug 3, 2024 · 3 comments
Open

File size savings over avar1 release, as a README badge #58

davelab6 opened this issue Aug 3, 2024 · 3 comments

Comments

@davelab6
Copy link
Member

davelab6 commented Aug 3, 2024

By my calculations...

File glyphs file-size bytes per glyph
RobotoA2-avar2-VF.ttf 1,042 476,856 457.63
RobotoFlex[...].ttf 948 1,787,292 1,885.33

1,885.3291139241/457.6353166987 = 4.11x smaller
457.6353166987/1,885.3291139241 = 24.27349757%

I wonder if @sannorozco can quickly set up a https://shields.io badge to keep track of this number right on the README :)

sannorozco added a commit that referenced this issue Aug 6, 2024
@sannorozco
Copy link
Collaborator

Added at the beginning.

@davelab6
Copy link
Member Author

davelab6 commented Aug 6, 2024

Nice! This isn't quite what I meant, which is the badge should only have the percentage calculation result, eg 24%, which is "this" number, and the table isn't needed - although if you have a way to dynamically calculate it and reinsert/update the read me file on each commit, it's fine to keep it.

Maybe sheilds.io can't do the calculations and this is not easy to do though...

@davelab6
Copy link
Member Author

davelab6 commented Aug 6, 2024

@sannorozco says it seems like Sheild doesn't support calculation so this has to be done manually, which is fine, but then we can just have the markdown table and remember to update it periodically :) The current shield is display 'live' file size though.

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