Adobe does something like that. When you look at a FrameMaker help
topic on the web, there's a pop-up menu of other versions in case
you're looking at the wrong one.
I don't think it makes any sense to do that by lumping everything
together in one project, HTML5 or otherwise.
On Tue, May 31,
Thanks for the presentation Bernard. I can think of one way to use that in the
products I document. I do have a couple of questions, however.
In your example it seemed as if the user would open a "default" HTML5 Help that
had both Word and FrameMaker information. The user would then choose
I can't imagine a real-world use case where I would trust users to
choose the right option.
On Fri, May 27, 2016 at 9:20 AM, Bernard Aschwanden (Publishing
Smarter) wrote:
> Working with conditional content? Need a better way to deliver than "2
> similar, but
Working with conditional content? Need a better way to deliver than "2
similar, but different PDF files"?
Imagine this:
You create a doc that compares 2 products. For example, you may start with a
title that reads "Working with Microsoft WordAdobe FrameMaker". Then body
content after it