Settings form translation for code field

Created on 26 July 2019, over 5 years ago
Updated 27 January 2023, almost 2 years ago

Made the code field translatable. This way the Olark interface can be translated using the Olark API.

Added a patch.

Feature request
Status

RTBC

Version

1.0

Component

Code

Created by

🇧🇪Belgium dimitri.baudonck@gmail.com Ghent

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

Not all content is available!

It's likely this issue predates Contrib.social: some issue and comment data are missing.

  • 🇧🇪Belgium tim-diels Belgium 🇧🇪

    I see the benefits for this. For now the Olark configuration is indeed not translatable, so the script is the same for all languages.
    Seeing in the Olark documentation there are multiple ways to integrate languages. But allowing to translate the code snippet has more benefits in having customisable options per language.

    The normal string type is not translatable. So it must change to label or text.
    For the change to the text string subtype, I would say it is indeed needed as this could be a long string.

    Please see the explanation for common string subtypes:

    There are some purpose specific subtypes of the simple string type, particularly for UI generation and translatability purposes, such as:

    • label: short and translatable string
    • text: long and translatable string

    As review for the patch, I can say this works as expected.

Production build 0.71.5 2024