Command Line Compile errors in RH6

[Dan_Gill]

We're evaluationg RH6. We can compile Webhelp from the command line, but on one of our machines we get the following template errors:
<Snip>___________________________________________
Applying WebHelp 5.50 Template...

Template Error: can not resolve macro: WH_LNG_LoadingData
..Template Error: can not resolve macro: WH_LNG_MergeError1
Template Error: can not resolve macro: WH_LNG_MergeError2
Template Error: can not resolve macro: WH_LNG_JS_alert_ProjectLoadingFail
.Template Error: can not resolve macro: WH_LNG_PreTooltip in c:\foo\whtopic.js
Template Error: can not resolve macro: WH_LNG_NextTooltip in c:\foo\whtopic.js
Template Error: can not resolve macro: WH_LNG_Show_Navigation_Component in c:\foo\whtopic.js
Template Error: can not resolve macro: WH_LNG_Hide_Navigation_Component in c:\foo\whtopic.js
Template Error: can not resolve macro: WH_LNG_Show_Navigation_Component in c:\foo\whtopic.js
Template Error: can not resolve macro: WH_LNG_Hide_Navigation_Component in c:\foo\whtopic.js
Template Error: can not resolve macro: WH_LNG_SyncTocTooltip in c:\foo\whtopic.js
.....Template Error: can not resolve macro: WH_LNG_IndexSelectTopicTitle
Template Error: can not resolve macro: WH_LNG_IndexSelectTopicLabel
.....Template Error: can not resolve macro: WH_LNG_LoadingContentsData
Template Error: can not resolve macro: WH_LNG_Book
Template Error: can not resolve macro: WH_LNG_Page
Template Error: can not resolve macro: WH_LNG_Remote_Page
....Template Error: can not resolve macro: WH_LNG_IndexBtnText
.Template Error: can not resolve macro: WH_LNG_CantSearch
Template Error: can not resolve macro: WH_LNG_LoadingData
..Template Error: can not resolve macro: WH_LNG_SearchPrompt in c:\foo\whfform.htm
Template Error: can not resolve macro: WH_LNG_SearchPrompt in c:\foo\whfform.htm
Template Error: can not resolve macro: WH_LNG_FtsBtnText
....Template Error: can not resolve macro: WH_LNG_JS_alert_ErrorInLoading
.......................................Template Error: can not resolve macro: WH_LNG_SearchPrompt in c:\foo\whtbar.js
Template Error: can not resolve macro: WH_LNG_ToolBarSearchBtnText in c:\foo\whtbar.js
Template Error: can not resolve macro: WH_LNG_Show_Navigation_Component in c:\foo\whtbar.js
Template Error: can not resolve macro: WH_LNG_Hide_Navigation_Component in c:\foo\whtbar.js
Template Error: can not resolve macro: WH_LNG_Hide_Navigation_Component in c:\foo\whtbar.js
Template Error: can not resolve macro: WH_LNG_SyncTocTooltip in c:\foo\whtbar.js
Template Error: can not resolve macro: WH_LNG_NextTooltip in c:\foo\whtbar.js
Template Error: can not resolve macro: WH_LNG_PreTooltip in c:\foo\whtbar.js
<Snip>----------------------------------------------------------------------
The compile is successful, and we can view the output.

Note that the project is under SVN (Tortoise). It does not generate the errors when compiled on the machine where it resides. The errors come when compiling from the other machine.

Can anyone tell me the source of these errors?

[Bobby_Walker]

Hello Dan,

The phrase "Template Error: can not resolve macro:" tells me that you are using a template, which means that you are likely generating printed or PDF output. Is this correct?

Can you generate printed output from this computer manually?
Has Microsoft Word been launched on this computer?
Are the macros setup in MS Word set high? You may consider lowering it some.

If these steps do not help narrow down the issue some, you might consider renaming normal.dot. You can look on Microsoft's web site for details on how to do this: http://support.microsoft.com/kb/822005.

Thank you,

Bobby Walker
Adobe Technical Support

[Dan_Gill]

No, we are not generating printed or PDF output. We are compiling only Webhelp. The command we are using is:

rhcl <path> -l webhelp -o <path>

Note that the first line of the errors says "Applying WebHelp 5.50 Template . . ."

[Dan_Gill · Accepted solution]

We discovered the source of these warnings. If the project is compiled through RoboHelp, then through the command line interface, the errors do not appear.
Comparing the .PSS files, we noticed differences in the LANGUAGE path between the file generated on the source machine and the one generated on the build machine. It turns out that setting the path to the version-controlled source files to the same directory structure soved the problem.