On Tue, Jun 2, 2015 at 2:26 PM, david.boerschlein@juno.com wrote:

(*) tex error > error on line 1 in file /var/www/vhosts/door43.org/tools/nototest.tex: ! Undefined control sequence l.1 \useregime [utf] 1 >> \useregime[utf] 2 \enableregime[utf] Version: 2015.05.24 12:42

If you are using MkII (that is: if you are running "texexec"), you should use \enableregime[utf-8] If you use LuaTeX, there's no need to enable UTF-8. It's already the default.

(*) Upgrading with "first-setup.sh" deleted all the third-party fonts which we had spent months installing.

I'm sorry to hear that. The idea is to install fonts to texmf-local or texmf-fonts or texmf-project or somewhere else. But the files get removed from "texmf", "texmf-context", "texmf-modules" etc. I'm sorry that that wasn't clear (or maybe not even mentioned) in the documentation.

(*) Installing the "context=current" installed a "beta" version of luatex: context --version mtx-context | current version: 2015.05.24 12:42 luatex --version This is LuaTeX, Version beta-0.80.0 (TeX Live 2015) (rev 5238)

A "non-beta" version of LuaTeX doesn't exist.

(*) http://tug.org/pracjourn/2005-2/schmitz/schmitz.pdf (none of the commands texfont, ttf2afm, updmap, come with the latest ConTeXt minimals 2015.05.24 12:42) [Is this really the up-to-date documentation on how to install a true-type font?] It does not seem to discuss what to do if all we have is an ".otf" but no ".ttf"

The documentation is from 2005 as the URL suggests. So no, it's not up-to-date. Use LuaTeX instead and you can forget about dirty workarounds to get the fonts to work.

(*) Documentation request: typescripts for "ttf" and "otf" files which may or may not have bold, italics, etc with fallback-families and Unicode ranges and separate files for Unicode-ranges (e.g., Google Noto fonts).

This is all possible (it might require a bit of work to get everything set up properly), but you should definitely switch to LuaTeX. Mojca