Translating Image Callouts
By Paul • Nov 4th, 2008 • Category: MadCap Capture, Tips and TricksWhen I worked for a company that had localization requirements for the help system, one of my tasks was to go through the project and remove all the images. The reasoning behind this was that images are hard to localize, so we should just remove them from the project. This is especially difficult if you are using images with callouts (the text on the image that describes)
MadCap Capture V3 solves part of that problem. See, Capture V3 is integrated with MadCap Ling 1.5, so when you use text callouts in Capture, then you package up your project to translate in Lingo, you will also be packaging in the Capture callouts.
Your translator using Lingo will then see those callouts when they are translating the project. The resulting localized project will include the translated image callouts, which are included on your images when you build the localized version of your project.
That is cool functionality.
—
Edit: Mad props go to MadCap Support guru Rick Ferrell for his help answering this quesiton for me today on the fly. Thanks Rick!
Paul is is a Certified Flare Instructor, and a MVP in the MadCap forums. He is also the author of the forthcoming book "Frame to Flare" due to be published in Q1 2009. He is married to Christina, and they are the parents of two beautiful children.
Email this author | All posts by Paul
This is actually something that isn’t working off the bat in Lingo 1.5.
I got a patch from the madcap software support team yesterday to make this work properly as you describe. Without this patch, editing any text callouts from Capture 3 in Lingo renders the file corrupted. point to note.
But it appears all is working beautifully now with this patch.
Welcome back from the middle east trip. It must be blazing hot.