I am using FM2015 in a Win 7 environment.
Sometimes a screenshot of a UI does not capture a border around the area of interest. If I put the screenshot into a document, the elements of the UI are poorly separated from the surrounding text. To set it off, I select the screenshot and the click the outline icon in the graphics toolbox. A line appears around the figure. It's usually 1.0 pt by default, and I change it to 0.5 manually.
This outline does not survive the conversion to .chm files. (I've greatly magnified the .chm and indeed there is no outline even at high magnification.)
I see that I can set a universal outline in the Settings that would apply to every graphic, but I don't want that for every image. Does anyone have a way to preserve the outlines I've put around individual graphics?
The only certain way to have the border outline appear in all output formats from FM is to create it in the graphic file before importing to FM. Depending upon which screen capture program you're using, this could be a fairly trivial thing to do. However, if you have a large library of existing graphics, then it will be a bit of a PITA.
The altenative in FM is to create the outline using the rectangle drawing tool. FM will rasterize onto the image when creating the output.
Thank you, Arnis. Arrrghh. Sounds like I will be doing some work in SnagIt, which won't be too bad. Far less painful than drawing rectangles around each figure in FrameMaker, though!
Arnis: The altenative in FM is to create the outline using the rectangle drawing tool. FM will rasterize onto the image when creating the output.
Rasterized even if the image is SVG?
In newer FMs SVG is supposedly able to be passed through to the HTML as the XML that it is. Even with a raster source image, it would be nice to avoid having the border rasterized as well.
Theoretically, this seems possible, if the client CHM viewer supports SVG (and older ones don't):
So, with suitable tools, one could
► paste the raster image into an SVG editor,
► add the border in the SVG, as vector,
► save it all as a single SVG,
► import it into the FM document, then
► cross your fingers and run the workflow to CHM.
We use pngs mostly, with some jpegs thrown in.
Is the svg method preferable (in the viewability and clarity of the border) to the method of adding the border in SnagIt?
re: Is the svg method preferable (in the viewability and clarity of the border)...
Only if it works
and I don't have a version of FM new enough to support testing SVG pass-thru.