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.
IMO, there is no 'ideal' solution for XML publishing at this point.
FrameMaker does represent a reasonable alternative provided the limitations
of Frame's implementation are not a problem. (In your case, the need for
unicode might be an important limitation.) I've heard people cite the fact
that Frame does not support schema as a major limitation, but XML Schema has
yet to be finalized, and from a publishing perspective (IMO) has little
relevance at this point.
Consider SGML. Frame has been a widely used solution for years despite being
somewhat limited compared to applications like Arbortext. Of course, you can
always extend Frames's capabilties via the FDK, but for smaller operations,
this is often impractical. The point is that one typically has to integrate
the workflow requirements with the requirements/limitations of the tools to
come up with a workable system. As long as your hands are not tied at the
start by known limitations, then it should be possible to make it all work.
Docbook may be a great standard, but IMO, don't try to adapt it to your
needs. It will be easier and more effective to develop your own structure
application based around your own requirements. Yes, the learning curve for
development in structured Frame is formidable, but it's not impossible. If
you have sufficient time you can probably climb the curve yourself. If time
is of the essence, you'd be wise to contract a Structured Frame
architect/developer to help you build the system.
Finally, research the other tools that seem suitable to your purpose.
Sometimes what may seem like a minor difference in functionality can make
all the difference in the final workflow.
Best of luck.
John
~~~~~~~~~~~~~~~~~~
John Root
Publishing Systems
jroot -at- publisys -dot- com
~~~~~~~~~~~~~~~~~~
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Check out SnagIt - The Screen Capture Standard!
Download a free 30-day trial from http://www.techsmith.com/rdr/txt/twr
Find out what all the other tech writers, including Dan, already know!
Order RoboHelp X3 in November and receive $100 mail in rebate, FREE WebHelp
Merge Module and the new RoboPDF - add powerful PDF output functionality
to RoboHelp X3. Order online today at http://www.ehelp.com/techwr-l
---
You are currently subscribed to techwr-l as:
archive -at- raycomm -dot- com
To unsubscribe send a blank email to leave-techwr-l-obscured -at- lists -dot- raycomm -dot- com
Send administrative questions to ejray -at- raycomm -dot- com -dot- Visit http://www.raycomm.com/techwhirl/ for more resources and info.
