10G - 11G Identity_H Encoding Issue In BIP While Previewing BIP Report In PDF (Doc ID 1565022.1)

Last updated on APRIL 04, 2025

Applies to:

Goal

Product version: BI Publisher 10.1.3.4.2.

The goal of this document is to answer a few questions about Identify-H enconding in font properties.

Question 1:

We have added a new font in <DIR>/Fonts to our xdo.cfg file also. When we preview our report templates in PDF format, the message 'Identity-H Encoding in font properties' is displayed. How can we change this Encoding to Custom so that when we send the report to other applications, the text is readable with the new font?

Question 2:

Restatement of problem:

We are adding 4 Vodafone fonts with TRUE TYPE in <DIR>/Fonts and the xdo.cfg file on a local desktop.
When we preview the template in PDF form and check for Document Properties (File-->Properties--->Fonts), we get Type:True Type(CID) and Encoding:Identity-H.

This happens as soon as a PDF gets Identity-H in Font properties. Why does this happen?

Business impact:

As a result of this, iText libraries written in Java cannot read the pdf, and it is stopping our integration with other Java applications. We need to integrate our BIP reports with other Java applications. This is not possible if Encoding:Identity-H appears.

How to avoid Encoding:Identity-H.

Question 3:

How to add pfb and pfm as attributes of type1 font element?

Solution

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.