Use ezParse to extract localizable content from various file formats. These files can use various encoding schemes such as UTF-8 or UTF-16. While ezParse can handle virtually ant type of text file, it works best on files that have a regular structure, or files that have common delimiters to identify text that needs to be extracted and translated.

For each proprietary file format, one or more ezParse rules can be developed. Each ezParse rule can contain a number of extraction methods that define what is localizable and what needs to be extracted and displayed to the translator.

Methods

Each ezParse rule consists of one of more extraction methods. These methods are created using Regular Expressions and are used to identify translatable content in text or proprietary file formats,

To translate a text file you need to follow two simple steps :-

one.bmp

Create an ezParse Rule: Create an ezParse Rule that can identify translatable text: Using ezParse you need to identify text that is to be extracted and translated. You do this by creating a rule. For each file type, you’ll define one or more rules.

For example, if you have a file with the extension .TXT, you may  create a rule called Tab-Delimited. You can have several rules defined for each file extension. Alchemy CATALYST will prompt you to select the most appropriate rule when the file is inserted into your Project TTK file.

two.bmp

Apply  the ezParse Rule when inserting files into a Project TTK:  When inserting  text files into Alchemy CATALYST you will be requested to select the most appropriate rule to apply during insertion.

If you’ve defined only one rule, Alchemy CATALYST will automatically select this and insert the file. If several rules have been defined you’ll be requested to select the most appropriate rule from a list.
 
That's it! You can no handle the translation of virtually any file format using Alchemy CATALYST.