VERIFIED SOLUTION i
X

AFP output created with Doc1 external keyed image map doesn't display the keyed images in Vault.

Issue

Symptom: AFP output created with Doc1 external keyed image map doesn't display the keyed images in Vault.

Cause

Cause: These ingest into Vault 7.0, but certain images don't show up. The e2loaderd log shows them as size zero.

 

05:33:14 replaced resource, filename [S1G00010], size [512837]

05:33:14 replaced resource, filename [S1G00002], size [20782]

05:33:14 replaced resource, filename [S1IMPTSA], size [0]

05:33:14 replaced resource, filename [S1IMMVSP], size [0]

 

I also tested in Vault 7.2. The images still don't show up, but I see this in the e2loaderd log:

 

17:20:11 extracted resource, filename [S1G00010], size [512837]

17:20:11 extracted resource, filename [S1G00002], size [20782]

17:20:11 extracted resource, filename [S1IMPTSA.jpg], size [160938]

17:20:11 extracted resource, filename [S1IMMVSP.jpg], size [119256]

 

Note that they are JPGs. This AFP was created in Doc1 using an "external keyed image map" that allows the insertion of JPGs into AFP. Per the Doc1 Designer Guide:

 

Output device Supported resource format

AFPDS Page Segment (FS45 & FS10 IOCA) and for printers with the relevant object container support, JPG, EPS, GIF, PDF Page Objects, TIF, BMP

 

Dumping the AFP shows the following information for one of the "bad" page segments:

 

Structured Field Type: IOB (Include Object, x'D3 AF C3')

Start byte: 6,155,893 (x'00 5D EE 75')

Length: 76 Bytes

 

Name: "S1IMPTSA"

Object Type: Other Object Data

Origin X axis: 864 (0.6 Inch)

Origin Y axis: 2,750 (1.9097 Inch)

Rotation X axis (clockwise): 0°

Rotation Y axis (clockwise): 90°

Origin of contents X axis: -1 (-0.0007 Inch)

Origin of contents Y axis: -1 (-0.0007 Inch)

Reference coordinate system: Page/Overlay

 

Triplet: x'4B' (Object Area Measurement Units)

Base unit X axis: 10 Inch

Base unit Y axis: 10 Inch

Units per unit base X axis: 3,000 (300 DPI)

Units per unit base Y axis: 3,000 (300 DPI)

 

Triplet: x'4C' (Object Area Size)

Values are valid for: Object Area

Size in X direction: 1,137 (3.79 Inch)

Size in Y direction: 750 (2.5 Inch)

 

Triplet: x'10' (Object Classification)

Object Class: Fix data at run time

Object data is carried in a MO:DCA object container: Unknown

Object container contains OEG Structured Fields: Unknown

Object data is carried in OCD Structured Fields: Unknown

ASN.1 Object Identifier (OID): 06 07 2B 12 00 04 01 01 17

Registered object type: JPEG File Interchange Format (JFIF)

 

NOTE the last line: Registered object type: JPEG File Interchange Format (JFIF) <--- This means that it's actually a JPG and not a Page Segment.

Resolution

UPDATED: September 7, 2017


page 171 of the Doc1 6 Designer Guide, you can put JPGs into an AFP file its going to a printer that supports relative object container.

 

This is Pages 171 and 172 from the Doc1 Designer Guide.

 

Defining external keyed images

The keyed object feature allows you to select some types of presentation objects dynamically according to variable criteria or ‘keys’. When you are working with keyed image resources you can import the relevant files into Designer where they can be referenced directly in a key map and be included in a HIP file ready for use with Generate. It is not always practical to import all the required image files into the Designer however, and to deal with this scenario Designer & Generate support an external key map.

 

The images you reference using an external key map can optionally be copied from a defined location and embedded in the output datastreams at production run-time. Where this is not the case the resources are assumed to be printer resident and only the image references are included in the datastream. When embedding external keyed images no conversion takes place so you must ensure that the format of the images to be used is already compatible with the output datastreams being generated. The following table shows which image formats are supported for each datastream.

 

Output device Supported resource format

AFPDS Page Segment (FS45 & FS10 IOCA) and for printers with the relevant object container support, JPG, EPS, GIF, PDF Page Objects, TIF, BMP

 

Metacode IMG

 

PCL PCL bmp – note that this is a proprietary format which is not generally available. Please contact Pitney Bowes Software Support for more information.

 

Postscript EPS

 

Line Data Not applicable

 

HTML Any, all images are referenced

 

PDF JPG and BMP – note that CMYK JPGs generated by products such as Adobe Photoshop may have had their color inverted so you must invert the colors of the image again using a similar product.

 

IJPDS BMP

 

VPS EPS

 

VIPP JPG

 

Conclusion: As of Vault 7.2, "relative object containers" are not supported in Vault.

 

Downloads

  • No Downloads