ezScript™ is a Command Line Language that is used to automate repetitive tasks. Using ezScript it is possible to integrate Alchemy CATALYST within your language build system or perhaps automate the acceptance testing and validation of your TTKs post-translation.

In this reference you'll find a complete listing of all ezScript Commands. This reference details the options available for each ezScript Command along with their syntax. It also contains examples of how you might use ezScript Commands within your localization process.

Pick a Topic

Align Translation

Analyse Projects

Apply Status

Clean Up to Alchemy TM

Check and Compact TTK

Comparison Expert

Create a CatPack

Create Project / Insert Files

Delete File or Folder

Details Files

Dialog Font (Change Dialog Font)

Divide Project

Extract Files

Export / Import all images

Export and Leverage Duplicates

Export Project (Create Glossary)

Find and Replace

Flip Dialogs

Fix Lead/Trail Spaces

Get File Names

Get Project Language

Get Project Statistics

 

Languages (Add new Language in Jar File)

Languages (Add new Language in Win32)

Languages (Get Project Languages)

Languages (Swap Source and Target Languages)

Layout Manager Expert

Leverage Expert

Licenses (Polling for a License)

Set/Reset TTK Properties (Project Title)

Set/Reset TTK Properties (Project Languages)

Set/Reset TTK Properties (Apply Keywords)

Pseudo Translate Expert

Rename File or Folder

Revert TTK Settings

Running Multiple Instances (JobIDs)

Statistics Report

Update Expert

User Profiles

Validate Expert

XLIFF Export / Import

Save Up TTK Version

Reference: ezScript Error Codes

Translation Memory Utilities

 

For a complete list of allowable Language codes, please refer to ezScript Language Codes.

GlobalLink Connectivity

GlobalLink Enterprise Submit

GolobalLink Enterprise Retrieve

TM Server Clean Up

TM Server Leverage

 

 

Running Multiple Instances

It is possible to run multiple instances of Alchemy CATALYST on a desktop PC. Each of these instances or sessions can have their own private configuration and setup options and they can run independently of each other.

Use the /StartJob and /EndJob commands to start and end one of these sessions.