Soluling home   Document home

General

General

Use this sheet to edit the general settings of the project.

Project ID

Shows the project ID. Click Regenerate to assign a new ID.

Project file structure

Specifies the structure of the project file.

Value Description
Store everything into a single .ntp file All project data is written into a single project file.
Store large sources into .nts files The project is split into several files. Large sources (more than 10 000 rows) are written into project source files. Small sources are written in the project file.
Store all sources into .nts files As above but each source is written into the project source file. Project file contains only project settings and references to project source files.

The default value is Store everything into a single .ntp file. This single file structure is most convenient because all project data (original items and translations) are stored in a single file. However, if your file gets large, a single file is not ideal for Git because Git always stores the whole file not only the difference from the previous version. If you use Git and your Soluling project file(s) is large, and you want to optimize the Git repository size by selecting a multi-file structure (i.e., second or third option in the above table).

Use indenting of XML in the project file

If checked, the Soluling project file uses indenting for the XML elements. This makes reading the file easier for humans but causes the file size to increase about 15%. Uncheck this to disable indenting and to make files smaller.

Component rules target

Specifies where the built-in component rules that are in use are saved.

Value Description
Project Into a project where they are common to all sources in the project
Source Into a source where they are source dependent.

Composite format string render mode

Specifies how the placeholders of composite format strings are rendered in the grid.

Value Description Example
Compact Soluling renders composite format strings in a universal, platform-independent format. Each placeholder is shown as a yellow box with the placeholder number. Compact placeholder
Extended As above, but in addition to the placeholder number, the placeholders show the format-specific items. Extended placeholder
Original Soluling renders the placeholders in the original format in a yellow box. The format depends on the platform of the source file. Original placeholder
Plain text Soluling renders composite format strings as plain text and handles the patterns as plain strings without checking the placeholders. Plain placeholder

Note! The first three options turn on placeholder checking. It helps you keep the same number and type of placeholders in the translations.

Note! The Soluling project file stores the strings in the original (platform-specific) format. The above settings define only how the patterns are rendered.

When Soluling creates a new project, it uses the Original placeholder method by default. You can change the default on the Options | General sheet.

Remove automatically those unused rows that have no translations

Specifies if Soluling removes unused rows that have no translations after each scan. Possible values are:

Value Description
Yes Those unused rows that have no translations are automatically removed after each scan.
Yes and write log As above but Soluling writes into a log the context of each row it removed.
No No rows are automatically removed.

If unused row has at least one translation, it is not automatically removed even above setting is set to Yes. To remove those unused items, click Home | Clear statuses | Remove Unused Items ribbon button.

Alternative original language

Sets the alternative original language.

History

History shows the dates when the project was created (Created) and last modified (Modified), and the version number of Soluling that was used to edit it (Version).