0 votes
351 views

Despite having the default Arial font selected in my Language Settings, that is not the font being used in my Glossary book. I won’t really care except whatever font is being used in the glossary currently does not differentiate between lowercase L and uppercase i

Paratext by (111 points) | 351 views

1 Answer

0 votes
Best answer

I’m confused by your statement that your selected font is not being use in the Glossary. The only way that this might happen is if you are using either a custom.sty or frtbak.sty flie that changes the font. This would happen if the style sheet contains a line like this to specify a different font:
\Fontname Courier New

However, your last comment about capital I (i) and lowercase l (L) is the result of using the Arial font since that font does not distinguish visually between these two characters. To better distinguish the characters you should use a serif font like Charis. When you are in the language settings there is a place to type an example text. You can test different fonts by typing these two characters side by side in the example area.

by (9.8k points)

Hey anon848905,
Thanks for your thoughts. So it is interesting because for both of the issues I am having you mentioned that a custom.sty or frtbak.sty might be causing the problem. I don’t know what a custom.sty or frtbak.sty is and I don’t remember ever adding one. But I’ve been away from our project for several years and am just getting back to it now, so it’s possible that we have a custom.sty or frtbak.sty and I have forgotten. How do I check to see if we have one of those?

So i looked around in My Paratext 9 folders and found a custom.sty in my project but looking at what was in it, it doesn’t seem to like it would be causing the issues I’m having.
Here is what was in it:

Custom style file created by the upgrade to Paratext 8.0. It is based upon

the original style files used by your project.

These files have been removed, but a backup of the files has been saved to

usfm.sty.bak and custom.sty.bak.

\Marker toc1
\OccursUnder h h1 h2 h3

\Marker toc2
\OccursUnder h h1 h2 h3

\Marker toc3
\OccursUnder h h1 h2 h3

I also found another custom.sty file outside of my project folder but still in the Paratext 9 folder. But it only pertained to the colors of the markers See the two screenshots:


I found several other .sty docs (see screen shot) in the same location, but none of them seem to be likely to be causing the issues.

Regarding the Arial font, despite having Arial selected as the font for the project, it was showing the capital i and lowercase L as different in the sample text area and also in the non-glossary books. It was only showing them as the same in the glossary. So i selected another font and applied that to the project and that worked in all the books including the glossary. I then went back and selected Arial again and it show correctly in all the books. So it must have been some sort of fluke/glitch in the matrix going on. Either way, that issue is fixed. its is just the matching markers not showing up that is still an issue. I’ll continue this conversation in that feed.

Related questions

0 votes
3 answers 311 views
I have created and installed a new font (Unicode, complex script, Khmer) to be used with my project. I can choose the ... ? I have no idea of what might be wrong. GB, anon015155
anon015155 153 asked Jan 22, 2020
0 votes
0 answers 158 views
A user has a project (ApalVB) that uses a legacy font. She reports that in the Parallel Passages and ... . Her internet bandwidth is extremely small, supporting only email.
anon895417 129 asked Oct 25, 2018
0 votes
2 answers 293 views
I receive an error when using \qt when the quote includes another marker such as \pg pg*. Does this mean no ... there anyway around this? What is there purpose for this error?
Clear7419 251 asked Sep 14, 2022
0 votes
2 answers 234 views
I just saw a case where the renderings in the project biblical terms list (for a text that is in a non-Roman ... be used for the renderings in the project biblical terms list.
jeffh 1.4k asked Oct 19, 2017
0 votes
1 answer 224 views
image975 442 64.2 KB Would anyone know why this term is not being recognized - and how to fix this? The term (the second ... the text, with * put in for the prefix and the suffix.
anon928451 127 asked Mar 1, 2023
Welcome to Support Bible, where you can ask questions and receive answers from other members of the community.
For we were all baptized by one Spirit so as to form one body—whether Jews or Gentiles, slave or free—and we were all given the one Spirit to drink.
1 Corinthians 12:13
3,037 questions
5,994 answers
5,661 comments
2,022 users