Translate .NET and Qt files
Translate .NET RESX and RESW resource files and Qt Linguist .ts files up to 12 MB. Resource names, headers and contexts stay, and only the strings are written.
.NET resource files (.resx and .resw) and Qt Linguist files (.ts) are accepted up to 12 MB. In both, the identifiers your code compiles against are structure and never change. Only the strings people read are translated.
What is translated, and what is left alone
| Format | Translated | Left as it was |
|---|---|---|
| RESX, RESW | The value of each string entry | name attributes, the resource header and schema, xml:space, the comment column, images and other non-string resources |
| Qt Linguist | The translation of each message | Context names, source strings, locations, %1 and %n, HTML fragments |
For Qt, the file’s language attribute is updated to the target when you translate into one language. A .ts file is recognised by its content: a TypeScript file with the same extension is refused.
What you can ask
Produces a Resources.fr.resx next to the original.
Translate the values into French. Keep placeholders such as {0} and {1} unchanged, and leave resource names and comments as they are.
Makes the plan list what it will write before you approve.
Translate only text strings into German. Leave embedded files, images and any entry that is not a string.
Fills every message of a Qt file for a native speaker to polish.
Translate all the unfinished messages into Spanish. Keep %1 and %2 unchanged and keep the mnemonic ampersands.
Leaves reviewed messages untouched after a new lupdate.
Translate only the messages that are unfinished in the Italian file, and leave the finished ones as they are.
Names the words that must read the same in every dialog.
Translate into Portuguese. Always translate “Settings” as “Configurações” and “Project” as “Projeto”.
Good to know
- One target language per upload for both formats. If you ask for two, the plan translates one and says so. Run the file once per language: your glossary carries over.
- Qt plurals. Messages that use Qt’s numerus forms are left as they are for now. The plan says how many there are so you can finish them in Qt Linguist.
- Compile as usual. For Qt, run
lreleaseafter, exactly as after translating in Qt Linguist. For .NET, compiling into a satellite assembly is unchanged. - Comments. A RESX comment documents the string for your team, so it is left in English unless you ask otherwise.
- Output filter. Not available: the whole file comes back.
- Ceiling. 12 MB.
Related
- Android and Apple strings and XLIFF for other localization formats.
- Other XML for XML that is not a resource file.
- All file formats