Skip to main content
Rom_Ba
Inspiring
Sep 6, 2020 9:30 AM UTC
Answered

Framemaker Dynamic Filters (HTML5) - Dash and Slash in condition names

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

This topic is closed to new replies. Start a new post to keep the conversation going.
Rom_BaCorrect answer
Inspiring
Sep 6, 2020 7:17 PM UTC

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

 

View reply

4 replies

Matt-Tech Comm Tools
Community Expert
Matt-Tech Comm ToolsCommunity Expert
Community Expert
Sep 10, 2020 5:37 PM UTC

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/

Translate
-Matt Sullivan, FrameMaker Course Creator, Author, Trainer, Consultant
    Rom_BaAuthor
    Inspiring
    Sep 10, 2020 9:10 PM UTC

    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

    Translate
    Bob_Niland
    Community Expert
    Bob_NilandCommunity Expert
    Community Expert
    Sep 6, 2020 2:24 PM UTC

    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.

    Translate
      Rom_BaAuthorCorrect answer
      Inspiring
      Sep 6, 2020 7:17 PM UTC

      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

       

      Translate
      Terms & ConditionsAccessibility statement
      Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices