.NET RESX format (.resx, .resw)
The .NET RESX format reads Microsoft ResX 2.0 resource files and their
string-only .resw variant — the standard localization container for .NET
applications (locale by satellite filename, e.g. Strings.fr.resx).
String <data> entries become translatable blocks: the name attribute is
the block name, <value> is the source, a sibling <comment> becomes a
translator note, and xml:space="preserve" is honored. .NET composite-format
placeholders such as {0} and {1:t} are protected as inline codes. Typed
and binary <data> (those carrying type/mimetype), <metadata>,
<assembly>, name-reference entries, and the <resheader> boilerplate pass
through untouched. Round-trips are byte-faithful — only changed <value>
content is spliced back into the original document.
Parameters
| Parameter | Type | Default | Description |
|---|---|---|---|
extractComments | boolean | true | Surface each string <data> entry's sibling <comment> element as a translator note on the emitted block. Comments always round-trip verbatim regardless of this setting. |
skipNameDataReferences | boolean | true | Exclude designer name-reference entries (those whose name starts with ">", e.g. ">>control.Name") from extraction. These carry WinForms field names, not UI strings. |
Configure these parameters interactively and copy the YAML on the Format Reference.
Examples
Ignore comments
Do not turn <comment> elements into translator notes.
extractComments: false
Processing notes
Only string
<data>entries are translatable; typed/binary data, metadata, assembly, and resheader entries pass through untouched.xml:space="preserve"on an entry sets the block's preserve-whitespace flag..NET composite-format placeholders (
{0},{1:t}) are protected as inline codes.
← Back to the Format Reference