![]() ![]() Use case: works perfectly for the projects where the same words might have various meanings depending on the context. Each duplicate will require a separate translation. When this option is selected, all the duplicated strings will be visible to translators. Strict duplicates detection – when comparing strings, Crowdin Enterprise considers both string identifiers (keys) and source texts. Regular duplicates detection – when comparing strings, Crowdin Enterprise considers only source texts. Hide (strict detection) – all duplicates will share the same translation. ![]() Hide (regular detection) – all duplicates will share the same translation.Show within a version branch (strict detection) – duplicates will be hidden only between version branches.Show within a version branch (regular detection) – duplicates will be hidden only between version branches.Show – translators will translate each instance separately.There are six main options to work with duplicated strings in Crowdin Enterprise: All other strings that are identical to the master string but were uploaded or created later are considered duplicated strings. Each unique source string that was first uploaded or added (for CSV and other formats that support string editing) in Crowdin Enterprise is considered the master string. Source strings are uploaded to the system in localization files. In Crowdin Enterprise, the localization process is based on translating the source strings to the defined target languages. It works as a ‘Select all’ option for fields in a section.Configure settings for duplicated strings to achieve the highest efficiency of the localization process and to save costs. Select all fields in this section: When you select this, all fields available in that section of a record are selected so you don’t have to manually select the fields in that section. This is particularly useful when there’s data in multiple fields and you only want to look at data that’s different in the two records. View fields with conflicting data: When you select this, only the fields that have conflicting data are shown so you can quickly select the fields from which you want to retain data. If both primary and secondary records have data in the same fields, the fields of primary record are selected. Merge records by choosing fields with data: When you select this, all the fields that have data are selected regardless of whether the data is in the primary record or secondary record. Use the following options to select the fields for which the data must be retained, and select OK: All notes, activities, and details associated with the secondary record are linked to the primary record. When you do that, data from the selected fields of the secondary record is copied over to the primary record and kept. You have an option to choose the fields from the secondary record, too. This means that the data in these selected fields will be retained. When you select a primary record, by default, all the fields of the primary records are selected. Data from the secondary record is copied over to the primary record. The primary record is kept, and the secondary record is deactivated. If a duplicate is detected when a new record is being saved, then the new record is always considered as the secondary record. The option to select a primary record is available when both records are existing in the system. ![]()
0 Comments
Leave a Reply. |