What's New in Localizer 10

.NET and WPF

.NET Framework 4.8 and .NET 5–10. Localizer detects the .NET version and bitness of each assembly; you can override them, and the choice is saved in the project.
WinForms form editor with two modes: Full shows the form as the application does, Safe opens forms that cannot be loaded completely. The editor runs in a separate process, so a failing assembly does not close Localizer.
64-bit resource processing and form editor.
WPF and BAML: parsing, preview, and writing of translations, including resources split across several assemblies.

DeepL, Google Translate, and Microsoft Azure Translator, with a Test button for the credentials. Credentials are stored for the current Windows user and are not saved in the project. See Machine translation.
Redesigned Translation Hints: several variants per provider with similarity and length, validation of each variant, and the checks chosen per project.

Import Matching Translations imports only the entries that match the project, from TMX, XLIFF, CSV and text, Lingobit translation memory files, a folder, or a ZIP archive, with exact, high (95%), and broad matches.
Translation memory statistics and Clean Up; export of translation memory and terminology to TMX, CSV, and text.
New terminology import with TBX and the Microsoft Terminology download (Enterprise).

Scan for Changes, import from localized files, and Import Translation Results show what changed in groups New, Updated, and Removed, with counts of text, status, and property changes.
Recent Changes and Any Merge Changes filters, Clear Merge Status.
Translation Readiness in the Statistics pane and the filters Needs Translation, Needs Review, and Ready for Release.

The Output panel replaces the Validation pane and shows all operations with their results.
New checks and automatic fixes, Fix all in this group, safe fixes after machine translation, and Validation before Create Localized. See Validation.
Create Localized Files reports characters that cannot be written in the output encoding.

Prepare Translation Task and Import Translation Results replace Send to Translator and Receive from Translator. The Delivery Bundle contains the translator project, the signed setup, a README, and your files.
XLIFF import presets: Standard, Any non-empty translation, Approved only.
Translator Edition is included with every Localizer license; available features follow the main license. At startup you can choose to start in Translator Edition.

gettext PO: output in UTF-8, msgctxt as part of the key, #. comments in Translation Hints, fuzzy removed from translated messages, language folders such as de_DE.
Qt TS: file suffixes such as app_de_DE.ts.
Java .properties in UTF-8, as in Java 9, with ISO-8859-1 as fallback; blank lines are kept.
HTML: in new projects EM, A, and SPAN do not break a sentence, and placeholder and aria-label are translated.
Apple: XIB and storyboard files from Xcode 5 and later; .lproj folders named as Xcode expects, such as de.lproj and zh-Hans.lproj.
MFC: resource-only DLLs named as MFC loads them, such as MyAppDEU.dll.
New macros $(PosixLang), $(AppleLang), and $(LangAbbr). Projects from earlier versions keep their output names. See Macros.

New theme, start page with samples, and rebuilt menus.
Reworked Translate Duplicates, Generate Project Report, and the Dictionary Manager for spell-check dictionaries.
Installation for all users or for the current user; setup installs the required runtimes.
Projects from earlier versions open in Localizer 10.

.NET 1.x, 2.0, and 3.5 assemblies. Use Localizer 9 for these applications.
The former Microsoft Translator integration, replaced by Azure Translator, DeepL, and Google Translate.
The Validation pane, replaced by the Output panel.