User Interface Translation using Alchemy Catalyst · Since a project is split into multiple drops, the content you are translating in one drop will re-occur in subsequent drops, usually

PUBLIC

2017-08-01

User Interface Translation using Alchemy Catalyst

Content

1 INTRODUCTION AND EXPECTATIONS ........................................................................................................................ 4 1.1 Translation Coverage.............................................................................................................................................................. 4 1.2 Subject Matter Coverage ....................................................................................................................................................... 4 1.3 SLS Expectations ..................................................................................................................................................................... 6 1.4 Translation Management Model .......................................................................................................................................... 6 1.5 Translation Environment Setup ........................................................................................................................................... 7 1.6 Translation Details ................................................................................................................................................................... 8

2 WORKFLOW ............................................................................................................................................................................. 9 2.1 Project Notification.................................................................................................................................................................. 9 2.2 Terminology Translation ........................................................................................................................................................ 9 2.3 Before Translation .................................................................................................................................................................. 11 2.4 During Translation ..................................................................................................................................................................12 2.5 Translation Delivery ...............................................................................................................................................................15 2.6 Correction Implementation ................................................................................................................................................. 16 2.7 Context Review Setup ...........................................................................................................................................................17 2.8 Context Review Steps ........................................................................................................................................................... 18 2.9 Invoicing ................................................................................................................................................................................... 19

Invoicing for Terminology Projects............................................................................................................................. 19 Invoicing for Context Review ........................................................................................................................................20

3 TOOLS ...................................................................................................................................................................................... 21 3.1 ALCHEMY CATALYST ...........................................................................................................................................................21

Catalyst Introduction.......................................................................................................................................................21 Installing Alchemy Catalyst .......................................................................................................................................... 22 Checking the Word Count ............................................................................................................................................. 23 Searching and Filtering .................................................................................................................................................. 24 Finding Context Information ........................................................................................................................................ 27 Removing Incorrect Carriage Returns .......................................................................................................................30 Validating Hotkeys .......................................................................................................................................................... 31 Maximum String Length ................................................................................................................................................ 33 Catalyst Status................................................................................................................................................................. 33 What's New in Catalyst 11 .............................................................................................................................................. 34

3.2 SANITY CHECK ...................................................................................................................................................................... 35 Sanity Check Overview .................................................................................................................................................. 35 Setting up your Machine................................................................................................................................................ 36 Executing the Script ....................................................................................................................................................... 37

P U B L I C 2 © 2016 SAP SE or an SAP affiliate company. All rights reserved.

User Interface Translation using Alchemy Catalyst Content

Error Logs ......................................................................................................................................................................... 38 3.3 SAPterm .................................................................................................................................................................................. 40

Worklist Search ............................................................................................................................................................... 40 Advanced Search ............................................................................................................................................................. 41 Translatability of Brand Voice Terms ........................................................................................................................ 45

3.4 QUERY TRACKER ...................................................................................................................................................................47 Introduction.......................................................................................................................................................................47 General Instructions and Expectations..................................................................................................................... 49 Setting up the Worklist filter ........................................................................................................................................ 50 Before Submitting Queries in Catalyst ...................................................................................................................... 51 Submitting Queries in Catalyst ....................................................................................................................................53 Tracking and Implementing Queries in Catalyst .................................................................................................... 54 Tracking and Implementing Queries in STM Rolling ............................................................................................. 56 SEARCHING QUERY TRACKER ................................................................................................................................... 57

3.5 OTHER TOOLS ....................................................................................................................................................................... 66 Searching Glossary Text Files ..................................................................................................................................... 66 Displaying Test Movies.................................................................................................................................................. 66 Taking Screenshots ........................................................................................................................................................67

4 REFERENCE MATERIALS ................................................................................................................................................. 68 4.1 Overview .................................................................................................................................................................................. 68 4.2 SAPterm .................................................................................................................................................................................. 69 4.3 Brand Voice............................................................................................................................................................................. 70 4.4 Exported User Interface Strings (UI Glossaries) ........................................................................................................... 71

Glossary Structure .......................................................................................................................................................... 73 4.5 Copyright Statements ..........................................................................................................................................................74 4.6 Product Documentation ....................................................................................................................................................... 75 4.7 Tips and Best Practises ........................................................................................................................................................ 77

5 ISSUES AND SUPPORT .....................................................................................................................................................78 5.1 Questions? ...............................................................................................................................................................................78 5.2 Glossary ....................................................................................................................................................................................78

User Interface Translation using Alchemy Catalyst Content

P U B L I C © 2016 SAP SE or an SAP affiliate company. All rights reserved. 3

P U B L I C © 2016 SAP SE or an SAP affiliate company. All rights reserved.

User Interface Translation using Alchemy Catalyst INTRODUCTION AND EXPECTATIONS 4

1 INTRODUCTION AND EXPECTATIONS 1.1 Translation Coverage

Introduction

SLS manages its product translation using different translation tools depending on the source systems and content format. This training material PDF file covers the translations of user interface strings in non-ABAP systems, its related documentation in DITA format and applicable terminology stored in SAPterm. The products covered are mainly from the SAP BusinessObjects product portfolio, see Subject Matter Coverage [page 4].

The translation process for the non-ABAP based products for the SAP BusinessObjects portfolio consists of the following procedures:

● terminology translation (SAPterm) ● translation of the user interface (Alchemy Catalyst/SE63) ● translation of documentation (Trados Studio/ORBITT) - some languages only ● translation of release notes (Trados Studio/ORBITT) - some languages only ● review of the translation user interface strings in context (context review) ● translation or taking of screenshots

The above procedures may happen in parallel. Issues found in any of the above will be fixed during the particular procedure as instructed by your SLS Project Manager.

1.2 Subject Matter Coverage

The SLS Support Portal Product Translation REFERENCE MATERIALS Product Information Pages ) contains summary pages about the majority of the products that are being translated by SLS. These summary pages contain a brief description of the product and links to product videos and tutorials. The instructions in this training material refer to the SAP BusinessObjects product portfolio within the SAP product portfolio which largely covers three product areas: BI (Analytics), EPM, and EIM.

Before you start any translation work, familiarize yourself with the product page information below.

Note The documentation is translated into a smaller language set than the user interface strings.

https://translation.sap.com/index.html

User Interface Translation using Alchemy Catalyst INTRODUCTION AND EXPECTATIONS


BI - Business Intelligence / Analytics

The products included in the BI area are used to simplify data manipulation, allowing users to access, navigate, analyze, format, and share information across a corporate environment. They include the following products:

● SAP BusinessObjects Cloud ● SAP Lumira ● SAP BusinessObjects Design Studio ● SAP BusinessObjects Analysis, edition for OLAP ● SAP BusinessObjects Mobile ● SAP BusinessObjects Predictive Analysis ● SAP BusinessObjects Business Intelligence platform ● SAP BusinessObjects Explorer ● SAP BusinessObjects Dashboards ● SAP Crystal Reports ● SAP BusinessObjects Web Intelligence

EIM - Enterprise Information Management

The products included in the EIM area help businesses deliver integrated, accurate, and timely data across the enterprise. They include the following products:

● SAP BusinessObjects Data Federator ● SAP BusinessObjects Data Integrator ● SAP BusinessObjects Data Quality Management ● SAP BusinessObjects Text Analysis ● SAP BusinessObjects Information Steward ● SAP BusinessObjects Data Services

EPM - Enterprise Performance Management

The products included in the EPM area help businesses gain real-time visibility into performance metrics, quickly adapt to changing business conditions, and drive decision making across the organization. They include the following products:

● SAP BusinessObjects Financial Information Management ● SAP BusinessObjects Profitability and Cost Management ● SAP BusinessObjects Intercompany ● SAP BusinessObjects Financial Consolidation ● SAP BusinessObjects Notes Management ● SAP BusinessObjects Planning and Consolidation ● SAP BusinessObjects Disclosure Management



1.3 SLS Expectations

We expect that you meet or exceed the quality standards listed below in all deliveries based on the agreed upon timelines, scope, and content type. We use the following criteria to rate the quality of your service.

Deadline compliance and delivery completeness: the supplier meets all agreed deadlines, or notifies the PM in advance of delays or extensions required.

Quality of deliverables: the supplier possesses the appropriate linguistic expertise that is required for the specific project.

Communication: the supplier communicates all project-relevant details in a timely manner.

Scalability/Responsiveness: the supplier demonstrates flexibility to accommodate changes and shows the ability to create open and fair estimates to justify additional costs incurred during translation.

Technical expertise: the supplier possesses the appropriate technical expertise to operate the translation tools/ environments and for processing translation files.

The criteria for determining the quality of the deliverables are the following:

1. Translated text is an accurate representation of the original source text, free of omissions, additions or misinterpretations. The translation must be both readable and accurate.

2. Translated text must be fully spell checked regardless of file type. 3. Translated text is free of grammatical, semantic or punctuation errors. 4. Translated text is free of potentially offensive statements or slang. 5. Style is consistent with the SAP style guides available on the SLS Support Portal. 6. All terminology is consistent with SAPterm and any other terminology references provided. 7. All query answers received from SAP have to be correctly implemented in the translated text. 8. Any specific linguistic or project instruction provided have been applied in the translated text. 9. Translations are suitable for the country standards of the target language. 10. Translation is suitable for the target audience specified.

If the above quality standards are not met (for example if files are missing, target text is found to be untranslated, or if queries were not implemented), your SLS PM will request you to redeliver the files. The turnaround time for making any fixes and/or redelivering files is 24 hours. In case of quality concerns, you will receive a list with the issues and corrections (if applicable). You are expected to review and implement these corrections and redeliver your files together with any comments to the Excel spreadsheet within 24-72 hours.

1.4 Translation Management Model Rolling Drop Translation Model

The non-ABAP product translation that is handled in Alchemy Catalyst and Trados Studio is being managed using the so-called rolling drop model. In a rolling translation model, multiple projects are divided into "drops" whereby each drop consists of multiple projects. The drops are sent to you in regular intervals on a predefined day and are expected back on a predefined day.

User Interface Translation using Alchemy Catalyst INTRODUCTION AND EXPECTATIONS


The actual word count of a drop will be provided to you a few days in advance. Drops are based on an agreed upon maximum word count, however, there is no guarantee that each drop will hit this maximum word count, some drops may only have a few words. If drops get cancelled, you will be notified one week in advance.

Since a project is split into multiple drops, the content you are translating in one drop will re-occur in subsequent drops, usually with more content added to it. This is important information to keep in mind when you schedule for implementations of corrections, queries, or global term changes. Preferably, implement these changes in the two last drops before a project is finalized. The last drop also is called the final drop or the RTM drop. For the final drop, always reserve some time for this implementation work.

Off-Cycle Translation Model

Occasionally, exceptions to the rolling translation schedule are required, for example, when the word count is very large (in new projects), a new language is added to our language set, or linguistic or other corrections need implementation that do not fit into the regular schedule (such as global term changes, orthographic reform). These exceptions are scheduled separately in so-called "off-cycle drops". You will receive specific information in advance by your SLS Project Manager.

Exceptions

The management of non-ABAP UI string translation in SE63 (short and long texts) and DITA-based documentation translation in ORBITT is NOT using the rolling drop model above. Consult Project Page for each project provided by your SLS PM.

1.5 Translation Environment Setup

Before you begin any translation work, go through the following checklist, install the required tools, configure them according to our requirements, attend training sessions if unfamiliar with the translation tool, make sure that you can access all other required tools and familiarize yourself with our reference material framework.

● Install Alchemy Catalyst, see Catalyst Introduction [page 21].

Note Make sure that you have enough resources to accommodate both off-cycle work and regular rolling drop work. The off-cycle translation work is considered in addition to, not instead of, the regular Rolling Translation. Both needs to be delivered on schedule and with the expected quality.

Note The instructions assume that you are experienced using this tool. If not, go to the Alchemy website and attend the recorded session.



● Set up your machine to enable the execution of the sanity check, see Setting up your Machine [page 36]. ● Ensure that you can access our query management tool Query Tracker, Introduction [page 47]. Set up your

worklist filters, see Setting up the Worklist filter [page 50]. ● Ensure that you can access our terminology management tool SAPterm, see SAPterm [page 69]. ● Install a tool for searching the exported user interface strings, see Searching Glossary Text Files [page 66]

(optional).

1.6 Translation Details Drop Details

The schedule for the user interface translation drops can be found on the SLS Support Portal Product Translation REFERENCE MATERIALS Rolling Drop Schedules UI Drops 201x ). You will receive a translation drop package every second Wednesday. A drop may contain files of several projects and up to 20,000 new words combined. The delivery day is the following Tuesday at 9 AM (PST).

Process Steps

The user interface translation process consists of the following steps.

1. It is important to familiarize yourself with the product. You will be provided with product information and its documentation in Project Notification [page 9] and .

2. The core product terminology should have been or is being translated in parallel. Make sure you know the component name in SAPterm that relates to the product you are translating.

3. The UI strings that you are translating are added to the UI glossaries on a weekly basis which are available for lookup, see Exported User Interface Strings (UI Glossaries) [page 71].

4. Close to the final drop of a project, you will get the opportunity to review your translated strings in context. The purpose of this context review is to allow you to test the accuracy of your UI translations from an end- user's perspective since translated strings in a TTK file may not be appropriate once displayed in a product (in context). See Context Review Setup [page 17].

5. Ensure that all open questions and queries, all global changes and corrections are implemented in the final drop.


User Interface Translation using Alchemy Catalyst WORKFLOW


2 WORKFLOW 2.1 Project Notification

Once a project is ready for translation (and it is smaller than 10,000 words), you will typically receive an email informing you that a new translation project is available for you in TED. Log on to TED and locate the project name indicated in the kick-off email. The project will be assigned to you at the Translation step and you can access the project instructions. Ensure that you read the project instructions carefully as they change from project to project. The files are available on the SLS Transfer Server inside your specific supplier directory. Each project folder is unique based on the project name and contains the Trados Studio project files.

\\dwdf204\SLStransfer\<region>\<lang>\<supplier name>\CorpContent\<projectname> (EMEA or AMERICAS)

\\sgpss073.sin.sap.corp\SLStransfer\<region>\<lang>\<supplier name>\local_data

\CorpContent\<projectname> (APA)

For projects larger than 10,000 words, your SLS PM or your respective BPM Resource Manager will inform you via email before project start in order to give you time for resource planning. The e-mail will contain the project name, a description of the content, the estimated volume, the kick-off and delivery dates, the file types, and the cost model and PO names. Review these details carefully and get back to your SLS PM in case of questions or concerns. Note that any project kick-off dates communicated to you are estimates and depend on the source files being finalized, along with the approval of our clients to begin work. If the kick-off dates are delayed, then the deadlines will be adapted accordingly.

Once you have received the kick-off email, and you have reviewed the project instructions, files, word count statistics, and cost model applied, please confirm acceptance of the deadline and receipt of the files within TED.

2.2 Terminology Translation

The majority of the projects start out with translating the core terminology in SAPterm. The translation of terminology in SAPterm is being managed using the rolling model. Every 2 weeks you receive an e-mail reminder and you have 4 days to translate the new terminology that has been added during the last days to any of the current open projects.

Often, the number of translatable terms may be small (less than 10), and in some cases there may be none at all. This is normal, but if you have any concerns, please don't hesitate to contact your SLS Project Manager. If you see any further anomalies, like the exact same terms appearing two drops in a row, please let your SLS PM know before you begin translating.

Sometimes, the number of new terms added to SAPterm is so large that SLS kicks off a special "off-cycle terminology drop" to give you more time to translate and research the terms of a particular project.

For Simplified Chinese and Japanese, all terminology translation work is handled internally.


User Interface Translation using Alchemy Catalyst WORKFLOW 10

Finding Terms to Work On

In order to cover all terms you need to work on - that is, translate/review/release - you must execute 2 different searches in SAPterm each time: the Worklist Search [page 40] and the Advanced Search [page 41].

In the Worklist Search, enter the following product keys:

● 343 - BI (Business Intelligence/Analytics) components ● 344 - EIM (Enterprise Information Management) components ● 345 - EPM (Enterprise Performance Management) components ● 398 - SAP BusinessObjects Brand Voice components

During Translation

When translating terms make sure that you fully understand the term, check all context information of a term and ensure consistency with existing translated product content.

1. To ensure translation consistency with existing translated content, search for the terms in the SAP BusinessObjects UI (User Interface) Glossaries on the SLS Transfer Server, see Exported User Interface Strings (UI Glossaries) [page 71].

2. To check the context information of a term in SAPterm, see Checking Context information of a term [page 70].

3. Additional context information can be found in the published product documentation, see the SAP Help Portal or the SLS Transfer server. For more information, see Product Documentation [page 75].

4. When translating and releasing product names, make sure you check the translatability status, see Translatability of Brand Voice Terms [page 45].

Submitting and Implementing Queries

The translation type for the rolling terminology translation in Query Tracker is STM Rolling. If you have questions about a particular term, please submit a Source query in Query Tracker. See Introduction [page 47] and the and Tracking and Implementing Queries in STM Rolling [page 56] sections.

Translation Delivery

To confirm completion of translation work, send an e-mail to your SLS PM in accordance with the deadlines set in the Rolling Terminology Schedule.

http://help.sap.com/



2.3 Before Translation

Before you start translating the project software strings, make sure that your work environment is set up and ready for translation. We recommend that you check the word count in Catalyst and compare it with the word count provided to you, see Checking the Word Count [page 23]. Verify that you can access Query Tracker and set up your worklist filter, see Setting up the Worklist filter [page 50]. Familiarize yourself with the reference materials available, see Overview [page 68], as well with the drop-specific instructions provided with the project files, see Finding Your Files [page 11].

Finding Your Files

When the files are ready for translation, your SLS PM will notify you through e-mail that the files are ready for pickup. Contained in this e-mail are important information regarding the current drop such as drop location and specific reference materials. Please confirm acceptance of the project. The files are placed onto the SLS Transfer Server inside your specific directory which is organized by drop number (e.g. uirdrop20120223).

\\dwdf204\SLStransfer\<region>\<language>\<supplier name>\SAPBusinessObjects\UI (EMEA or AMERICAS)

\\sgpss073.sin.sap.corp\SLStransfer\<region>\<language>\<supplier name>\Local_Data

\SAPBusinessObjects\UI (APA)

The folders inside a drop are structured in such a way that the files provided by SAP are placed under 1_From_SAP, whereas you should deliver you translated files into 2_To_SAP.

There are two subfolders under 1_From_SAP:

● Files: contains all UI files to work (Catalyst TTK, TXT, or Excel files) on are saved in this location, under a folder with the project name (e.g. Mira_SP).

● Project info: a file list for the sanity check script is saved under the Filelist folder. A folder called Instructions contains one or more documents with instructions for the drop, products and terminology. Ensure that you are familiar with the entire set of documents.

There is one folder under 2_To_SAP: ● Place the modified UI files in this location, under the correct folder with the project name.



Translation Instructions

Each drop contains instructions that are specific to the drop as well as instructions that are specific to a product (split in multiple drops). These instructions are placed into the Instructions folder. There are two types of instructions: instructions that are specific to a drop, and instructions that are specific to a product.

Instructions that are specific to the drop are labeled <drop number>_instructions. They contain the Query Tracker filter information to help you ensure the implementation of all queries for a particular drop. In addition, we provide release-specific and product-specific information for each project in a drop.

● Product Group: the group of products that the project belongs to. ● Product: which product the project belongs to. ● UI Glossaries: the name of the text file that contains the exported project strings. ● Release Type: indicates whether the project is released as a support pack, a major release, or a minor release. ● Can previously translated strings be changed (Yes/No): indicates whether or not you can implement

correction requests or query answers into previously translated strings. ● Full set of TTKs (Yes/No): indicates whether or not you have been provided with all TTKs of a particular

project.

Instructions that are specific to a product may apply to more than one project. That typically happens when you translate multiple releases of the same product, or if one product references another product.

Scope and Cost Report

The scope and cost report will be sent to your financial e-mail address on the day when the drop is ready for translation. The report contains the word count statistics for the project and the associated costs, additional services requested and the number of hours allotted, and the PO name on which this project can be invoiced against.

2.4 During Translation

While translating in Alchemy Catalyst keep the following tips and guidelines in mind. String Status in Catalyst

● Do not leverage (pretranslate) the TTK files unless explicitly instructed by the SLS PM.

● Do not sign off any strings. All newly translated or modified strings must be in For Review ) status when you deliver the files.

● Do not edit any strings in Signed Off ) status or Leveraged ) status unless you implement queries or are otherwise instructed to do so.



● When you find an 100% match in the Reference pane and apply it to the translation, an unwanted Leveraged

status will be introduced. Make sure to change it to"For Review". Leveraged status should be shown only in special cases when SLS does the leverage.

● Do not lock any strings ) and do not unlock any locked strings. Do not use any of the translated locked

strings as a reference since they may not have been reviewed yet.

For an overview of all string statuses, see String Status [page 34]. Asian languages

For all Asian languages, please ensure you use single byte square brackets where square brackets are used in the English source. e.g.

[ProductName] [PATCHDISPNAME][_WiseDialogSuffix]

If you need to add any square brackets to the translation, please follow the instruction in your language, see Linguistic Guidelines [page 68] for more information.

Placeholders

A source string may contain placeholders which are variables that stand for a word, a number or an entire string.

For example, in the sentence “The port with name: "{0}" does not exist.”, {0} is a placeholder.

● Ensure that your translated string contains the same amount of placeholders as the source string. ● There are 2 kinds of placeholders: "numbered" and "un-numbered" placeholders. The sequence of numbered

placeholders can be adjusted according to your language sentence structure. e.g. “{0} extension point can't get class {1} from plugin {2}.” The sequence of un-numbered placeholders cannot be changed, you must adapt the sentence structure (maybe add a colon), e.g. Connected as user %s to system %s in language %s.



● Only change the syntax of a string if you know what the placeholder stands for. The string "An error occurred

in the Job Server: {0}" should not be translated as "An error occurred in the Job Server {0}" since the placeholder can also contain an entire, multi-line error string.

Hotkeys

A hotkey is the keyboard shortcut that a user presses in order to execute a command. If the source string contains hotkeys, you must add a hotkey in the translated string following the conventions of your language. For some languages, there are specific instructions of how to handle hotkey translations, for more information see the SLS product style guides available on the SLS Support Portal (Product Translation Reference Materials Product Style Guides) . Ensure that you do not add duplicate hotkeys in the same menu or dialog box. Before delivering your files, run the hotkey validation checks as described in Validating Hotkeys [page 31].

Carriage Returns

Do not introduce extra carriage returns in your translation. Before delivering your files, run the carriage return validation check as described in Removing Incorrect Carriage Returns [page 30].

Keep consistency

Follow the instructions provided in the Translation Delivery [page 15] section to ensure your translations are as consistent as possible.

Working with Query Tracker

Submit your queries as early as possible. Ensure that all applicable queries are implemented. Check the filters in the project-specific instructions. For information on how to search and filter for strings in Catalyst, see Searching and Filtering [page 24].

Copyright Statements

You may come across copyright strings. Do not translate these strings yourself but use the official and legally approved translations found on the transfer server. In some cases, products contain copyright statements from previous years, in that case you need to make sure to use the corresponding translations from that particular year. If in doubt, submit a query. More information can be found in Copyright Statements [page 74].




2.5 Translation Delivery

When preparing files for your delivery, go through the following checklist: Quality Check

Ensure that your translation adheres to the SLS quality guidelines, see SLS Expectations [page 6] for more information.

Query implementation

Implement all your answered queries that show in the filters as instructed in the drop-specific instructions. Ensure that all applicable queries are correctly implemented in your translation, see Show me all my answered queries [page 64] and Tracking and Implementing Queries in Catalyst [page 54]. For information on how to search and filter for strings in Catalyst, see Searching and Filtering [page 24].

Validation checks in Catalyst

There are some quality checks available in Alchemy Catalyst. We recommend that you run the following checks which are being explained in further detail in the Catalyst section below.

● Ensure that all strings are translated and the Statistics pane in Catalyst does not show any strings in Untranslated status, see Catalyst Status [page 33].

● Remove incorrect carriage returns, see Removing Incorrect Carriage Returns [page 30]. ● Run the Hotkey validation checks, see Validating Hotkeys [page 31]. ● All applicable European languages should run the Catalyst spellcheckers, see the Catalyst Help file.

Term Q-Check

For new projects, a Term Q-Check will performed. We use the Term Q-Check to:

● Validate if the translation of each term in SAPterm is correct based on the product knowledge translators have gained through the translation of UI. Make any correction as needed.

● Validate if the translation of each term in the UI is consistent. Make any correction as needed.

If there is a Term Q-Check, you will be provided with detailed instructions in addition to your drop-specific instructions.



Sanity Check

The sanity check is a script that verifies that all your translated strings are corruption-free and can be imported into our systems. Set up your machine to enable the sanity check, execute the script, review the error log and fix any errors, if applicable. For more information, see Sanity Check Overview [page 35].

● Execute the sanity check of your translated TTK files, see Executing the Script [page 37]. ● Fix all issues reported within the sanity check logs, see Error Logs [page 38].

Delivery of files

You are now ready to deliver your files and place them at the correct location. The following checklist makes sure that you deliver your files according to our expectations.

● Do not rename any files or folders and make sure that you have not renamed any of them by accident. ● Do not add any extra folder levels into the folder structure. ● Place the TTK files in the correct location on the SLS Transfer Server. ● All TTK files that we provided to you must be delivered back to SAP. ● Send an e-mail to your SLS PM to confirm the delivery of the translated files within the delivery deadline.

2.6 Correction Implementation

You may receive correction spreadsheets or similar requests to fix translation errors. These spreadsheet have either been forwarded to us from software testing, or from a linguistic reviewer. We usually place them into the folder of a particular drop, or send them to you via an email if you are already working on a drop. We ask you to carefully review these implementation requests. If you decide that the correction request is justified, ensure that you fix all occurrences of the indicated error in all applicable project strings. In order to find all occurrences of a string, search the UI glossaries, see Exported User Interface Strings (UI Glossaries) [page 71]. If you don't agree with or have objections to any of the corrections requested, enter your comments into the column Partner Comments, or send an e-mail to your SLS Project Manager. Otherwise, we expect that all correction requests have been implemented in the TTKs provided to you within the drop at the time of delivery.

Process

1. You receive the feedback form containing corrections either via email or as part of a drop. 2. Review the feedback and screenshots provided (if any). In some cases, the column Partner's Comments will

contain specific questions for you. Please answer them and return the spreadsheet with the drop. 3. If you have any concerns or questions about the implementation requests, contact your SLS PM either via

email or enter your question into the spreadsheet. 4. If a correction request requires you to make changes to a very high number of leagcy strings, and will take a

considerable amount of time to implement, contact us via Query Tracker or email before you go ahead.



5. Implement all applicable changes in all files. Use a search tool to search the exported UI files to find all occurrences of a string. See Searching Glossary Text Files [page 66] for more information.

6. Check Query Tracker to make sure that all outstanding queries for the file(s) have been implemented. See Tracking and Implementing Queries in Catalyst [page 54] for more information.

7. Place the updated TTK files, as well as the updated spreadsheet (if applicable) into the correct delivery location.

2.7 Context Review Setup

The purpose of a context review is to test the accuracy of the UI translations from an end-user's perspective (in context). Translations which appear correct in a Catalyst TTK may not be appropriate once displayed in the user interface of a product.

The following tasks are NOT to be performed as part of a context review:

● reviewing the online help ● translating new strings (even though you may see empty strings in the Catalyst TTK files) ● correcting of non-linguistic issues

The main expectation during the Context Review is for you to make sure that the translated texts appear correctly and consistently in context. Focus instead on typos, mistranslations, grammatical errors and obvious mistakes. Do not spend time polishing the translations.

Materials for context review

A context review package will be placed onto the SLS Transfer server (EMEA and APA) which includes the following information:

● context review instructions ● test plans in Excel or Video format ● if multiple products are reviewed at once, there will be a priority list ● a spreadsheet where you will log the issues found ● a full set of TTK files containing all user interface strings for the product(s) to be reviewed

Tools

Make sure you set up your work environment as follows:

● Two monitors: we recommend using two computers per user, both of which can access the same shared folders. One computer is used to connect to the Translation Portal with the mapping of the network drive. The other computer is used for implementing the changes in Catalyst and to play the video media. On this monitor you can also view the user interface test plan (UITP) in full screen mode while following steps in the build on the second screen.



● a tool for displaying the test videos, see Displaying Test Movies [page 66] ● a tool for searching the UI glossaries, see Searching Glossary Text Files [page 66] ● a tool for taking screenshots, see Taking Screenshots [page 67] ● Alchemy Catalyst - where you open the TTK files to make corrections, see Installing Alchemy Catalyst [page

22] ● access to Query Tracker - for posting questions, see Introduction [page 47]

2.8 Context Review Steps

Read the context review instructions carefully. Then open the test plans or the test videos, connect to or open the build and follow the instructions. If you cannot follow the instructions in the test plan, submit a query, see Submitting Queries in Catalyst [page 53].

Most likely, you will encounter both linguistic as well as functional issues in the localized build. Correcting Linguistic Issues

Linguistic issues are issues that you can fix in the TTK files yourself. These include mistranslations, inconsistencies, spelling mistakes, etc. When fixing these issues, make sure that you search the glossaries to ensure that all occurrences within the product are fixed, see Exported User Interface Strings (UI Glossaries) [page 71].

If you see a mistranslation and you cannot find the string in the translated product glossary, it is most likely a concatentation. For more information, see the next section.

Reporting Functional Issues

Functional issues are those where strings do not appear correctly in the UI, but are not translation issues. Possible functional issues include the following:

● Truncation: the size of a UI control, like a button or textbox, is too small for the translated string. If this happens, you may see a cut-off - i.e. truncated - string on a button or elsewhere in the dialog box.

● Display of string IDs: instead of a proper localized string, you see just the ID of the string, such as BOBJ_XLIFF_STRINGS.

● Layout Issues: the layout of the strings is incorrect in the Target UI. This is most likely to occur with languages that do not read left-to-right and horizontally, such as Asian languages, Hebrew, and Arabic. For example, the directionality of a string may be wrong, where it shows up vertically instead of horizontally, or left-to-right instead of right-to-left.

● Concatenation: a string is being concatenated from two separate strings. Concatenation occurs when developers use parameters or placeholders in their strings, later replacing the parameter with a variety of other strings to form different sentences or phrases. If the string is grammatically incorrect, please report the issue in the tracking spreadsheet so that the developers can modify the source code.



While reporting functional issues are not the primary focus of the context review, please record any functional issues you come across in the Tracking Issues spreadsheet provided. Refer to the template in the spreadsheet for how to record these types of issues. Taking screenshots are also very useful in terms of highlighting issues; see Taking Screenshots [page 67]. If you run into any technical difficulties with e.g. the product build, connecting to the virtual machine, following the test plan, or if you have any other questions, please report them by submitting a query in Query Tracker. See Submitting Queries in Catalyst [page 53] and Tracking and Implementing Queries in Catalyst [page 54].

File Delivery

Queries: Ensure that all applicable queries are implemented, see Tracking and Implementing Queries in Catalyst [page 54]. For information on how to search and filter for strings in Catalyst, see Searching and Filtering [page 24].

Sanity Check: The sanity check is a script that verifies that all your translated strings are corruption-free and can be imported into our systems. Set up your machine to enable the sanity check, execute the script, review the error log and fix any errors, if applicable. For more information, see Sanity Check Overview [page 35].

Delivery location: Place TTK files and the tracking issues spreadsheet (if any) in the correct location on the SLS Transfer Server. All TTK files that were provided to you must be delivered back to SAP.

Confirmation: Send an e-mail to your SLS PM to confirm the delivery of the translated files within the delivery deadline.

2.9 Invoicing

The PO assignment and invoicing happens in accordance with current SLS SUS processes. The basic process is as follows:

1. The SLS BPM Resource Manager opens the POs and provides the number to you. 2. SLS will provide a "services completed report" to your financial e-mail address using an automated email on

the 3rd of every month. 3. You create SUS confirmations in accordance with the document "How to Create SUS Confirmations" on the

SLS Support Portal Billing Information SUS User Guides ). These reports must be attached to the confirmations.

Ensure that all information entered in confirmations is correct in order to avoid rejection. 2.9.1 Invoicing for Terminology Projects

PO assignment and invoicing work in accordance with the current SLS SUS TERMO processes. For further information on TERMO, visit the SLS Support Portal Billing Information Volume-based Billing ).





2.9.2 Invoicing for Context Review

The SLS Project Manager will send you an initial scope and cost report which contains the estimated number of hours required for the context review work. If you find that you require more hours than estimated, you must inform the SLS PM before exceeding the stated hours.

The SLS PM will review the request and grant/reject as required. The amount of hours will be changed in the final scope and cost report when the drop is complete. The amount that you invoice is based on this revised report.

User Interface Translation using Alchemy Catalyst TOOLS


3 TOOLS 3.1 ALCHEMY CATALYST

3.1.1 Catalyst Introduction Before using Alchemy Catalyst, ensure to check the Alchemy website for more information and/or attend their web-based lessons to learn more. The following sections assume that you are familiar with the tool.

Install Catalyst

See Installing Alchemy Catalyst [page 22]. Catalyst Overview

The following screenshot shows the areas that we want you to pay particular attention to when translating SAP content.

Note When watching the web-based lessons keep in mind that some of them have been recorded using the previous Catalyst version.


User Interface Translation using Alchemy Catalyst TOOLS 22

1. This is the TTK file name. You need to use the file name when submitting queries and/or identifying the location of strings.

2. This is the resource file name. You need to use the file name when submitting queries and/or identifying the location of strings.

3. This is the string ID (see also String ID [page 27]). You need to use the file name when submitting queries and/or identifying the location of strings.

4. Displays the String Status [page 34] icons. 5. Use the translation filters when translating or reviewing strings (see Using Filters [page 24]). When using

the filters, be aware that you may exclude preceding and following strings that carry valuable information for translation (see Strings preceding and following a string [page 29]).

6. Use QuickFind when implementing corrections and/or checking the consistency of your translations (see Using QuickFind [page 26]).

7. Ensure to check the content of the Memo field (see Memo [page 28]). 8. The Maximum Size field provides information about the maximum permissible length of a translated string

(see Maximum String Length [page 33]). 9. Check the word count before and after a translation in the Statistics pane (see Checking the Word Count

[page 23]). 10. Attach glossaries as active TMs to the Catalyst file to ensure consistency. Since the concordance search has

certain limitations, we recommended to search our glossaries using a commerically available search tool (see Searching Glossary Text Files [page 66]).

Catalyst Validation Checks

The validation checks in Catalyst will automatically detect errors such as duplicate hotkeys, inconsistent translations, and other issues. In order to comply with our , make sure to run the following validation checks before delivering files back to us:

● Removing Incorrect Carriage Returns [page 30] ● Validating Hotkeys [page 31]

3.1.2 Installing Alchemy Catalyst Installing Alchemy Catalyst

Please refer to the Patch Installation section below to install the correct version of Catalyst. Make sure to use the default installation settings. Please note that Translator/Lite edition works only in conjunction with Catalyst Developer. For running the sanity check, at least one of the two licenses to be purchased by the agency: Localizer or Developer/Pro. In addition, ensure that the application is installed on either of the following paths C:\Program Files or C:\Program Files (x86) in order for the sanity check (see Sanity Check Overview [page 35]) to run properly.



Patch Installation

Alchemy has released Catalyst 11.0 SP3. To install SP3 you must have Alchemy Catalyst 11.0 installed. Make sure that all open sessions of Alchemy Catalyst 11.0. are closed before installing SP3. The current required version is 11.3.255. Please use Internet Explorer to access the links below.

● Full installer for Catalyst 32bit: ftp://user:[email protected]/Catalyst_11/113255/Alchemy_Catalyst-win32_11.3.exe

● Full installer for Catalyst 64bit: ftp://user:[email protected]/Catalyst_11/113255/Alchemy_Catalyst-win64_11.3.exe

Segmentation Setting

Please check your Catalyst segmentation setting, and change it to “paragraph based”. If it is already “paragraph based”, no action is required on your end. It is very important that your setting is changed to “paragraph based”. This is because the EN .ttk will from now on be set to “paragraph based” as a default. In case we have an inconsistency in the settings between the EN file and the language file, translation can introduce a serious corruption into our files.

Steps for setting update:

1. Open Catalyst 11. 2. DO NOT open any ttk files (if you do this while you have a ttk open, you will also introduce corruption). 3. Go to “Home” tab. 4. Click on “Segmentation”. 5. Change your setting to “Paragraph based parsing”. 6. Click “OK”. 7. Close Catalyst.

Once this is done, you can open Catalyst, and start translating your ttk file.

3.1.3 Checking the Word Count

It is recommended to compare the word count statistics in Catalyst with the word count statistics we provided to you to ensure that there are no discrepancies. To display the word count before and after a translation, do the following steps:

ftp://user:[email protected]/Catalyst_11/113255/Alchemy_Catalyst-win32_11.3.exe

ftp://user:[email protected]/Catalyst_11/113255/Alchemy_Catalyst-win64_11.3.exe



1. Open a TTK in Alchemy Catalyst. 2. Click on the Statistics tab at the bottom left corner of the window.

3. Click the Refresh icon ) to see the most up-to-date word count information.

The word count in Catalyst 11 is grouped into the following categories:

● Words: Absolute number of words in a TTK file. ● Translatable: Number of words that are translatable in a TTK file. Segments that are locked are not included in

the word count analysis. ● Translated: Absolute number of words that are marked as Translated in a TTK file. This includes all For

Review, Leveraged and Signed-Off segments. ● For Review: Number of words that are marked Leveraged and For Review in a TTK file. ● Signed Off: Number of words that are marked as signed off. ● Not Translated: Number of words that are not yet translated. ● Untranslated Uniques: Number of translatable words minus the total number of untranslated duplicated

words. ● Untranslated Duplicates: Combined word count of all untranslated segments that are duplicated or repeated.

3.1.4 Searching and Filtering Using Filters

Catalyst allows to group strings of the same status using specific filters which are available from a dropdown list at the top of the Project Workspace pane.

Note Your translation task involves that you only work on strings marked as Not Translated. For the implementation of query answers, correction requests and other changes, you may touch strings in all other statuses (except Locked).



The most frequently used filters are:

● Untranslated: Use this filter to display strings that need to be translated. ● For Review: Use this filter to display strings that have been translated and need to be reviewed by a reviewer. ● Duplicates: Use this filter to display repeated strings and repetitions. Together with Translate All and Translate

Interactively buttons, this filter helps to ensure consistency and improve efficiency at translation and review time.

When not to use filters

Example 1:

A sentence has been split into 2 strings, and 1 string has already been translated in a previous drop (screenshot 1). Switching the filter from Untranslated back to No Filter shows the lacking context information (screenshot 2). Another similar example is provided in section Strings preceding and following a string [page 29].

Note Although these filters help to display only the strings you need, the exclusion of other surrounding strings may result in a loss of context information. The following section When not to use filters [page 25] provides examples that show that the filters need to be handled with care and be removed in order to see more context information.



Example 2:

When using the Duplicates filter, keep in mind that duplicated English strings may refer to different concepts and different translations may be needed for duplicated English strings. In the example below, all English occurrences of "Date" have been grouped together by applying the “Duplicates” filter. In this particular case, only the last “Date” as an argument should be translated, as the other “Date” strings are function names that need to be kept in English.

Using QuickFind

In order to make corrections to or to ensure the consistency of a certain set of strings, you can either use the Find and Replace action and work from the results in that pane, or you can use the QuickFind filter to view the results in the translation pane. You can use the Refine QuickFind button to refine the search result..



3.1.5 Finding Context Information

The challenge in user interface translation is that many strings consist of one word or two words or of ambiguous strings. In Catalyst, there are 3 methods to find more context information: the ID of a string, the Memo field and strings following or preceding a string.

String ID

Example 1: The string ID “action.local.phone.short” tells you “tel” is the short form for “telephone”.

Example 2: The string IDs “stringTable$CEOIdPathPrompt1$value” and “stringTable$CEOIdPathPrompt2$value” tell you that those two strings will be concatenated into one sentence at run time.

Note If none of the below methods help you to establish the missing context information, submit a query in Query Tracker and ask for a screenshot displaying the string in the running build.



Memo

Developers may add text information about the usage of a string. This information is displayed in the Memo field of the Properties.

In the below examples, the string “Estimated Time to complete: “%seconds%s” contains a memo, which gives the explanation and instruction about “%seconds%”.



Strings preceding and following a string

If you use any of the strings filters (show New strings only) or QuickFind for correction implementation purposes, you may miss important context information that sits in preceding or following strings if these are filtered. In the following example, the word "Active" is ambiguous.

When removing the filter, the following string is called "Inactive" which may provide the sufficient information for you to make your translation decision.



3.1.6 Removing Incorrect Carriage Returns Carriage Return

These extra carriage returns must not be contained in any translated string and must be removed prior to delivery. Follow these steps to remove these returns.



1. Open a TTK file in Catalyst. In the Navigator pane, click into the TTK root _ttk_xx (xx represents the language code) to make sure that the search is applied to all resource files contained within a TTK file.

2. Click HOME Find & Replace . 3. In the Find & Replace window, click the General tab.

4. Select the radio button Active object. 5. In the Find What text box, type "\n". 6. Enable the Search in translated and Use regular expression checkboxes. 7. Click OK.

The results are shown in the Find and Replace pane. Review the returned strings and remove all reported carriage returns.

3.1.7 Validating Hotkeys

Hotkey

To validate that strings with hotkeys have been rendered correctly in your languages, execute the hotkey validation checks available in the Catalyst Validate Expert. We expect you to run the following validation checks:



Steps to run the validation

1. Open a TTK file in Catalyst. In the Navigator pane, click into the TTK root _ttk_xx (xx represents the language code) to make sure that the search is applied to all resource files contained within a TTK file.

2. On the menu, click EXPERTS Validate Expert . 3. In the Validate Expert window, click the Options tab. 4. Click the Deselect All button. 5. Depending on which file type you are working on, only certain validation checks make sense. For all files,

check the following: ○ Inconsistent hotkey count ○ Invalid ampersand (&) position (Not applicable for zh, zf, ja, ko and th)

6. For .rc files, you can check the following in addition:



○ Duplicated hotkeys in dialogs ○ Duplicated hotkeys in menus

7. In the Object Types tab, enable the Select All checkbox. 8. Click OK. 9. The results are shown in the Find and Replace pane. Review the returned strings and correct any hotkey issue.

3.1.8 Maximum String Length

Some strings have a maximum length limit that was set by developers. These strings are marked by a black rectangular box. In the Properties tab, you can see the number of allowed characters in the Maximum Size field. Once your translation exceeds that number, the box around your translated string turns red as you can see in the screenshot below.

3.1.9 Catalyst Status Translation Status

The translation status of the strings in a TTK files can be found on the Project Statistics pane. Check these word counts before you start with a translation as well as when you are finished. To get the latest word-count, click the

Refresh icon in the Statistics pane.



String Status

A string in Catalyst can have one of the following string statuses:

- Signed Off: string has been reviewed and has been approved.

- Leveraged: string has been 100% leveraged and needs to be reviewed.

- Fuzzy Match: string has been fuzzy leveraged (less than 100% match) and needs to be reviewed

- For Review: string has been translated and is ready for review. (no icon) - Untranslated: string needs translation

- Locked: string is locked in the TTK file and must not be unlocked. Developers lock strings that either do not

require translation, or the string is pending review by an information developer. You may also see locked translated strings which usually are to be removed.

3.1.10 What's New in Catalyst 11

Familiarize yourself with the Catalyst software before you start translating with the new version. Visit Alchemy Software resources page and the product documentations for details.

Here are some of the new features you will find useful in Catalyst 11:

● QuickFind With the new Refine QuickFind button, you can now narrow down the search result.

● New Options in Validate Expert Validate Expert has the following new options: ○ Consistent Pattern Tests ○ Correct Translation Tests ○ Invalid Terms Tests

● New Options in Find & Replace Find & Replace has the following new options:



○ Search in memo ○ Search in ID ○ Match whole word only

3.2 SANITY CHECK 3.2.1 Sanity Check Overview

The sanity check is a script that you execute on your translated files. It ensures that the translated files align with our and that the files can be imported into our systems without any errors.

The sanity check script checks the following aspects and creates a file called sanitcheck.log which details the process steps. If issues are found, then an error log file is created in addition which provides the error details. For more information, see Error Logs [page 38].

Untranslated strings

The script searches for any string marked as Untranslated within a TTK file. For more information on string statuses See Catalyst Status [page 33].

Missing TTK files

The script compares the TTK files listed in the file list of a translation drop with the TTK files placed into the delivery location. All TTK files provided to you for translation should be returned into the delivery location.

Changed TTK file names

The script searches for TTK files that are listed in the file list of a translation drop. None of the TTK files provided to you for translation must be renamed under any circumstances.

Corrupted TTK files

The script searches for any corruptions within a TTK file.



Missing XLIFF files

The script compares the number of XLIFF files contained in the TTK files provided to you with the number of XLIFF files contained in the delivery location. This is to ensure that none of the XLIFF iles within a TTK file was deleted by accident.

Signed-off segment found

All strings translated by you should be in the For Review status and none should be in Signed Off status. The script compares the string status of the files provided to you with the string status of the strings in the delivery location. For information on string status, see Catalyst Status [page 33].

Locked strings

You are not allowed to lock any of the strings in a TTK file. The script searches for strings that were accidentally locked by you.

Incorrect project title

The project title within a TTK must be _ttk_xx (where xx represents the language code) instead of –project title–. The script will search for any occurrences of incorrect project titles.

3.2.2 Setting up your Machine Installing Perl and Catalyst

In order to successfully run the sanity check script, Perl 5.8 and Alchemy Catalyst 11 must be installed on the same machine. follow the steps below to install and configure Perl 5.8

1. Download the sanity check package from SLS Support Portal Product Translation Tools Catalyst ).

2. Unzip the package to your local drive. The package contains a Perl 5.8 installation file (.msi file), a perl script (.pl), and 4 Perl library fils (.pm files).

3. Click .msi file and install Perl by using the default settings. 4. Copy the files XShareDriveDirFile.pm, XLog.pm, and XLogging.pm to C:\perl\lib. 5. Create a folder called XML under C:\Perl\site\lib and copy the file DOM.pm to C:\Perl\site\lib\XML. 6. Create a folder C:\SAP_BOBJ and copy the SanityCheck.pl into it.

Iinstall Catalyst 11 if you haven't done so yet, see Installing Alchemy Catalyst [page 22].




Verifying Settings

Please follow the steps below to verify the settings on your machine

1. On your machine, click Start Run . 2. Type cmd in the Open text field. 3. To verify that the correct version of Perl is installed, type perl -version in the command line window. 4. The information displayed should match the information in the screenshot below. If not, make sure you install

Perl version 5.8.

5. To verify that the correct version of Alchemy Catalyst is installed (version 11), type the following on the DOS

command line: If you have a 64-bit machine: cd C:\Program Files (x86)\Alchemy Software\Catalyst 11.0. If you don't have a 64-bit machine: cd C:\Program Files\Alchemy Software\Catalyst 11.0.

6. Type catalyst.exe which opens up Catalyst version 11. If that is not the case, make sure to install Catalyst version 11.2 or higher, see Installing Alchemy Catalyst [page 22].

7. You have now verified that all settings are correct and can close the command line windows.

Now you are ready to execute your script, see Executing the Script [page 37].

3.2.3 Executing the Script

Follow the steps below to execute the sanity check script (SanityCheck.pl):

1. On your machine, click Start Run . 2. Type cmd in the Open text field. 3. In the command line window, type cd C:\SAP_BOBJ and press Enter. 4. Type perl SanityCheck.pl and press Enter.



5. Enter the values for the four required arguments: untranslated folder, translated folder, ttk filelist and language set.

Untranslated folder: contains the TTK files that we sent to you for translation. Ensure that you enter the full path, e.g. C:\1_From_SAP\Files.

Translated folder: contains the TTK file that you translated and placed into the correct delivery location, e.g. C: \2_To_SAP\Files.

ttk filelist: please enter the full path to the file list as well as the its file name. e.g. C:\sanitycheck.pl\out \general\filelist\swdrop_filelist.txt. The file list of a UI translation drop is always located here: .. \1_From_SAP\Project_Info\Filelist\.

language set: enter the language(s) that you need to check. There are two options: all and xx. The option all runs through all languages. xx here represents the two-letter language code, you would enter fr for French, nl for Dutch (xxxxwhere is the list of the all language codes? Do we have suppliers that run the script on more than one language?). To separate language codes, use a space, e.g. nl fr es.The default value is all.

Once you have entered the above argument information, press Enter to execute the script. The script generates two types of error logs if issues are found. If no issues are found, no error logs are being created. See Error Logs [page 38] for more information.

3.2.4 Error Logs

While running, the SanityCheck.pl script creates 2 folders called Output and Log at the following location: C: \SAP_BOBJ\Translation. If there are no errors are found, the Output folder will be deleted at the end of the script run, and you will only see the sanitycheck.log file under the C:\SAP_BOBJ\Translation\Log folder.

If issues are found, different error log files are created depending on the type of error:

● The errors of the types Untranslated strings [page 35], Signed-off segment found [page 36] and Locked strings [page 36] are written into a log file which is named after the TTK without the ".ttk" extension and which will be placed into the C:\SAP_BOBJ\Translation\Output\file\<project name> folder. (For example: C:\SAP_BOBJ\Translation\Output\files\aurora_sp\product.businessobjectsruntime_export_nb.xliff.log)

● The errors of the types Missing TTK files [page 35], Changed TTK file names [page 35], Corrupted TTK files [page 35], Missing XLIFF files [page 36], and Incorrect project title [page 36] are written into the sanitycheck.log file in the C:\SAP_BOBJ\Translation\Log folder. The summary.log file is also created in this folder and contains a summary of the issues listed in the sanitycheck.log file.

This is an example of the sanitycheck.log:

Note The sub-folder structure of the From SAP folder (untranslated) must be the same as in the To SAP folder (translated). It is also important that both folders are at the same level in the file path, e.g. if the path for From SAP folder is C:\1_From_SAP\Files\, then the path for the To SAP folder should be C:\2_To_SAP\Files.



This is an example of the summary.log:

Fix any issues that were reported in any of the log files. Then run the script again until no more errors are returned.

If there are no errors, no summary.log or no file-specific error log files are created. The sanitycheck.log file is always created regardless of errors found. Place this file together with the rest of your delivery into the delivery folder.

Note Occasionally, the sanity check script generates log files that don't contain real errors. (For example, the error Corrupted/Wrong Project Name may have been caused by the xx code contained in the TTK file name which is not a "real" error.) In such cases, and regardless of the "errors" found by the script, place the



Furthermore, if you find anything unusual during the sanity check run that is not described above, report this issue to your SLS PM and detail the steps that you went through (plus screenshots, if applicable) so that we can reproduce the issue on our side.

3.3 SAPterm 3.3.1 Worklist Search

Worklists in SAPterm (STM) show all new terms added to your domain. Worklists are called up by entering the project keys. The steps below show you how to enter the projects keys and to call up your worklist. See also the Terminology Reference Priority section in 4.2.

1. From the Utilities menu, hover over Create and choose Worklist (the screen shot below is from an old version).

2. Enter your target language and the project key. Click the Execute icon on the top left corner.

sanitycheck.log file as well as any other error log file generated into the delivery folder together with your delivery.



Enter the project keys that are indicated in the Terminology Translation step above. 3.3.2 Advanced Search When translating terminology rolling drops, you need to locate additional terms that cannot be retrieved using the standard worklist process. The advanced search process requires you to upload a specific notepad to SAPterm which have been placed onto the SLS Transfer server:

\\dwdf204\SLStransfer\SLS\SAPBusinessObjects\References\SBOP_Terminology

\SAPterm_Notepads (EMEA/AMERICAS)

\\sgpss073.sin.sap.corp\SLStransfer\SLS\SAPBusinessObjects\References\SBOP_Terminology

\SAPterm_Notepads (APA)

Note These notepads are updated regularly, so make sure that you always download the latest version for each translation drop. Pick the notepad by the abbreviation of your language which matches the abbreviations found in SAPterm.



1. Click Advanced Search on the initial screen.

2. On the Advanced Search screen, set the search criteria as indicated below.

○ For each rolling drop, set your target language and the Term Status to "3".

○ Under Administrative Information, set the date range for Term Changed On as follows: ○ Set the end point of the date range to the Tuesday that the drop starts. ○ Set the start point of the date range to the Tuesday two weeks prior. For example, the screenshot

below shows the settings for the rolling drop kicked off on January 14, 2013. ○ Set the date range for as follows:

○ Under Component, make sure both the Added and Original checkboxes are de-selected. Under Include

Only The Following, make sure the following checkboxes are selected:Standard Entry, Internal Entry, Terms with Definition and Terms w/o Definitions.



○ Under the Component section, click on the arrow icon next to Component. The Multiple Selection for Component dialog appears.

○ Click the Import from Text File icon to import the language-specific notepad you downloaded earlier.



○ The components in the notepad will be imported as shown below.

○ Click the Copy icon to return to the general screen. You will notice that only one component abbreviation

appears in the text box. This is just a display issue. Not to worry - all components have actually been selected.



3. Click the Execute icon to execute the search. 4. Scan the results list. Translate any entries in the list that do not have a translation for your language, review

any terms at status 1 or 2, and then release the terms.

3.3.3 Translatability of Brand Voice Terms Non-Translatable Brand Voice terms

The non-translatable marker ) in SAPterm designates terms that should not be translated.

For non-translatable product names under the component BV-*, the English name has been copied to your language automatically by the system. Any non-translatable product names at Status 1 or 2 for your language should be released to Status 3. If there are any reasons for your language to translate a certain name, please submit a Target query in Query Tracker. Work on all terms in the search results list, including the Retired terms.

Translatable Brand Voice terms

Translatable product names under BV-* require particular handling because it does not necessarily mean you can translate these terms at all cost. There are two scenarios:

1. If the value of Term Category is PRODUCT and the Non-Translatable marker is not checked, you can tranlate the term. When you translate, follow the specifications in the language-specific Brand Voice Translation Guidelines found in SLS Support Portal Terminology REFERENCE MATERIALS Brand Voice Translation Translation Guidelines .




2. If the value of Term Category is not PRODUCT (e.g. OTHER PROPER NAME, BASE FORM, PRODUCT LINE), and the Non-Translatable marker is not checked, you can translate the translatable portions of term in accordance with your language conventions.

General Reminders

To understand which words in a term are translatable, look in the Comment field ) or the Entry Note field

( ) of the English term.

If you see terms at Status 2 in your worklist, review the terms and make any necessary corrections and release them. Please work on all terms in the search results list, including Retired terms.



3.4 QUERY TRACKER 3.4.1 Introduction

Query Tracker is an internally developed web application tool. Translators can use it to submit issues they find and retrieve the answers. Query masters review the issues, assign them to developers or authors, or answer the queries. The translators are responsible for retrieving the answered queries and taking necessary actions to implement the corrections (Note: All queries may not get answered on time. If you have unresoluved issues at the time of the translation delivery, please use your best-guess translation). The tool is also used to categorize the issues raised for further follow-up actions.

There are two different user types (internal and external users) and four different roles in Query Tracker:

● Submitter - the user who submits the query ● Query Master - the user who reviews, monitors, assigns and answers incoming queries ● Answerer - the user who answers the query ● Implementer - the user who implements the query

Accessing Query Tracker To access Query Tracker, click this link using Internet Explorer 9, 10, or 11. When you sign in for the first time, use your SAP_GLOBALl username and password.

If you changed your passwords since last accessing Query Tracker, see the section “No access after password change”.

User Interface of Query Tracker

After logging into Query Tracker, the following tabs are available.

Tab Name Description

Submit Query This tab allows you submit queries. You submit queries by first selecting the correct translation type.

Answer Query This tab displays all queries that have been assigned to you for answering. Click on a link to view a single query.

Note As an external C-user, you can access Query Tracker only through the Standard Translation Portal. When you sign in for the first time, register as a correct user type. If you are a translator working for an agency or a freelance translator, check "Yes" and select your agency name from the dropdown. "No" is only for SAP employees. Selecting the right agency name is very important for certain filters.

https://querytracker.pgdev.sap.corp/



Tab Name Description

Search This tab allows you to search the queries within the entire Query Tracker application and across all translation types.

● The Basic Search searches only a limited number of fields (Source Text, Query ID, Target Text, Note Number, Course/Certification ID, Object Name).

● In the Advanced Search tab you can refine your search results by adding conditions.

Filters If you use the same search conditions on a regular basis, you can save these search conditions, and give this filter a name which will then appear in the Filters tab.

Help This tab contains the online help in PDF format.

Technical Support Use this tab to submit a BCP incident if you encounter a technical issue or need help creating a filter.

Sign Out Use this tab to sign out of Query Tracker.

Translation Types

Different translation tool environments and authoring systems require you to submit different details in order to find the string in question in our systems. Before you can submit a new query you must select the right translation type which brings up the appropriate submission mask to enter these details. The translation types currently available are listed in the table below. For information which translation type to select for which project, read the project instructions or contact your SLS PM.

Translation Type Translation Scope Query submitter will receive an email ...

Catalyst User interface strings using Alchemy Catalyst.

When a query is in Submitter to Clarify status.

File-based Translation Translation of file-based documents using Trados including Sybase, Ariva, and SuccessFactor projects

When a query is in Submitter to Clarify or Answered status.

TED Marketing and Corporate translation managed in TED.


Marketing Marketing translation projects which starged before the TED translation type rollout in Query Tracker.


SAP Notes SAP Notes using ORBITT. When a query is in Submitter to Clarify or Answered status.

System Translation (SE63) User interface strings or documentation using SE63 (including ORBITT for Ixiasoft and KW).


STM Rolling Rolling terminology drops on a bi- weekly or monthly basis in SAPterm.

When a query is in Submitter to Clarify status.



Translation Type Translation Scope Query submitter will receive an email ...

Training Training material in Trados. When a query is in Submitter to Clarify or Answered status.

Notification emails

Query Tracker connects to an internal reporting system that allows notifications to be sent to the query submitter via email when certain conditions are met. Currently the notifications are set differently across the different translation types. Please refer to the table above to see in which cases the query submitter will receive an email. If you want to request a change in the email notification system, or if you want to set up your personal customized email notification, submit a BCP incident by clicking on Technical Support.

3.4.2 General Instructions and Expectations

Before submitting a query

● IMPORTANT: When you log on to Query Tracker for the first time, be sure to register your Agency Name. This

is critical for using filters provided by SLS. Search Query Tracker to check whether your query has already been posted by another translator. See the Basic Search and the Advanced Search sections in Query Tracker Online Help file in SLS Support Portal Product Translation Tools Query Tracker ).

● Submit your queries as early as possible. Since authors and developers work across several time zones, answers may require up to 48 hours.

● Check all reference materials and project instructions. ● Check the relevant Product Information pages. Go to SLS Support Portal Product Translation

REFERENCE MATERIALS Product Information Pages ). ● Are you a new translator? Check with the agency's power user to avoid posting queries that are "too simple". ● Do not submit a query to report any technical issues.

When submitting a query

● Each translation type allows you to submit several queries in batch by selecting the same query details. ● Pay attention to enter the correct details of a query. Query masters and answerers need these details to

locate the string in the system and assign the query to the right answerer. ● Submit one query for each individual problem. If there is an issue of a similar nature across multiple files or

objects, enter ONE query and indicate that the same issues exists in multiple occurrences in the Details field. ● If possible, enter a suggested translation into the Target Text field (unless instructed otherwise).





While translating ● Copy the Worklist filter that corresponds to your translation type (see Setting up the Worklist filter [page

50]). ● Check your worklist filter daily to avoid accumulating too many answered queries at the day of delivery. ● Make sure that queries are not excluded from your Worklist filters. ● Send queries with insufficient answers back to us using the Request Clarification action at your earliest

convenience. Before translation deadline/delivery

● Check your worklist filter one last time and ensure that all applicable queries are correctly implemented in the

translation. See the Tracking and Implementing Queriesacking section for more details. ● For translation projects using Catalyst and Desktop Workbench, make sure all answered queries are in

Implemented status before delivery. ● For translation projects using ORBITT, regularly export the answered queries to an Excel spreadsheet and

mark as implemented. Before the translation delivery, merge all the exported spreadsheets during the translation and make sure all the queries have been checked/implemented in ALL OCCURENCES. Please deliver this merged spreadsheet as a proof of implementation.

3.4.3 Setting up the Worklist filter

In order to see all queries in Answered status for a particular translation type, use one of the predefined filters available.

1. Go to Filters -> Predefined Filters. 2. Select the applicable filter(s) and click on Copy to My Filters. 3. The selected filter(s) will show under the My Filters tab.

Note In all dropdown lists, you can type the first letter of a value project to move quickly within the list. For example, press "g" on your PC keyboard to access names starting with "G" quickly.



Use this filter and/or modify this filter according to the project instructions provided, if any.

It is possible to modify these filters and save them under a new name. For more information, see the Using Filters section in Query Tracker Online Help within the tool or in Service Marketpalce (Tools>Query Tracker). However, to process queries (Request Clarification, Implement), please only use these filters.

3.4.4 Before Submitting Queries in Catalyst Finding context information

Before submitting a new query in the Translation Type Catalyst, check if you have:

1. Checked the string ID: the ID of a string in Catalyst may carry important content information. 2. Checked the strings before and after a string in question. They may provide more context. 3. Checked the Memo field: the memo field is used by developers to provide more context information.

Choosing the right issue

Different queries are forwarded to different people. Please make sure to choose the issue that reflects the question you are inquiring about in the most appropriate way. Use the following overview for guidance.

Note Avoid adding "Please confirm my translation" anywhere in your query. In most cases, the source and localizability queries are forwarded to English-speakers (authors, developers, project managers) who DO NOT speak your language and who CANNOT confirm your translation. For Target queries, it is recommended to post them in English, too, so that query masters and project managers can support you in the decision-making and implementation process.



Scenario Issue to select Answerer

One-word strings or short phrases without much context information, where multiple translations are possible.

Source: Explain meaning of string/ sentence.

developers (English speakers)

You come across a technical term or a technical concept, that is not entered in SAPterm, and not contained in the reference materials. There is not enough context available to make an informed translation decision.

Source: Explain meaning of string/ sentence.


Any errors, mistakes, typos in a string Source: Possible error in source. developers or technical writers (English speakers)

Quoted UI elements or quoted error messages not found in remaining TTK files or project glossary

Source: UI text not found in references. developers or technical writers (English speakers)

A placeholder in a string where it is important to know what it stands for in order to translate the string grammatically correct

Source: What does the placeholder stand for?


Strings in uppercase letters, capitalized strings, camel-cased strings, function names, operator names, where it is not clear whether these strings should be left in English. Before submitting a query, search the glossary to see if they have been exposed for translation.

Loc: Is the string/object translation- relevant?

developers (English speakers), if the answer is Yes, internal linguists will provide guidance on HOW to translate, if needed.

The references (glossaries, TMs, SAPterm) contain different translations for the same concepts for the same product and you want to inquire whether these need to be aligned or not. Please provide the translation that you think should be used moving forward.

Target: Inconsistent/wrong translation in references.

internal linguists, query masters

You find a wrong translation in the legacy translations (TM, older strings) or in the glossary. Please provide the correct translation and a short explanation of what is wrong.

Target: Inconsistent/wrong translation in legacy translation.


You do not see translation of an UI string in the translated sections in UI Glossaries but the English string is found in Untranslated Glossary. This happens when certain UI strings were not exposed for translation before the documentation translation. Please suggest the translation of the string

Target: UI text found in Untranslated Glossary.




Scenario Issue to select Answerer

and use it consistently once the term is exposed for translation.

Any other issue about the source Source: Other issue. query masters

Any other issue about the target Target: Other issue. internal linguists, query masters

3.4.5 Submitting Queries in Catalyst

Before submitting new queries, see the General Instructions and Expectations [page 49] and Before Submitting Queries in Catalyst [page 51].

Once you have gone through the above checklists, you can start entering a query. If you are accessing Query Tracker for the first time, follow the registration instructions on the screen. After signing into Query Tracker, you are on the Submit page. To submit a query for an Catalyst project, select the Translation Type Catalyst from the dropdown list.

The Submit screen for Catalyst queries is displayed.

1. In the Translation Type dropdown list, select Catalyst. 2. In the Projects dropdown list, select the project name as instructed in the drop-specific instructions. 3. In the Source Language and Target Language fields, verify that the correct languages are selected. 4. In the Drop Number dropdown list, select the drop number that matches the drop folder name.



5. In the Source Text field, enter the source text. In the Target Text field, enter the suggested translation. If you don't receive an answer before the translation deadline, we will assume that the text entered into the Target Text field has been used in your translated files.

6. Copy and paste correct information in the TTK File Name field, the Resource field, and the String ID field. 7. Select the appropriate issue from the Issue dropdown list. Make sure to select the right issue. Enter additional

comments in the Details field. 8. If needed, upload an attachment by clicking on Browse. 9. Repeat the above steps to enter as many queries as needed. Click on Add More Queries if you need to submit

more than 5 queries at once. 10. Click Submit to enter your queries into the system. A success message shows the query IDs of the queries

submitted.

3.4.6 Tracking and Implementing Queries in Catalyst

Follow the general instructions as described in While translating [page 50] as well as Before translation deadline/ delivery [page 50].

The drop-specific instructions (1_From_SAP\Project_info\Instructions) in the Query Tracker Information section will contain one or more filters specific to each UI translation drop as well as specific implementation instructions. Create these filters and check them regularly while you are translating. Before translation delivery these filters must show 0 queries.

Example of a drop-specific instruction:

The Worklist filter as well as the project-specific filters contain queries both in Answered and in Submitter to Clarify status. If spawning is enabled, you will also see answered queries submitted by other languages. You may



refine the search by adding conditions. See the Sample Filters for Translation Agencies section in Query Tracker Online Help found within the tool or in Service Marketpalce (Tools>Query Tracker) . If you need help creating a filter for a particular search scenario, go to the Technical Support tab and submit a BCP incident.

Implementing Queries

When implementing an answered query, make sure to fix that all occurrences of a queried string within the entire project. Do not only correct the string in the TTK file that was indicated in the File Name field but search the project glossary for the source string and make a correction in all applicable TTK files.

When implementing queries submitted during previous rolling drops, the following scenarios may occur:

● The queried string cannot be found in the TTK file anymore: search the glossary for parts of the string, queried key term, and/or the string ID. If it still cannot be found, you may implement the query.

● The TTK is not part of the translation drop: check the project-specific instructions to make sure that you are using the correct filter. If that is the case, search for the queried string and/or the string ID in the glossary (the TTK file may have been renamed or the string may have been moved to a different file). If you cannot find anything AND you are using the correct filter, you may discontinue this query.

● The answer is valid but does not apply to your language: implement the query to remove it from your worklist filter.

Only set the status of a query to Implemented when you have made corrections in all applicable files. When delivering your files, the Worklist filter must show 0 queries. We will ask for redelivery if that is not the case.

Queries in Answered status

The following actions are available to external users for queries in Answered status

Action Description

Implement The query has been answered and the answer is sufficient to make a translation decision.If the Answer is no longer relevant, use this action too to close (acknowledge).

Request Clarification The query has been answered but the answer is insufficient to make a translation decision.

Queries in Submitter to Clarify status

The following actions are available to external users for queries in Submitter to Clarify status

Action Description

Clarify Query The submitter adds missing details to the query or rephrases the issue.



Action Description

Discontinue The query is not relevant anymore.

3.4.7 Tracking and Implementing Queries in STM Rolling

Follow the general instructions as described in While translating [page 50] as well as Before translation deadline/ delivery [page 50].

Copy the pre-defined filter STM Rolling Worklist to track queries for STM Rolling. For information on how to copy this filter, see Setting up the Worklist filter [page 50]. The Worklist filter as well as the project-specific filters contain qfueries both in Answered and in Submitter to Clarify status. If spawning is enabled then you will also see answered queries submitted by other languages. You may refine the search by adding conditions. See the Sample Filters for Translation Agencies section in Query Tracker Online Help. If you need help creating a filter for a particular search scenario, go to the Technical Support tab and submit a BCP incident.

Implementing Queries

If you haven't received your answer before translation deadline, please enter a best-guess translation into SAPterm but do not release the entry. Notify your PM and include the query ID number. When you receive an answer about a term, you can go back and change the entry if needed.

When you receive an answer about a term, you may add a comment in the target language to supplement the existing source information in SAPterm, or to provide instructions on how to use the translation.

Queries in Answered status

The following actions are available to external users for queries in Answered status

Action Description

Implement The query has been answered and the answer is sufficient to make a translation decision. If the Answer is no longer relevant, use this action too to close (acknowledge).

Request Clarification The query has been answered but the answer is insufficient to make a translation decision.

Queries in Submitter to Clarify status

The following actions are available to external users for queries in Submitter to Clarify status



Action Description

Clarify Query The submitter adds missing details to the query or rephrases the issue.

Discontinue The query is not relevant anymore.

3.4.8 SEARCHING QUERY TRACKER

3.4.8.1 Basic Search

The Basic Search tab allows you to search all queries within the entire Query Tracker application and across all translation types. It searches only a limited amount of fields (Source Text, Query ID, Target Text, Note Number, Course/Certification ID, Object Name). If you get too many search results, use the Advanced Search [page 57] tab to refine your search results by adding search conditions.

The following basis search options are available:

Query ID only - Enable this checkbox to search through the Query ID field only. This allows for a faster search performance.

Match Case - Enable this checkbox if your search is case-sensitive.

Original Query Only - Is enabled by default and excludes the spawned queries. If you want to include the spawned queries in your search, disable the checkbox and run the search again.

3.4.8.2 Advanced Search

If the Basic Search provides too many search results, you can use the Advanced Search tab to narrow the scope for searching. You can limit your search scope to a particular word, a phrase, a file, projects languages or other criteria.

The following screenshot shows the elements of the advanced search.

Note See the section of the for some limitations when using the search.



Field Names

The field names are the searchable columns. There are generic field names that are the same for all translation types, like the Submitter Source Text field or the field, the field, the Target Language field. Other field names are specific to a certain translation type, for example the Note Number field in the SAP Notes translation type, or the XLZ Name field in the WS DWB translation type. To reduce or increase the number of field names, you can click on Customize Advanced Search above the filter area and remove or add the fields as required in your searches. For a description of the available field names and values, see .

Operators

The operators link the field names with the values. For information on using the operators, see .

Values

The values are the information stored in the database. Some fields, for example the Status field or the Projects field, contain dropdown lists so you don't have to type the value. For other fields, it is impossible to have dropdown lists (for instance the Source Text field). For more information on the values, see the table in .

Adding or removing conditions

To add a condition click on the plus symbol. To remove a condition, click on the trash can symbol.



Exclude spawned queries

Searching for a word or a phrase in Advanced Search requires you to choose the Source Text field. Since you search across all translation types, you may see queries returned in many different ways (original queries and their spawned queries). In order to exclude these spawned queries, you either add the Is Original Query condition or the Translation Type condition.

Exclude other projects and languages

Here is an example showing all queries containing the word “report” in all answered Target queries for the Olysmpus_SP project in French. Here you can add the Status and Target Language conditions.

3.4.8.3 Viewing Search Results

As default, the search results are displayed using the following columns: Translation Type, Status, Source Text, Issue, and Answer. The columns can be sorted by clicking the column header.

Note If you need help creating a specific filter, submit a BCP incident by clicking on Technical Support. Provide a brief description of what you want to search for.

Example

Example



To show/hide the search panel

When the search results are displayed, the search panel disappears. To show the search panel again, click on the small arrow to display it.

To change the search results view

1. Click on the Customize link on the right side of the action bar. 2. Use the left and right arrows to move the columns from the Available Columns to the Selected Columns area

and/or vice versa as required.



3. Use the up and down arrows to change the order of the columns as required. 4. When you are done, click on Close Window to apply your changes.

To change the number of search results

The default number of queries returned is set at 50. You can increase this number to a maximum of 500. When increasing this number, keep in mind that the higher the number, the slower the search. When reducing the number, queries may be excluded from your search:



1. Click on the Customize link on the right side of the action bar. 2. In the Number Of Search Results field, change the number. 3. Click Update and then Close Window to apply your changes.

3.4.8.4 Using Filters

Each search performed in the Advanced Search tab can be saved for future use. In order to save a filter click on the Save as Filter button. The new filter appears under the My Filters tab.

The separate to be used for the operators is one of and is not one of is a semicolon. For more information on operators and how to use them see .



Disable/Enable Auto-Search

With the magnifying glass icon on the left side of a filter, you can select to automatically run the search (Display search result) or only display the search criteria (Display search criteria only) . It is ON as default which means when you click a filter, the search starts automatically and display the search result. If you would like to check the search criteria and modify the condition, click the icon to turn OFF so that the search will not start till you confirm.

Rename a filter

Click the pencil icon on the left side of a filter to change the name of the filter.

Delete a filter

Click the trash can icon on the left side of a filter to remove the filter.

Export a filter to share with other users

Click the Export icon on the left side of a filter to export it as a .qtfilter file so that other users can use the same search conditions. Other users can import the .qtfilter file by clicking Import Filter.

Import a filter

You can now import a filter. The filter to be inported should be in a .qtfilter format. Click Import Filter, then locate the .qtfilter file you need to import. Click Import. Please note: the importing filter cannot have the same name as one of your existing filters. If you are not sure, veryfy the name of the filter with the person who provided the .qtfilter file to you (the .qtfile filter name is not the actual filter name).

Get Statistics

You can now see the number of search results of a given filter without clicking on the filter. In order to do so, select the checkbox next to the filter (or choose Select All) and click on Get Statistics. The number of queries is displayed in brackets on the right side of the filter name.



Display filter name in search results

When clicking a filter, the filter name appears at in the top right corner of the Display screen.

Using the Worklist filters

External users who have registered in Query Tracker with a translation agency, can use the pre-defined worklist filters available for each translation type. The filters conveniently show the subset of queries that the external user is deemed responsible for: all applicable queries that are in the Answered and Submitter to Clarify statuses.

1. Go to Filters Predefined Filters . 2. Select the appropriate filter. If you have a question, see Translation Types [page 48] or contact your SLS PM. 3. Click Copy to My Filters. 4. The filter is now available in the My Filters tab.

3.4.8.4.1 Sample Filters for Translation Suppliers

Technical Support tab.

This topic provides some filter examples for translation suppliers. If you require further assistance in adapting these filters to your specific needs, please submit a BCP incident by going to the

Show me all my answered queries

This topic provides some filter examples for

There are Worklist filters available predefined for each translation type which show all answered queries for a particular language. To use these worklist filters, see Show me all my answered queries [page 64].

Show me all queries I have submitted

This filter shows all original queries submitted by a translator.

This filter shows all original queries submitted by a translation agency.



In both cases the condition Is Original Query must be added to exclude the spawned queries. It is recommended to also include the translation type if you or your agency have submitted queries in different translation types.

Show me all queries of one project in my language

This filter shows all original queries submitted for a certain project.

Show me all queries for a project which are answered in a certain time range

This filter shows all queries for a certain project you are working on which are answered in a certain time range.

3.4.8.5 Search Tips To search for whole words

In order to search for whole words only, you can use the following 2 workarounds:

1. Enter one space before and after the word to search. (Keep in mind that this will exclude words at the beginning of a sentence, words before punctuation marks such as full stops, commas, or tags.)

2. Use the browser search function (Ctrl+F) which contains the Match Whole Word Only or Match Case options.



To improve the search performance for a faster search

There are several ways to improve the search performance in Query Tracker.

● Set the number in the Number of Search Results under the Customize link to a lower number. See To change the number of search results [page 61].

● Use the Is Equal To operator instead of the Contains operator. See . 3.5 OTHER TOOLS

3.5.1 Searching Glossary Text Files

In order to search the Exported User Interface Strings (UI Glossaries) [page 71], you can either use a commercially available search tool (we recommend using Search and Replace by Funduc), or you can open the files in Microsoft Excel where you use the Search or the Filter function.

3.5.2 Displaying Test Movies

The test plans for context review may be created using a video format. In order to view the test plan videos, we suggest that you install VLC Media Player on your local machine. This player supports most audio and video formats (MPEG-2, MPEG-4, H.264, DivX, MPEG-1, etc.).



3.5.3 Taking Screenshots

The recommended tool to take screenshots is Snagit 9 or higher. Save screenshots in GIF format unless you receive different instructions. More details on the screenshot process can be found in the project-specific instructions.


User Interface Translation using Alchemy Catalyst REFERENCE MATERIALS 68

4 REFERENCE MATERIALS 4.1 Overview

Reference materials are an important part of the translation process. There is a variety of information available to you to allow for high-quality translations. We expect you to familiarize yourselves with all reference materials described in this section upfront, before you begin any translation project. Each project or drop will contain additional instructions specific for that project, indicating which reference materials to use.

Terminology References

All approved core product terminology is contained in SAPterm [page 69].

Referenced user interface strings and product terminology that are not contained in SAPterm can be found in the UI glossaries, see Exported User Interface Strings (UI Glossaries) [page 71].

To get an overview of the structure and maintenance model of the product glossaries, see Glossary Structure [page 73].

Linguistic Guidelines

The style guides are available on the SLS Support Portal Product Translation REFERENCE MATERIALS Product Style Guides ). Contact your SLS PM if you have any question about any of the instructions contained.

For information about the Brand Voice Guidelines, see Brand Voice [page 70].

Product Background information

The published product documentation can be found on the SAP Help Portal.

For information about product documentation in translation, see Product Documentation [page 75].

Additional information about SAP products, such as the product summary, feature descriptions and webinar links, can be found on the product pages posted on the SLS Support Portal Product Translation RERFERENCE MATERIALS Product Information Pages ).


http://help.sap.com/


User Interface Translation using Alchemy Catalyst REFERENCE MATERIALS


Miscellaneous References

When translating copyright statements, see Copyright Statements [page 74].

Any sample data (for instance, from the translated universes Beach, eFashion) is available on the SLS Transfer Server:

\\dwdf204\SLStransfer\SLS\SAPBusinessObjects\References\Miscellaneous\Sample Data

(EMEA/AMERICAS)

\\sgpss073.sin.sap.corp\SLStransfer\SLS\SAPBusinessObjects\References\Miscellaneous

\Sample Data (APA) 4.2 SAPterm SAPterm is SAP's central repository for defining and standardizing the use of special terms. It contains the core terminology of the SAP products.

As info developers who are responsible for adding terminology into SAPterm typically limit the amount of terms to the core terminology of a product, you cannot expect to find all product terminology in SAPterm. If you cannot find a particular term in SAPterm for a particular product, look it up in the exported user interface glossary (see Exported User Interface Strings (UI Glossaries) [page 71]). The SAPterm component and the glossaries to be used should be indicated in the drop-specific instructions. If you still did not find the term you are looking for, expand the search scope of SAPterm to first all SBOP products area, then the whole SAPterm. Please refer the following table as your guide (Priority 1 as the highest):

Table 1:

Pri ority

Terminology Reference and Scope Additional Information

1 SAPterm under the project-specific component

See the drop-specific instructions for the SAPterm component(s) of this project.

2 Exported UI Strings (UI glossaries) See the drop-specific instructions for the glossary location. This reference is to check user interface strings only.

3 SAPterm under the SBOP components In the Component field in SAPterm (STM), click the Import from Text File, then select the SAPterm Notepad for your language (\\dwdf204\SLStransfer \SLStransfer\SLS\SAPBusinessObjects\References\SBOP_Terminology \SAPterm_Notepads)

4 The whole SAPterm Clear the selection in the Component field in SAPterm (STM). Make sure the definition is applicable for your current project . Make sure the definition is ap plicable for your current project.

If you still don’t see a candidate, submit a query in Query Tracker (Source: UI text not found in references).

Basic guidelines for looking up terms

When you look up a term in SAPterm during translation, it is important that you know the context in which it is used. Depending on context, the same source term may be translated differently if it represents a different



concept or because of a specific convention of your language. Before you look up the term in SAPterm, you must therefore identify the context of the source text.

Determine the appropriate translation based on the SAPterm component of the context and other related information including definition. This is important regardless of whether the look-up yields one or more hits.

Identifying content and its components

Refer to the drop-specific instructions to identify the product or the type of material you are translating and its SAPterm component. If you cannot find content or component information, contact the SLS Project Manager.

Checking Context information of a term

Always ensure you check the definition ) of each term when available. Please also check its comment ( )

and entry note ) for additional information when available.

If the context information in SAPterm is insufficient, you can search for the term in the compiled English documentation content (i.e. product documentation in previous or current projects) on the SLS Transfer Server:

\\dwdf204\SLStransfer\SLS\SAPBusinessObjects\References\English_Files_and_References

(EMEA/AMERICAS)

\\sgpss073.sin.sap.corp\SLStransfer\SLS\SAPBusinessObjects\References

\English_Files_and_References (APJ) 4.3 Brand Voice

Brand voice is what we say and how we say it. It's the style we use to communicate or content, and help us find the right words for SAP.

SAP Brand Tools

You will find the SAP approved names for products and solutions in the SAP Brand Tools website . To access the website, you need to register. When prompted, enter Juliet Elliott's name as the contact person (for all translation areas).



Approved Names

The Naming Center replaced the Approved Names list in January 2013. To access the Center, go to SAP Brand Tools Naming Center Approved Names ). The approved product and solution names are also included in SAPterm.

Writing Style

The SAP Writing Style provides a single, comprehensive source for key messaging, positioning, and naming iinformation for all SAP offerings. Please go to SAP Brand Tools Brand Elements Voice Basics Writing Style ) for more information. When using the non-English versions of the SAP writing style guidelines, be aware that the English version is always the most up-to-date. Please consult the document in English for the latest information.

SLS uploads the most important Brand Voice documents to the SAP Brand Tools websiste. 4.4 Exported User Interface Strings (UI Glossaries) The user interface strings of a product are made available as text files called UI glossaries. These text files contain the entire string set of an application in English and the translated language as well as technical location information such as the TTK file name, the resource file name as well as the string ID. The string ID is unique value that helps developers to identify the string in the system.

These UI glossaries are used as a reference both for lookup of translated UI strings and for a consistent translation of terminology. Whereas SAPterm contains the core terminology of a project, the UI glossaries contain any terminology beyond that. Your SLS PM indicates in the project-specific instructions which UI glossaries are to be used for a particular product translation. Depending on the number of products referenced in your translation, you may see more than one glossary to be checked.



\\dwdf204\SLStransfer\SLS\SAPBusinessObjects\References\UIGlossaries (EMEA/AMERICAS)

\\sgpss073.sin.sap.corp\SLStransfer\SLS\SAPBusinessObjects\References\UIGlossaries

(APA)

Specific instructions on which text file to use is indicated in the project-specific instructions.

You can either search this text file using a commonly available search tool (see Searching Glossary Text Files [page 66]), or you can open the glossary in any text editor or in MS Excel. When opening a glossary in Excel, you will see 5 columns:

Note Because the glossaries are updated every two weeks with new and corrected strings, you should always download the latest version and never use a glossary downloaded for a previous project translation.

Note If you open the glossary files with a version of MS Excel lower than 2007, please be aware of the limitation that Excel cannot view more than 65,000 lines. Some of our glossaries exceed this limit.



4.4.1 Glossary Structure

The glossaries are grouped by project code names. A project can consist of a single product (e.g. Cundus), one product consists of several components (e.g. Aurora_4.1), or multiple products (e.g. Olympus_SP). A project usually represents one release (major or minor).

The next level in the folder structure separates the glossaries into Translated and Untranslated glossaries. Translated glossaries contain all translated strings, the Untranslated glossaries contain the strings that are currently translated and will be added to the Translated glossaries after two weeks.

The next level after the Translated/Untranslated glossaries are the folders named after either the products or the components contained within the translation project.

Search the _FullProject.txt if you need to access all strings of a project.

Both the Translated and the Untranslated folders contain the glossaries of the product(s), or product components. The text file at the highest level is called FullProject and contains all strings of the entire project. Search this file if you need to do a cross-project-search.



If your search needs to be more granular and focused on a particular product or component, drill down one more level and you see one FullApplication text file which lets you search the entire product or component as well as all text files of each resource file that make up a product or component.

4.5 Copyright Statements

The Copyright Statements folder contains the official and legally approved translations of the copyright statements for all languages grouped by years. These statements are being translated by SLS once a year and

Note Depending on which level you execute your search, it may return a different level of "inconsistencies". Be aware that terminology can be specific to a certain component, a product, a product portfolio, or a product release. Terminology changes are regularly made between releases, so you may see the same term translated differently depending in which glossary you look it up. That may or may not be desired, if in doubt, submit a query.



placed onto the network for your reference. When you come across copyright statements in your translations, make sure that you use the official and legally approved translations found in these folders. Please take care to never translate these statements yourselves but always use the legally approved translations from the server

The copyright statements are available on the SLS Transfer Server:

\\dwdf204\SLStransfer\SLS\Copyright (EMEA/AMERICAS)

\\sgpss073.sin.sap.corp\SLStransfer\SLS\Copyright (APA)

4.6 Product Documentation Product Documentation for Translation Reference

The documentation source files are placed on the SLS Transfer Server grouped by drop number. Depending on the content you translate, you will find PDF files, jpg files for diagrams and xml files. Link information for a particular project/product you are working on is available in the project-specific instruction.

\\dwdf204\SLStransfer\SLS\SAPBusinessObjects\References\English_Files_and_References

(EMEA/AMERICAS)

\\sgpss073.sin.sap.corp\SLStransfer\SLS\SAPBusinessObjects\References

\English_Files_and_References (APA)



The "All_Documentation" folder contains compiled English documents from all previous documentation drops, which may be used for UI or Terminology translation.

Translated Titles of product documentation

In order to facilitate the searching of referenced documentation titles, we created a reference XLZ file for you that contains all translated documentation titles.

\\dwdf204\SLStransfer\SLS\SAPBusinessObjects\References\DocTitle_XLZ (EMEA/AMERICAS)

\\sgpss073.sin.sap.corp\SLStransfer\SLS\SAPBusinessObjects\References\DocTitle_XLZ

(APA)

You can either search the English and the translated documentation guide on the SAP Help Portal (http:// help.sap.com/) or you can open the Doc Title XLZ file to pull out the translation from there. If a guide title cannot be found in the XLZ file, there is either a citation error or the guide has not been translated into your language. Submit a query to confirm.

If you come across documentation titles mentioned in your translation project, open this XLZ file and search for the applicable translation.

If no search result is available, it may be explained by the following reasons :

● There is a mistake in the source ● The documentation title will not and has never been translated into your language ● The documentation title will be translated in one of the upcoming translation drops ● The documentation title is part of an older release ● The documentation title has not been translated by SLS NA



In such cases, please submit a query in Query Tracker.

Referenced guide titles can appear in all dita files except the Ditamap file. The ditamap file contains the guide title and is to be translated. You may use the Doc Titles XLZ file to check the translations of previous documentation versions.

4.7 Tips and Best Practises

The following will help you making the right decisions when it comes to looking up terms in the reference materials.

Proper Names

If you come across terms that look like product/feature/service/component names do the following:

1. Look up the term in SAPterm, and if you find it, please use that translation or leave in English as applicable; 2. If it’s not in SAPterm, look it up in the Brand Voice Naming Center, see Brand Voice [page 70]. If you find it,

follow the translatability guidelines for the translatable portions of the name as described on the <xref format="html" href="http://https://translation.sap.com/index.html" scope="external">SLS Support Portal</xref> Terminology REFERENCE MATERIALS Brand Voice ).

3. If it’s not in the Brand Voice Naming Center, look it up in the UI Glossaries. If you find it, it’s a feature/service/ component name, so you can use the translation found in the glossary.

4. If you cannot find it anywhere, please submit a source query.

If you find inconsistencies between the various references, please submit a target query. SAPterm vs. UI glossaries

To look up translation for UI or other terms, check the reference materials in the following priority order:

1. SAPterm under the project-specific component - See Project Page or Drop-Specific Instructions for the SAPterm Component(s)

2. Exported UI Strings (UI glossaries) - If your translation is referencing a software product UI, look it up in the UI Glossaries to keep consistency. See Project Page or Drop-Specific Instructions for the glossary location.

3. SAPterm under the Analytics components - In the Component field, click the Import from Text File, then select the SAPterm Notepad for your language (\\dwdf204\SLStransfer\SLStransfer\SLS\ SAPBusinessObjects\References\SBOP_Terminology\SAPterm_Notepads)

4. The whole SAPterm - Make sure the definition is applicable for your current project. Note: Brand Voice’s approved names are now found in the BV components in SAPterm.

If you still cannot see a candidate, submit a query in Query Tracker (Source: UI text not found in references).


User Interface Translation using Alchemy Catalyst ISSUES AND SUPPORT 78

5 ISSUES AND SUPPORT 5.1 Questions?

Before asking questions, make sure that you are familiar with the entire content of this PDF as well as further referenced documentation. In addition, review all project-specific instructions provided to you by your SLS PM.

We also recommend visiting the websites of the translation tool vendors for more information as well as checking the specific help files within the application.

● Tool-related issues: For issuess about tools and setup, make sure that you have read the available installation instructions and carefully followed them. Search the Infotool which is available both on the Translation Portal as well as on the SLS Support Portal Product Translation TOOLS ). When you encounter a technical issue with Alchemy Catalyst, send an email message about the issue, including steps to recreate it, to the SLS Project Manager.

● Translation-related issues: Use Query Tracker for all issues about the source text, the translations, and the reference materials.

● Project-related issues: For about the project setup and all other issues, send an e-mail to your SLS Project Manager.

5.2 Glossary

Alchemy Catalyst

A software localization suite developed by Alchemy Software Development Ltd; translation tool used at SLS.

asset

The files that contain the content in a translation project and none of the formatting from the original text, and where any markup (such as HTML tags) is hidden from view.

batch action

The process of changing the status of a group of queries in Query Tracker.


User Interface Translation using Alchemy Catalyst ISSUES AND SUPPORT


BPM

Abbreviation, see Business Partner Management team.

Business Partner Management team

The SLS group responsible for the strategic development of 3rd party resources aligned to SAP global language requirements, including negotiating contracts and prices, ensuring required knowledge transfer to resources, and coordinating project resource availability with translation partners.

context review

A quality assurance process step to ensure the correctness and validity of the translated strings in the running localized product.

Corporate Content service team

The Corporate Content service team provides or manages the translation of communication materials, financial reports, HR documents, legal agreements, sales and consulting collateral, and executive and supervisory board communications.

correction implementation

The process of reviewing the corrections received from review and inserting them into the translated files.

cost model

An equation used to calculate the cost of a translation project.

DITA file

An XML file type used for authoring content.



DITAMAP file

The container for topics used to transform a collection of content into a publication.

drop

A package containing files from several projects that are processed at regular intervals.

external user

A user type in Query Tracker which includes translators, reviewers, and coordinators from an external supplier.

filter

A set of saved search conditions used to display queries in Query Tracker.

final drop

The last translation package that is sent out before the project is completed.

freeze date

The date when no more changes to the files are allowed.

full set of TTKs

Refers to the entirety of all TTK files of a project.

global implementation

The process of making a correction to all occurrences of a string or a phrase within a project.



glossary file

See user interface glossary.

hotkey

The keyboard shortcut that a user presses in order to execute a command. In the user interface a hotkey is a letter that is represented by a special character (typically an ampersand, some cases an underscore).

internal user

A user type in Query Tracker which includes all SAP employees that have access to Query Tracker.

legacy

A type of text stored in translation memory systems that is used for reference and re-use purposes.

localizability query

A translation issue category in Query Tracker that asks about whether or not a string or a phrase is translatable.

maintenance schedule

The translation plan containing the translation dates for products in maintenance mode.

non-RTM drop

Any translation package in a rolling drop except the final drop.

off-cycle drop

A translation package that is scheduled outside the rolling drop schedule.



offline translation

The translation of documentation, training materials, and other files using a computer-assisted translation tool. online translation

The translation of interface texts and online help in an SAP translation system environment.

ORBITT

Acronym of "Online Resource-Based Integration of Translation Tools". The tool environment used to translate SAP XML documentation and other selected formats.

placeholder

A piece of code associated with a value and whose associated value may be changed.

purchase order

A request from an organization (SLS) to a vendor (external supplier) to perform services at a certain point in time, basis for suppliers to invoice their delivered services.

query

An issue/question submitted by a translator or a reviewer about the source or the target text.

query implementation

A quality process step to ensure that the answers received through Query Tracker have been replicated in the translated files.



query master

The person who is responsible for coordinating the answering of queries in Query Tracker.

Query Tracker

The query management tool used to submit and track issues/questions about translation.

QT

Abbreviation, see Query Tracker.

regional review

A step in the translation workflow whereby your translation is given to a reviewer and corrections are returned to you for implementation.

resource file

The original file that contains the user interface strings. Multiple resource files are combined into a TTK file.

rolling drop

A translation package that is sent out and delivered back in regular intervals based on a predefined schedule.

rolling translation

A translation management model whereby translation packages are sent out and delivered back in regular intervals based on a predefined schedule.



RTM drop

The final drop before the software is frozen or the final drop before a documentation is published.

sanity check

A script that the translators are expected to run before file delivery which validates that the files are free of technical errors and fully translated.

SAP Language Services

The department in Globalization Services responsible for both efficiently creating clearly-worded language versions of SAP products that accurately reflect the substance of the original language and for producing translated versions of content to support product sales and after-sales processes.

SAPterm

The SAP terminology database.

scope and cost report

A file that contains information on the scoping analysis, cost model(s) used, PO name, and total costs of a project.

SD

Abbreviation, see service description.

segment

A unit stored in a translation memory which can consist of a letter, a word, a phrase, a sentence or entire paragraphs.



service description

A services agreement between our company (in this case SAP Language Services) and a supplier.

SLS

Abbreviation, see SAP Language Services.

SLS Support Portal

https://translation.sap.com/index.html A publishing platform used by SLS to store translation project related contents and training materials. Contents in SLS Service Marketplace (retired) have been fully migrated to this location.

source

An abbreviated form to refer to the original language of a text.

source query

A translation issue category in Query Tracker that asks about a specific aspect in the source text.

spawning

A feature in Query Tracker to generate answered queries for all languages and translators.

string, software string

A phrase containing of at least one word appearing on the user interface of a product.



style guide

A language-specific document containing guidelines for the stylistic rendition of certain aspects in a target language.

Supplier Self-Services

A Web-based SAP application used to collect, review, and approve both billable and non-billable time and expenses.

SUS

Abbreviation, see Supplier Self-Services.

tag

A piece of code used to mark up text.

target

An abbreviated form to refer to the translated language of a text.

target query

A translation issue category in Query Tracker that asks about a specific aspect in the target text.

term Q-check

A quality process step that validates the consistent translation of the terms that have been added to SAPterm for a particular project.



Transfer Server

The server location that SLS uses to exchanges files for translation and reference materials with translation suppliers.

Translation Portal

A Citrix environment through which SAP translators access their virtual translation desktop.

TTK file

A package of resource files in the proprietary file format of Alchemy Catalyst. TTK stands for Translation Tool Kit.

UI

Abbreviation, see user interface.

UI glossary

Abbreviation, see user interface glossaries.

UITP

Abbreviation, see user interface test plan.

untranslated glossary

A collection of all user interface strings that are currently in translation.

user interface

The text appearing on an application screen which is to be translated.



user interface glossary

A text file that contains the entire set of software strings of a product or application in English and the translated strings as well as location details (file name of the TTK, of the resource file and the string ID).

user interface test plan

A prescribed step sequence to help you navigate through the user interface of a product during context review. They may be provided in video, Excel or Word format.

variable

A piece of code associated with a value and whose associated value may be changed.

Important Disclaimers and Legal Information Coding Samples

Any software coding and/or code lines / strings ("Code") included in this documentation are only examples and are not intended to be used in a productive system environment. The Code is only intended to better explain and visualize the syntax and phrasing rules of certain coding. SAP does not warrant the correctness and completeness of the Code given herein, and SAP shall not be liable for errors or damages caused by the usage of the Code, unless damages were caused by SAP intentionally or by SAP's gross negligence.

Accessibility

The information contained in the SAP documentation represents SAP's current view of accessibility criteria as of the date of publication; it is in no way intended to be a binding guideline on how to ensure accessibility of software products. SAP in particular disclaims any liability in relation to this document. This disclaimer, however, does not apply in cases of wilful misconduct or gross negligence of SAP. Furthermore, this document does not result in any direct or indirect contractual obligations of SAP.

Gender-Neutral Language

As far as possible, SAP documentation is gender neutral. Depending on the context, the reader is addressed directly with "you", or a gender-neutral noun (such as "sales person" or "working days") is used. If when referring to members of both sexes, however, the third-person singular cannot be avoided or a gender-neutral noun does not exist, SAP reserves the right to use the masculine form of the noun and pronoun. This is to ensure that the documentation remains comprehensible.

Internet Hyperlinks The SAP documentation may contain hyperlinks to the Internet. These hyperlinks are intended to serve as a hint about where to find related information. SAP does not warrant the availability and correctness of this related information or the ability of this information to serve a particular purpose. SAP shall not be liable for any damages caused by the use of related information unless damages have been caused by SAP's gross negligence or willful misconduct. All links are categorized for transparency (see: http://help.sap.com/disclaimer).

User Interface Translation using Alchemy Catalyst Important Disclaimers and Legal Information


http://help.sap.com/disclaimer/

go.sap.com/registration/ contact.html

© 2016 SAP SE or an SAP affiliate company. All rights reserved. No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP SE or an SAP affiliate company. The information contained herein may be changed without prior notice. Some software products marketed by SAP SE and its distributors contain proprietary software components of other software vendors. National product specifications may vary. These materials are provided by SAP SE or an SAP affiliate company for informational purposes only, without representation or warranty of any kind, and SAP or its affiliated companies shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP or SAP affiliate company products and services are those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty. SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP SE (or an SAP affiliate company) in Germany and other countries. All other product and service names mentioned are the trademarks of their respective companies. Please see http://www.sap.com/corporate-en/legal/copyright/ index.epx for additional trademark information and notices.

https://go.sap.com/registration/contact.html

https://go.sap.com/registration/contact.html

http://www.sap.com/corporate-en/legal/copyright/index.epx

http://www.sap.com/corporate-en/legal/copyright/index.epx

Documents

User Interface Translation using Alchemy Catalyst · Since a project is split into multiple drops, the content you are translating in one drop will re-occur in subsequent drops, usually