Rationalise use of fonts in documentation
The Polyglossia documentation needs, inevitably, many different fonts. All of them can be found on the Web, probably even under a free software licence, but they’re not all available in one place, so that when setting up a new working environment (for example a new computer) it can be time-consuming to hunt after all the fonts. With the latest (pre-freeze) TeX Live 2020 I needed to download no less than nine different fonts. This can be improved, for example by adding as many fonts as possible in TeX Live, and replacing those that can’t by others.
These fonts are inherent part of polyglossia and the output is nice, in my opinion.
Perhaps the workflow process of github can be used to construct the working environment.
It would be nice, if every commit could trigger a process generating the actual manual, having all the fonts needed.
I've changed the documentation to use fonts that are included in TeXLive, with one exception: There does not seem to be a Syriac otf/ttf font available. The one we use (Serto Jerusalem) is at least included in the x11-fonts collection on Linux, and it can be freely and legally downloaded from the Syriac Institute (as now documented in a comment).
Please check whether this is sufficient.
I detected another font that is not in TeXLive: GFS Ambrosia, used for the Πολυγλωσσία title. I didn't find a similar font that supports Greek in TeXLive and thus replaced it with GFS Complutum (with the nicely matching font file name GFSPolyglot).