I installed German Drupal 8.5.3 and enabled English as second language. I changed the language names from German to de and English to en, path drupal/admin/config/regional/language/edit/

Now, German is labeled de but English is still labeled English. This is a bug I reported already very long ago! Please see the screenshots too.

CommentFileSizeAuthor
Bildschirmfoto 2018-05-02 um 14.49.57.png118.08 KBAnonymous (not verified)
Bildschirmfoto 2018-05-02 um 14.49.33.png151.54 KBAnonymous (not verified)

Comments

Anonymous’s picture

20 Drei created an issue. See original summary.

cilefen’s picture

Was this forum topic the original report?

If yes, forum topics are not bug reports. They are discussions. This is a bug report.

Anonymous’s picture

Yes, this is a bug report. This problem still occurs in Drupal 8.5.3 but I fixed it now following Ismail Cherri's suggestion in that discussion.

Version: 8.5.x-dev » 8.6.x-dev

Drupal 8.5.6 was released on August 1, 2018 and is the final bugfix release for the Drupal 8.5.x series. Drupal 8.5.x will not receive any further development aside from security fixes. Sites should prepare to update to 8.6.0 on September 5, 2018. (Drupal 8.6.0-rc1 is available for testing.)

Bug reports should be targeted against the 8.6.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.7.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.6.x-dev » 8.8.x-dev

Drupal 8.6.x will not receive any further development aside from security fixes. Bug reports should be targeted against the 8.8.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.9.x-dev branch. For more information see the Drupal 8 and 9 minor version schedule and the Allowed changes during the Drupal 8 and 9 release cycles.

rishabhthakur’s picture

Version: 8.8.x-dev » 8.9.x-dev
nicrodgers’s picture

Status: Needs work » Closed (cannot reproduce)

I've been unable to reproduce this, I've tested 8.9.0 and 9.0.0. Closing. Feel free to re-open with steps to reproduce, if it's still a problem.

drupaldope’s picture

still an issue in 10.2.4

drupaldope’s picture

Status: Closed (cannot reproduce) » Active
cilefen’s picture

Status: Active » Postponed (maintainer needs more info)
Issue tags: -language, -multilingual +Needs steps to reproduce
drupaldope’s picture

Needs steps to reproduce

As the OP mentioned, the steps to reproduce, as of Drupal 10.2.4 are:

- install Drupal using for example German as a first default language
- enable English
- do some stuff, create content, etc.
- enable UI, config and content translations

(maybe all of the above steps aren't necessary to reproduce the bug)

then:
- go to languages /admin/config/regional/language and change the label of both languages, for example, name Deutsch "de" and English "en"

maybe it will first appear to work. maybe not.
if you do something else, like adding content in one or the other language, one might jump back to the original name "Deutsch" or "English".

The strange thing is that the YML config item shown by DEVEL is all correct.

If trying to add translations to the language names, an error message will appear "English translation was not added. To add a translation, you must modify the configuration."

Sometimes there is no error message, and the translation seemingly gets accepted, but the name of the language will jump back to the original anyway, even if on the languages page /admin/config/regional/language everything seems normal and both are displayed as "de" and "en", but either Deutsch or English will appear as its original name no matter what settings.

after doing something else on the site, ONE of the labels on the languages page /admin/config/regional/language will revert back to original.

it's very frustrating.

this bug has been going on for years and has been reported in one form or another many times.

I wrote more about it here:
https://www.drupal.org/project/drupal/issues/3337864#comment-15540567

cilefen’s picture

If there are two issues and the other has more information we should close this as a duplicate.

drupaldope’s picture

there are a dozen or so of related issues, maybe more if counting those logged to other modules where users believed the bug isn't in core.

pameeela’s picture

Version: 8.9.x-dev » 11.x-dev
pameeela’s picture

@DrupalDope are the issues related or duplicates? If they are duplicates, it is more likely to be resolved if all but one are closed, so that all work is being done toward the same resolution.

drupaldope’s picture

@pameeela
if I knew if the bugs were related or duplicates, it would mean I knew the exact nature of the bug, but I don't.
I spent hours on the problem trying to figure out what is wrong, but wasn't able to pinpoint the problem.

anaconda777’s picture

quietone’s picture

I have been unable to reproduce this problem on 11.x HEAD today. I tried 3 cases;

  • standard install in English and then added a second language
  • standard install in Italian then added a second language
  • Umami

In all cases I was not able to reproduce the problem where the translated name for 'English' , which was 'xy', was changed to "English".

It is not clear to me if this is a problem with the language switcher block. If it is, then this should be closed as a duplicate of #2797961: Language switcher label cannot be changed for English

drupaldope’s picture

@quietone

the issue is in language admin, not the switcher block.

did you follow the steps described here?
https://www.drupal.org/project/drupal/issues/2797961#comment-15629652

Version: 11.x-dev » main

Drupal core is now using the main branch as the primary development branch. New developments and disruptive changes should now be targeted to the main branch.

Read more in the announcement.

quietone’s picture

Priority: Major » Normal
Status: Postponed (maintainer needs more info) » Closed (outdated)
Issue tags: +Bug Smash Initiative

I tested again on 11.3.6 using the steps here and those in the other issue. Again I could not reproduce the problem. I also tried to reproduce the problem with the language switcher and failed.

I see this is tagged as major. I don't think an incorrect label is a significant bug and there is workaround, an admin must reenter the translation.

The comment in the other issue states that the problem exists in 10.2.6. So, it was fixed in 11 but not backported. I don't know what issue it was fixed but the decision to back port is made at the time of the commit according to our backport policy.

Therefore closing as outdated.

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.