Re: OT: MacOS 'keeping' adobe from implementing Macros?
Re: OT: MacOS 'keeping' adobe from implementing Macros?
- Subject: Re: OT: MacOS 'keeping' adobe from implementing Macros?
- From: "Welch, John C." <email@hidden>
- Date: Tue, 13 Mar 2001 16:51:26 -0500
On 3/13/01 4:45 PM, "Bill Briggs" <email@hidden> wrote:
>
>>
>
>> PrintToPDF will look for URLs in your text and turn them into links. When
>
>> you
>
>> click such a link, Acrobat Reader will attempt to open it in an appropriate
>
>> helper
>
>> application, such as a web browser. In order for this to work:
>
>>
>
>>> Mac users? (BTW, neither Distiller, PrintToPDF, or any other type of
>
>>> software does this on a Mac. All you can do is dump to a dead PDF file,
>
>>> and
>
>>> recreate the links by hand)
>
>
>
> That's any URL, and only works if the link is a URL. It doesn't do
>
> anything for Tables of Content links, tables of figure links, or any
>
> other kind of non-URL links or structures.
>
>
That may be true of Word, but it's not true in general. All
>
hypertext and cross-reference links, Table of Contents entries, List
>
of Figures entries, List of Tables entries, Index page numbers, and a
>
host of other things that are possible to include in a FrameMaker
>
document pass intact from FrameMaker binary --> PostScript -->
>
Distillation --> PDF. Just one of the many things that make
>
FrameMaker the powerhouse it is.
<sigh>...I know...now if I could only get my company/clients to see this.
Unfortunately, it's a Word world, and FrameMaker is expensive, esp. on the
Solaris side....
If I had the resources, I'd try and put a team together to write one and
open source the VBA and AppleScript code, just to stick a finger in Adobe's
"The MacOS keeps us from doing this" nonsense.
john
--
Pain is only weakness leaving the body
anon. special forces instructors