-
-
Notifications
You must be signed in to change notification settings - Fork 0
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
Test SSTORE reconstruction. #6
Comments
This is much smarter than the last proposal I saw. (0xBeans/FontRegistry#3) Probably what you want to do is use Python via wasm: This would benefit free fonts community as a whole as a working fontmake that runs in wasm is broadly useful. Another thought is that what you are doing here is essentially just recreating METAFONT. You could instead use METAPOST (via, perhaps, wasm once again, this time made through e.g. emscripten). |
Rendering VS Assembling, Combining or SýnthesiAs for metafont, I do notice what you mean, specifically that it includes drawing equations, like maybe:
We do have considered the idea of adding initial shapes not from existing files but from lists of coordinates existing in the instructions themselves, and be able to manipulate some individual coordinates for minor fixes, but we have no capacity yet to do things like draw a variable stroke single line letter ( Metafont 😲), someday? maybe? At the moment I try to keep it at "plumbing" level, just connecting the letter partials, modular stuff, and letting the user figure out the connections system. This allows me to also invest my time in a way that the team will not be overwhelmed. Basically we try to remove duplication wherever we see it, without creating a very demanding rendering system, more of a recombining system. Node EditorI would also consider the idea of a node editor to help visualize the results and also make drag and drop adjustments. enSYFFying Existing FontsThen maybe, from our existing codebase, we could use the Similarity Extractor that checks for letters that are similar, funny enough it's the same used for kerning compression, and one could throw in an existing font, and the SMEX could suggest what letters could be removed as they are dups and add the SYFF code for their generation from other letters or partials. Current Needs and PlanI am trying to work on this while working on AEOLUM font, here is the plan and the needs of the font and how I am thinking of using SYFF to generate the letters. On or OffTruthfully whether this will be used #onchain or off, it is still a good method as it is a size reduction and also a design system, that could be beneficial as CSS is for the web. @ctrlcctrlv thank you for your evaluation, and MFEK, and others who are interested, we will try to put some traction into this one, your help is appreciated. Have an awesome weekend! #metafont #metapost #wasm #emscripten |
METAFONT is a programming language. So you could very well write exactly what you've done here in it. Some METAFONT fonts are even written this way. |
Here's an example from file
If I run... mpost '&mfplain' "\\mode:=localfont; mag := 20.0; outputtemplate := \"%j-%c.svg\"; outputformat := \"svg\"; input /usr/share/texlive/texmf-dist/fonts/source/public/cm/cmsy10.mf;"
|
SYFF_Node_Editor_005.mp4 |
@eliheuer @davelab6
The size of a font on SSTORE:
From the email, identified chunks:
We get all that build the font on the client with Javascript like with fontkit and varLib models that exists in JS already with client-side code.
Or we provide an API service that builds the font with Python or whatnot, but this defeats the purpose cause KBs on the net, while it could be done on the client with no bandwidth. Hints at SYFF but in JS.
Cost $13.82/KB? Advise on GAS please.
The font would be about 35KB reconstructed a lot bigger but client side. 483.7$ per font. But keep in mind the alterations also cost in case we have to change the content.
The text was updated successfully, but these errors were encountered: