Computers & Writing Systems
Incorrect Behavior of SIL legacy fonts in Word 97/2000/2002/2003 – FAQ
This FAQ addresses issues related to SIL legacy fonts such as SIL IPA93, SIL Galatia, and SIL Ezra in Microsoft Word for Windows. Other FAQ documents that may address your questions are available here.
Question: Is it possible to use the SIL IPA, Greek, and Hebrew fonts in Microsoft Word 1997 and newer?
Answer: See below.
Question: In Word 2000 (and newer) I find that spaces typed in SIL Galatia, SIL Ezra, and SIL IPA93 do not operate as spaces – so word wrap and word selection operate inconveniently. What might I be doing wrong?
Answer: See below.
Question: We find when typing with the IPA fonts that words will break suddenly at the end of sentences. Is there some way to ensure that words do not break?
Answer: The problem you are experiencing with the SIL legacy fonts (SIL IPA, SIL IPA93, SIL Galatia, SIL Ezra) is because they are encoded as symbol fonts, rather than normal text (UGL) fonts. Fonts for Windows may be encoded either as symbol fonts or UGL fonts. Most fonts containing alphabetic characters (e.g., Times New Roman, Arial) are encoded as UGL fonts. Fonts containing symbols (e.g. Wingdings) are typically encoded as symbol fonts. Although the SIL legacy fonts contain alphabetic characters, they are encoded as symbol fonts because doing so enables more characters to be included in the font.
I assume you are using the fonts with Microsoft Word 97, 2000, 2002, or 2003. At the time the SIL legacy fonts were developed, Word treated UGL fonts and symbol fonts in the same way. You could use the spell-checker and thesaurus, move the cursor to the beginning and end of a word with keyboard shortcuts, and lines would break at spaces. But beginning with Word 95 (Word 7), Word began handling UGL fonts and symbol fonts differently. Although Word 95 still recognized word boundaries as previously, you could no longer use the spell-checker or thesaurus on text formatted with a symbol-encoded font. Beginning with Word 97, the characters in a symbol-encoded font are assumed to be symbols, not words, and Word makes no assumptions about what constitutes a word.
If the SIL legacy fonts were UGL fonts, Word would assume they have the standard Windows character set, and would “know” which characters are word-building characters and which are not. But since they are symbol fonts, Word 97/2000 doesn’t try to guess what characters are in the fonts.
Specifically, the following restrictions apply:
For solutions to these and other problems related to symbol fonts, please see Display Issues – FAQ
Note: If you want to add a response to this article, you need to enable cookies in your browser, and then restart your browser.
Note: the opinions expressed in submitted contributions below do not necessarily reflect the opinions of our website.