Versions Compared

Old Version 1

changes.mady.by.user Alex Do (Unlicensed)

Saved on

compared with

New Version 2

changes.mady.by.user Alex Do (Unlicensed)

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Tip

Also known as “Europe Launch” stage 2.

Release Date

1 November 2023

Application

WebNG

System URL

<site URL>

Related Articles

Overview

Expand
titleLanguages provided with stage 2:

  • English

  • French

  • German

  • Polish

Info

If a new language is needed, please use #localization-help

...

Expand
titleWhat's the difference between System Generated Content and User Generated Content?

Reference: https://equiem.monday.com/docs/5144582138

  1. What is System Generated Content ?

The content that is automatically generated or populated by a software. 

System-generated content often includes user interface elements, error messages, system prompts, placeholders, and other text strings that are dynamically generated based on system settings or user interactions.

  1. What is User Generated Content ?

User-generated content generated through site configuration and ongoing contributions from the client and its users.

  • Admin Users

    • During the creation of a site, a site administrator configures various elements including buildings, levels, apartments, companies, resource types, and more.

  • End Users

    • Any form of content, such as images, videos, text, testimonials, and audio, that has been posted by users on online platforms.

...

Expand
titleWhat the hierarchy of languages ?

  1. Language Picker in end user interface
    If the user selects a language from their language picker, it will prevail over the default site language if it is available.
    e.g. my default site language is in German, I chose French in my language picker.

  2. Default Site Language defined in Admin Panel
    If the language the user selects in their site picker is not available for that application or parts of the application, the application or parts of the application will default back the default site language.
    e.g. my site is in German, I chose French in my language picker but French is not available for Inviting Visitors, the interface for inviting visitors will remain in German.

  3. English US Fall back
    If the default site language is not available for the application or parts of the application, the application or parts of the application will fall back to English.
    e.g. my site is in German, the translation for confirmation message for inviting a visitor is not translated in German, the email for inviting visitors will remain in English.

Expand
titleWhat demo site can I use?

The shell of the Commercial EU platform is available here: https://commercial-eu.web.getequiem.com/

Next steps:

  • Decide who needs permissions to manage this on an ongoing basis

  • Decide what content - news, events, info and quick links - and in what languages, you want to add to get started

  • Decide if you want any custom content feeds addedg. for segmentation/visitor mgmt receptions etc)

  • Decide what resources, and in what languages, you want to add to get started

  • Decide what vendors, and in what languages, you want to add to get started

  • Decide how you will manage the above "things to note" elements on the platform when changing languages for demos

FAQs

Question

Answer

  • 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 localized.

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

  • 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 localized the defaults, and localized 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 localized. As these are customizable fields, do these only localize if they are left as the default titles, or can these be overridden and still localized, or do we need to localize these titles directly in Admin Panel?

  • As mentioned above, defaults are localized, if you override them, then they become custom fields and are not localized, 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 localization of webng.

  • As part of the localization 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.

Note

Until the localisation og WebNg is complete, internal Equiem users might notice inconsitencies, this is linked to the fact they access to sites across different regions and locale.

If you only have web-ng access, your User locale preference will be initialized with the default locale of whichever site you logged into first after the localisation framework was added

e.g. If I register with a US webng site, and then register with a UK webng site, I will see that UK site in US English.

(because user locale preference is user scoped, not user-site scoped)

e.g. if I log into Commercial, and select German, then log into Equiem Tower, I will see Equiem Tower in German.

Our end users will almost exclusively use one site, or sites in the same region. The only real external users who will notice this are client staff managing sites across different regions.

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 localization.

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.

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.

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

No, the roles are not translated because they are hard coded at this point. Groups will be picked up in the language they have been included in Admin Panel.

The 2 customizable menu items "My Building" and "Store" have been left as the default name in Admin Panel but have not been localized 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)?

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

...