有使用者在另一個論壇回報，他們在 Windows 10 上安裝的字型無法在 PrintDraft 中正常運作。Windows 10 最近已更改設定，允許非管理員使用者安裝字型。然而，這類由使用者安裝的字型存放位置與管理員安裝的字型不同，且可能未列於 Windows 登錄中。
我懷疑問題出在 XeTeX，或 xdvipdfmx（由 XeTeX 呼叫），或是 XeTeX 所使用的其中一個函式庫（例如 FreeType 或 fontconfig）。因此，我認為（就目前而言）不應對 Paratext 進行任何變更。
我在此提及此問題有兩個原因：
- 讓使用者知道這個問題，並可以管理員身分安裝字型，從而規避此問題。
- Paratext 開發人員或許也能採取簡單的規避措施，即在用於 PrintDraft 的生成 .tex 檔案中列出所需字型檔案的完整路徑。然而，如果問題是（假設是 fontconfig）在由 XeTeX 呼叫時找不到使用者安裝的字型，那麼如果 Paratext 呼叫 fontconfig，也可能會遇到相同的問題。
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
