dev/translation#13 Enable users to choose their own language for accessing CiviCRM

[aydun]

Overview

Users on multilingual sites are able to select their language of choice from the available languages. Monolingual sites have only been able to set the language for all users.

This change enables users of monolingual sites to select their own language without affecting other users.

The background for this is https://lab.civicrm.org/dev/translation/issues/13 although this implementation has evolved from that suggested in the 'Approach' section. This replaces PR #12405

Before

In monolingual mode, /admin/setting/localization

After

In monolingual mode, /admin/setting/localization

Results in Language Switcher block being shown (same as in multilingual mode)

Technical Details

This introduces a new localization setting 'uiLanguages'. The existing logic for determining the appropriate language in multilingual mode is extended to monolingual (looking at request url, session, uf_match etc). In line with that, the language switcher block is not shown if the setting 'Inherit CMS Language' is set. The UI Languages setting on the settings page is not shown in multilingual mode nor when 'Inherit CMS Language' is selected.

There are no (intentional!) changes to multilingual mode

Comments

A documentation PR will be provided.

[civibot]

(Standard links)

• If this is your first pull-request for CiviCRM, please browse CONTRIBUTING.md for information about the development and testing processes.
• If you are reviewing this pull-request, you may wish to consult the test sites and the Review Standards (long template, short template).

[seamuslee001]

Jenkins re test this please

[seamuslee001]

Test Failure looks related @aydun

[aydun]

@seamuslee001 In the test environment, are the l10n files installed? So does CRM_Core_I18n::languages() return all the languages or just en_US ?

[seamuslee001]

Jenkins re test this please

[seamuslee001]

hmm test failure here https://test.civicrm.org/job/CiviCRM-Core-PR/23519/testReport/junit/(root)/CRM_Core_I18n_LocaleTest/testUiLanguages/ still looks to be an issue @aydun maybe FR_CA isn't in the default one

[seamuslee001]

ping @mlutfy You might be into this one

[aydun]

ping @mlutfy You might be into this one

Yes - this is the thing we discussed at the Governance Summit

[aydun]

@seamuslee001 Thanks for tracking down the issue in #13246 The tests here are passing cleanly now.

[mlutfy]

Hi @aydun, this works great! I have only a small superficial request: can you change the string "UI Languages" to "Available Languages"?

When we are in multi-lingual mode, the interface looks like this:

I think the wording should be imitated. "UI" is a geeky term, and "Available languages" does not imply multi-lingual data anyway.

(The "Languages available to users of this installation" doesn't mean anything useful, so I would ignore that string.)

Testing

• Test backend, as an admin, used the language switcher to change languages (on a new install, added French)
• Test front-end as anonymous user (event registration)
• Test enabling multi-lingual (it does not auto-enable the languages, but I think that's OK)
• Test on existing multi-lingual sites

Documentation

• This should have a clear warning that many settings and option values will not be properly translated, but that this should not have a major impact on end-users. Ex: "individual prefix/suffix" will not be translated, gender options, etc.

[aydun]

Thanks @mlutfy - I've changed "UI Languages" to "Available Languages"

[mlutfy]

Great! Seems OK to merge.