PowerGREP can convert files in many proprietary file formats to plain text in order to search through them. Many examples earlier in this section explain how to set this up. This example assumes you’ve already done so.
If you need to process these files with other applications that can’t read their proprietary formats, use PowerGREP to convert the files to plain text, and then use the other applications on the converted files.
Doing this conversion is also useful if you will be repeatedly searching through the same set of files and the files are too large to fit in PowerGREP’s conversion cache. It’s even more useful if many people on your network are searching through the same set of files, as the conversion cache is not shared between PCs. This way, the conversion needs to be done only once. Converting files from their proprietary formats to plain text usually takes much longer than searching through that plain text.
When PowerGREP is the target application, set “target file text encoding” to UTF-16LE. Also make sure that “text encodings to read files with” has the option “write a byte order marker at the start of Unicode files” turned on for the default settings and all format specific settings. The predefined “generic auto detection” configuration does this. This ensures that all the converted files use UTF-16LE with a BOM. These files support all characters and PowerGREP will always read them correctly due to the BOM, regardless of the text encoding configuration used when searching through these files in the future. Set “target file line break style” to “same as original file” as PowerGREP handles all line break styles automatically.
When there are new or modified files to be converted, you can repeat the action to convert just the modified files. To do this, set “file modification dates” in the File Selector to “modified on or after”. Set the date to the day you last ran the conversion.