A user reported on another list that a font they installed on Windows 10 was not working with PrintDraft. Windows 10 has recently changed to allow non-administrators to install fonts. However, such user installed fonts are placed in a different location that admin installed fonts, and might not be listed in the Windows registry.
I suspect the issue is with XeTeX, or xdvipdfmx
(which is called by XeTeX) or one of the libraries XeTeX uses (such as FreeType or fontconfig). Thus I don’t think (at the current time) any change should be made to Paratext.
I mention the issue here for two reasons
- So users know of this issue and can install fonts as an administrator, thus working around the issue.
- Paratext developers might be able to also do a simple workaround, and list the full path to the needed font file in the generated .tex files used with PrintDraft. However, if the issue is (let’s say with fontconfig) not finding user installed fonts when called by XeTeX, Paratext could possibly have the same issue if Paratext called fontconfig.