Visual localization
Translate desktop UI in visual context.
Lingobit Localizer opens the dialogs and forms of your build, so translators type where the text appears, see what no longer fits, and fix it before release, without the IDE or the source code.
- Visual editors
- Win32 / MFC dialogs, WinForms and Delphi forms
- Preview
- WPF, HTML, XML, and menus
- In the editor
- Type in place, move, resize, align, flip for right-to-left
- Who works there
- Translators, without the IDE or the source code
On this page
One window: the tree, the table, and the dialog itself.
A visual editor or a preview on each platform.
Win32 / MFC dialogs, WinForms forms, and Delphi / C++Builder forms open in a visual editor. WPF, HTML, and XML open in a preview with the current translation.
-
Delphi / C++Builder
Visual editor
VCL forms from the binary: move, resize, align; menus in the preview.
Menus open in the preview with their items in Win32, Delphi, WinForms, and WPF.
What a string table cannot show you.
Is Open a command or a status? In the table it is one word. The form shows it is a node of the order tree, so it becomes Offen, not Öffnen.
- Lists and trees with their contents. Column headers and groups of a list view, tree nodes, list and combo box items appear in the form.
- Sizes and fonts per language. Move and resize controls, or change the dialog font for a language; the changes are stored with the translation.
Designer tools for the translated layout.
WinForms forms open with or without your third-party controls.
Where the third-party components your forms use are installed, Full shows each form exactly as your application does. Where they are not, for example on a translator's computer, Safe builds a very close form from standard controls.
You choose which standard control stands for each of your control types, for example any type whose name ends in Label as a Label. Every string is translatable in both modes.
What visual localization does and does not promise.
What Lingobit provides
- Visual editors for Win32 / MFC dialogs, WinForms forms, and Delphi / C++Builder forms: type in place, move, resize, align, and flip for right-to-left languages
- A preview for WPF windows, HTML pages, XML, and menus, with the current translation
- Translation and review of the UI without sending translators into the development IDE
What still needs project-side verification
- WPF uses a preview of compiled BAML, not a full WPF designer; there is no standalone XAML preview, and text that does not fit is not reported automatically
- Menus show the menu resource, not items the application adds or draws at run time; menu layout is not edited
- The XML and HTML previews are not runtime or browser testing
- Custom controls, runtime-generated UI, scripts, and application logic may need verification outside Localizer
- Preview does not replace final testing in the real application; the build, packaging, and runtime behavior remain the project's responsibility
Related capabilities
- Localization QAValidate placeholders, hotkeys, and cut-off text across the project, and use Crash Finder where needed.
- PreparationExtract hardcoded strings, lock technical content, and pseudo-translate before translators start.
- Translation workflowSend translators a task; they work with the same visual editor and preview.
- Supported formatsWhich file types get a visual editor, a preview, or resource-level localization.
Test visual localization on representative application files.
Visual support depends on the application type and resource format. Review the extracted resources, the previews or visual editors, and the localized output in the real application.