Compare language translation UIs to adopt consistency where useful

Created on 20 May 2013, almost 12 years ago

Updated 3 February 2025, 3 months ago

Problem/Motivation

Creating many UIs for translation tools, needs high-level review to recommend a cohesive user experience.

Proposed resolution

Simple design of three different interfaces to make translating consistent across different interfaces, CSS changes, may need some larger changes, will see.

Add direct links to "Language" (admin/config/regional/language) configuration page to other multilingual pages - such as:
Content Language Settings (Add / Edit Content Types and other Entities that need to be translated) = admin/config/regional/content-language
User Interface Translation (Directly translate parts of the Drupal User Interface) = admin/config/regional/translate

Add a joy ride to explain different editing options. (See issue: http://drupal.org/node/1998516)

Remaining tasks

Recommendations and layouts as needed.

User interface changes

This is what we're working on!

API changes

TBD

Important to Note

There seems to be a consensus that having all translation functionality for one language (or even for all of Drupal) in one place would be the most user friendly ("I've added Spanish, now I want to change everything to Spanish - where can I see that?"). However, this is not likely to happen for core because of the need for context in translations (Where is this string coming from?). Instead we will need to rely on "education" and good documentation to help people make sure they have changed everything. A good tutorial in documentation is essential.

Reference Links:

node/1#overlay=admin/config/regional/translate
node/1#overlay=node/1/translations&overlay-context=node/1
en/admin/config/regional/language/detection/url

📌 Task

Status

Postponed: needs info

Version

11.0 🔥

Component

content_translation.module

Created by

🇺🇸United States kristindev

Live updates comments and jobs are added and updated live.

D8MI
(Drupal 8 Multilingual Initiative) is the tag used by the multilingual initiative to mark core issues (and some contributed module issues). For versions other than Drupal 8, use the i18n (Internationalization) tag on issues which involve or affect multilingual / multinational support. That is preferred over Translation.

language-content

stale-issue-cleanup
To track issues in the developing policy for closing stale issues, [Policy, no patch] closing older issues

Incomplete comments

Comments & Activities

Not all content is available!

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

Comment 3 months ago →
🇺🇸United States smustgrave
Thank you for creating this issue to improve Drupal.

We are working to decide if this task is still relevant to a currently supported version of Drupal. There hasn't been any discussion here for over 8 years which suggests that this has either been implemented or is no longer relevant. Your thoughts on this will allow a decision to be made.

Since we need more information to move forward with this issue, the status is now Postponed (maintainer needs more info). If we don't receive additional information to help with the issue, it may be closed after three months.

Thanks!
Status changed to Closed: outdated 4 days ago2:20pm 5 May 2025
Comment 4 days ago →
🇺🇸United States smustgrave
Since there has been no follow up in 3+ months going to close out, but don't worry we can always re-open!

Thanks all

contrib.social Blog FAQ Discussions

Production build 0.71.5 2024