Using Liquid markup to support multiple languages in automations, macros, and triggers (Professional and Enterprise)

Have more questions? Submit a request

6 Comments

  • Thomas Joussot

    This might sound like a dummy question but is there any advantage using Liquid markup in such a case instead of Dynamic Content when dealing with multiple langages ?

    1
  • Adam Reid

    Hi Aimee,

    Thanks for this wonderful example with Liquid markup. I've tried using your example but it always defaults to the last else statement.

    Are you using the short or long versions of the language codes?

    0
  • Adam Reid

    This is currently what I'm using and it's returning only the last else.

    {% case ticket.requester.language %}

    {% when 'Japanese' %}

    Ciao {{ticket.requester.first_name}} - Japanese

    La tua richiesta (#{{ticket.id}}) è stata ricevuta, è stato esaminato dal nostro staff di assistenza.

    Per esaminare lo stato della richiesta e aggiungere ulteriori commenti, segui il link qui sotto:
    http://{{ticket.url}}


    {% when 'Spanish' %}

    Hej {{ticket.requester.first_name}} - Spanish

    Din anmodning (# {{ticket.id}}) er blevet modtaget og bliver gennemgået af vores supportmedarbejdere.

    At gennemgå status for anmodningen og tilføje yderligere kommentarer, skal du følge nedenstående link:
    http:// {{ticket.url}}


    {% else %}

    Hello {{ticket.requester.first_name}}

    Your request (#{{ticket.id}}) has been received, and is being reviewed by our support staff.

    To review the status of the request and add additional comments, follow the link below:
    http://{{ticket.url}}


    {% endcase %}
    0
  • Brett - Community Manager

    Hey Adam,

    It looks like when specifying the locale name you need to do so in the local language. For example, Danish would be Dansk. If you take a look at the following comment by one of our community members it looks like you can capture this information using the API: Understanding Liquid markup and Zendesk Support

    Additionally, you may want to look into using Dynamic Content to provide multiple language support. This wouldn't require you to set up multilingual support via Liquid Markup and may save you a bit of a headache down the road.

    Hope this helps!

    0
  • Adam Reid

    Hey Brett,

    Thanks for your reply. That example worked perfectly. After running the API call I got these outputs and was able to grab the exact keyword to match.

    0
  • Brett - Community Manager

    Happy to help Adam :)

    0

Please sign in to leave a comment.

Powered by Zendesk