These file formats 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 default configurations for these file formats should identify the translatable content in your assets correctly most of the time. You can create specific configurations for all file types by going to
.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 could apply the Binary File Type to an image file that contains content that you want translated. A workflow can send it to a translator, who would need to use the appropriate tools to prepare a localized file in that format, and then upload the target file into WorldServer.
For text file formats, the file types parse and retrieve translatable text from files using popular markup languages including HTML, Adobe FrameMaker MIF files, and Quark Express export formats.
Some text file types are meant for simple files that don’t involve complicated rules for parsing the file and that only contain plain text.
The WorldServer SDK lets you create custom file types in any category and specify particular processing behaviors. For example, you can create a text file type to process a text file with a strict format for the translatable portion of the file.