Plain text files underpin software string exports, data pipeline outputs, and legacy system content.
TXT files appear simple but often contain nuances that require care: UTF-8 or UTF-16 encoding, Unix or Windows line endings, key-value string pairs, tab-delimited data, or inline variables enclosed in brackets or percentage signs. A translator who delivers a Word document from a TXT source creates unnecessary integration work.
BeTranslated translates TXT files in the format they arrive in, preserving encoding, line endings, and any variable placeholders. Translators are briefed on the presence of non-translatable elements, and the delivered file is ready to drop into your software build or data pipeline without reformatting.
UTF-8, UTF-16, and ISO-8859 encodings are preserved. The delivered file uses the same character encoding as the source, ensuring compatibility with your existing systems.
Inline variables such as %name%, {count}, or {{placeholder}} are identified and locked before translation so they are never inadvertently translated or broken.
Unix (LF) and Windows (CRLF) line endings are matched to the source file. Your parsing scripts and build tools receive exactly the format they expect.
Large volumes of TXT files, common in software localization projects, are processed in batch with consistent terminology applied across all files using a project glossary.
“I recently used a translation agency in France to translate several administrative and commercial documents into Spanish. The service I received was absolutely exceptional. Not only were the translations accurate and professional, but the team was also very +”
Google review (FR) , 2 years ago
“We regularly use BeTranslated's translation services and are very satisfied with their work. The team is professional and highly efficient! We highly recommend them.”
Google review (FR) , 2 years ago
“It is a real pleasure to work with the BeTranslated team who has been very professional, flexible and responsive during all projects.”
Google review (INTL) , 3 years ago
Everything you need to know about translating Plain Text files.
Yes. Key-value formats where the key should not be translated and the value should are handled by locking all keys before translation begins. Please include a note about the format structure when submitting. If your strings file uses a specific format such as Android strings.xml or Apple .strings, consider using the XML or JSON format pages for more specific information.
If a TXT file contains content in multiple source languages that all need translating into one target language, we handle this as a multi-source project. Quote on request with the language breakdown included in your submission.
Turnaround for plain text depends on word count rather than file count. We calculate word count after receiving the files and provide a firm quote and timeline. Rush processing for large TXT batches is available with advance notice.
Send us your Plain Text file and we will quote as quickly as possible. Format preserved, meaning accurate, delivered on time.
