Skip to main content
L
LNHarding
Inspiring
October 19, 2021
Answered

Possible Bug in Latest Release of FrameMaker (16.0.3.979) related to DitaVal - Bug in User Manual...

  • October 19, 2021
  • 1 reply
  • 137 views

Ever since I updated to the last patch/release my DitaVal files have not been working. They worked just fine previously. I decided to look up the User Manual to verify that my DitaVal file is correct or to possibly try to create one using FrameMaker. The User Manual has an error in it here: Adobe FrameMaker (2019 release) where they interchange @ATT (correct) with @10557939 (incorrect) so that was one issue I found. I still have not been able to get my DitaVal files to work with my maps and I was curious if anyone else had this same issue? Or if there's a good way to "force" FrameMaker to process my files?

 

 

    This topic has been closed for replies.
    Correct answer LNHarding

    So after a little more research I removed a line <!DOCTYPE val PUBLIC "-//OASIS//DTD DITA 1.3 DITAVAL//EN" "ditaval.dtd" []> from my Ditaval files and then when I selected the Ditaval file through the Publish dialog I deselected the "Use ditaval file to filter content" checkbox and then reselected the checkbox and it seems to work now...

    1 reply

    L
    LNHardingAuthorCorrect answer
    Inspiring
    October 19, 2021

    So after a little more research I removed a line <!DOCTYPE val PUBLIC "-//OASIS//DTD DITA 1.3 DITAVAL//EN" "ditaval.dtd" []> from my Ditaval files and then when I selected the Ditaval file through the Publish dialog I deselected the "Use ditaval file to filter content" checkbox and then reselected the checkbox and it seems to work now...

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