Copy link to clipboard
Copied
This topic was asked in another post, but never answered: .svg images are not appearing in HTML5 generated in FrameMaker 2019
When I generate Responsive HTML5 output in FrameMaker 2020 (Version: 16.0.0.754), the output does not display SVG images. It displays all other formats, however, like PNG, BMP, etc.
I tried selecting the "Convert SVG to Raster image" check box, and I also tried clearing it. I tried IE, Chrome, and Firefox. Nothing seems to work.
FM is exporting and linking SVG properly, Source SVG needs to be re-validated.
Copy link to clipboard
Copied
Hi,
I have FM 16.0.1.814 (that's a beta version of the next update), and there SVG files are in the HTML5 content.
The SVG file has another file name, but the size and date is the same.
I use Firefox. Convert SVG to Raster image is deactivated. No special settings. The SVG file is very simple, just a warning icon.
I do not know, if this was fixed now in this update or if you should try again with a very simple file. Or with a default sts file.
Best regards
Winfried
Copy link to clipboard
Copied
FM is exporting and linking SVG properly, Source SVG needs to be re-validated.
Copy link to clipboard
Copied
Thank you, Pulkit. The SVG images were exported using Visio, and did not have the proper xlink validation.
Copy link to clipboard
Copied
Hi @Ed Geis
I understand your concern and would be more clarified if you kindly post a sample file and SVG image here or mail it directly to me.
Thanks
Pulkit Nagpal
punagpal@adobe.com
FM Engg.
Copy link to clipboard
Copied
Thank you, Pulkit. I will reply directly to your email with an SVG file from the "assets" folder, a small part of published help output, and some detail about how I created the file.
Copy link to clipboard
Copied
Where in the FM file structure does the SVG reside?
If on a Body page, this might be a bug.
If on a Master Page, content of various sorts on MPs does not flow to HTML.
Copy link to clipboard
Copied
The SVG, and all other image-file types, reside in a separate folder. We do not embed images in teh FM document itself; rather, we import them by reference.
We did not experience this issue in previous versions of FrameMaker.
Copy link to clipboard
Copied
re: … import them by reference.
Roger that, but imported onto Body pages, or onto Master Pages?
Chances are this is a bug, but if onto-MP, it's not.
Copy link to clipboard
Copied
Ah, gotchya. Imported on body pages. We do have some simple svg images on reference pages that are coming through fine. We do not have any images on master pages, though.
If you think it's a bug, what's next? I sent sample output to Pulkit Nagpal.
Copy link to clipboard
Copied
re: If you think it's a bug, what's next? I sent sample output to Pulkit Nagpal.
The usual process is to file a bug on Adobe's Tracker page, but you are already at the usual next step after that, so just stay engaged.
Copy link to clipboard
Copied
Hi,
So some of your SVG files are exported to HTML5 correctly?
Are only those from the reference pages converted and none of the others?
Are the SVG files just missing? What's there? Which files are there where SVG images should be?
What's special with the missing SVG images?
Best regards
Winfried
Copy link to clipboard
Copied
Hi, Winfried.
I was partially mistaken. We have simple separator lines on our reference pages (for notes and warnings and such), which are drawn with the FrameMaker line tool. When I use FrameMaker to Publish Responsive HTML5 output, it converst these lines to svg, which is what I saw in the HTML code as svg. The output displays these lines just fine.
In other words, the only actual, original svg files we have are imported by reference onto body pages. These are the only types of images that the Help output fails to display.
Copy link to clipboard
Copied
Please also consider support to inline <svg>...</svg> into html5 output, so that interaction with svg elements becomes possible.
Copy link to clipboard
Copied
Hi @pj_lm ,
This thread is rather old, and your request is only little related.
To get more attention, please create a new thread and also report your request in the Adobe Tracker:
And please in more detail, so that it is clear what you mean.
You can also post the link to your Tracker report here, so that others can vote for it.
Best regards, Winfried
Get ready! An upgraded Adobe Community experience is coming in January.
Learn more