Cleaning files for translation

Translation files exported from Sage People frequently contain labels not requiring translation, such as brand names or numbers. When Sage People commission translations, we clean the translation files to remove labels we do not want to translate before passing the files to our translators.

In some cases, such as brand names, you can search by value to identify the items you want to remove. In other cases, such as numbers for days in a month, searching by the key or an element in the key is more efficient than searching by value.

The key (in STF files) or ID (in XLIFF files) helps you to understand what the field is and which package it is associated with as shown in these two screenshots:

Annotated screenshot pointing out different parts of a label associated with a custom object

Annotated screenshot pointing out the parts of the key for a custom label

Key or ID component	Description
Label type	Labels can be associated with a number of different components, such as: ButtonOrLink CustomField CustomReportType LayoutSection LookupFilter PicklistValue RecordType ValidationFormula WebTab CustomLabel FieldSet QuickAction
Package	The name of the Sage People package the custom object or custom label is associated with. Sage People package namespaces: fSync: Fairsail Async Reporting fCPUSA: Fairsail Country Pack - USA fDL: Fairsail Data Loader fHCM2: Fairsaill Human Capital Management fpay: Fairsail Payflow fRecruit: Fairsail Recruit fRecruitE: Fairsail Recruit Enterprise fResource: Fairsail Resource Manager fta: Fairsail Time spapi: Sage People API spcompplan: Sage People Compensation Planning spperfmgmt: Sage People Performance Management spustaxforms: Sage People US Tax Forms Not shown if: the object is a Salesforce standard object, such as Case or Opportunity the custom label originates in your org
Object name	Name of the custom object.
Package*	If the label is part of a managed package, the package name is repeated here. Not shown if: the object is Salesforce standard object, such as Case or Opportunity the custom label or object originates in your org
Label name	Name of the label.

At Sage People we remove the following string types from translation files. When you remove labels from STF files, remove entire lines containing labels that do not require translating, and in XLIFF files, remove the entire <trans-unit> segments.

Type of string	Information and examples
Product and brand names	When the entire label is a product or brand name, remove it from the translation file. There are a small number of labels where Sage People product names are used as part of longer pieces of content needing translation. Product names associated with Sage People and Salesforce such as Fairsail, Sage People, Human Capital Management, Workforce eXperience, Recruit Other product and brand names such as Twitter, Youtube Named benefit providers such as AIG, Cigna, and similar. Named job portals and other recruitment services such as Monster, Broadbean, etc.
Labels for Salesforce standard objects	Labels for Salesforce standard objects where the object name contains: Account Campaign Case CollaborationGroup CommunityMemberLayout Contact Lead Opportunity Standard User Searching for these values in translation files is easier if you search for the object name surrounded by full stops, exactly as they appear in the label key, to avoid finding other labels where these words might occur.
Country and region names	As Sage People uses its own picklists for country and region names, you can remove the Salesforce standard country and region lists from translation files: AddressCountry AddressState Country names are present in a number of Sage People picklists in the translation files: PicklistValue.fHCM2__Team_Member__c.fHCM2__Citizenship PicklistValue.fHCM2__Work_Location__c.fHCM2__Country PicklistValue.fHCM2__Passport__c.fHCM2__Country PicklistValue.fHCM2__Visa__c.fHCM2__Country PicklistValue.fRecruit__Vacancy__c.fRecruit__Location_Country PicklistValue.fRecruit__Vacancy__c.fRecruit__Location_Region Depending on the language, country names may be the same in English and the target language. When translating to a language for the first time, leave the country names in the translation file to get the appropriate translations. When you next update translations, the Outdated and untranslated file contains the country names where English and the target language versions are the same, and you can remove those from the file before having it translated.
Numbers	Numbers are present in a number of picklists, including: PicklistValue.fHCM2__Absence_Accrual_Rule__c.fHCM2__Reset_Day PicklistValue.fHCM2__Policy__c.fHCM2__Bonus_Annual_Effective_Day PicklistValue.fHCM2__Policy__c.fHCM2__Bonus_Effective_Day PicklistValue.fHCM2__Policy__c.fHCM2__Salary_Increase_Effective_Day PicklistValue.fHCM2__Policy__c.fHCM2__Vacation_Year_Start_Day PicklistValue.fHCM2__Policy__c.fHCM2__Year_Start_Day PicklistValue.fAsync__WX_Report__c.fAsync__Show_Data_for_Report_Levels_Down PicklistValue.fHCM2__Work_Days_Holiday__c.fHCM2__Day This picklist also contains ordinals (1st, 2nd, 3rd, 4th, 5th) which need translating. A small number of picklists contain some numeric values you can exclude: PicklistValue.fpay__Download_Map__c.fpay__Format.0,1 PicklistValue.fpay__Upload_Map__c.fpay__Format.0,000.00 PicklistValue.fpay__Upload_Map__c.fpay__Format.0.000,00
Locale codes	Locale codes are standard, not language specific, and must not be translated. The following picklists contain locale codes: PicklistValue.fHCM2__Corporate_Notice__c.fHCM2__Locale PicklistValue.fHCM2__Corporate_Notice_Instance__c.fHCM2__Locale PicklistValue.fHCM2__Corporate_Notice_Locale__c.fHCM2__Locale PicklistValue.fHCM2__HR_Notice__c.fHCM2__Locale PicklistValue.fHCM2__Competency_Library_Language__c.fHCM2__Locale PicklistValue.fHCM2__Indicator_Library_Language__c.fHCM2__Locale PicklistValue.fHCM2__Scale_Language__c.fHCM2__Locale PicklistValue.fHCM2__Scale_Response_Language__c.fHCM2__Locale PicklistValue.fHCM2__Skill_Library_Language__c.fHCM2__Locale PicklistValue.fRecruit__Candidate_Portal__c.fRecruit__Language_Locale PicklistValue.fRecruit__Candidate__c.fRecruit__Language_Locale PicklistValue.fRecruit__Recruit_Notice__c.fRecruit__Locale
Single letters	Default values in job grade picklists are individual letters, which you do not need to translate for languages using the Latin alphabet: PicklistValue.fHCM2__Job_Description_Library_Item__c.fHCM2__Grade PicklistValue.fHCM2__Job_Description__c.fHCM2__Grade
Image Aspect Ratio	Labels expressing image aspect ratios do not need translating in most cases. PicklistValue.fHCM2__Corporate_Notice__c.fHCM2__Detail_Image_Aspect_Ratio PicklistValue.fHCM2__Corporate_Notice__c.fHCM2__Tile_Image_Aspect_Ratio PicklistValue.fHCM2__Corporate_Notice_Locale__c.fHCM2__Detail_Image_Aspect_Ratio PicklistValue.fHCM2__Corporate_Notice_Locale__c.fHCM2__Tile_Image_Aspect_Ratio PicklistValue.fHCM2__HR_Notice__c.fHCM2__Image_Aspect_Ratio
Page and font sizes	Page sizes and font sizes are expressed with standard labels and do not require translating: PicklistValue.fHCM2__PDF_Template__c.fHCM2__Page_Size PicklistValue.fRecruit__Offer_Template__c.fRecruit__Page_Size PicklistValue.fHCM2__PDF_Template__c.fHCM2__Font_Size PicklistValue.fRecruit__Offer_Template__c.fRecruit__Font_Size
Example values	Some picklists contain example values you do not need translate: PicklistValue.fHCM2__Absence_Accrual_Rule__c.fHCM2__Pay_Code.PC1 PicklistValue.fHCM2__Salary__c.fHCM2__Pay_Code.PC1 PicklistValue.fHCM2__Bonus__c.fHCM2__Pay_Code.PC1 PicklistValue.fHCM2__Benefit__c.fHCM2__Deduction_Code.DC1 PicklistValue.fHCM2__Benefit__c.fHCM2__Employer_Contribution_Code.AAA
Technical labels	A small number of labels hold values and placeholders you must not translate: PicklistValue.fpay__Download_Map__c.fpay__Node_Type.CDATA PicklistValue.fHCM2__RecipientRoleTab__c.fHCM2__TabType PicklistValue.fHCM2__RecipientStatusTab__c.fHCM2__TabType CustomField.fHCM2__Global_Configuration__c.Hold_Absence_Balance_Id CustomField.fHCM2__Global_Configuration__c.Internal_Communications_Confirmation_ID CustomField.fHCM2__Global_Configuration__c.Is_Manager_ID CustomField.fHCM2__Global_Configuration__c.Survey_Confirmation_ID Any labels with values such as EncodeID, SObject, CO2, or tmpPassword
Labels associated with deprecated objects	If custom objects in your system are later deprecated, labels associated with them change to "Deprecated". These labels do not need to be translated as they are not in use.
Labels for Sage People developer test data	All labels associated with Unit Test object (Time package) All labels associated with UnitTestFieldsetContainer object (HCM package)