[Date Prev][Date Next]
[Thread Prev][Thread Next]
[Date Index]
[Thread Index]
[New search]
To: "'framers@xxxxxxxxx'" <framers@xxxxxxxxx>
Subject: RE: Fixing condition text mess--RESOLUTION
From: Ed Treijs <etreijs@xxxxxxxxxxxxxxxx>
Date: Thu, 17 Apr 2003 14:53:18 -0400
Sender: owner-framers@xxxxxxxxx
Hi all; A lot of interesting suggestions from the list! We discovered one thing: got in touch with a writer who had worked on the docs before, who told us that a good effort had already been made to clean up and remove conditionally-tagged text (but, alas, not the multitude of tags/formats themselves). So it's unlikely that there is any conditionally-tagged text that we would miss. The person working on the docs did a manual clickfest to remove conditional text from one doc, and is satisfied with the results. Tackling one doc a day is reasonable with this approach. Basically, we are trading away any elegance (and the thought/effort needed to implement it) for a straightforward approach of "clamp it with Vise-Grips and hit vigorously with hammer". FrameScript is pretty cheap, but I think all our software acquisition funds are going to our upgrade from Frame 5.5.6/Acrobat 4.0.5 to Frame 7.0/Acrobat 6.0. We'd have to justify FrameScript based on a lot of recurrent batch-oriented tasks that could be automated; I'm not sure we have any of these. Thomas Michanek's scripts certainly warrant further investigation. I think we have forgotten what we could do with Frame on UNIX. The chances of the Frame 5.5 UNIX licence being upgraded to 7.0 are very slim, and we "missing font" messages are inevitable because the fonts we use in our docs are installed on our PCs. Oh yeah, and the forgotten takes a while to remember. Ed (now, where's my hammer?) Treijs ** To unsubscribe, send a message to majordomo@omsys.com ** ** with "unsubscribe framers" (no quotes) in the body. **