Exit
  • Global community
    • Language:
      • Deutsch
      • English
      • Español
      • Français
      • Português
  • 日本語コミュニティ
  • 한국 커뮤니티
0

ExtendScript hanging

Contributor ,
Apr 17, 2012 Apr 17, 2012

I've got a script (discussed in http://forums.adobe.com/message/4297510) that updates FrameMaker source in RoboHelp.

It works, but it's hanging due to a "The font information for your system has changed" error in FrameMaker. It looks like if FrameMaker is not open, RoboHelp changes the printer from Adobe PDF to WebWorks Rasterizer. If I have the FrameMaker book open and the correct printer selected, the script completes properly.

Any suggestions other than calling Adobe support?

var projectPath = "<path><.xpj file name>";

main();

function main()

{

        if(projectPath == "")

        {

               //Error!. Quit RoboHelp

               alert("Project path is not defined. \nPlease update the 'projectPath' variable in the script.");

               RoboHelp.quit();

        }

        RoboHelp.openProject(projectPath); //Open the project

        RoboHelp.project.updateAll(true); //Update all linked documents (pass true for Force update)

        RoboHelp.closeProject(); //Close project

        RoboHelp.quit(); //Quit RoboHelp

}

726
Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
LEGEND ,
Apr 17, 2012 Apr 17, 2012

Hi,

As far as I can make out from what you say, the problem is not in the script but in FM or the RH/FM integration. Can you manually force update the FM books that are linked in your RoboHelp project? The script does no more than simply force update all linked documents. And this *should* be the same as manually updating the linked documents.

Greet,

Willam

Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Contributor ,
Apr 18, 2012 Apr 18, 2012

I don't encounter the problem if I run the force update command manually.

Which I guess pretty much indicates it's a bug.

Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Contributor ,
Apr 18, 2012 Apr 18, 2012
LATEST

Never mind, the problem is that the default printer somehow got changed from Adobe PDF to WebWorks Rasterizer. Odd that that wasn't uninstalled along with WebWorks.

Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Resources
RoboHelp Documentation
Download Adobe RoboHelp