Not clear what happens when you enable 'Account administration pages' in Language > Detection and selection

I've updated the IS to better explain the situation, but I am not sure what the appropriate resolution is.

Could it be as simple as updating the description to say "User profile setting for administration pages language." or "Allows users to configure their administration pages language."?

I had the same issue while trying to set up multilingual site. It could be more helpful if the description contains more information, or a status message like "You can configure the settings on your profile edit page." is displayed after enabling it, or there is a configure button which takes the user to the profile page to configure the settings.

I've just been playing around with those settings. All the configure buttons on the page take you to page where site configuration is done so adding a configure button here to modify your own profile just seems wrong. The description text definitely needs improvement, it really doesn't convey what enabling that option does. I don't have any suggestions for the text. Maybe ask in #ux?

Also, when this is fixed the relevant doc page should be updated, https://www.drupal.org/node/3192982.

We discussed this issue at #3205081: Drupal Usability Meeting 2021-03-26. It is pretty clear that

• The current behavior is very confusing.
• The text in the Description column does not give any more information than the text already in the "Detection method" column.

As a first step, we suggest that you add a link to /admin/help/language, assuming that the Help module is enabled. The explanation there is not perfect, but it is pretty good:

Account administration pages follows the configuration set as Administration pages language on the profile page of an administrative user. This method is similar to the User method, but only sets the interface text language on administration pages, independent of the interface text language on other pages.

While you are at it, it might be a good idea to update that help page, putting the options in the same order as this page.

If you want to go further, then think of a way to improve the text on this page. There are two things we need to communicate:

1. The language can be configured for each (admin) user. It is configured on the profile page.
2. This setting only affects administrative pages.

Maybe we do not have to be more explicit in the UI than "administrative pages", but I am curious: does this setting affect every route that is declared as administrative? Most of the time, that means a path under /admin/.

The current text, "Account administration pages", does not convey either of these points. If you drop "Account", then it comes close to describing (2).

Personally, I think that (1) should be mentioned in the first column and (2) in the second column. I do not have any good suggestions for expressing (1) in 2-3 words.

@benjifisher I think column 1 can say "Administration pages"
and column 2 something like "Preferred language for administration pages(can be configured in edit profile)" .
Along with that, I strongly feel that the status message should describe what to do next eg. "You can configure administration pages language on your edit profile page." after enabling this option.

I agree with rest of the points i.e to add a link for help page and improve the help page, will create a patch for it.

• Added link to help page on detection and selection page
• Changed name from Account administration page to Administration pages.
• Changed description to Preferred language for administration pages(Can be configured on edit profile page).

I read the response from the usability review (#) and applied the patch and read through all the screens. My first thought is that this is so much better! And the patch does make changes for all the points in the review.

1. +++ b/core/modules/language/language.module
   @@ -43,16 +43,17 @@ function language_help($route_name, RouteMatchInterface $route_match) {
   +
   

   Remove added blank line.

2. +++ b/core/modules/language/language.module
   @@ -64,7 +65,7 @@ function language_help($route_name, RouteMatchInterface $route_match) {
   +      $output = '<p>' . t('Define how to decide which language is used to display page elements (primarily text provided by modules, such as field labels and help text). This decision is made by evaluating a series of detection methods for languages; the first detection method that gets a result will determine which language is used for that type of text. Be aware that some language detection methods are unreliable under certain conditions, such as browser detection when page-caching is enabled and a user is not currently logged in. Define the order of evaluation of language detection methods on this page. The default language can be changed in the <a href=":admin-change-language">list of languages</a>. Learn more about <a href=":help-page-link">detection and selection methods.</a>', [':admin-change-language' => Url::fromRoute('entity.configurable_language.collection')->toString(), ':help-page-link' => Url::fromRoute('help.page', ['name' => 'language'])->toString()]) . '</p>';
   

   The period is inside the tag instead of outside for the new link for detection and selection methods.'

3. +++ b/core/modules/user/src/Plugin/LanguageNegotiation/LanguageNegotiationUserAdmin.php
   @@ -21,8 +21,8 @@ use Symfony\Component\Routing\Matcher\UrlMatcherInterface;
   + *   description = @Translation("Preferred language for administration pages(can be configured in edit profile)")
   

   s/pages(/pages (/. No, looking at the screen again it might be better to be similar to the text for 'User' which is 'Follow the user's language preference.' Can this be 'Follow the user's language preference for administration pages.'? That way they are consistent in style and neither refers to where to configure the settings, it is implied. shriaas2898 commented that they felt the text should include what the user can do next to configure this setting. I am not convinced (but can be) for two reasons a) the text for User doesn't have it and b) an administrator is viewing this page and it is reasonable to expect them to know that user preferences are set on user profile pages.

The issue summary needs to be updated to include, at least, the proposed resolution.

@quietone I will change the first two points.

it might be better to be similar to the text for 'User' which is 'Follow the user's language preference.' Can this be 'Follow the user's language preference for administration pages.'?

I agree this will make the help text consistent, however we may need some more rephrasing, right now this one is little confusing, like what is the difference between User and Administration Pages or why changing User settings doesn't affect Administration Pages?

like what is the difference between User and Administration Pages

Yes, I had to read that page twice when I first saw it. And I have yet to figure out better language for 'Detection Method' and the items in that column.

or why changing User settings doesn't affect Administration Pages?

Not sure I follow. If I select 'User' and not 'Administration pages' then the entire site, including admin pages, uses my preferred language.

If I select 'User' and not 'Administration pages' then the entire site, including admin pages, uses my preferred language.

Oh! my bad, I was not aware of this behavior I thought User will not change language for admin pages.

@Shriaas just ran into these strange namings, are you still planning to make these fixes?