Translations

Where

The areLanguage Translations Supported

feature

Currently,allows translationsadministrators areto onlymanage supportedmulti-language onsupport and customize specific terminology displayed across the user side,portal. however,Its theyprimary purpose is to ensure that all user-facing text, labels, and system messages are managedaccessible and setalign upperfectly onwith your organization's local terminology (e.g., changing the adminword side, by admins that have the correct permissions set up"ticket" to work"citation"). withThis languages. 

localization.

NavigatingSetup toand TranslationsConfiguration

To begin reviewing, editing or creating your translations/languages, you will need to navigate to System Config → Content & Designs → Translations.

This willfeature takeis youa core administrative tool used to the Installed Languages page where you can begin managing your current languages.

Adding New Languages 

To begin adding your own languages simply click Add Language ondictate the Installedtext Languages page which will bring up a new modal to add a label and locale.

When you are finished click Save Changes and your new language will be instantly added to the list. Once the language has been added, your users can begin using itdisplayed on the user-side assumingportal.

you

Admin Side: Administrators must have the appropriate system role permissions enabled to manage language enabled.settings and edit translations.

1. Hover over System Configuration, click Content & Designs, then Translations to access the Installed Languages page.

User Side: The translation configurations directly control the language options and specific wording available to end-users navigating the parking portal.

TheWhen localesreviewing the translation list in the backend, translations displayed in black text are usedactive whenon wethe wantuser side and can be freely changed. Translations displayed in red text are located on the admin side and are not currently supported for localization; they will remain in English until admin-side translations are fully supported.

Using this Feature

Administrators can use the following instructions to add new languages, create localized sub-languages, whileand manually edit specific terminology across the label is used to identify our translations throughout the site. system.

Adding Sub Languages

Installing and HowAdding doLanguages

They

Work

• Sub-Install Default Languages: If base languages like English or French are createdavailable bybut usingnot ayet locale that currently exists with an underscore '_' followed by the sub-language that you want to set up.

  

  For example,installed, you can supportinstall multiplethem variationsdirectly ofto the English language for your users. In the image below I have createdload a sub-languagecomplete forpreset American English using the locale en_us.

  

  When you create a new sub-language, it will automatically use the translations that have been set up on the main language, which is the locale on the left side of the underscore, such as en_us. You will need to create the main language first before creating any sub-languages, otherwise the sub-language will always default to English instead of the main language you may have intended to use. 

  Installing Languages

  Installing a language will create a new languagetranslation template with thea translationsdefined weName haveand setLocale.

  up
for
• it

  Add asCustom wellLanguages: asClick the NameAdd Language button to bring up a modal. Enter a custom label and Locale we have created for you. You canlocale, then click EditSave TranslationsChanges. toThe adjustlabel identifies the presettranslation translationsthroughout tothe yoursite, liking.while Ifthe therelocale is notused afor languagesystem alreadyidentification.

  in

• Enable or Disable Languages: Toggle the system that can be installed you will need to add a new language and setup the translations yourself. Currently, we only support the ability to install French and English.

  

  Disabling or Enabling Translations 

  We can choose to disable particular languages that we don't want to be selectable from the user side. To do this we can toggle the visibly of our languagesswitch under the Enabled column on the Installed Languages Page.

  page.

  

  OnceDisabling a language isimmediately toggledremoves it as a selectable option for end-users on the portal.

Adding Sub-Languages

Sub-languages allow you to support regional variations (e.g., American English vs. British English).

1. Ensure the primary "main" language is already created and installed.

2. Click the DisabledAdd Language button.

3. Enter the existing main locale, followed by an underscore _, and the sub-language identifier (e.g., entering en_us for American English).

4. Click Save Changes. The sub-language will automatically inherit the translations set up on the main language.

Editing Translations and Terminology

The translator is not just for foreign languages; it canis noessentially longera belist selectedof bycode terms and their corresponding display text, allowing you to easily replace local terminology (e.g., changing "ticket" to "citation" everywhere on the users of your site as seen in the example image below.portal).

1. 

   Click

   Searching LanguageEdit Translations

   You can search for all translations that relatenext to a language.

2. Enter a specific word or component in(e.g., the"permit" systemor using"ticket") into the search bar at the top right ofto filter the Editlist.

   Translations
page.
3. For

   Click example,the wespecific cantext searchbox for permitsthe term you wish to find all permit related translations.

   

   We can also go onto the user sidemodify and usetype the Token language, which will show all of the Names found on the Edit Translations page, under the Name column, (See the image above) to find where that translation exists so it can be changed. This can't be seen by logging is as the user from the user side but requires an admin to go to the profile of a user and click the Login as User button from the admin side. This is to ensure thatin your regularpreferred userslocalized don't see the token language option.text.

   

4. The token language finds the tokens used so you can better search where the translations are being used on the user side.

   Edit Translations

   To begin editing language translations you have to make your changes and then clickClick away from the input field. OnceThe you do this youtranslation will see that the translation gets highlightedhighlight in yellow indicatingto thatindicate aan changeunsaved haschange, beenand made. Thethe number of affected records will also display at the bottom of the translations page.
   

   

5. WhenClick you are finished making your changes clickthe Save Changes forbutton to apply the updatetext toupdates take effect. 

   Delete Languages

   To delete languages, you can clickacross the delete button next to the language you want to remove. Keep in mind that if you remove the base English and French language it can be re-installed. However, if you delete a language that we do not provide you, then this data will be lost and you will need to contact support for assistance with recovering these translations.system.

   

Keep

in mind that deleting a language will not delete any of the sub-languages you may have created. For example, if I were to delete English, the English US language would still remain with all of its translations.

Creating Templates and Messaging for New Languages

It's important to note that whenWhen you create a brand new languagecustom language, it will not automatically rely on the default templates and system messaging thatset you have setupup for your previous languages. For example, if I use the new French American language I created, and go onto the user side where languages are supported, then IThey will see aappear blank templateuntil as well as blank messages.configured.

Adding Templates

1. ToHover addover aSystem newConfiguration, templateclick forContent your& languagesDesigns, that you create you will need to go intothen Templates & Design.

   followed
by

2. Click Toggle Templates for the templates that are currently being used.

   From
there
3. you will have the option to click

   Click the Create button to add the new template.template If you just wantfor your newlanguage, or click Edit on an existing language to use the same template, from a language that is already in the system, just go into Edit and copy theits text over intoto yourthe new language,one.

   after
clicking
4. the

   Hover over CreateSystem Configuration, button.
   

   click

   

   Content

   Adding& Designs, then System Messages

   .

5. System messaging will work a bit differently than templates as you will need to go into each individual message and clickClick the Edit button next to thatan message.

   individual

   

   From there you should be able tomessage, select your new language.

   

   If you want multiple messages to display for all your languages you will need to create a new system messagelanguage, and type out the translationslocalized translation.

---

Best Practices and Considerations

• Use the Token language for thattroubleshooting: Use the "Token" language template. 

  Changing Terminology Usingon the Translatoruser side to easily identify exactly where a translation exists so it can be changed. To do this securely, navigate to a user's profile on the admin side and click the Login as User button. Switching to the Token language reveals the backend code names for every text element on the screen. Regular users cannot access the Token language.

• ThereEstablish the main language first: You must create the main language first before creating any related sub-languages. If the main locale is another use formissing, the translationsub-language toolwill fail to inherit the correct text and will default back to standard English.

• Protect custom language data: Be aware that maydeleting a custom language permanently removes its data, requiring OPS-COM support to recover. While base languages like English and French can be easily re-installed, custom entries cannot. Note that deleting a main language will not bedelete obviousits atassociated first.sub-languages.

  Since
the
• translator

  Leverage isbulk essentiallyterminology aupdates: listWhen ofediting code terms and a corresponding list of what is actually displayed on any page not only can you edit the various languages but for each language you can also edit the display termterminology to fit a local "version"phrasing, of the term. A perfect example of this is in some areas one might refer to receiving a "ticket" as receiving a "citation". It is entirely possible to replace any spot in the interface where the term ticket is used with the term citation.

  To do so go into the language editor and search for the term you wish to localize. In our example simply enter ticket in the search bar and hit return. A list ofupdate all translatable instances of the word ticketbefore saving. Searching for a term like "ticket" will appear.pull Clickup theall boxtranslatable whereinstances the(e.g., term is editable and type in your preferred term. In this case we are changing Manage Ticket Categories, toPay Manage Citation CategoriesTicket). OnceEditing youthem saveall at once ensures complete consistency across the changesuser you have made the displayed text associated with Manage Ticket Categories will display as Manage Citation Categories throughout the system. You may edit the remaining instances of the word Ticket that are in the list before saving to change the term in bulk for all entries listed.portal.