talque
  • External integrations for talque
  • JSON API (readonly)
    • General
      • Locales and Text
    • Organization
      • Read
    • Lecture
      • List
      • Read
      • Files
      • Authorization
    • Speaker
      • List
      • Read
      • Authorization
    • Participants
    • Vendors
      • List
      • Read
      • Authorization
    • Room
      • List
      • Read
    • Enumerations
      • Locale
  • Deep links
    • General
    • Organization
    • Profile links
    • Lecture links
    • Partner links
    • Post links
    • Map links
    • Video rooms
  • Webhooks
    • General
    • Authentication
    • File upload
    • Users
    • Invites
    • Tickets
    • Vendors
      • Create
      • Update
      • Delete
    • COMING SOON: Announcements
    • COMING SOON: Lectures
    • Map Data
      • Map layer
      • Map features
      • Update references
  • COMING SOON: Chat Bots
  • Wordpress Plugin
    • Installation
    • Pages
    • Shortcodes
      • Filters
      • Optional settings
    • Routing
    • Configuration
  • Javascript plugin
    • Introduction
    • Installation
      • Initial page
      • Filters
      • Optional settings
    • Routing
    • Configuration
  • Single Sign-On
    • OAuth2 Login
    • Website data
    • OAuth2 Flow
      • Request an Authorization Code
      • Exchange for Access Token
      • Authorized Requests
  • SELF-SERVICE LINKS
    • Event Ticket Token
  • Old Wordpress Plugin
    • Download
    • Pages
    • Shortcodes
    • Filter Options
    • Style Options
  • Old Javascript Plugin
    • Introduction
    • Routing
    • Installation
  • Troubleshooting
    • Firewall Configuration
  • Talque Plugin
    • Download
    • Installation
    • Configuration
Powered by GitBook
On this page

Was this helpful?

  1. JSON API (readonly)
  2. General

Locales and Text

PreviousGeneralNextOrganization

Last updated 1 year ago

Was this helpful?

All records contain text that must be displayed different for different user locales, this is always encoded in a JSON dictionary of the form

{
    "DE_DE": "Deutscher Text",
    "EN_US": "English text"
}

The user agent should render the field using the appropriate locale (JSON object key) for the user. If that key is absent, the organization primary locale should be used. If that is absent as well, an arbitrary value should be used. The object might be empty to indicate that the optional field is not filled out and should be hidden by the user agent.

The currently supported locales are listed in the section

Locale