diff --git a/app/assets/javascripts/app/views/import/otrs.jst.eco b/app/assets/javascripts/app/views/import/otrs.jst.eco index f93f77737..c14f05cf2 100644 --- a/app/assets/javascripts/app/views/import/otrs.jst.eco +++ b/app/assets/javascripts/app/views/import/otrs.jst.eco @@ -2,14 +2,14 @@ <%- @Icon('full-logo', 'wizard-logo') %>
-

<%- @T('Download OTRS Migration Plugin') %>

+

<%- @T('Download %s Migration Plugin', 'OTRS') %>

<%- @T('Go Back') %> @@ -17,13 +17,13 @@
-

<%- @T('Link OTRS') %>

+

<%- @T('Link %s', 'OTRS') %>

<%- @T('Enter the link provided by the plugin at the end of the installation to link the two systems') %>:

- +
@@ -37,12 +37,12 @@
<%- @T('Go Back') %> -
<%- @T('Migrate OTRS Data') %>
+
<%- @T('Migrate %s Data', 'OTRS') %>
-

<%- @T('OTRS Migration') %>

+

<%- @T('%s Migration', 'OTRS') %>

@@ -85,7 +85,7 @@
@@ -93,7 +93,7 @@

<%- @T('Notice') %>

<%- @T('We detected OTRS BPM processes which can\'t get imported into Zammad, since we currently don\'t support these kind of workflows.') %>

-

<%- @T('We found many dynamic fields. We use a different approach towards ticket attributes. Zammad uses also tags in addition to custom fields to classify tickets. This difference may conflict with your current use of dynamic fields in OTRS.') %>

+

<%- @T('We found a lot of dynamic fields which are not common in Zammad, as we follow a different approach to ticket attributes. Zammad uses also tags in addition to custom fields to classify tickets. This difference can create a new philosophy of your ticket attributes / tags compared to your current use of dynamic fields in OTRS.') %>