Last Updated: 08/08/23
What can be localized?
Registration transactional emails error messages, static page properties, etc. Session titles and abstracts Speaker bios and job titles Filters, tabs and all interactive elements Event webpage navigation menu and account pane Emails sent from RainFocus to attendees, speakers or sponsors session and sponsor data consumed through API from Rainfocus (if data is translated in Rainfocus, the app will display translations) Some properties in Mobile app are hard carded in English and can not be localized
What can not be localized?
As of Aug 2023, the Event CMS platform which is used to build Event homepages can only support a single language. For World Forums 2023, homepages were done in a single language only. (Tokyo in Japanese, Paris in French) text entered into the Live Chat by attendees. Attendees can chat in local language; no machine translation will present it back in another attendee’s preferred language. dates and times will remain in US English (Oct 21 8:45 AM) See image below. survey questions in Rainfocus must be in a single language Footer can only be in single language due to limitations from DXP Some properties in Mobile app are hard coded in English and can not be localized Check-in screens onsite can be localized, but check-in machines must e set to specific language.
Out of scope for localization due to high volume of words and level of effort:
Exhibitor Resource Center SRC & ERC invite/welcome email SRC & ERC task reminder email Digital Experience hosted on Rainfocus World Forum 2023
What is the translations process?
Current process: The Event Platform team works with the DXP Marketing Localization team to get approved English copy translated for event tech platform webpages/tools. SAFe tickets are submitted through SURF by Event Platform and Content teams as translation projects. The Marketing Localization team retrieves the English assets from these tickets, submits the assets through Cloudwords and works with the preferred ServiceNow translation vendor for human translation, review and approval. to Marketing Localization intake process. The translated assets is returned to the Event Platform team through the SAFe ticket and imported into the event system (Rainfocus), then the workflow goes into a review by the local regional team for functional and translation review.
[2021 Process] The Event Platform team will work with preferred/onboarded ServiceNow translation vendors through Cloudwords, the ServiceNow translation management system (TMS), to get all event platform text translated. With this process, the translation memory along with human translation is leveraged with an additional review step for regional teams to verify and approve the translated words.
Required: Dedicated ServiceNow local language reviewers will need to be assigned pre, during and post event for review and approval of all translations. This resource is critical to keeping the project on schedule. At least one person per language is required. The can assist with identifying these resources. What is the timeline?
Localization does add additional time to the event platform development. It takes an averages of 3-4 weeks for final copy to get translated, reviewed, approved and finalized in the platform. Please account for this additional time in your event and content timelines.
World Forums 2023:
What local languages have we done for past events on Event Tech:
Localization Terminology
Globalization (g11n) Globalization represents all the tasks and activities associated with delivering an end-user experience in languages other than English. Internationalization (i18n): ensuring that a product or service can be suitably and effectively used by international users, meeting their functional, cultural, locale and language requirements without code changes. Localization (L10n): Process of translating and adapting internationalized products and services to make them acceptable for consumption in other languages, markets and cultures. Transcreation applies for creative content (marketing) and market-specific demands (website content), a different process is needed, in order to ensure that the content suitably hits the mark with the target audience.
Internal notes:
Translated strings: