Translation and optionally changing terminology

Created on 19 January 2023, almost 2 years ago

Problem/Motivation

We should support translation of the bpmn_io interface. And while we're doing that, we may also consider "translate" BPMN-english into Drupal-english. There has already been a discussion about domain specific terminology in #3272871: Adjust Drupal terminology .

Proposed resolution

To see what's possible, I've started a discussion in the BPMN forum at https://forum.bpmn.io/t/domain-specific-terminology-and-translation/8674

It turns out, there is a translation package at https://github.com/bpmn-io/bpmn-js-i18n which provides half a dozen languages. But that package also provides support for a custom translation implementation. We could use the latter to utilize the Drupal t-function and therefore would be able to use Drupal's generic translation API. That would allow us to support all languages easily.

This way, we could also translate from BPMN-english into Drupal-english, if we wanted to.

📌 Task
Status

Active

Version

1.1

Component

Code

Created by

🇩🇪Germany jurgenhaas Gottmadingen

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.

No activities found.

Production build 0.71.5 2024