In-context editing ›

In-context editing in Windows applications (SoluPick)

SoluPick brings in-context editing to Windows applications. A translator or a reviewer runs your application in a target language, holds Ctrl, and clicks a text. SoluPick finds the string the text comes from and opens it for editing, in Soluling Cloud or in Soluling Desktop.

Why SoluPick

  • No changes to your application. SoluPick reads the texts the way screen readers do, so most applications need no library, plug-in, or code of their own. They only have to be an in-context build, made with hidden ids. Delphi applications add one unit to make labels and FireMonkey controls pickable.
  • The real application, the real translations. The translator sees each translation in its dialog, next to the texts around it, with its real length, and finds the string by clicking it instead of searching for it.
  • Cloud or Desktop. The string opens in a compact Soluling Cloud editor next to the application, or it is selected in the project open in Soluling Desktop. Each application remembers its own choice.
  • Many frameworks. Windows Forms, WPF, Win32 and MFC, Delphi VCL, and Delphi FireMonkey. See what can be picked.

How it works

  1. An in-context build writes the string id of each row after its translation, as invisible characters. The application looks the same.
  2. SoluPick runs in the notification area of the taskbar. While you hold Ctrl, a frame follows the control under the mouse: purple when its text has a string id, gray when not.
  3. Ctrl+click reads the text of the control through Windows UI Automation, or asks the application itself if it uses Soluling's in-app unit, decodes the string id, and opens the string. The click itself doesn't reach the application, so a button isn't pressed.
  4. SoluPick finds the language the application shows from the files it has loaded, such as a Delphi resource DLL Driving.fi or a .NET satellite assembly fi\Driving.resources.dll. When the files don't tell, the editor compares the clicked text with the string's translations. The string opens in that language.

What you need

  • Windows 10 or 11.
  • An in-context build of your application, running in one of the project's target languages. The original language has no ids.
  • For Soluling Cloud: a Cloud account that is a member of the project, and a service plan that includes in-context editing. The editor window uses Microsoft Edge WebView2, which is part of Windows 11 and of current Windows 10.
  • For Soluling Desktop: the Enterprise or Build Automation edition of Soluling, and the project's .ntp file. No Cloud account is needed.

Install SoluPick

  • With Soluling Desktop. Soluling's setup installs SoluPick in the same folder as Soluling and adds SoluPick to the Start menu.
  • Without Soluling Desktop. If you translate only in Soluling Cloud, download the SoluPick setup. It installs SoluPick for you only and needs no administrator rights. Uninstall it from Windows Settings, Apps.
SoluPick's own setup
SoluPick's own setup, for translators who work only in Soluling Cloud. It installs SoluPick for the current user.

Start SoluPick from the Start menu. Its icon appears in the notification area of the taskbar. To have it always running, choose Start with Windows in its menu. Only one SoluPick runs at a time.

1. Build your application with hidden ids

With Soluling Desktop, turn on hidden id injection in the project's build options, or give SoluMake the -incontext option:

SoluMake build -incontext MyProject.ntp

When you translate in Soluling Cloud, the Cloud project must be the same project as the one you build, so that the ids match: upload the .ntp file to the cloud, or download the cloud project, before building.

.NET and Delphi applications that use Soluling's runtime library to choose their language need the current version of the library. Older versions don't expect hidden ids in the language names of the resources.

Use the in-context build only for translating and reviewing, never in production. See Keep it out of production.

2. Pick a text

  • Start the in-context build in a target language, for example Finnish.
  • Hold Ctrl and point at a text. The purple frame shows a text that can be picked.
  • Ctrl+click the text. The first time you pick from an application, SoluPick asks where you translate it: Soluling Cloud or Soluling Desktop. It remembers the choice for that application.
  • If the control has several strings, for example a text and its tooltip, a menu asks which one you want.
  • Ctrl+Shift+click opens the string in the other one, Cloud or Desktop, this time only.
  • If nothing can be opened, a short message next to the text says why, for example that the text has no id because the application runs in its original language.
SoluPick's purple frame around a menu of a Finnish application
A Finnish application with Ctrl held. The purple frame shows that Tiedosto (File) can be picked.

3a. Translate in Soluling Cloud

The string opens in SoluPick's editor window, right below your application when there is room on the screen, otherwise below the text or beside the application. It is the same editor as on web pages, with the original, its comment, where the string comes from, its length limit, and Soluling's spell checker.

SoluPick's editor window below a Finnish application
Etäisyys: was picked in a Finnish WPF application. SoluPick's editor window opened right below it, with the original, where the string comes from, and its Finnish translation.
  • The first time, sign in to Soluling Cloud in the window, and choose the application's project from the list of your projects. SoluPick remembers the project for that application.
  • Type the translation and click Save, or press Ctrl+Enter. Pick the next text: the same window shows it.
  • The editor offers only the languages you may edit. If several of them have the same translation, it asks which language the application shows, and remembers the answer for the next pick.
  • To fix the language of an application, choose it in the editor's Language list. SoluPick then uses it for every pick from that application. Automatic finds the language from the picked text again.
  • Open in Translate opens the string in the full Translate grid, in a SoluPick window that uses the same sign-in.
  • The editor window keeps its own sign-in, apart from your browser. Sign out in the editor, or Sign out of Soluling Cloud in SoluPick's menu, ends it.

3b. Translate in Soluling Desktop

  • SoluPick selects the string's row in the project open in Soluling, switches to the language the application shows, and brings Soluling to the front. If several languages have the same translation, Soluling keeps the language you have selected.
  • If Soluling isn't running, or another project is open, SoluPick opens the application's project in Soluling and selects the string when the project has loaded. It looks for the .ntp file in the application's folder and the folders above it. If it doesn't find one, it asks you to choose it, and remembers the file for that application.
  • If Soluling has a dialog open, close it and pick again.

When the translation reaches the application

The translation is saved in the project at once. The running application still shows the old text: it shows the new one after you build it again.

What can be picked

SoluPick can pick a text when the control gives it to other programs through Windows UI Automation, as it does for screen readers, or when the application uses Soluling's in-app unit for its framework.

Framework What can be picked
Windows Forms Forms, labels, buttons, menus, and the other standard controls.
WPF Windows, labels, buttons, menus, and the other standard controls.
Win32 and MFC Windows and the standard controls. Not owner-drawn controls.
Delphi VCL Forms, buttons, menus, and other windowed controls. Labels (TLabel) and other controls that draw their text themselves when the application uses the NtInContext unit, see below.
Delphi FireMonkey Everything when the application uses the FMX.NtInContext unit, see below. Without it only the window title and the menus of TMainMenu: FireMonkey draws its controls itself.

Delphi VCL labels and FireMonkey

VCL controls without a window of their own, such as TLabel and TSpeedButton, and all FireMonkey controls are not visible to UI Automation. Add a unit of Soluling's Delphi library to the in-context build of your application, and SoluPick asks the application itself for the text under the click. For VCL:

uses
  NtInContext;

For FireMonkey:

uses
  FMX.NtInContext;

The units have no functions to call. They answer SoluPick only when the texts under the click have hidden ids, so you can leave them in your production build: there they do nothing. If you prefer to keep them out, add them only to the in-context build, for example with {$IFDEF INCONTEXT}. The VCL unit needs Delphi 2009 or later.

Also not:

  • Texts in the original language, which have no ids.
  • Texts that a control draws itself, such as in owner-drawn grids and in games.
  • Applications that run as administrator, unless you start SoluPick as administrator too.
  • Applications in another Windows session, for example in Remote Desktop or a virtual machine. Run SoluPick in the same session as the application.

Right-click SoluPick's icon in the notification area:

SoluPick's menu in the notification area
SoluPick's menu. The application items name the application you last picked from.
  • Picking on turns picking on and off. Ctrl+Alt+P does the same.
  • Open the editor window shows the Cloud editor again after you closed it.
  • Choose the project of the application you last picked from, in Soluling Cloud.
  • Open picks from the application in Soluling Cloud or Soluling Desktop.
  • Sign out of Soluling Cloud.
  • Pick with Ctrl+click or Ctrl+Alt+click, if your application uses Ctrl+click itself.
  • Start with Windows and Quit.

Security and privacy

  • SoluPick watches the mouse only while picking is on, and reads texts only under the point you click or point at with Ctrl held. It sends nothing anywhere by itself.
  • SoluPick never stores passwords or tokens. The Cloud editor's sign-in is kept like a browser's, in SoluPick's own data folder.
  • The editor is Soluling Cloud's normal Translate, with its normal access checks: you see only the projects you are a member of.
  • A pick sent to Soluling Desktop carries only the project, the application's file name, the string id, and the clicked text. Desktop acts on it only if it is the open project's.
  • The in-app units, NtInContext and FMX.NtInContext, answer only on the computer where the application runs, and only with texts that have hidden ids.
  • SoluPick keeps its settings in %APPDATA%\Soluling\SoluPick.json and the editor's sign-in in %LOCALAPPDATA%\Soluling\SoluPick.