TechWhirl (TECHWR-L) is a resource for technical writing and technical communications professionals of all experience levels and in all industries to share their experiences and acquire information.
For two decades, technical communicators have turned to TechWhirl to ask and answer questions about the always-changing world of technical communications, such as tools, skills, career paths, methodologies, and emerging industries. The TechWhirl Archives and magazine, created for, by and about technical writers, offer a wealth of knowledge to everyone with an interest in any aspect of technical communications.
zzPinkham, zzJim wrote:
> Wow -- thanks, Peter, for that very useful analysis. The conditional
> text and cross-references would be important for us.
Conditional text needs might be solved by processing exported
XML and reimporting it. I'm not sure how much of this can be
scripted. It's one area you could research.
DTP Tools (dtptools.com) is working on some plug-ins for
FrameMaker-to-InDesign conversions, and also possibly add some
missing abilities.
> None of the other
> missing pieces you mentioned are deal-breakers. Based on what you've
> presented, it sounds as though it wouldn't take all that much for Indy
> to outstrip Frame and become an even more robust alternative.
I didn't mention FrameMaker's little-discussed layout abilities.
In FrameMaker, you can create connected ("linked," or
"threaded") text frame flows ("stories") that jump across
pages. You can use x-refs to create "continued on page..." and
"continued from page..." items.
FrameMaker is missing some abilities for layout use.
For example, there is no ability to auto-number left- and
right-hand pages in a two-page spread layout; most layout
tools can do this easily. In FrameMaker, you can set up a few
constructs to do a good job of faking the appearance, but the
fakes don't provide correct page numbers in x-refs and
generated lists.
> Makes one
> wonder about the merits of going to FM 8 versus making do until and if
> InDesign catches up.
As with the decision to buy a new current-technology-edge
computer now, or wait to buy the imminent next-generation
model with fantastic and affordable innovations, it depends on
what you need NOW. Migrating complex document sets and
workflows across applications isn't trivial. You'll probably
test a parallel workflow in the candidate product, while
continuing to produce output in the established workflow,
until proof-of-concept results justify or cancel the move. If
currently FrameMaker satisfies your requirements, why change
to anything? If the next FrameMaker release opens options that
are compelling, moving will not impose the same impact as
switching to a new and different product.
> Do you happen to know when the next major release
> of Indy is likely?
Absolutely!! Be careful what you wish for, because after I
tell you, some big guys will come to take you away forever!
Probably, they'll take me, too!<G>
Seriously, there's about 18 months between major releases of
most major software products, not just Adobe's. Third-party
add-ons, scripts, and plug-ins can arrive at any time.
HTH
________________
Regards,
Peter Gold
KnowHow ProServices
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Create HTML or Microsoft Word content and convert to Help file formats or
printed documentation. Features include support for Windows Vista & 2007
Microsoft Office, team authoring, plus more. http://www.DocToHelp.com/TechwrlList
Now shipping: Help & Manual 4 with RoboHelp(r) import! New editor,
full Unicode support. Create help files, web-based help and PDF in up
to 106 languages with Help & Manual: http://www.helpandmanual.com
---
You are currently subscribed to TECHWR-L as archive -at- web -dot- techwr-l -dot- com -dot-
