Copy link to clipboard
Copied
Hello fellows,
It appears that when setting up the FM Publisher HTML5 dynamic filters, FM replaces a dash and a slash in the condition flag names with underscore. Any way to avoid that? Tried html entities for dash and slash - no luck.
Thanks,
Roman
1 Correct answer
Hi Bob,
Thank you for your response!
Unless I miss something, nothing happens when adding this unicode representation of these characters.
Framemaker doesn't parse it (turns it to "U_").
Regards,
Roman
Copy link to clipboard
Copied
What happens with:
[∕] U+2215 DIVISION SLASH
[‐] U+2010 HYPHEN (among other Unicode "dash" options)
For anything that's going to end up in an HTML or XML filename, characters need to not only be compliant with all random operating systems that might end up hosting, browsing or locally saving the work, but sound practice also needs to avoid characters red-flagged as phishing surrogates (which U+2215 is), and FM may be honoring such factors.
Copy link to clipboard
Copied
Hi Bob,
Thank you for your response!
Unless I miss something, nothing happens when adding this unicode representation of these characters.
Framemaker doesn't parse it (turns it to "U_").
Regards,
Roman
Copy link to clipboard
Copied
I recommend removing special characters like dash, slash, pound, tilde, exclaim, etc. from your labels across all your catalogs, and across your markers as well. When exporting to things like HTML5 and EPUB, you'll discover those characters are confused with code used in those systems and you're likely to get unexpected results.
An easy way to clean out those labels is Rick Quatro's FindChangeFormatsBatch https://techcommtools.com/my-fm-secret-weapon-findchangeformatsbatch/
FrameMaker Course Creator, Author, Trainer, Consultant
Copy link to clipboard
Copied
Hi Matt,
Thank you for your response!
In our use case, we need a hyphen and a slash to appear in the names of dynamic filter tags. This is the only place where these chars are not parsed correctly.
Regards,
Roman

