Hi, John...
You should be able to just reference your graphics by file name,
without any path information, like:
<imagedata fileref="ABSio.wmf"/">
Your graphics path setting will provide the list of directories to
search for this file. So, on your editor machines, you might have:
set graphicspath="G:\TM 9-2355-319-10\Graphics\CHAPTER 3"
while on the PE server, you'd have:
set graphicspath="E:\IETM-Backups\IETM-Docs\MRAP Full TM\TM
9-2355-319-10\Graphics\CHAPTER 3"
These lines could go in a few different places, such as init.acl, your
doctype.acl, etc., based on whether the set of graphic paths are
specific to certain subsets of publications.
-Brandon
On Wed, Mar 3, 2010 at 5:43 PM, John Jarrett
<-> wrote:
> I'm still working the 38,000 pager - thanks for the help so far guys! Got me
> in the ballpark.
>
> One issue is the PE not finding graphics. Not sure why it is an issue if
> Editor can find it, then PE should, too, or get it from the Editor
> client...isn't that what it says in the PE PDF?
>
> PTC has me editing the document on the PE server with PE services turned
> off - that helps...get a few more error messages...like lost graphics
> (graphics randomly showing up - different graphics with every print!) I
> coded the path to the graphics directory in Tools | Preferences | Files |
> Graphics and that seemed to fix it - but that only works on a local machine.
>
> How do I tell the PE where the dozens of graphics directories are?
> Preferably without having to update every graphic with a public identifier.
> Can I use the catalog file to map to the directories without mapping to each
> graphic?
>
> Take this for example:
>
> A network graphic location - G:\TM 9-2355-319-10\Graphics\CHAPTER
> 3\ABSio.wmf
>
> The local location on the PE (they are on the same physical hard drive as
> the PE) - E:\IETM-Backups\IETM-Docs\MRAP Full TM\TM
> 9-2355-319-10\Graphics\CHAPTER 3\ABSio.wmf
>
> Looking at the entities references, they vary:
>
> a. G:\TM 9-2355-319-10\Graphics\CHAPTER 3\
>
> b. Graphics\CHAPTER 3\
>
> c. No directory reference
>
> So, if I can use the catalog, I can map all three ways and PE will figure
> it out? I've searched help and PDFs and can't find any examples of mapping a
> drive.
>
> And there is no Tools | Files window on the PE...
>
> Thanks,
>
> John T. Jarrett
> BAE Systems | Arbortext version 5.4 | LOGSA XSL-FO v 1.5
>
> ----------
You should be able to just reference your graphics by file name,
without any path information, like:
<imagedata fileref="ABSio.wmf"/">
Your graphics path setting will provide the list of directories to
search for this file. So, on your editor machines, you might have:
set graphicspath="G:\TM 9-2355-319-10\Graphics\CHAPTER 3"
while on the PE server, you'd have:
set graphicspath="E:\IETM-Backups\IETM-Docs\MRAP Full TM\TM
9-2355-319-10\Graphics\CHAPTER 3"
These lines could go in a few different places, such as init.acl, your
doctype.acl, etc., based on whether the set of graphic paths are
specific to certain subsets of publications.
-Brandon
On Wed, Mar 3, 2010 at 5:43 PM, John Jarrett
<-> wrote:
> I'm still working the 38,000 pager - thanks for the help so far guys! Got me
> in the ballpark.
>
> One issue is the PE not finding graphics. Not sure why it is an issue if
> Editor can find it, then PE should, too, or get it from the Editor
> client...isn't that what it says in the PE PDF?
>
> PTC has me editing the document on the PE server with PE services turned
> off - that helps...get a few more error messages...like lost graphics
> (graphics randomly showing up - different graphics with every print!) I
> coded the path to the graphics directory in Tools | Preferences | Files |
> Graphics and that seemed to fix it - but that only works on a local machine.
>
> How do I tell the PE where the dozens of graphics directories are?
> Preferably without having to update every graphic with a public identifier.
> Can I use the catalog file to map to the directories without mapping to each
> graphic?
>
> Take this for example:
>
> A network graphic location - G:\TM 9-2355-319-10\Graphics\CHAPTER
> 3\ABSio.wmf
>
> The local location on the PE (they are on the same physical hard drive as
> the PE) - E:\IETM-Backups\IETM-Docs\MRAP Full TM\TM
> 9-2355-319-10\Graphics\CHAPTER 3\ABSio.wmf
>
> Looking at the entities references, they vary:
>
> a. G:\TM 9-2355-319-10\Graphics\CHAPTER 3\
>
> b. Graphics\CHAPTER 3\
>
> c. No directory reference
>
> So, if I can use the catalog, I can map all three ways and PE will figure
> it out? I've searched help and PDFs and can't find any examples of mapping a
> drive.
>
> And there is no Tools | Files window on the PE...
>
> Thanks,
>
> John T. Jarrett
> BAE Systems | Arbortext version 5.4 | LOGSA XSL-FO v 1.5
>
> ----------
On Thu, Mar 4, 2010 at 1:04 PM, Jarrett, John T
<-> wrote:
> Thanks - set it up for the editors on the PE in custom\editini\editini.acl - got that part working for everyone except two of us. Any reason it wouldn't load automatically on just two clients? It looks like all of our file settings are the same, I work off the same DTD successfully as everyone else, and I use the PE more than everyone else combined. I even changed the editini.acl in my local directory to a different filename, rebooted, restarted PE, whole nine yards.
Off the top of my head, the only thing I can think of is the fact that
the file you need to modify is custom\editinit\editinit.acl (note the
final 't' in the directory and file names, which was missing in your
descriptions), but that might have just been a hiccup in translation
on the way into your email.
If that's not the issue, then I'd just start tracking it down one step
at a time. Make other changes in that file, whose effects are easy to
see, to determine if it is getting run at the right times (or at all).
If not, make sure the custom directory structure is being pointed to
correctly on the problem machines.
-Brandon
<-> wrote:
> Thanks - set it up for the editors on the PE in custom\editini\editini.acl - got that part working for everyone except two of us. Any reason it wouldn't load automatically on just two clients? It looks like all of our file settings are the same, I work off the same DTD successfully as everyone else, and I use the PE more than everyone else combined. I even changed the editini.acl in my local directory to a different filename, rebooted, restarted PE, whole nine yards.
Off the top of my head, the only thing I can think of is the fact that
the file you need to modify is custom\editinit\editinit.acl (note the
final 't' in the directory and file names, which was missing in your
descriptions), but that might have just been a hiccup in translation
on the way into your email.
If that's not the issue, then I'd just start tracking it down one step
at a time. Make other changes in that file, whose effects are easy to
see, to determine if it is getting run at the right times (or at all).
If not, make sure the custom directory structure is being pointed to
correctly on the problem machines.
-Brandon
