Hi,
I have been trying to consolidate approximately ten project search path image folders into one.
I followed the process of exporting a .hmxz to HTML5/WebHelp to obtain a consolidated images folder. But during that process, a lot of image files were renamed to this style:
hmfile_hash_03fa3c0a.png
When I added the resultant "images" folder back into the search path, the H+M document did not recognize these filenames, and this obviously resulted in many missing images.
Next, I went to the source hmxz to publish as Word RTF. This process did not change the filenames.
So, is it advisable to export only to Word RTF to consolidate image files, or to follow both HTML5 and Word RTF to ensure all the images are consolidated...and ensure there are no illegal characters or spaces in filenames? After reading the forums, I noticed that these could be the problem.
Best regards,
Simon
HTML5/WebHelp image filename corruption
Moderators: Alexander Halser, Tim Green
-
simonjatkinson
- Posts: 4
- Joined: Mon Jul 08, 2024 3:18 pm
- Tim Green
- Site Admin
- Posts: 7818
- Joined: Mon Jun 24, 2002 9:11 am
- Location: Bruehl, Germany
- Contact:
Re: HTML5/WebHelp image filename corruption
Hi Simon,
Filenames containing spaces, umlauts, accented characters, many punctuation characters and others simply don't work on the Web. If you want to be safe you need to observe some simple rules that are stricter than necessary, but ensure that your filenames will always work:
You need to locate the original image files and use those instead.
This only happens on export and only to image filenames that aren't compatible with HTML. Unlike local operations on computers, where the operating systems like Windows and macOS now successfully hide the fact that filenames containing spaces and special characters are very problematic, web servers don't and can't do this, for a number of quite complex reasons. So Help+Manual is forced to give the file a new name that will be compatible, otherwise your images wouldn't display in your output.simonjatkinson wrote: Thu Jul 03, 2025 12:33 pm But during that process, a lot of image files were renamed to this style:
Filenames containing spaces, umlauts, accented characters, many punctuation characters and others simply don't work on the Web. If you want to be safe you need to observe some simple rules that are stricter than necessary, but ensure that your filenames will always work:
- No spaces
- No accented characters, umlauts or punctuation characters except - and _
- No non-alphanumeric characters
- only English/Latin a..z, A..Z, 0..9.
- Don't start a filename with a number
That's happening because Help+Manual doesn't touch or rename your original image files, only the exported ones. If you then try to use the exported ones as original images, their names don't match the ones in the references to them in your project, and Help+Manual can't find them.When I added the resultant "images" folder back into the search path, the H+M document did not recognize these filenames, and this obviously resulted in many missing images.
You need to locate the original image files and use those instead.
Regards,
Tim (EC Software Documentation & User Support)
Private support:
Please do not email or PM me with private support requests -- post to the forum directly.
Tim (EC Software Documentation & User Support)
Private support:
Please do not email or PM me with private support requests -- post to the forum directly.