![\"What's](\"https:\/\/www.textform.com\/tf2019\/wp-content\/uploads\/2016\/05\/slls.png\")
<\/a><\/p>\nThis is what the result of scoping may look like in the translation statistics.<\/em><\/p>\n In the SAP system, translation volumes are measured in so-called “SAP lines\u201d, which can range from 1 to 255 characters in length, from an \u201cOK\u201d button to a full error message. When translating from German or English, you can expect an average SAP translation line to contain 3,5 to 4,5 words. An experienced SAP translator can process up to 500 SAP lines per full working day, on average, depending on how difficult to translate the source texts are, and of course, how well they are written.<\/p>\n There are three types of texts that can be relevant for translation, short texts, long texts, and forms. Each of those is processed by the translator using a different built-in text editor. Short texts are texts that appear on the user interface, such as text elements, button texts, or table entries. Long texts are used in F1 help texts, for example. And there are also different types of\u00a0forms, such as Smartforms and SAPscript forms, the latter of which come with their own editor.<\/p>\n For short texts, the metric of \u201e3,5 to 4,5 words per SAP line\u201c is fairly accurate, and since short texts are the most common text type by far, this metric will give you a good idea of how many words need to be translated. Things are more tricky with long texts and forms, however \u2013 for those text types, it is not strictly accurate to talk about a number of lines, since the number SE63 give here is more of a \u201efootprint\u201c than an actual line count.<\/p>\n With long texts and Smartforms, lines are generally much longer than 4-5 words, since these are full sentences, but on the other hand, tags such as <b><\/b><\/em> are counted towards a line, and both headings and empty lines count as full lines as well. With SAPscript forms, things are even more complicated, which starts with the fact that the names of formatting elements such as \u201eItalic\u201c are also translated.<\/p>\n But looking at translator throughput on average over many years of SAP translation projects, the \u201eup to 500 lines per full working day\u201c metric is generally fairly accurate on average, be it for short texts, long texts or forms.<\/p>\n There are exceptions, however – a few text types that come up in SAP translation such as SAP Forms by Adobe that cannot be measured in SAP lines, since SE63 displays them as having one single line in the worklist, even though they actually contain a lot more text. The form in the screenhot below contains 543 lines of texts (this number varies by how you choose to display the text), but in SE63\u2018s worklist, it is displayed as a single line.<\/p>\nThe\u00a0SAP Translation Line<\/h3>\n
<\/a>
\nThis dialog box contains texts ranging from two characters in length (\u201cNo\u201d) to\u00a0a text with 43 characters.<\/em><\/p>\nDifferent Text Types<\/h3>\n
<\/a>
\nThe explanation text in the F1 help box is a long text, while the rest of the texts visible on this screen are short texts.<\/em><\/p>\nHow Accurate Are Our Estimates?<\/h3>\n
Exceptions to Prove the Rule<\/h3>\n