The Glossary is maintained in SAPterm. Glossary entries are definitions, or explanations, of existing terms in SAPterm. End users can use the glossary links in documentation to branch to existing glossary definitions.
For more information, see Terminology and Glossary in SAPterm (BC-DOC-TER).
At present, there are two different types of glossary links. You need to proceed differently when translating each type.
You need to translate an 'old-style' link like this: <DS.GLOS:Buchungskreis>Buchungskreis</>
The first text company_code is the actual link to SAPterm and the second text company code is the text that appears in the documentation.
Note the underscore (_) instead of a blank space between words in the link. Links only work if they are not separated by line breaks.
code>company code</> will not create a link because the link is spread across two separate lines. Using an underscore instead of a blank space keeps the words in a link together. The text that appears in the documentation, however, can be separated by line breaks and need not be identical to the link text. You could translate the link as <DS.GLOS:company_code>Company codes</> if the link starts a sentence and the text describes several company codes, for example.
The end user sees the glossary links as highlighted texts and will be able to access glossary entries by clicking this link.
The 'new-style' link uses a 32-character string called a GUID, which creates HTML links. For example:
The GUID is a unique number, which is not language-dependent and creates links to the correct text based on the logon language. You should translate the link as follows:
If the GUID is too long for the line, you need to insert another line and enter the entire glossary link in that line.
Old-style links still work. If, however, an old-style link is updated to a GUID in the source text, you should also update the link in your target text. Otherwise, treat the old-style links as before.