So, for example, for Arabic, there is an already-implemented solution for the changes that occur with initial/medial/final and stand-alone forms. These are the kind of issues that arise on font-making fora not conlang-related stuff. You may have a font-maker who’s worked with alphabetic scripts before but has no idea how Chinese works, and so is seeking help. They may have been tasked with creating a single font face that will be identifiable in the Roman alphabet, but also in Chinese, Japanese, Korean, Arabic, Cyrllic, Greek and Hebrew. Many of the people on these fora will be professional font makers who have been hired by businesses to create a font face for their new product.

All of these are problems within the font-making community that have been solved in various ways, and font-makers share tips on how to do it. They have to deal with how to implement Unicode how to do multiple styles (say you don’t just want regular, bold, italic and bold-italic, you also want a condensed version, a half-sized version, an italic version that’s more slanted, etc.) how to do a cursive-like font how to make Arabic ligatures work how to make Hindi ligatures work, etc. The problems that font-makers face are how to create fonts for existing scripts-and that’s it. If you go to font-making forums looking for help with conlang-related questions, you will find absolutely no help, because NO ONE there is doing the same thing and has any idea how to implement what you’re talking about-and, again, the program wasn’t designed to do it.

Remember that a conlanger (assuming you’re a conlanger interested in creating a script) is using a program like Fontlab Studio or any other font-making software for a purpose for which it was NEVER intended. Regarding tutorials, the best thing to do is take a look at the Fontlab Studio manual, which, is, like, 900 pages and free (not kidding). Yes and yes, but I don’t think that things work the way you may imagine they do.

Fontlab studio 5 user manual