Add an indication of the language of the page in the footer. This enhancement improves accessibility and user experience by explicitly showing the language of the displayed content

[ChongZhe001025]

See JENKINS-62419.

Summary

This PR adds an indication of the language of the page in the footer. This enhancement improves accessibility and user experience by explicitly showing the language of the displayed content.

Justification

Even if some localizations are missing, showing a baseline language is useful for users. The locale field should be determined from the response page so that plugins like Locale Plugin are handled correctly. Reference to the Locale Plugin filter:
LocaleFilter.java

Testing done

• Implemented changes in Jenkins Core.

• Verified that the Request object returns the correct Locale information when using the Locale Plugin.

• Screenshots attached:

  before：

  

  after：

  
  
  

Proposed changelog entries

• Indicate the language of the page in the footer to improve accessibility and user experience.

Proposed changelog category

/label localization

Proposed upgrade guidelines

N/A

Submitter checklist

• The Jira issue, if it exists, is well-described.
• The changelog entries and upgrade guidelines are appropriate.
• There is automated testing or an explanation for the lack of tests.
• New public classes, fields, and methods are annotated appropriately.
• For dependency updates, external changelogs and full differentials are linked.
• For new APIs, there is a link to at least one consumer.

Desired reviewers

@mention

Before the changes are marked as ready-for-merge:

Maintainer checklist

• There are at least two (2) approvals for the pull request and no outstanding requests for change.
• Conversations in the pull request are over, or it is explicit that a reviewer is not blocking the change.
• Changelog entries in the pull request title and/or Proposed changelog entries are accurate, human-readable, and in the imperative mood.
• Proper changelog labels are set so that the changelog can be generated automatically.
• If the change needs additional upgrade steps from users, the upgrade-guide-needed label is set and there is a Proposed upgrade guidelines section in the pull request title (see example).
• If it would make sense to backport the change to LTS, a Jira issue must exist, be a Bug or Improvement, and be labeled as lts-candidate to be considered (see query).

[welcome]

Yay, your first pull request towards Jenkins core was created successfully! Thank you so much!

A contributor will provide feedback soon. Meanwhile, you can join the chats and community forums to connect with other Jenkins users, developers, and maintainers.

[comment-ops-bot]

I wasn't able to add the following labels: newbie-friendly, user-experience

Check that the label exists and is spelt right then try again.

[comment-ops-bot]

I wasn't able to add the following labels: newbie-friendly, user-experience

Check that the label exists and is spelt right then try again.

[janfaracik]

Thanks for the work on this, but personally I don’t think we should surface the language or page generation time in the UI (which AFAIK was removed from Jenkins a long time ago now). I think for the majority of users this adds noise rather than value.

Happy to discuss further if others feel strongly, but my vote would be to leave this out.

[mawinter69]

I don't see much value in this. Most people know which language they use in their browser. And the truth is that many texts are not translated so we anyway have basically on every page text in english.
We have so many pages with dynamic content so the timestamp when the page was generated is not saying much. And when the page is a bit longer the footer is anyway not visible, you would first need to scroll to the end to see that information. I've never missed this since it was removed.

[timja]

Agree with Jan and Markus thanks for your time on this but I don't think its something we want.

[ChongZhe001025]

Got it! I'm a beginner who just started learning how to solve jenkins issues. May I ask if there are any newbie-friendly issues you would recommend? 🙏

[timja]

There's some here which are probably newbie friendly: https://github.com/jenkinsci/sig-ux/issues?q=sort%3Aupdated-desc+is%3Aissue+is%3Aopen