TechWhirl (TECHWR-L) is a resource for technical writing and technical communications professionals of all experience levels and in all industries to share their experiences and acquire information.
For two decades, technical communicators have turned to TechWhirl to ask and answer questions about the always-changing world of technical communications, such as tools, skills, career paths, methodologies, and emerging industries. The TechWhirl Archives and magazine, created for, by and about technical writers, offer a wealth of knowledge to everyone with an interest in any aspect of technical communications.
"Index not available" under Unix only for indexed pdf collection
Subject:"Index not available" under Unix only for indexed pdf collection From:Ted Rose <tedr -at- frontline-pcb -dot- com> To:"TECHWR-L" <techwr-l -at- lists -dot- raycomm -dot- com> Date:Wed, 19 Dec 2001 13:20:09 +0200
I have an indexed collection of manuals in pdf format (approx. 50
manuals). The search and index works correctly in Windows NT, but
not in Unix. The index is not available under Unix.
I am using FrameMaker 5.5.2 and Acrobat Catalog 3.0, on Windows NT,
Service Pack 6. All the pdfs and the index were built under Windows NT.
I have an indexed collection of manuals in pdf format (approx. 50
manuals). The search and index works correctly in Windows NT, but
not in Unix. The problem seems to occur when the directories containing
the pdf files and index files are copied from one computer or network
drive to
another. They are moved together, so I do not understand why the
relative path name changes (if it does). Copy the files to another
location,
and the "index not available" error message appears. I regenerate the
index in the directory where
the files reside, being sure to purge the subdirectory containing
the nine support files of the index before rebuilding. This is supposed
to
maintain the relative path names, but it does not, apparently. We plan
to
burn the directory onto a CD for distribution to customers.
I am accessing the files through a
symbolic link in UNIX. Would this cause any problems? But my boss
has a UNIX machine, can access the files directly, and has the same
problem.
This problem has never occurred before. I have issued the yearly doc
cycle twice, and never had a problem. I have a document of procedures
that I follow, and it has always worked until now. Note
that all file names have been converted to lower case for use in Unix.
Any suggestions will be most welcome.
Thanks for listening.
--
Ted Rose
Technical Writer
Frontline PCB Solutions
P.O. Box 680 Yavne 81106 Israel
Tel: (972)-8-9322183 Ext. 159
Fax: (972)-8-9322186
Email: tedr -at- frontline-pcb -dot- com
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Collect Royalties, Not Rejection Letters! Tell us your rejection story when you
submit your manuscript to iUniverse Nov. 6 -Dec. 15 and get five free copies of
your book. What are you waiting for? http://www.iuniverse.com/media/techwr
---
You are currently subscribed to techwr-l as: archive -at- raycomm -dot- com
To unsubscribe send a blank email to leave-techwr-l-obscured -at- lists -dot- raycomm -dot- com
Send administrative questions to ejray -at- raycomm -dot- com -dot- Visit http://www.raycomm.com/techwhirl/ for more resources and info.