Localization of Mobile and VMS - 1 November 2023

Application

Mobile IOS/Android
Vendor Management System (VMS)

System URL

Mobile apps: N/A

VMS:
https://us.vendor.staging.getequiem.com
https://eu.vendor.staging.getequiem.com
https://au.vendor.staging.getequiem.com

Related Articles

• Equiem One Internationalisation and Localisation

• Equiem One language switcher

• Mobile 10.0.0 Release

• Will our Platform block users from using web browser translation services (i.e. google chrome often offers to translate terms for me when i visit european customer/ supplier websites and I can't read their privacy polices as published

• No, we will not block browser translation services. I have already tested it on all our apps, if my browser is Set to French then all our apps are translated in French. This will be specifically useful for Iris which is not localised.

Will default English content in the Admin Panel site set-up localised?

• Registration buttons e.g. I live here, I work here, I'm visiting

• My Building page title, and subpages

• Marketplace page title

• Welcome Page Heading & Subheading

• Yes, we have localised the defaults, and localised defaults will be used in all the same situations English defaults are currently used.

• You mentioned things like the registration buttons and marketplace title are localised. As these are customisable fields, do these only localise if they are left as the default titles, or can these be overridden and still localised, or do we need to localise these titles directly in Admin Panel?

• As mentioned above, defaults are localised, if you override them, then they become custom fields and are not localised, they become user generated content so they will default to the language they have been included in.

• T&Cs, Privacy, Cookies policies will be set in English and may need to be changed for demos in other languages

• the Product Team will provide the CX team with translations for T&Cs and Privacy Policies.

• Custom Homepage feed headings will default to the language they are created in.

• Content will default to the language it was created in, including quick links.

• Resources will default to the language they are created in.

• Yes, Custom text will be used in all the same situations custom text is currently used.

• It appears the (date) formatting on the 'Upcoming Events' carousel has changed on WebNG Home Page. Though this is not consistent across all sites.

• Yes, this is an intentional change as part of the localisation of webng.

• As part of the localisation project, we are migrating to a standard set of value formats, and these changes are deployed to production as they are implemented (you may have previously seen similar value format changes in Equiem One and VMS).

• The web-ng homepage is now internationalised (not the other pages yet but they will), and this includes date/price/number/etc. formatting.

• The most common standard value formats are documented in the Style Guide confluence space here: https://equiem.atlassian.net/wiki/spaces/SG/pages/1254228053/Localis+z+ation

Can I please check if vendors will still be able to access the VMS from the URL https://eu.vendor.getequiem.com?

Yes of course they can. We are talking about new clients here who will require the localisation.

What happens when a new vendor is registering? Do they get the opportunity to pick their language on the VMS registration process?

No, the vendor would need to get assigned the Workplace Manager role in EQ1, select their preferred language (Polish/French/German/English) and it will carry through to VMS, otherwise, VMS will follow the default language for the site.

For new or migrating customers (short term) - we currently have the following regions in Iris, are we happy that EU clients will go into the UK bucket? Or are we creating a new bucket for EU customers, or renaming the existing bucket?

the renaming of UK to EU will be half a day of work. I am going to be transparent, I would prefer not to use dev's time to do this right now we have still a lot to do for Essentials. Can I ask you how crucial it is for you and if it can wait until early next year? I am afraid this one will need to be later, probably more around March if I am realistic with our backlog.

Is the Check-in app localised?

The Check-in app is not localised.

https://checkin.staging.getequiem.com/

Does the end-user browser translation work on a mobile app? If not, then my assumption would be that we'd need these docs in any languages we're doing for localisation.

The simple answer is no. A mobile app does not work like a website and cannot get translated by your browser because it's an independent system.

what's the future plan for localisation in terms of user generated content? In particular, marketplace is very user-generated content heavy, how do we anticipate enabling someone to be able to understand deals, things for sale, bookable events etc? This is particularly important for sites looking to deliver dual languages. I tried to check the Confluence release notes for what is still come, but I can no longer access (?); there's also limited info on next phase of Localisation the roadmap so I wasn't able to self-serve to answer this question.

Andrew and I are currently running i a discovery on best practices to handle end-user generated content rendered in multiple languages.We have had calls with the SpaceOS team to learn from their experience and the limitations with their current solution.As we are sprinting currently with a lot of "hot" deliverables before December ends, I will not be able to provide you with detailed plans.The only thing I can say is, it is on our radar and we are in a learning phase. Any best practice that you can know of in terms of a content management system handling end user content generation in multiple languages, please share with us.The ideal state is, at a page level, the user is able to automatically generate content in multiple languages using machine translations. If the content is not auto-generated, there is a big chance that some users will only provide the content in one language and end-up with patchy sites which I would like to avoid. Stay tuned and any info you have, please shoot them through.

something else that is hard coded in Iris is content Categories e.g Deals, Nearby, Community etc. These display on the content underneath the title. Just checking if this is on your radar already?

There's actually a UI for managing this in Iris but it's only available to Super admins. New ones can be added, or existing ones amended, but this list is global and was curated by the content team so I wouldn't make any changes without consent of the CX/Content team.

have the check in SMS messages been considered for localisation?

For Check-In and Store SMSes, the body is hard-coded strings. We will localise this the same way we do emails so coming soon.For Iris, the body is client-generated content, so they should enter it in the default language of the site. (

I have 1 question for WebNG localisation - the 2 customisable menu items "My Building" and "Store" have been left as the default name in Admin Panel but have not been localised when I switch my language to German for Die Macherei München site, so they are still pulling the English on WebNG. Should these be being updated or does this still technically count as user-generated content (because it is possible to change these)?If we need to add manually, so be it, I just need the translation for "my building" confirmed and added to the glossary. Store is already on there.

These are user generated content - you need to input the names in German in Admin Panel. 

Are roles localised in the New User invite when you pre-assign a role in the New User Invite widget?

No, roles are not translated because hard coded