hier eine anfrage von einem freund aus norwegen, der gerade heftigen stress hat und dringend hilfe braucht … ich hoffe ihr könnt helfen … leider kenne ich mich opi überhaupt nicht aus … danke …

Here is the case.
We have a program that create PDFs using destiller PDF and omit images. It does create filed based on OPI 1.3 standard. We get around 150 new images from different places each day and all transfer of the files takes up a lot of banwidth. Its used on a system using online system and not a regular DTP workflow and therefore size matters.

Problem is as follows:
We create a OPI image replacement file
We move it
System grabs it and we run an output
images should resolve, but don’t without a lot of manual manipulation of files.

Reason
Helios go for the full path in the PDF and not for the image name only. Its located on a Unix system but the creation of the file is on a Windows system

The path collected in the PDF is from the pickup place and not keeping the high-resolution path.

How to avoid this?

Suggestion: A script that redefine the PDF image path to the Unix path instead of the windows path since image name is not changed, only the path.

Suggestion2: change to different OPI that have a database connected to it?

I must emphasise that the system creates correct OPI files based on the Standard, but it seems that Helios have a problem with all type of input using moved OPI files to swap.

Also, just to keep the preasure up – I need answers ASAP, and tomorrow mid day is more or less our dead-line finding a solution

Wenn ich das richtig verstehe ist das ganz einfach.
oie sollen die Finger von den hochauflösenden Daten lassen, nachdem die Grobdaten für die Layouts erzeugt wurden.
Oder andersherum erst Grobe erzeugen wenn die Feindaten an ihrem endgültigen Speicherort angelangt sind, und nicht evtl. schon im email Attachement Eingangsordner.

bist du so lieb das das in die englische sprache zu verfassen … leite alles weiter … danke  

Meister propper

Is it correct that PDFs are generated with OPI comments? You then generate a layout file of this PDF and use it in a layout?

If yes, the OPI comments in a PDF always hold the full path to the used image seen by the system that generated the inital PDF. This is most likely a Windows or Mac path. If you do a resolving, Helios uses this full path and tries to find an image. If no image can be found, Helios is searching the image by its name in the defined searchpath list.
If still no image can be found you get an error.

Hope this helps to understand the vaguely described scenario

Zitat

Is it correct that PDFs are generated with OPI comments? You then generate a layout file of this PDF and use it in a layout?

Yes

Zitat

If yes, the OPI comments in a PDF always hold the full path to the used image seen by the system that generated the inital PDF. This is most likely a Windows or Mac path. If you do a resolving, Helios uses this full path and tries to find an image. If no image can be found, Helios is searching the image by its name in the defined searchpath list.
If still no image can be found you get an error.

A image full path ( windows). Image not found. Helios seems not searching the image at all.
Could it be so easy that helios is not set up with a searchpath list?
You know how to set this up?

Zitat

Hope this helps to understand the vaguely described scenario

Yes it helps
Thanks

Antwort auf:

A image full path ( windows). Image not found. Helios seems not searching the image at all.
Could it be so easy that helios is not set up with a searchpath list?
You know how to set this up?

Is this Windows Volume a share setup by this Helios System? If not, then Helios for sure can not resolve the path, since the internal mapping from a windows path to the unixpath can not be done.

The search path can be entered in the ImageServer Settings of Helios Admin.

Antwort auf:

A image full path ( windows). Image not found. Helios seems not searching the image at all.
Could it be so easy that helios is not set up with a searchpath list?
You know how to set this up?

Is this Windows Volume a share setup by this Helios System? If not, then Helios for sure can not resolve the path, since the internal mapping from a windows path to the unixpath can not be done.

The search path can be entered in the ImageServer Settings of Helios Admin.