The UI Text Space Calculator

Abbreviated texts such as COAr and PerNo are nowhere near as user-friendly or intuitive as full texts such as Controlling Area and Personnel Number. They therefore have a negative impact on user satisfaction.

Truncated texts cause similar problems.

For example, Данные производства is Russian for Production Data. If the last four characters of this Russian translation are simply not displayed on the user interface, user satisfaction suffers as a result even if the user can guess what Данные производ is supposed to mean.

Some abbreviations are so unclear that they cause confusion, and may even lead to user errors.

For example, CC could stand for any of the following:

Abbreviations and truncated texts considerably increase the amount of time that you need for the pseudo-translation phase of the development project. By using the UI text space calculator to avoid such texts on translated interfaces, you help ensure that pseudo-translation finds far fewer bugs for you to fix during the development cycle that would otherwise cause problems, and significantly increase costs, during the subsequent translation cycle.

Abbreviations often lead to requests for you to modify and re-transport objects so that translators have enough space to enter full translations. Finding, modifying, re-transporting, and re-translating objects is far more time-consuming and expensive than ensuring from the outset that translators have enough space to enter full translations.

Abbreviations have a detrimental effect on the quality of any translation memory that you decide to use, such as the proposal pool for short texts translated in the short text editor. This can cause quality problems and longer turnaround times.

You can use the UI text space calculator for all programming languages and development environments.

The recommendations in the UI text space calculator are merely a guide. Experience shows that they prevent text space problems for approximately 95% of SAP texts. Nevertheless, even if you follow every recommendation all of the time, it does not necessarily mean that every translator into every target language will always have enough space to write out their translations in full.

Even if a text string length is unrestricted and every translation is perfect, this does not automatically mean that every translation will fit into the UIs and look great in every language. You can refer to the values in the Size Unit em* column to ensure that you have reserved enough space for all translations on your UIs.

It's okay to ignore outliers, if necessary. For example, your English text has a length of 5, so you extend the text string length to 14 in accordance with the UI text space calculator. This provides enough space for every translation into every language except Hungarian, which needs 22 characters. If extending the text string length to 22 characters has a detrimental effect on the quality of the English UI, then it's okay not to extend the text string length even if the quality of the Hungarian UI suffers as a result.