When Soluling reads items that have been added into the project, Soluling extracts elements that need to be localized. The strings, images, and other values from the elements are editable on the translation grid that is an Excel type of grid. However, in most cases, it is not enough to see just the original string value in order to translate it correctly. You need more information. You need to see where the string comes from or where it is used. This is why Soluling has visual editors. Their purpose is to show elements or entire files as WYSIWYG.
Not all the elements or nodes have visual editors. They are used with those nodes that contain some meaningful visual information. For example, dialog nodes or XML nodes can provide valuable information through visual editors. However, a string table cannot provide this. There are two kinds of visual editors: previews and full editors. Preview just shows the original or localized node but not let you change anything. Changing is done in the translation grid. Once you change the value in the grid Soluling updates the data in the preview to show the updated data. The full editor lets you change values. For example, a dialog editor lets you change the positions and sizes of the controls on the dialog. It does not let you change the text properties of the controls. You have to use the translation grid to edit strings, colors, fonts, etc.
Each programming platform has its own set of user interface controls. This is why dialog/form editors of Soluling are platform-specific. The is an editor for Visual C++, Delphi, Windows Forms, and WPF. Each platform-specific editor provides similar features, but the internal implementation is different. Each editor uses the native controls of the platform to show forms and controls. This makes it possible to provide 100% right WYSIWYG. Form and controls on Solulings editor show up just like in the development tools (Delphi, Visual Studio, etc.). Even if you use 3rd party controls, Soluling can show them visually correctly. If you send your project to the translator, Soluling will include the 3rd party controls libraries with the project. Some platforms, such as .NET require a runtime platform in order to work. If you are the developer, you have the right runtime platform already installed, and Soluling can automatically use it. If your translator does not have the same version of the runtime platform, Soluling cannot start the visual editor. In order for the translator to use the editor, he or she must install the right runtime. In such a case, Soluling will show the translator a dialog that explains this and contains a URL where the translator can download and install the right runtime.
Currently, only Windows Forms and WPF use runtime platform. If your .NET platform is 3.0, there is no need to install runtime platforms because Windows 7 and later contain it by default. If you use .NET 4.0, you have to install the runtime if you use Windows 7 or Windows 8.x. If you use Windows 10, you already have all .NET runtimes. In all cases, you don’t have to worry about the translator’s runtime because if needed, Soluling will prompt the translator and let him or her to download and install the right runtime.
Soluling's VCL editor shows all the standard VCL controls visually in the same way they would appear in the application when running it. However, if you use 3rd party controls or your own controls, the editor shows only the type of control and the position and size of the control. For example, the following form contains a standard TLabel that is shown normally and a custom TMyLabel that is shown as a yellow box.
This lets you move and resize the 3rd party controls even the editors do not fully render them.
Soluling can localize all FireMonkey applications; even Soluling does not have an editor for FireMonkey.