Problem/Motivation

The issue is that if the text format or other non translatable properties are concatenated into the source, then it cab create confusion, its not correct and when you use the copy functionality, it will appear in the translated value.

Steps to reproduce

  1. enable babel_content_entity
  2. in /admin/config/regional/babel/settings/content-entity under Content Entity -> EntityTypes select taxonomy term, save
  3. create a term with a name and description
  4. go to /admin/config/regional/babel and search for the descitpion value
  5. you should see the description value under source, but you will also see the text format

Proposed resolution

Fix

Issue fork babel-3585377

Command icon Show commands

Start within a Git clone of the project using the version control instructions.

Or, if you do not have SSH keys set up on git.drupalcode.org:

About issue forks

Comments

andras_szilagyi created an issue. See original summary.

andras_szilagyi opened merge request !84

huzooka’s picture

huzooka
Primary language Hungarian
Location Hungary 🇭🇺🇪🇺
commented
Related issues: +#3580366: Create strategy to handle translation of multi-column fields

Connecting dots.

alorenc’s picture

alorenc
Location Wolsztyn, 🇵🇱
commented

MR did not my issue

I wanted to translate the term, but I see problems when I translate the Barbell UI once and then the default UI

alorenc’s picture

alorenc
Location Wolsztyn, 🇵🇱
commented
Status: Active » Needs work
andras_szilagyi’s picture

andras_szilagyi commented
Status: Needs work » Needs review

Fixed

alorenc’s picture

alorenc
Location Wolsztyn, 🇵🇱
commented

It works for me but I have added some suggestions

alorenc’s picture

alorenc
Location Wolsztyn, 🇵🇱
commented
Status: Needs review » Needs work
andras_szilagyi’s picture

andras_szilagyi commented
Status: Needs work » Needs review

Fixed thank you

alorenc’s picture

alorenc
Location Wolsztyn, 🇵🇱
commented
Assigned: andras_szilagyi » alorenc
alorenc’s picture

alorenc
Location Wolsztyn, 🇵🇱
commented
Assigned: alorenc » Unassigned
Status: Needs review » Reviewed & tested by the community
huzooka’s picture

huzooka
Primary language Hungarian
Location Hungary 🇭🇺🇪🇺
commented

This is not the right solution to the problem, only a workaround.
There might be field types where not just the main property is translatable (text with summary), and there are field types where main property makes no sense to be translated, but the other properties do (file).

The change what you just did made the file fields' description non-translatable.

So, this causes a regression in case of file fields.

claudiu.cristea’s picture

claudiu.cristea
Primary language Romanian
Location Arad 🇷🇴
commented

Let's accept this workaround for now (we're still in alpha) and provide a proper fix in #3580366: Create strategy to handle translation of multi-column fields

claudiu.cristea’s picture

claudiu.cristea
Primary language Romanian
Location Arad 🇷🇴
commented
Status: Reviewed & tested by the community » Fixed

Thank you

Now that this issue is closed, review the contribution record.

As a contributor, attribute any organization that helped you, or if you volunteered your own time.

Maintainers, credit people who helped resolve this issue.

huzooka’s picture

huzooka
Primary language Hungarian
Location Hungary 🇭🇺🇪🇺
commented

This is not just a workaround, as I wrote in my previous comment:

The change what you just did made the file fields' description non-translatable.

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.