To split interface texts into separate sentences, which are imported from XML file as they are stored like that in the configuration, you need to use the Dictionary merging data processor. You can open it by clicking the button with the Translate by dictionary, dictionary merging tooltip or in Translation section click Tools and then Dictionary merging.
In both Dictionary to be translated and By dictionary fields there should be the dictionary where you imported interface texts.
The only check box that should be selected is Split 1C configuration interfaces into sentences.
Now click Refresh. And you will see the list of found dictionary entries, having more than one sentence in original text. They will be split into sentences, and if in translation there is the same number of sentences, check boxes on the left will be selected. In that case we guess that sentences in original text match one by one the sentences in the translation. If the number of sentences do not match, you attention is more likely required and check boxes are not selected.
You need to review the result, select rows that you prefer to add to the dictionary. You can also edit suggested translations by clicking Edit translation suggestion button on the command bar of the table.
When finished, click the Write selected translations button and you will have the result saved in the dictionary that you selected in the Dictionary to be translated field.
In this step: "When finished, click the Write selected translations button and you will have the result saved in the dictionary that you selected in the Dictionary to be translated field." must I select other (new) Dictionary with ONLY Russian sentences of interface?
To use the resulting dictionary for translation of interfaces, you need all dictionary entries that are used in texts as interfaces to be in that dictionary; and that dictionary should be used as a primary dictionary in the project of the 1C application interface translation type.
So as for me, you don't need to place them into another dictionary. Simply use this dictionary as a primary or if you already have a primary dictionary, merge them together using the same data processor, but selecting the Add new items to the dictionary from the source dictionary option.
I have imported interfaces SB 1.5, which contains Russian and English lexemes. For example: Расходная накладная -> Customer invoice. I have an xml-file with interface texts UNF 1.6, which has only Russian language. How can I use the dictionary SB 1.5, to translate user interface of the UNF 1.6? I can not understand order, sorry.
Dmytro, on previous steps you have prepared the primary dictionary to start the translation.
Now you need to:
Create a project with the 1C application interface translation type.
Set that dictionary as a primary dictionary in that project.
Export the entire configuration files (Flat list mode).
Import those files into original texts of project texts.
Export translations of texts.
Load configuration from files.
Check syntax and test the application.
More details on the translation procedure you can find in the 1C:Translator user guide. Section Translating application source code. In case of interface translations there will be only one difference: in dictionary entries after indexing there will be only interface texts, and no sources will be translated.
I understand in a whole. I can not understand how to translate lexemes of UNF dictionary by available (and already translated) Small Business lexemes. Can I use dictionary of one project to translate dictionary of another project (merge)?
Yes, Dmytro, you are correct, you need to use the Translate full matches option of the Dictionary merging tool. You can also try using other options to fill as much translations as possible. Until you write them there will be no changes made in the target dictionary. It is better to select one option at a time. Except for Overwrite already translated dictionary entries, this option in general you better don't use.
The other possible option is simply selecting the Small business dictionary as a primary in your UNF translation project. Projects can share folders between each other.