v1.0 Emo graduates: More emoji, a more robust implementation

They grow up so quickly, don't they? 🎓

• The emoji table now abstracts over emoji, their Unicode codepoints, and Unicode groups to enable easy reuse of that information.
• The documentation builds on that macro interface to include a nicely formatted list of all emoji in the default configuration, organized by Unicode groups.
• The default configuration now includes all 1,415 emoji in Unicode 15.0 that do not modify gender, hair, or skin. You can still enable the remaining 2,240 emoji with emo's configuration script.
• The implementation has been completely restructured to use LaTeX hooks. That way, it avoids code duplication and is more easily extensible.

Emo has been submitted to the ACM for inclusion in the list of supported LaTeX packages. If you too want to use emoji in your scholarly writing, it wouldn't hurt to let them know!

v0.4: Remove extra space & introduce test suite

v0.3 inadvertently introduced a bug into \emo, with the macro expanding to the (desired) emoji and an (illegitimate) space with some LaTeX engines. My bad!

This release fixes the bug and does penance by also introducing a shiny new testing framework for emo. It may not enforce that many assertions (3 each for 3 engines) but those assertions provide full coverage of normal macro operation and the results are presented in most handsome and helpful reports. You can use the same build.sh script that produces the documentation in emo.pdf for also producing the combined test results from pdflatex, xelatex, and lualatex in canary.pdf. 🥳

v0.3: Handle More Backends More Elegantly

To make sure that emo-generated emoji don't get stuck in LaTeX and PDF, emo now supports TeX4ht in addition to LaTeXML for converting LaTeX to HTML. This time, I didn't create a binding'' or configuration'' but integrated the necessary backend (which emits Unicode code points without font changes) into the package implementation. That triggered a substantial refactoring of emo's core to be more structured and to avoid alternative macro definitions for user macros (which used to repeat quite a bit of code across all alternative definitions). That resulted in \lingchi and \YHWH delegating to \emo by default, which is just sweet. Alas, the font backend still requires alternative definitions to actually use the correct fonts. That's unavoidable.

v0.2: Add LaTeXML support; clearly name runtime files

Since we need our best humor on April 1, here are nicely improved emo•ji for all (LaTeX engines):

• Use emo- prefix for graphics and font files to uniquely identify the package.
• Use pdftex to extract files from emo.dtx without building documentation.
• Include LaTeXML binding for conversion to HTML.
• Replace broken lingchi.otf with working emo-lingchi.ttf—notice the .ttf extension vs the previous .otf
  • Under LuaLaTeX, drawing a box around 凌遲 resulted in a box with zero height—even though both fonts
    have the same OS/2 and hhea tables. Suspecting some issue with the CFF tables, I created a TrueType
    version, which works. Go figure!