Contrib.social

Turn formality into a checkout setting

Open on Drupal.org →
Created on 17 March 2024, 3 months ago
Updated 15 May 2024, about 1 month ago

Problem/Motivation

When translating website content from English to both Dutch and German, if your brand is sort of innovative (e.g. you're a start-up') you will choose to use informal "Je" in Dutch. However, in German it's not equally as acceptable to use the informal "Du" in place of the formal "Sie".

This idea is supported in real life website.

Example:

Dutch using Je: https://salesforce.com/nl
German using Sie: https://www.salesforce.com/de/

There are also B2B sites that use "Du" but I think it would be great to leave the decision up to the translator. You may also want to translate more formal on your landing pages and less formal on blog pages, or leave it to automatic when translating user-generated content.

Steps to reproduce

Proposed resolution

Let translators override the formality setting in the translation checkout panel

Remaining tasks

User interface changes

Add a form element to the checkout panel

API changes

Data model changes

✨ Feature request
Status

Needs review

Version

2.2

Component

Code

Created by

🇳🇱Netherlands JurriaanRoelofs

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

Merge Requests

Comments & Activities

  • Issue created by @JurriaanRoelofs
  • Comment 3 months ago →
    🇳🇱Netherlands JurriaanRoelofs
  • First commit to issue fork.
  • Assigned to SteffenR
  • Comment 3 months ago →
    🇩🇪Germany SteffenR Germany
  • Merge request !20#3430285: Turn formality into a checkout setting → (Open) created by SteffenR
  • Issue was unassigned.
  • Status changed to Needs review 3 months ago
  • Comment 3 months ago →
    🇩🇪Germany SteffenR Germany

    @JurriaanRoelofs
    Some time ago, there was a similar issue concerning the formality level per language. But the suggestion to add the selection right to the checkout process makes more sense.
    Please test the MR and give feedback in this issue.

    Testing instructions

    • run database udpates to get default values for new config setting override_formality
    • ensure, that new checkbox Allow override of Formality in checkout is available in configuration form of the DeepL translator
    • if Allow override of Formality in checkout is enabled, you'll be able to set the formality level while checkout
    • ensure, that the override has an effect on the translations
  • Comment about 1 month ago →
    🇩🇪Germany SteffenR Germany

    @JurriaanRoelofs
    Did you find time testing the Merge Request?
    Besides asking for new features, it would be great, if you could help testing issues ;)..

contrib.social Blog FAQ Discussions
Production build 0.69.0 2024