Skip to main content
davidcfrye5910298
davidcfrye5910298
Inspiring
December 14, 2022
Answered

% Sign Being Changed to %25 during HTML5 Conversion

  • December 14, 2022
  • 1 reply
  • 1580 views

Has anyone run into issues with the HTML5 conversion in Frame 2022 automatically changing % into %25 (the UTF code for %)? There was a similar issue with ? in Frame 2020 (https://tracker.adobe.com/#/view/FRMAKER-11210). While the issue specific to ? has been fixed (theoretically), this issue remains. I'd like to confirm whether anyone else has or can reproduce the issue. Browser type makes no difference. Most current version of Frame--17.0. 

 

Note: we have links in our materials to sites we don't control, so changing paths or naming conventions isn't always going to be an option. 

    This topic has been closed for replies.
    Correct answer davidcfrye5910298

    It was not fixed. The Version 17.0.3.546 has the same Mistake. What can we do?


    Are you sure this is the root cause of your particular issue? Version 17.0.0.226 had the issue. Version 17.0.1.305 fixed it. Version 17.0.2.431 seems to have broken it again. But, I had a member of my team experiment with 17.0.2.546 and it appeared to be fixed again. We were able to simultaneously compare output of the exact same links, from the exact same source files, using all of those versions. Can you confirm that the affected copy of Frame you experienced this with was the version you noted? Perhaps someone on your team is a version behind?

    1 reply

    Bob_Niland
    Community Expert
    Bob_NilandCommunity Expert
    Community Expert
    December 16, 2022

    What's the context in which the % is being percent-encoded,
    and what's an example string in which this is happening?

     

    Although the % character is Unicode U+0025, ASCII 25h, the % notation was actually developed for escaping ASCII characters that are problematic in URIs (URLS). Even % itself is expected to sometimes be %-encoded, especially if the string it's in might be confused for %-encoding when it's not (for example, the source string has digits following the %, e.g. abc%12345).

    davidcfrye5910298
    davidcfrye5910298Author
    Inspiring
    December 16, 2022

    The URL is in a hypertext marker. We're doing a standard Publish as HTML5 Responsive file generation. The URLs are lifted from various places and already have things like %20 or %2F etc in the visible URL. When the HTML is generated, the hyperlinks are converted to something like %2520 for %20. It appears to be a straight up conversion of all % signs in the hypertext marker into %25. Does that help clarify the issue? 

    Bob_Niland
    Community Expert
    Bob_NilandCommunity Expert
    Community Expert
    December 16, 2022

    re: Does that help clarify the issue?

    For those with experience in HTML5 gen from FM, I'll bet it helps.

     

    I don't use FM to generate HTML, but have some awareness of wider character encoding issues, in this case that the "escaping" character itself probably needs to be escaped because it already is elsewhere in the string(s).

     

    I had been wondering if this was just a matter of some mapping option or table in the Publish workflow, but where the hypertext already includes %-encoded content, the presence of a literal % may be triggering some logic that has no user controls.

     

    Nonetheless, I would expect the encoding to not cause problems. Servers & clients should be accustomed to this notation, and serve the object as requested.

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