[Date Prev][Date Next][Subject Prev][Subject Next][
Date Index][
Subject Index]
Re: Subject: Re: pdf2xy routine
- Subject: Re: Subject: Re: pdf2xy routine
- From: Patricia M Godfrey pmgodfrey@xxxxxxxx
- Date: Thu, 13 Jan 2005 12:18:25 -0500
**Reply to message from Robert Homgren ≪holmgren@xxxxxxxx>
Date: Wed, 12 Jan 2005 19:41:03 -0500
≪This frame couldn't care less where your data files are -- that's your
affair. All it cares is where your sourcefile is≫
Yes, but the sourcefile is a datafile. Anyway, I had never realized
(because some frames do work with a partial filespec; I run cd
e:\xyinfo\2005 and then SE e:*.* /searchstring/ all the
time successfully) that one needed to give a fully qualified path name if
the file wasn't in one's working (d:\xyw4dos) directory. So thanks,
that's one more useful item of information.
≪I don't like your example filename, either. ≫
Well, it's _your_ file: the one you created from my fontproof. But I will
change its name and see what effect that has. The similarity to
POSTGHST.PRN could indeed be skewing things. I have, however, tried a
couple of times with another pdf (thinking this one might be too big),
and still failed.
≪Put right after the call to XSR [etc]≫
Did so. On first step, S/G 52=c:\gs\gs8.15\bin
≪S/G 52 has content, then put right after the
_first_ call to SFN/NV≫
Did so. S/G 50=c:\gs\gs8.15\bin\pstotxt3.exe
N.B. Both done with a different .pdf file, in the Editor.exe directory.
≪track the progress of that GS path spec and find out where it
evaporates. ≫
Will do and report. Thank you for your patience, and if this turns out to
be the fault of Redmond Rubbish again, I will grovel (though it's BBBG
that should).
Patricia M. Godfrey
PMGodfrey@xxxxxxxx