[Framers] FrameMaker 2019 Issues and First Look

[Robert Lauriston]

My guess is Adobe took Windows out of the PDF-generation loop so that
Microsoft updates or selecting the wrong printer driver can't break
it.

This is the 1.0 release of that code. Give them six months or a year
to get the bugs out and address limitations.

On Mon, Sep 3, 2018 at 5:03 PM, Tom Beiswenger
<tom.beiswenger at emhartglass.com> wrote:
>
> I don’t know if Adobe monitors this list, but the pdf issue, for me, also
> is a deal breaker. Seems absurd that they would take something that worked
> and “improve “ it so well that it now is pretty much useless.
>
>> On Sep 2, 2018, at 6:04 PM, Harding, Dan <dharding at illinois.edu> wrote:
>>
>> The new PDF creation mechanism and its inflexibility is a complete
> dealbreaker for me. I need to be able to easily create my PDFs in different
> locations with different names on the fly. Having neither of those aspects
> settable at output time nor saved on a per-file basis is utterly dain
> bramaged.