E1: XMLP: Field with Custom Font Shows Gibberish/Garbage Characters when Template is Reopened in Microsoft Word
Last updated on MAY 30, 2017
Applies to:JD Edwards EnterpriseOne Tools - Version 8.98 and later
Information in this document applies to any platform.
Sometimes after a custom font is applied to a field and the document saved, the next time the document is opened, the BI Publisher code and field name appear as gibberish/garbage. At this point, if the document is saved, the field will be corrupt will not work in BI Publisher.
This issue is typically seen when using the font 128R00.TTF (Code 128) delivered with BI Publisher Desktop.
During initial setup, the field and its definition look fine:
But after the document is saved and opened again in MS Word, the field will appear corrupt:
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms