RT @techcommdood: Fix for Acrobat license problem in TCS2 http://bit.ly/7etdWd (h/t R. Combs on Framers)
Filed under: Software, TCS Integration, Technical Communication | Leave a comment »
RT @techcommdood: Fix for Acrobat license problem in TCS2 http://bit.ly/7etdWd (h/t R. Combs on Framers)
Filed under: Software, TCS Integration, Technical Communication | Leave a comment »
For the past few years I’ve represented Adobe at various Tech Comm conferences, including the last 2 STC Summits. In discussing options for FrameMaker to RoboHelp integration, I developed a “chalk-talk” that usually took about 15 minutes to draw out and explain. The end result looked something like this:
In the diagram above, the solid lines represent inputs for both applications, while the broken lines represent traditional outputs. In some cases, like PDF output, there are overlaps between the capabilities of the two applications, where you can choose between the strengths of each application.
As one person observed, “It looks like 2 spiders mating”
While I can’t really argue that point, what I see instead is a blueprint for managing content using FrameMaker.
Now, when I give out this same info, I can just cross out the elements that a client might not be interested in, and give them the same perspective in less than 1/2 the time.
Most folks expect this process to be really involved, and to be both expensive and stressful. In reality, it takes only a few hours to map out the FrameMaker formatting into RoboHelp, and then another few hours to work out the formatting bugaboos in HTML and CSS, and to define your single source layouts in RoboHelp.
The first time through the process can have a learning curve, so plan on either seeking services or education from a training provider like roundpeg, or invest some time in online tutorials like those from RJ Jacquez at http://blogs.adobe.com/rjacquez/2009/05/linking_framemaker_9_books_in.html
Either can make the process both rapid and pain-free.
Filed under: FrameMaker, RoboHelp, TCS Integration, Technical Communication | 1 Comment »
Suggestions or comments? Please comment below
If you are in a noisy environment, be aware of controls for muting your microphone. Examples requiring muting include: exessive white noise, feedback and echo, as well as loud co-workers.
Filed under: Connect/Presenter, e-learning | Leave a comment »
When you’ll be creating more than one RoboHelp project, either maintained directly in RoboHelp or with content linked from FrameMaker and other sources, consider keeping a CSS with a separate name other than default.css or RHStylemapping.css for use in your projects. A separate custom CSS will allow you to, among other things, put in code that addresses limitations or omissions in the standard CSS files (see http://wp.me/pKaGh-K)
When your custom CSS has a custom name, it will be easier to avoid confusion than if you simply overwrite one of the default CSS.
Filed under: RoboHelp, TCS Integration, Technical Communication | Leave a comment »
When linking FrameMaker 9 to RoboHelp 8 projects using TCS2, you may get frustrated at the (lack of) control over the size, font, and other properties associated with the autonumbered lists.
Often I hear folks erroneously blame this on the mapping from FM to RH. The mapping actually produces quite clean HTML, but there is a CSS issue that you must also address.
Here’s a quick fix, using the <body> tag to apply global formatting defaults:
In a text or css editor (I use Dreamweaver) open your conversion CSS (by default, it’s RHStyleMapping.css in your RoboHelp project directory) and add the following entry at the top:
body {
font-family:Verdana, Geneva, sans-serif;
font-size: 8.5pt;
}
Of course, feel free to edit the properties applied or adjust their values to suit your project.
Because nearly everything in your converted file will use a specific mapping to a CSS element, the values specified will become your “base” values, overridden by the other definitions in your CSS. Only when there are no rules defined to format content will you see the <body> values applied.
Filed under: RoboHelp, Software, TCS Integration, Technical Communication | 2 Comments »
I noticed the other day that the pretty Captivate path motion functions differently than I previously thought…
The initial path direction is always to the the left or right (when not going either straight up or straight down) rather than being controlled by whether the starting mouse position is on one side or another of the horizontal or 45 degree axes (sp. for plural of axis??)
Filed under: Captivate, e-learning, Software, Technical Communication | 1 Comment »
When working with software, do you ever think that a feature would be more obvious if properly named/described/organized? Do you think there’s been an omission from a menu or dialog box?
This is the first of a series of planned, constantly updated posts related to minor corrections to the labels and dialogs used in applications. If you agree or disagree, please comment below. If you really agree with an item, go to the Adobe Features/Bugs Form and vote for it yourself. It takes 3 minutes, and is the best way to be heard, especially when a request is logged by multiple users.
Now that we can edit text by double-clicking in the text caption, I’d like to see the Caption Type added to the right-click menu (context menu) for captions. Often I need to go into Text Caption Properties for only this purpose.
Unlike other objects, my hilight box is inserted at “0” on the timeline, rather than at the current location of the playhead.
Filed under: Captivate, Software, Technical Communication | 1 Comment »
Matthew Ellison has written an in-depth review of 10 popular screen capture utilities. The link is at http://www.writersua.com/articles/capturetools/index.html
Filed under: e-learning, RoboHelp, Software, Technical Communication | 1 Comment »