Error or error message
- A font used in Word is not transferred to the PDF.
- Possible error message:
Unexpected error / The index was out of array range.
This error message when creating the PDF with axesPDF for Word may indicate a problem with stored fonts.
What happens to the fonts used during conversion?
axesPDF for Word only obtains fonts from the following location for the creation of the PDF:
If a font used in Word is not stored there, axesPDF automatically replaces that font with the font Arial.
So if Arial appears in the PDF instead of the font used in Word, axesPDF for Word could not find the font used in the "C:/Windows/Fonts" location.
What fonts does axesPDF for Word support?
axesPDF for Word supports almost all fonts that are also supported by Word. Even some fonts that Word only displays in a pixeled way are supported by axesPDF for Word.
axesPDF for Word supports TrueType and OpenType.
Possible sources of error
If fonts are not transferred correctly to PDF, there may be several reasons:
- Fonts are embedded only in the Word file itself.
- Fonts have not been installed using admin privileges.
- Fonts managed by Fonts Managers are used.
(1) Fonts are embedded only in the word file itself but do not exist on the system itself
Here's how to check if the font doesn't exist at all on the system:
If the font does not exist on the system, axesPDF for Word will not be able to use it during the conversion and will therefore use Arial as a replacement font.
(2) The font has not been installed using admin rights for all users
Fonts should be installed using a user account with administrative privileges. The easiest way to do this is by right-clicking on the font and selecting the option with the administrator icon ("Install for all users" or "Run as administrator"). This may solve the problem.
(3) Fonts managed by Font Managers
axesPDF for Word will also be able to support this way of font management in the future. Currently, axesPDF for Word does not support this method yet.