See the problem? How can we get around this? Well I am glad you asked. Finally the CHM file is finished compiling and ready to be moved.The batch file goes to its next command which is to move (a currently non-existent) CHM file.HTML Help Workshop will begin to compile the CHM file.AppLocale will call HTML Help Workshop under the Japanese code page, and as soon as the application is launched, AppLocale will quit.For example, let's say we want a batch file to compile a Japanese language CHM file, then move it to a location on another computer. The second issue is a bit more tricky because you want the spawned application to complete before continuing to the next batch command. Luckily there is a patch/hack for AppLocale to remove the nag screen that can be found here. AppLocale runs, spawns the called application in a child process, then quits while the child process is still active.A nag screen appears when calling AppLocale from the command line.However there are two drawbacks to this utility if you want to use it in an automated batch script. You can find more info about the utility here. This is ideal for applications, such as HTML Help Workshop, that require to be run under a target locale code.
The Microsoft AppLocale is a nifty utility that allows a program to run under a different system locale without having to reset the region settings and reboot the PC. Run Microsoft AppLocale Utility successfully in a batch script by calling it with a wrapper written in.
0 kommentar(er)
