有用户在另一个列表上报告称，他们在 Windows 10 上安装的字体在 PrintDraft 中无法正常工作。Windows 10 最近更改了策略，允许非管理员安装字体。然而，这类由用户安装的字体存放位置与管理员安装的字体不同，并且可能不会列在 Windows 注册表中。
我怀疑问题出在 XeTeX 上，或者 xdvipdfmx（由 XeTeX 调用）上，或者是 XeTeX 使用的某个库（例如 FreeType 或 fontconfig）上。因此，我认为（目前）不应该对 Paratext 进行任何更改。
我在这里提及此问题有两个原因
- 让用户了解此问题，并可以以管理员身份安装字体，从而绕过此问题。
- Paratext 开发人员可能也能采取简单的变通方法，在用于 PrintDraft 的生成的 .tex 文件中列出所需字体文件的完整路径。但是，如果问题在于（例如 fontconfig）在被 XeTeX 调用时找不到用户安装的字体，那么如果 Paratext 调用 fontconfig，Paratext 也可能遇到同样的问题。
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.
机器翻译自 English
