RayLopez99 said:
I'm leery of trying Adobe products since editing in them is a pain in the behind,
at least with Acrobat. I doubt Framemaker is as good as Word. So for now, at 300 pages,
I will stick to Word. Also not clear if FM is being actively supported* (where
there's smoke there's fire).
At the time, my employer bought a 10,000 seat license for it, it's that good.
Before that, employees were buying copies at perhaps $500 each (with a purchase order),
and it was starting to add up. So they negotiated a price for enough seats, to make
a dent in the wasted financial resources. The price per, would be a secret.
The product did not start out as Adobe. It was made by another small company, and
Adobe bought the company. We were buying it, before it was Adobe branded. I even got
to phone the small company's tech support one day. In terms of software design practices,
I expect even to this day, it does things differently than Adobe staff would have liked.
(Virtually every decision point in the tool, has a 64 bit error code, which you can send to
Tech Support for bug resolution. Adobe wouldn't do that. And no, they don't give
a table of codes to the public
Of course, we asked.)
And it's *better* than Word, in the sense you can do large documents, without
taking a lot of coffee breaks while things load or whatever. The only time there's
an appreciable delay, is when making the final output of your book, generating
TOC or Index, resolving cross-references, it can take ten minutes on a slow
computer for a 500 page document. But in terms of editing chapters, as a
contributor to a book, everyone can work on their own chapter, with no delay
at all.
The tool stores information in a couple formats. The normal storage format
is binary. But there is also a Maker Interchange Format (MIF), which is
a text based format. And on occasion, we'd generate MIF programmatically,
to achieve a desired result. There was also the RTFTOMIF tool provided with
it, for *attempting* to import RTF. Any RTF constructs the tool would not
recognize, it would throw away, with the same kind of results you expect
from any of the other failed attempts at RTF importation.
It's also an *acquired* taste. If you're an MS junkie, you're going to hate
it. Except when the person next to you is using it, and getting work done,
while you're sitting there "looking at a busy cursor". That's the diff.
Paul