This topic covers the third method of translation content in STEP, manual translation. This topic will cover, in detail, how a user can translate content in the workbench by adding content directly into the attribute for the target language.
Manual translation is only appropriate when two criteria have been met:
If either of these criteria are not met, the structured translation process is likely to be a better option.
As an example of an instance where manual translation might be a good option, we'll say that Company Z sells t-shirts. All of their product information is translated and up to date. Marketing sends a directive that a word used in the product description for one t-shirt brand needs to be changed for the US and all other global markets. As this work is very limited in scope, manual translation can be a good (and potentially fast) method to approach this challenge. In this example, the user would access the product in question, visit each language for that product, and update the relevant description for each.
If you see this, follow step four (below), and select the desired source language. Your STEP system will remember this selection and display it as the source language in Translation Mode until it is changed or the STEP cache is cleared.
In this way, most translatable data can be added for all language dependent attributes in all languages. However, because each language dependent attribute must be amended for each language manually, manual translation is not recommended for any translation except those with a very limited amount of content to translate.
Note: When using manual translation to translate attributes on the System Setup tab, manual translation using the Translation mode view only allows you to translate the attribute names, not any of an attribute's description attributes. However, using Context view, users may manually translate an attribute's description attributes.
2017, Stibo Systems