Disclaimer: The content mentioned herein is for informational purposes only, and represents Saudisoft's sole opinion/experience. It should not be relied upon as a substitute or replacement for SAP formal documentation/information.
Welcome to the world of SAP software translation and localization. Before you can open up the gate to this massive world, our SAP software translation and localization team at Saudisoft would like to make you aware of all the basic information that you will need to go through this world with ease and comfort. We recommend you to keep up with us in the coming blog series on SAP technical and linguistic environments, where you will have an overview of SAP software translation and localization tools, SAP software translation style guide, and some tips on how to proceed with translating and maintaining SAP-specific terminology.
Let us start with what SAP stands for as you may have already forgotten; SAP stands for Systems, Applications and Products in data processing, and of course it is a global multinational company that develops enterprise software to manage customer relations and facilitate business processes. For more information on SAP, please refer to Search SAP.
As an Arabic translation and localization services partner to SAP, Saudisoft provides SAP with a broad range of language services. This range of language services is primarily made up of: Translation, Testing and Desktop Publishing (DTP).
The most important service that we are going to highlight in the coming blogs is definitely translation, as it is the main service that Saudisoft provides to SAP. Before handling various SAP materials, the first question that may come to the mind of any SAP beginner translator is: Why SAP software translation is different?
First, let us start by defining the translation unit. In SAP software translation world, the most common unit is Lines not Words; which of course has different productivity matrix.
Second, the source type is not defined by the file format; e.g., RTF, doc, …etc. It is rather defined by the type of the lines (short/long). Short lines are mainly in the user interface (UI) content of SAP software in general (forms/dialogs, …etc.) and systems in particular, while you can encounter the long texts mainly in the SAP system-related content, such as end-user documentation, online help and business blueprints.
Third, terminology. Just like any software localization, translating SAP-specific terminology is of ultimate importance. Yet, the process/tools that SAP provides help translators find definitions, notes, descriptions, and instructions to be able to deliver a quality translation from the initial phase.
Thus, you have come now to the fact that in order to translate SAP software, you are going to translate short lines, long lines, and terminology. You can consider that as the most significant information that you, as an SAP beginner translator, need to know for now in this regard.
Let's come now to the second question that may be raised by an SAP beginner translator again, which is: What software and tools shall I use in translating SAP-related content? The answer of this question is another focal point in our blog series that we provide to you to better facilitate your journey with SAP environment. SAP has been developing all the essential interactive translation software, tools and technologies that you can utilize to handle any SAP content effectively and efficiently. For example, the short text editor for translating short lines, and the long text editor for translating long lines. For further interesting information in this concern, we would like to extend an invitation to you to follow us in the next blog titled "SAP Software Translation: An Overview of SAP Translation Tools" for some detailed answer of this question.
If you want to get a broader overview of SAP translation community along with this blog series, please visit SAP Language Services