Skip to content
Mutant Standard Build Files
Branch: master
Clone or download
dzuk-mutant Removed font manifests
Font manifests aren't meant to be here atm and they contain UUIDs (*screaming internally*).
Latest commit 4d1e1a2 Apr 12, 2019
Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
input Mutant Standard 0.4.0 Apr 12, 2019
manifest
.gitattributes Initial commit Oct 31, 2018
.gitignore
license.txt Mutant Standard 0.3.1 (Initial Commit) Oct 31, 2018
out_final.command Mutant Standard 0.3.1 (Initial Commit) Oct 31, 2018
out_test_svg.command Mutant Standard 0.3.1 (Initial Commit) Oct 31, 2018
out_web_content.command Mutant Standard 0.3.1 (Initial Commit) Oct 31, 2018
out_web_content_json.command
readme.md
translating.md Mutant Standard 0.4.0 Apr 12, 2019

readme.md

Mutant Standard Build Files

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.

This repository has no warranty and has only been tested in macOS.


License

Everything in this repository is licensed under a Creative Commons Attribution-NonCommercial-ShareAlike 4.0 International License.


How to use

  • Download the latest version of Orxporter.
  • Place Orxporter in the /orxporter directory.
  • Start running export commands from the root directory of this repo.

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.


Translating?

Check out the translation doc for some guidance.


Locations of things

  • /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.
  • /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).

PNG exports take a long time!

There are thousands of emoji, and rendering all of them in PNG will take many hours, especially depending on what resolutions and how many PNG versions you wish to export.

So just be careful and be prepared to set aside a few hours to wait for a full export if you're not using a computer that has serious horsepower.

You can’t perform that action at this time.