Duplicate SVG file names in Responsive HTML5 "assets" folder

[CaptLauren]

I am using FrameMaker V17 to publish Responsive HTML5 help.

The Assets folder in the Output contains graphic elements (screen shots) in their original .png formats and three corressponding .svg files. Each of the .svg file names are the same except for numbers appended to them. I would have thought that files with the same name would be overwritten each time I published.

My only thought is that these SVG files are for other formats such as mobile apps.

Any thoughts?

pls refer to the attached image

[Jeff_Coatsworth]

Are you publishing to the same location each time? Or are you generating output to a new destination?

[CaptLauren]

Hi Jeff- I did change the Output folder. Would doing so have appended a different file name to the topic?

[Jeff_Coatsworth]

No, I was thinking if you had published into the same folder each time, maybe it hadn't cleared it out. But now that I think about it, it could be that you're referencing it in a couple of different places in your content.

[CaptLauren]

That's an interesting thought. I think I'll clear out my files and re-publish the help. Any clue as to the meaning of the appended FOM_SVG_<nnn> in the file name? Would this have anything to do with the fact that it is Responsive HTML5? I suppose I could test that too by publishing to straight HTML.

[Jeff_Coatsworth · Accepted solution]

I don't think the HTML5 vs plain HTML made any difference - I've just noticed in one of my FM to RH import projects that if I use the same image in multiple spots, the conversion routine duplicates that name and applies a counter to the image files. Since the HTML5 Publish engine is really just RH under the hood, the same mechanism may be happening when you go FM > HTML5.

[Evelyn31028108aq7t]

It's great that you're using FrameMaker V17 to publish Responsive HTML5 help. Regarding the Assets folder in the output, it's interesting that you have both .png and .svg files with similar names, except for the appended numbers. It's natural to assume that files with the same name would be overwritten during the publishing process, but there could be a specific reason for the presence of multiple .svg files.

SVG files (Scalable Vector Graphics) are widely used for their scalability and flexibility. They can adapt to different screen sizes and resolutions without losing quality. It's possible that the additional .svg files are meant for different formats or device-specific variations of the graphics.

For example, the original .png files could be used for general purposes, while the corresponding .svg files may serve as alternatives specifically optimized for mobile apps or different screen resolutions. By providing multiple versions, the publishing process can dynamically select the most suitable format based on the target device or platform.

To confirm this, you can review your documentation or consult the documentation provided with FrameMaker V17 to see if it explains the purpose of the additional .svg files. Alternatively, you may reach out to the support resources or community associated with FrameMaker for further clarification.

Understanding the specific use and purpose of the .svg files in your particular publishing workflow will help you determine the necessity of these files and whether they serve a specific function for different formats or devices.

Overall, it's essential to follow the recommended practices and guidelines provided by FrameMaker and leverage the advantages of SVG files to ensure optimal scalability and quality in your Responsive HTML5 help.

[CaptLauren]

Thanks for the reply. I had thought about the use of SVG files for the different output formats (phone/tablet/desktop). I don't know how the conversion from PNG to SVG affects resolution, however. Because I am targeting a desktop layout only at this point, I haven't experimented with the others.