Languages / Translations
Proximi.io platform supports multi-language setup. The following items can be translated:
- Point of Interest names
- Segment names
- Information related to each Point of Interest and Segment
- Navigation instructions
Please note that Proximi.io has the capability of managing multiple translations, but we do not have any pre-existing translations available. Translations are to be produced by the customer/reseller or a third party, as selected by them. Just inform Proximi.io about which languages you will be using in your project, and we will setup your account to support those languages.
Translations on the editor
Translations for POI names, segment names and information related to those are handled in the wayfinding editor.
Translations on the guidance instructions
For providing the navigation instructions in text and speech, Proximi.io platform utilizes a list of strings. The list is currently 88 rows long, and looks like this:
"update_turn": "In {{distanceInt}} {{distanceUnit}} {{direction}}.",
"update_turn_left_hard": "turn hard left",
"update_turn_left": "turn left",
"update_turn_left_slight": "turn slight left",
"update_turn_straight": "continue straight",
"update_turn_right_slight": "turn slight right",
"update_turn_right": "turn right",
"update_turn_right_hard": "turn hard right",
"update_turn_around": "turn around",
"update_destination": "you will arrive at your destination",
To add new translations, request the most up-to-date translation files from Proximi.io team. We will then push an update of the library with those fixed.
To insert into your project:
- Add your translations json file into assets folder -> https://github.com/proximiio/ngx-wayfinding-client-v5-private/tree/master/src/assets/i18n
- Add new language in app.component.ts file -> https://github.com/proximiio/ngx-wayfinding-client-v5-private/blob/master/src/app/app.component.ts#L43
- If you want to catch language from url params, add new line here for the new language -> https://github.com/proximiio/ngx-wayfinding-client-v5-private/blob/master/src/app/app.component.ts#L39
Audio navigation
The audio navigation is produced on iOS by operating system level Text-to-Speech capability, and on Android through utilizing the pre-installed and pre-enabled Google Text-to-Speech application. You can find the list of supported languages through these links:
iOS: https://support.apple.com/en-us/HT206175
Android: Go to Smart assistance -> Accessibility -> Text-to-speech -> Speech services by Google (info button) -> Language to see the options.
Please note that as the audio is automatically produced, it does sound slightly robotic and pronunciation can be off sometimes - but it serves the purpose perfectly well. Our demo app picks up the language from the device language automatically. If you would want to add some manual selection for language, you should develop that yourselves.
Important note on Arabic and other languages using different alphabet
The default font in our maps, KlokanTech Noto font, has a bug relating to visualizing some of the letters of POI labels on the map. The issue is specific to mobile libraries, and can be seen with some letters at the beginning or end of words not being visualized. Issue occurs sometimes also with other languages using non-Latin alphabet, such as Russian and Hebrew.
The issue is fixed by changing the font used for the labels. We have had success with using the Amiri bold font. The font needs to be converted into pbf format and hosted on a server. If your project is hosted on our servers, contact us for setting it up. If you are self hosting your project, you are in charge of setting up the font correctly.