Adobe 9622 bug entered in January still not fixed

Forum|Forum|4 years ago
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.

Matt-Tech Comm Tools

Community Expert

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

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.

C

cheryls1730789Author

Known Participant

Also forgot to mention, by automatically adding the Comment tag back in, we go back and remove that. That is annoying, but doable.

Sign up

To post, reply, or follow discussions, please sign in with your Adobe ID.

Sign in to Adobe Community

To post, reply, or follow discussions, please sign in with your Adobe ID.

Scanning file for viruses.

This file cannot be downloaded