🚀 go-pugleaf

RetroBBS NetNews Server

Inspired by RockSolid Light RIP Retro Guy

Article View: adobe.framemaker
Article #1195

Re: Forcing relative pathnames for linked images

#1195
From: Jang Graat
Date: Tue, 06 Jan 2009 13:43
11 lines
1628 bytes
Thanks Art,

but this does involve changing the way the translation agencies work. Translators do not get the FM files to work on, but some kind of files exported from the MIF files. I am afraid the changes to the image directories happen at some stage along their (automated) ways to create the input for the translators and then import the output from the translators to create a set of MIF files again.

Also, sending the entire set of files (including graphics) in an archive, preserving the paths, is not an option as the graphics easily reach 100 MB or more and this makes it virtually impossible to transfer the files via e-mail. I am only sending an archive of the FM files, with a low-res PDF that includes the images, for reference.

With some agencies this process works flawless, but the cheaper the agency, the lower the quality I guess. Unfortunately, my customers go for cheap rather than quality, and I have the job of fixing the problems in the layout.

Thanks for the suggestion, anyway.

Ciao again from Amsterdam
Technical Details
Message-ID: <59b76fb2.1@webcrossing.la2eafNXanI>
Path: arc1-ca.pugleaf.net!g2news1.google.com!news2.google.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!news2.google.com!newshub.sdsu.edu!webcrossing
Newsgroups: adobe.framemaker
Subject: Re: Forcing relative pathnames for linked images
Message-ID: <59b76fb2.1@webcrossing.la2eafNXanI>
Date: Tue, 6 Jan 2009 05:43:27 -0800
References: <59b76fb2.-1@webcrossing.la2eafNXanI>
Lines: 23
MIME-Version: 1.0
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 8bit