Have you ever wondered, how you should present your text for translation to a professional translator? While most of our work comes in as .doc or other Microsoft Office files, we can handle just about any common file format for translation. That means, no more converting of text back and forth and no more worrying whether the formatting will stay intact during the translation process. Here is a list of some monolingual file formats we can handle:
- HTML documents (*.html, *.htm)
- Microsoft® Word® documents and Rich Text Files (*.doc, *.rtf)
- Microsoft® Office 2007–2016 Word® documents (*.docx, *.docx)
- Text files (*.txt, *.inf, *.ini, *.reg, and many more). There is an unstructured and a structured filter for these.
- Microsoft® Excel® files (*.xls, *.xlt)
- Microsoft® Office 2007–2016 Excel® files (*.xlsx)
- Microsoft® PowerPoint® files (*.ppt, *.pps, *.pot)
- Microsoft® Office 2007–2016 PowerPoint® files (*.pptx, *.potx)
- OpenDocumentText (OpenOffice.org Write; ODT) documents
- Adobe® Framemaker® files (*.mif)
- Adobe® InDesign® INX and IDML files (*.inx, *.idml, *.indd)
- XML and SGML files (*.xml, *.sgml)
- XLIFF files (*xlf; *.xlz)
- .NET resource files (*.resx)
- Portable Document Format (PDF)
- Java properties files (*.properties)
- AuthorIT projects (*.xml)
- DITA documents (*.dita)
- Excel 2003 XML spreadsheets (*.xml)
- FreeMind mindmaps (*.mm)
- Microsoft Visio charts (*.vdx)
- Microsoft Help Workshop files (*.hhc, *.hhk)
- Scalable Vector Graphics drawings (*.svg)
- Typo3 pages (*.xml)
- JSON (*.json)
- YAML (*.yaml)
- WPML XLIFF files (*.xliff, or no extension)