[Date Prev][Date Next]
[Thread Prev][Thread Next]
[Date Index]
[Thread Index]
[New search]
To: "Framers1" <Framers@xxxxxxxxxxxxxx>, "Framers2" <framers@xxxxxxxxx>
Subject: Frame XML to HTML Help via XSLT
From: "Rick Quatro" <rick@xxxxxxxxxxxxxxx>
Date: Mon, 12 Aug 2002 15:12:20 -0400
Sender: owner-framers@xxxxxxxxx
Hello Framers, I am doing some research for a client who is struggling the whole "single-source" idea. They recently switched to Frame from Interleaf. Most of their help is done with RoboHelp and they have been reluctant to switch to Webworks Publisher Professional. What ends up happening is that the information goes back and forth between FrameMaker and RoboHelp during the life of the project. This doesn't work very well, even with MIF support in RoboHelp. I have an idea, but would like some opinions on real-world feasibility. My thought is for them to use structured FrameMaker 7 to produce content. Then they would export XML and transform it using XSLT to HTML. The HTML would have to be in a format that RoboHelp could use. I don't know much about RoboHelp, so I don't know how practical this is. Ideally, it would be nice to be able to put some context-sensitive help information in the FrameMaker structure so that this could be used by RoboHelp as well. I understand that this scenario probably would work in the reverse direction (RoboHelp to Frame). But if the Frame to RoboHelp path could be streamlined by using Frame to XML to HTML via XSLT, it might not be necessary to do this anyway. If anyone has any experience with this and can offer some advice, I would appreciate it. Thanks in advance. Rick Quatro Carmen Publishing rick@frameexpert.com http://www.frameexpert.com ** To unsubscribe, send a message to majordomo@omsys.com ** ** with "unsubscribe framers" (no quotes) in the body. **