Who I am, in working terms
I am the creator and editor of Fancy Text Generator. This page describes me by the work I do on this site, rather than by a name and a life story, because what should matter to you is the work and the standards behind it.
Fancy Text Generator is an independent project, built and run by one person. When a page here says “we tested this”, it means I tested it, on real devices, before the words went live.
What I do on this site
I build and maintain the generator itself: the alphabets, the decoration wrappers and the effects that make up the 717 styles. Every style in the library was added by hand and checked letter by letter against the Unicode charts.
I also write and edit every page. The guides under each tool exist because a list of styles is not enough. You deserve to know where a style works, where it breaks, and which letters an alphabet honestly does not have.
When something is wrong, I fix it. A broken style, a wrong count, a claim that a new app update has made untrue: those are my jobs, and reader reports are how I hear about most of them.
The standards I work to
Every style count on this site is the real count from the engine. Nothing is rounded up for effect, and the number never grows before the styles behind it exist and pass testing.
Claims get tested before they are published. If a page says a style works in an app, that claim comes from a paste test, or the page says plainly that the test is still pending. I would rather publish a smaller true claim than a bigger shaky one.
Corrections are welcome and acted on. If you spot an error, tell me, and if you are right the page gets fixed.
Being corrected by a reader is not a failure here. Leaving a known error live would be.
What I check every day
My daily round covers three things. First, new style requests from readers, which decide which packs get built next. Second, display problems: reports of styles showing as boxes or breaking in an app after an update.
Third, page accuracy. Apps change their rules and their fonts, so I re-check the guides against how things work now, and update any page that has gone stale.
Talk to me
The fastest way to reach me is the contact page, or email at [email protected]. Style requests, bug reports and corrections all land with me directly.
If you want the wider picture of the site and why it exists, the about page covers that. This page stays what it is: a plain account of the person behind the work, in the role that does the work.