Product

Platform

Operating system

Error

Symptoms

There are occasionally cases where there is a known bug between a specific glyph for a certain font and the Prinergy RIP (for example, the "ban" glyph on the Japanese font "ShinGo-Ultra" had trouble on the Prinergy 2.2 and lower RIP).

Sometimes a customer will want Prinergy to warn on certain glyph/font combinations, so this workaround outlines how you can configure Normalizer JTP's manually to detect the combination.

When this function (CID Font Glyph Detector) is enabled and a file containing one or more of the specified CID Font/Glyph pairs is Refined, the file will fail Refine. If the Refine process failed only because of the CID Font Glyph Detector, there will NOT be a big black X on the Refined PDF.

Cause

Solution

A. How to enable the CID Font Glyph detector

.

1) start regedt32.exe or regedit.exe

2) navigate to HKEY_LOCAL_MACHINE\SOFTWARE\CREO\Araxi\Settings\Default\ENOR

3) double click on ENOR key to expand

*

4) double click on <NormJTPName> key to expand (should see Debug and DistillerDefault keys)

5) highlight <NormJTPName> key and select Add Key from Edit menu

6) type "CIDFontGlyphDetector" (no quotes) in the Key Name field of Add Key dlg box

7) click OK and the CIDFontGlyphDetector key is created

**

8) highlight the CIDFontGlyphDetector key

9) Select Add Key from Edit menu

10) type <CID Font Name> (e.g. ShinGo-Ultra) in Key Name field of Add Key dlg box, where <CID Font Name> is the name of the Font for which there is one or more glyphs you want to detect. Click OK and the <CID Font Name> is created.

***

11) highlight key created in step 10).

12) select Add Value from Edit menu

13) type Glyph1 in Value Name field, select REG_DWORD for Data Type in dropdown, click OK

14) type <Glyph Id> in Data field, where <Glyph Id> is the CID of the Glyph to be detected.

E.g for the ShinGo-Ultra "ban" glyph, enter d6b (hex) or 3435 (decimal)

***

15) Repeat steps between *** for each glpyh that needs detection. The name of each new value must be distinct (e.g Glyph1, Glyph2 etc.)

**

16) Repeat steps between ** for each font that needs detection

*

17) Repeat steps between * for each <NormJTPName> that exists in ENOR

18) Re-start all Normalizer JTPs

.

So an example of what the registry would look like after setting up some CID Font/Glyph pairs (Glyph ids are in hex)

.

ENOR

.Normalizer1 <----------------- <NormJTPName>

..CIDFontGlyphDetector

...ShinGo-Ultra <---------- <CID Font Name>

....Glyph1 = 0xd6b <----- <Glyph Id>

..Debug

..DistillerDefaults

.Normalizer2

..CIDFontGlyphDetector

...ShinGo-Ultra

....Glyph1 = 0xd6b

..Debug

..DistillerDefaults

.

-------------------------------------------------------------

B. How to disable the CID Font Glyph detector:

1) For each <NormJTPName>, delete the CIDFontGlyphDetector key

2) Restart all Normalizer JTPs

Permanent fix:

See also

Keywords

font, normalizer

Technical contact(s)

Junko Hamada

Submitted by

Junko Hamada

Date submitted

16 Jan 2004