🚀 go-pugleaf

RetroBBS NetNews Server

Inspired by RockSolid Light RIP Retro Guy

Article View: adobe.framemaker
Article #1211

Re: Forcing relative pathnames for linked images

#1211
From: Jang Graat
Date: Tue, 06 Jan 2009 17:39
9 lines
1631 bytes
Hello again Art,

I am currently investigating creating a FrameScript that will correct the paths - this has the added advantage that the script can tell me which images are missing, in a list instead of the very limited "Missing File" dialog (which does not even resize to see the full path and thereby creates some confusion sometimes). Also, when Frame finds a file by me pointing to the correct path it assumes that all further files will be in the same place. And since I have files with the same names (but different contents - as they are used in different machine modules), this causes unexpected errors.

And of course you are right in your comment about the translation agency: the previous one that I used responded to my problem reports by changing their methods of exporting and importing. But they are too expensive for the taste of my customers. Ah well, I am getting more out of it this way and my customer knows that, but I hate stupid work even if I do get paid for it.

Ciao again

Jang
Technical Details
Message-ID: <59b76fb2.3@webcrossing.la2eafNXanI>
Path: arc1-ca.pugleaf.net!g2news1.google.com!news4.google.com!news1.google.com!news.glorb.com!newshub.sdsu.edu!webcrossing
References: <59b76fb2.-1@webcrossing.la2eafNXanI>

Show Full Headers
Complete Article Headers
X-Google-Thread: fd315,f8e6bd426b2766d7
X-Google-Attributes: gidfd315,domainid0,public,usenet
X-Google-Language: ENGLISH,ASCII-7-bit
From: "Jang Graat" <jang@jang.nl>
Path: arc1-ca.pugleaf.net!g2news1.google.com!news4.google.com!news1.google.com!news.glorb.com!newshub.sdsu.edu!webcrossing
Newsgroups: adobe.framemaker
Subject: Re: Forcing relative pathnames for linked images
Message-ID: <59b76fb2.3@webcrossing.la2eafNXanI>
Date: Tue, 6 Jan 2009 09:39:23 -0800
References: <59b76fb2.-1@webcrossing.la2eafNXanI>
Lines: 22
MIME-Version: 1.0
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 8bit