Soluling home   Document home

Visual Editors

When Soluling scan files 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 (plus an optional comment) to translate it correctly. You need more information. You need to see where the string comes from or where it is used. Therefore 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 does 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 in the editor. 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. Use the translation grid to edit strings, colors, fonts, etc.

Platforms

Each programming platform has its own set of user interface controls. This is why dialog/form editors of Soluling are platform-specific. There is an full editor for

• Delphi
• Windows Forms
• Visual C++

There is a preview editor for

• WPF
• HTML, XML, SVG, and source code.

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 Soluling's 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. 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.

Important

Don’t expect too much for the visual editors. The companies that developed the development tools (Microsoft, Embarcadero) have invested a huge amount of work for their visual editor. We cannot do the same. In addition, we have several editors to develop and maintain. So if your UI element does not show up correctly on the editor, it does not mean that Soluling cannot localize the item. Most likely Soluling has correctly scanned and extracted the items, even if the visual editor cannot show it correctly.