Skip to main content
C
cheryls1730789
Known Participant
May 11, 2021
Question

Adobe 9622 bug entered in January still not fixed

  • May 11, 2021
  • 1 reply
  • 895 views

I entered a bug for Framemaker 2020 back in January in Adobe's tracker tool (bug  9622). It had to do with the following conditional tags being added to the product by default:

FM_PDF_Comments_Highlight

FM_PDF_Comments_Underline

5 others also requested that the bug be fixed also. However, it is now May and it is still Open, not fixed. I have been waiting for this fix so i can upgrade Framemaker where i work to Framemaker 2020. We use conditional text heavily here and won't go to FM 2020 until this bug is fixed. How do we get Adobe to fix this bug?  Does anyone have any ideas?

    This topic has been closed for replies.

    1 reply

    Matt-Tech Comm Tools
    Community Expert
    Matt-Tech Comm ToolsCommunity Expert
    Community Expert
    May 11, 2021

    I'd be happy to vote for your issue on the tracker, if you can help me (and Adobe) how these tags are impacting you and preventing you from upgrading to the newest version. They appear on my new documents as well, but I just ignore them, as I do the default Comment tag.

    Apart from the fact that they exist, what's the workflow issue?

     

    -Matt

    -Matt Sullivan, FrameMaker Course Creator, Author, Trainer, Consultant
    C
    cheryls1730789Author
    Known Participant
    May 11, 2021

    We use conditional tags a lot in the manuals. Some have expressions. The expressions take into account the tags that have been configured. We don't want to change our expressions because 2 additional tags have been added that should be hidden. The tags mentioned cannot even be deleted like the Comment tag can.

    S
    Community Manager
    Stefan GentzCommunity Manager
    Community Manager
    May 11, 2021

    Thank you, that would be greatly appreciated. We have a lot of conditional tags here and having 2 that are not used and making sure they stay that way will some day cause someone to make a mistake. One of the others that approved this bug mentioned they do translations and can't have any conditional tags when sending over their translations. What's is involved with all that, I don't know. We do not do translations here. 

    thanks

    Cheryl


    That is a strange comment regarding translation. I'm not aware of any CAT tool, that does NOT support conditionals in FrameMaker files. And I guess I know pretty much all which are on the market …

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