Caius Nocturne b0f12c2c34 Bundle improvements and fixes | hai 5 meses | |
---|---|---|
input | hai 5 meses | |
manifest | hai 5 meses | |
texts | hai 6 meses | |
.gitattributes | %!s(int64=6) %!d(string=hai) anos | |
.gitignore | hai 1 ano | |
README.md | hai 1 ano | |
out_all_slice.sh | hai 1 ano | |
out_bundle_test.sh | hai 5 meses | |
out_coherence_test.sh | hai 1 ano | |
out_final_full.sh | hai 6 meses | |
out_final_slice.sh | hai 6 meses | |
readme.md | %!s(int64=4) %!d(string=hai) anos | |
translating.md | hai 1 ano |
This repository contains all of the files required to build a custom Mutant Standard package using Orxporter.
These files are for anyone who is techy enough and is interested in seeing what a large Orxporter project looks like, or wants to create their own Mutant Standard packages in a format that's not offered by the website.
If you're a regular user, I highly suggest you go to Mutant Standard's download page and download a package that's best for you.
Everything in this repository is licensed under a Creative Commons Attribution-NonCommercial-ShareAlike 4.0 International License.
There shouldn't be any significant difficulties in using this on various major OSes, and both Orxporter and Forc have been written to be cross-platform. From one time to another these tools have been used on both macOS and Linux.
If you want some ideas on how to make your own scripts and commands, in the root of this repo there are .command
executable scripts, all of which are the ones I use in everyday tests and for the final export of each release.
The Orxporter repo has full documentation on how to create your own build commands and understand manifest files.
Check out the translation doc for some guidance.
/input
is where the input emoji SVGs are./manifest
is where all the manifest files are, including license metadata./Orxporter
is where Orxporter should go./Forc
is where Forc should go./out
is where the exported emoji go (I recommend putting the output of any task in a sub-folder so you can make multiple types of exports without conflicts).(I have decided to stop developing font technology on my end, but it's still easy to compile a font using Orxporter and Forc.)
./Orxporter/orxport.py -m manifest/out.orx -i ../input -q 32x32 -o out/font_sources -F svg,png-32,png-64,png-128 -t 4 -f %f/%u
Forc
directory../Forc/Forc.py -m manifest/font/manifest.json -a manifest/font/aliases.json -i out/font_sources -o out/fonts -F [formats] --afsc
See Forc's help (-h
flag) to see what formats you can export to. Forc also has a readme and documentation.
(the --afsc
build flag is super-important if you're building a SVG font with Mutant Standard's images, do not remove it.)