Contrib.social

Installation profiles should consume both Drupal core AND profile-specific .po translation files during installation

Open on Drupal.org →
Created on 5 April 2014, about 11 years ago
Updated 13 March 2025, about 1 month ago

Problem

  1. For a custom installation profile, there is only one way to use both Drupal core's and custom translations:

    The maintainer (?) has to manually run msgmerge to merge the Drupal core translations into an own .po file whenever the core translations have changed.

  2. This must be re-done if either the Drupal core OR the custom translations are changed in any way.

  3. The only workaround is to publish the custom installation profile on drupal.org, so that localize.drupal.org's inheritance mechanism becomes available. But not every installation profile is meant to be published publicly.

  4. The corresponding D7 code actually appears to read-in multiple .po files for a given language code.

Proposed solution

  1. Add an .info.yml file property for installation profiles to signal whether the profile's translation file is partial; e.g.:

    locale_translation_partial: true

  2. If TRUE,

    1. always download translations for Drupal core from the translation service (defaults to l.d.o).
    2. assume that a custom .po file exists in the profile's ./translations directory (do not attempt to download translations for the installation profile).

  3. Make the file translator service read-in the both (or all) locally available translation files for the selected language code.

📌 Task
Status

Postponed: needs info

Version

11.0 🔥

Component

install system

Created by

🇭🇺Hungary boobaa

Live updates comments and jobs are added and updated live.
  • distributions

    Used in Documentation issues for documentation of distributions

  • 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.

  • stale-issue-cleanup

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

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.

  • Comment about 1 month 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!

contrib.social Blog FAQ Discussions
Production build 0.71.5 2024