Multingual for ticket metadata
Pain point
TIXNGO V3 uses an implicit method for multilingual ticket details. As an organizer, you must set up many hidden keys for translations or translate later from the TIXNGO back-office, which can lead to human error.
TIXNGO V4 offers a direct method. You set up translations once in the S-360 ticket template, and you can easily adjust them from there.
How to set up?
The logical idea
For example, you served 10 slots for each language, and don’t worry if you don't fill all 10/10 slots. Not only defining key and value as V3, but on V4, you should also define key, value, and lang for each slot.
Sample format
ticketDetails.main.<slot number>.key
ticketDetails.main.<slot number>.va
ticketDetails.main.<slot number>.lang
ticketDetails.extra.<slot number>.key
ticketDetails.extra.<slot number>.value
ticketDetails.extra.<slot number>.lang
ticketDetails.hidden.<slot number>.key
ticketDetails.hidden.<slot number>.value
ticketDetails.hidden.<slot number>.lang
Sample setup
For example, you planned to have the ticket details information as follows
Slot number | Language | Main | Extra |
|---|---|---|---|
1 | English | Gate opening time | Original booker information |
2 | English | A welcome message | Re-entry policy |
3 | English |
| Information to spectator |
… | … | … | … |
10 |
|
|
|
11 | Spanish | Gate opening time | Original booker information |
12 | Spanish | A welcome message | Re-entry policy |
13 | Spanish |
| Information to spectator |
… |
| … | … |
20 |
|
|
|
And you also want to add the hidden feature
Slot number | Hidden | Note |
|---|---|---|
1 | Hospitality room information | Please don’t associate the hidden setup with a language |
Let's set up on the S-360 ticket template
How does the ticket look on the TIXNGO back-office & mobile app
In English
In Spanish
Additional information
The hidden setup that we add from the ticket template, which is not associated with a language, appears in the “Other” section.
© TIXNGO 2023 - Login