Simple yet powerful translation and localisation library for .NET applications. Supports XAML binding, language fallbacks, count-specific translations, placeholders, and number and time formatting.

It only takes about 4 minutes to read this page.

tl;dr: Overview of the advantages and features:

  • Localisation support for all types of .NET applications
    (WPF, WinForms, ASP.NET, Service, Console)
  • Easy syntax through XAML extension and Windows Forms binding
  • Comfortable editor application for dictionaries with consistency checks and similar translations suggestions
  • Fallback language on missing translation of a text
  • Complete solution for drop-in localisation for independent developers and small businesses
  • Count-specific translations (singular/plural)
  • Named placeholders to include data
  • Formatting of numbers and dates/times
  • Typographic support (quotation marks, punctuation etc.)
  • Storage of all translations in a single XML dictionary file
  • Wizard for existing literal strings in Visual Studio (C#, XAML)
  • Usage as one DLL or a few C# source files
  • Run-time logging

The Tx concept

Tx is a simple yet powerful translation and localisation library for .NET applications. It manages a dictionary containing all the text snippets and phrases you need, for multiple translations. If a translation is not available in your preferred language, it can be looked up from other languages. Texts can also contain named place-holders that are filled with your data at runtime so that you don’t need to concatenate all the parts yourself in the right order. Localisation tasks like typography, number or time formatting according to the local standards are also covered.

A special feature of Tx dictionaries is that each text can have different translations depending on the subject count you’re talking about, also called pluralisation. One day is a different word than two days. This allows you to speak to your users in the most natural way, avoiding ugly parentheses or alternatives for plural words in the user interface.

All texts and translations are stored in an XML dictionary file, one per project. This XML file usually contains all languages. The dictionary can be installed with your application, or compiled right into it as an embedded resource.

The TxLib library can be used from any .NET application and is the part you’ll distribute with your application. For more portable applications, you could also directly copy the class files into your project – it’s only a few files. Its main class, Tx, is further described in the documentation.

Text keys

All texts are associated with text keys. A text key is a short string that uniquely identifies a text or phrase and is usually used in the application source code to refer to a specific text. Text keys can be freely assigned by the developer, but there are some structuring guidelines described at the end of the documentation and a few additional requirements when using the TxEditor tool.


The .NET framework uses the concept of cultures to specify a combination of language and data formatting rules. Each culture has a code that describes the language and optionally a region. There are more variants but they are not supported by TxLib. Examples are “en” for the English language, “de-DE” for the German language in Germany or “pt-BR” for the Portuguese language in Brasil (as opposed to Portugal which many would probably first think of). TxLib uses these cultures to identify translations and both, region-specific and language-only codes, are used where the latter ones always serve as fallback if a translation is not found for a specific culture.


The TxTranslation solution also comes with a graphical translation file editor that provides all the functionality for translating personnel that don’t necessarily have any programming experience. The TxEditor application can load a dictionary file, list all the text keys that it defines and allows viewing and editing the translation texts. It performs consistency checks to point the user to potential errors and highlight missing translations. TxEditor also makes use of TxLib itself so it is fully localisable and can be used to translate itself into other languages.

Compatibility: .NET Version 4.0 or newer


The following C# example shows several usage possibilities of the Tx class.

// Simple text retrieval by key:
Tx.T("my text key")

// Count-specific translations:
Tx.T("days", daysCount)

// Use of named placeholders:
Tx.T("user info",                // The text key
    "name", userName,            // Pairs of placeholder names and values
    "location", User.Location,
    "status", statusValue)

// Quote text (put it in local quotation marks):

// Combine translation and quote:
Tx.QT("my text key")

// Date formatting:
Tx.Time(DateTime.Now, TxTime.MonthDayLong)

// Relative time formatting:

// Bonus: ISO 8601 time interval handling:
new DateTimeInterval(DateTime.Now, "PT3H25M").TimeSpan

// Dictionary culture listing (returns string[]):

The following XAML example shows several usage possibilities of the WPF bindings.

<Window x:Class="WpfDemo.MainWindow"
        xmlns:Tx="http://unclassified.software/source/txtranslation" ...>
    <TextBlock Text="{Tx:T my text key}"/>
    <TextBlock Text="{Tx:T n months, {Binding Value, ElementName=Counter}}"/>
    <TextBlock Text="{Tx:Number {Binding Power}, 3, Unit=kW}"/>
    <TextBlock Text="{Tx:DataSize {Binding FileSize}}"/>
    <TextBlock Text="{Tx:Time {Binding LastUpdate}, Details='DowLong,YearMonthDay'}"/>

The documentation (docx and pdf in the code repository) describes the TxLib methods usage as well as the TxEditor application more detailed.


Here are several screenshots of the TxEditor application:

TxEditor main window
TxEditor main window
Count-specific translation
TxEditor with extras
Add new text key
Highlighting of translation errors


Note: Releases after 2016-01-09 are no longer digitally signed because there are no more free code signing certificates available for open source developers. A commercial certificate from 200 € per year doesn’t pay for me. I’m sorry for the confusion this may cause with your next download.

TxSetup-1.389.78_61a1bb.exe1.7 MiBInstallation package with TxEditor, TxLib, documentation, source code, and code reference
Version 1.389.78 of 2016-01-25, Commit 61a1bb

TxChanges.txt2.3 KiBChange log of published versions

master.zipLatest source code directly from GitHub

Previous versions

You can also head over to GitHub to download any previous revision or check the issue tracker:

TxTranslation repository on GitHub

This package is also available through NuGet. That way, it can be integrated and updated in a Visual Studio project very quickly. This package only includes the TxLib assembly for .NET 4.0. For installing TxEditor you need to download the setup program above.

Unclassified.TxLib package on NuGet

Current development state

TxLib and the dictionary file format are now considered stable but little tested yet. There are plans for future additional features but no API change.

TxEditor is still new and also incomplete. Some indicated functions are missing or stop working in some conditions. The user interface is not yet rock-solid or even very clean. This is currently being improved.

The documentation is almost complete, but some sections about unfinished parts in TxEditor are also missing. The source code reference is not ready for the public yet, use the inline comments through IntelliSense instead (original source code or .xml file).


Version 1.389.78 (Commit 61a1bb8)
  • TxEditor: Text key wizard: Preset language from current file type in the Visual Studio editor
  • TxEditor: Text key wizard: ASP.NET Razor .cshtml files are handled for code and content text
  • TxEditor: Text key wizard: "Add colon" option when one was found in the text
  • TxEditor: Text key wizard: Skip unused placeholders in code generation
  • TxEditor: Text key wizard: Enter key in "Similar texts" list select key instead of clicking the OK button
  • TxEditor: Text key wizard: Fixed file extension recognition for unsaved files (* after file name)
  • TxEditor: Text key wizard: Fixed parsing end of string quote within one level of parentheses in code
  • TxEditor: Load files selection: Double click opens file when the list is complete
  • TxEditor: Load files selection: Automatically load only found file with /scan option
  • TxEditor: Consider ellipsis character for inconsistent punctuation
  • TxEditor: Only accept numeric values in count and module fields
  • TxEditor: Avoid flickering of main window after closing text key wizard dialog
  • TxEditor: Writing XML comment with TxEditor download link into .txd files
  • Updated documentation (docx only)

Version 1.383.76 (Commit da9f9bb)
  • TxEditor: Copy text key to clipboard from the context menu
  • TxEditor: Text key wizard: Support for C# 6 interpolated strings
  • TxEditor: Text key wizard: C# 6 string parsing, accelerator keys
  • TxLib: Obfuscation compatibility for XAML use
  • Shared code update and cleanup, updated formatting to new style guide
  • Update to Visual Studio 2015

Version 1.184.37 (Commit 7f3858f)
  • TxLib: Fix: .txd file is not reloaded when saved with TxEditor

Version 1.113.79 (Commit b4ffb00)
  • Allow disabling special verbose single-unit texts in Tx.TimeSpanRaw for generic use
  • Build script and tools updated

Version 1.53.78 (Commit a21990a)
First log entry in this file.

For a full list of changes please refer to the Git repository commit history.

Licence and terms of use

The TxLib library, which is used in applications, is released under the terms of the GNU LGPL licence, version 3. The other projects (TxEditor, demos and converters) are released under the terms of the GNU GPL licence, version 3. You can find the detailed terms and conditions in the download or on the GNU website (LGPL, GPL).

Statistic data

  • Created on 2013-07-01, updated on 2016-01-26.
  • Ca. 15 300 lines of code, estimated development costs: 15 000 - 61 000 €