There are many other file formats that go beyond more traditional desktop-document file formats. Many are simply containers for component text and strings, e.g., .json, .csv, .xlsx, .xml, etc. These file formats can store any kind of information, so if you deploy them, it’s important to find out if the TMS has features that can support them. These files can include instructions or contextual descriptions for translators, string keys for UI string matching (.json, .yaml, .properties), or string plurals for Android (.xml) or iOS (.stringsdict, .plist).

Some TMS providers can have the ability to build custom file filters for proprietary file formats. They can set up custom rules or configurations that can handle specific proprietary file formats. These filters allow the TMS to parse and process the content within those proprietary file formats and enable text customization, especially content which can be customized in text (.txt) or MS Office formats (.docx, .xlsx, .pptx, etc.). For example, in a logging system, custom TXT formats with specific file filters can help organize and extract relevant information from log files. If you have a custom TXT format for application logs with structured entries, a custom file filter lets you extract logs based on specific criteria, such as date range, severity level, or specific error message, and use them for tasks like analyzing and troubleshooting issues in the application