These file types include Microsoft Office applications (such as Microsoft PowerPoint, Microsoft Word, and Microsoft Excel), specific “flavors” of XML (such as DITA and DocBook), Java server pages and .NET resources.

The configuration defaults for these file types should, in the majority of cases, correctly identify the translatable content in your assets. For all file types, you can create specific configurations for your assets on the Management > Linguistic Tool Setup > Filter Configurations page.

In general, image file types are not translatable. The exception is the Binary File Type, which by default handles files with .png, .jpg and .gif file extensions.

Note: You can confgure the filter to handle other image types, such as .bmp, by creating a new MIME type for that file type.

The Binary File type handles images within the translatable content in WorldServer Browser Workbench. It can be used to mark a file as translatable, but not segmentable. For example, you would apply the Binary File Type definition to an image file that contains content that you want translated. A workflow can send it to the translator who would need to use the appropriate tools to prepare a localized file in that format and then upload the target file to WorldServer.

For text file types, the filters parse and retrieve translatable text from files using popular markup languages including HTML, Adobe FrameMaker MIF files, and Quark Express export formats.

Some text filters are meant for simple files that don’t involve complicated rules for parsing the file and that only contain plain text.