One limitation after migrating to Paratext 8 is you cannot change the font used by resources you download. I’ve figured out it is possible to specify a different font for a resource with a little manual editing of the user.config There is a section called ProjectFontOverrides, that looks like this:
<setting name="ProjectFontOverrides" serializeAs="Xml">
<value>
<SerializableStringDictionary>
<item>
<string>NIV11</string>
<string>Sylfaen:14::</string>
</item>
<item>
<string>NRSV</string>
<string>Tahoma:12::</string>
</item>
<item>
<string>CEVUS06</string>
<string>Times New Roman:14::</string>
</item>
</SerializableStringDictionary>
</value>
</setting>
You can type a different font name in the second “string” section, below the string identifying the project name. For instance if I would rather have the CEVUS06 in Arial, I’d change this to
<setting name="ProjectFontOverrides" serializeAs="Xml">
<value>
<SerializableStringDictionary>
<item>
<string>NIV11</string>
<string>Sylfaen:14::</string>
</item>
<item>
<string>NRSV</string>
<string>Tahoma:12::</string>
</item>
<item>
<string>CEVUS06</string>
<string>Arial:14::</string>
</item>
</SerializableStringDictionary>
</value>
</setting>
This user.config file is in the Appdata folder. Complete path: c:\users_yourusername_\Appdata\Local\United_Bible_Societies\paratext.exe (followed by a long string of random letters)\Paratext version #
Be aware, if you have Paratext 7, it puts settings in a “United Bible Societies” folder in Local, with spaces between the names, Paratext 8 uses the “United_Bible_Societies” folder.
If you don’t see a “ProjectFontOverrides” section in your user.config, you can have Paratext begin it for you by changing the point size for a resource that permits this, like the NIV11.
Developers, any hidden dangers in editing this file? I think if it gets corrupted or missing, Paratext will just recreate a default copy. So if you make any special font assignments, you’ll have to redo them if you ever reset Paratext.
