Document home

File

Result File

Result file is a project specific result file that Soluling creates after each operation that might change the rows or translations (e.g. scan or import). Use the file to see what has been changed in the project file. File extension is .ntr. By default the file format is XML. However if you prefer JSON you can change the format to be JSON using the result file settings (Options | General | Result file).

Data that result file contains

Result file contains information about rows and translations statuses. In addition if contains list of changes that were made during the last scan, import or translate.

Value Description
rows Rows element contains statistical information about the row statuses and the changes made during the last scan.
translations Translations element contains statistical information about the translation statuses and the changes made during the last operation (e.g. import or translate).
imports Import element contains list of all translations that were imported during the last operation.

XML

The default format of a result file is XML. Here is a sample XML result file:

<?xml version="1.0" encoding="utf-8"?>
<result created="20181223T191140Z">
<rows>
<statuses new="0" inuse="54" changed="0" contextchanged="0" unused="0"/>
<lastscan new="0" inuse="0" changed="0" contextchanged="0" unused="0"/>
</rows>
<translations>
<statuses nottranslated="51" bestguess="0" autotranslated="0" translated="3" forreview="0" complete="0"/>
<lastimport clear="0" import="2" overwrite="1">
<language id="fi" clear="0" import="2" overwrite="1"/>
</lastimport>
</translations> <imports>
<language>
<import context="Project1.exe.RCData.TFORM1.Label1.Caption" original="&amp;Filename:" value="&amp;Tiedosto:"/>
<import context="Project1.exe.RCData.TFORM1.Button1.Caption" original="&amp;Browse..." value="&amp;Selaa..." previous="&amp;Selaa"/>
</language>
</imports>
</result>

JSON

Soluling stores all internal data into XML file. The only exception is that you can configure Soluling to use JSON in result file instead of XML. result file is ment to uses in the build automation and it might be that JSON suits you process better than XML. Here is a sample JSON result file.

{
"created": "2018-12-24T03:28:04Z",
"rows":
{
"statuses":
{
"new": 0,
"inuse": 54,
"changed": 0,
"contextchanged": 0,
"unused": 0
},
"lastscan":
{
"new": 0,
"inuse": 0,
"changed": 0,
"contextchanged": 0,
"unused": 0
}
},
"translations":
{
"statuses":
{
"nottranslated": 51,
"bestguess": 0,
"autotranslated": 0,
"translated": 3,
"forreview": 0,
"complete": 0
},
"lastimport":
{
"clear": 0,
"import": 2,
"overwrite": 1,
"languages": [
{
"id": "fi",
"clear": 0,
"import": 2,
"overwrite": 1
}
]
}
},
"imports":
{
"fi": [
{
"context": "Project1.exe.RCData.TFORM1.Label1.Caption",
"original": "&Filename:",
"value": "&Tiedosto:"
},
{
"context": "Project1.exe.RCData.TFORM1.Button1.Caption",
"original": "&Browse...",
"value": "&Selaa...",
"previous": "&Selaa"
}
]
}
}

SoluResult.exe

Soluling directory contains a command line application, SoluResult.exe. You can use it in your build process to easily read row and translation properties from an XML or JSON result file.

 

Related files are project file.