Hi, Monique, et. al.
I am in the SF Bay Area and you are totally correct about the trends here … all
of our new documents are on-line, with PDF generation as needed.
I only use FrameMaker occasionally now … my new specs are all done in TeX
(well, LaTeX actually!)
Z
From: Monique Semp
Sent: W
Yes, what Z said!
I haven't used FrameMaker for a goodly number of years now, having
moved to jobs that use a docs-as-code approach. (So Markdown, SSGs
[static site generators], developer tools.) And given the job market
and location I'm in -- the San Francisco Bay Area, and lots of
Unfortunately, this is essentially the kind of "licensing" and upgrade pricing
policy changes that I expected some years ago when the subscription versions
were released.
I stopped using FM for _all new_ documents after version 12 and switched to
writing all my new documents to TeX ... my needs
Doug,
I find it helps to require vendors use a specific version of software. In
this case, you have to go back to your vendor and ask for files you can use.
Traditionally, current FrameMaker versions have been able to save as .FM
one version older. So, FM 2019 can save as FM 2017.
If the differe
from FM 2019 you have to save as an earlier version that can be opened by
2017
On Wed, Oct 23, 2019 at 12:18 PM Doug wrote:
> Is it possible to do this? I just had some 2017 documents translated for
> me and when I open them in my FM 2017 it says:
>
> Although XXX appears to be a FrameMaker doc
MIF might work as an intermediary format, but otherwise you need to backsave
FM2019 documents as FM2017 format documents in order to open them in FM2017.
Old applications can't know what differences there are in file formats for
future/forthcoming versions. Application formats like PDF and MS Wo
Is it possible to do this? I just had some 2017 documents translated for
me and when I open them in my FM 2017 it says:
Although XXX appears to be a FrameMaker document, it can't be opened with
tihs release of the product.
Is there an add-on or something?
Doug
__
