but it would be a good one from a user standpoint.

Could you explain why?

If I go to the trouble of modifying the parameters around the content language, such as the name, the native title, and possibly the URL Language code, then that's what I should be seeing on the Administrative interface when I'm building my content. I'm not writing in en-GB or fr-FR, I'm writing for English (Canada) or French (Canada). I realise that those are too long to display on such things as the menu, but the URL Language Code is short (en or fr). More reflective of what I am writing.

I dont know about french but I do know there is a language pack for English (Canada)

I would agree - if there was a way to eliminate en-GB as a content language and if en-CA was maintained by the project team. The challenges are that there is no way to eliminate en-GB and I have encountered issues with trying to use the en-CA language pack. I made the decision to use en-GB as the starting point of English. There is no fr-CA language pack, so I have to use fr-FR language pack.

if there was a way to eliminate en-GB as a content language

There is you just remove it from the content language list.

Actually, that does not work. I have installed English (Canada), added it to the Content Languages, changed all of my English content to use English (Canada), and set the default content language to English (Canada). I also removed English (United Kingdom) from the content language list. As you can see from the attached screenshots, English (United Kingdom) is still showing as a selectable language for my content in many places, such as associations.

On an earlier post, I was told that English (United Kingdom) could not be removed, since it is the default installation language. That's why I chose to make minor changes - can't fight city hall.

There is no language pack for French (Canada), so again, I had to make changes to fr-FR in order to make it "look" like it is Canadian.

The fact that Language tags are used instead of the URL Language Code looks quite ugly when building content.

You cannot remove the en-gb language but you should be able to remove the en-gb content setting and if not then its a bug

I think you forgot the screenshots

Had a malfunction between chair and keyboard. Screenshots are attached. I do remove the content setting. I suspect that I cannot disable en-GB as a Site Language and that's probably where the issue is arising.

I'd like to offer a suggestion. For those language packs, such as en-CA or en-US, that are 'officially supported' by the Joomla project team, why not allow the user a choice of using those as an installation option. So, instead of just offering English during the installation, offer English (United Kingdom), English (United States), English (Australia), English (Canada), etc. American users must go nuts with British spellings. Canadian users not so much, since we use a happy mix of both American and British English.

Do the same thing for your German users. I'm not sure what you would do for your Portuguese users, since I'm not sure how well supported the two versions of Portuguese are.

Just thinking outside of the box.

its already there as part of the install process

The en-GB content language has to be deleted to take it off from all multilingual editing. It works fine.
Also, it is possible to install any supported language at install time. Look at the last screen of installation

.

I don't recall seeing that option during the main installation of Joomla. Since I'm not too far along, I can re-install Joomla from scratch and see if I have that option. Please note that I am installing Joomla using Softaculous that is provided by my webhosting provider. I don't know if that makes a difference.

If it's not on the installation for Joomla itself, then please explain how I get the screen that you showed.

I do want to say "Thank you/merci" for the time that you are spending helping me with this issue.

I did go into the Extensions to see if I could uninstall en-GB. As the screenshot shows, it's locked and a protected extension. I have made en-CA the default for the site and for administration.

You can not uninstall the en-GB language as it is needed for when language packs are not 100% up to date.

What @infograf768 was referring to was deleting the CONTENT language which is not the same.

Also I see that you installed using softaculous installer which is their own code and does not offer the ability to set languages at installation

I took your suggestion and re-installed my website using the Joomla package directly. That seems to have solved the majority of the problems that I was having with the multilingual bits in my website. There is nothing that I can do about the French, which shows as fr-FR using the Language tag, instead of fr, using the URL Language Code. There is no French (Canada) language pack.

I can live with it, but it sure would be nice if the change could be made to use the URL Language Code.

If that's not a change that you want to put in the hopper, then feel free to close this ticket.

Again, many thanks for the time you have taken to help me solve the significant problems that I was experiencing!

Glad to hear you have made good progress.

Not my call about the language tag change but I suspect it will be a no as its quite a disruptive change

You can use the Language Code system plugin to display fr-ca in html produced instead of fr-FR

Is there another "trick" to solve these two places

Thank you for the hint about the Language Code. Since I am using only en-CA and fr-FR in my website, I have changed them to en and fr respectively.

I am hoping that someone can solve for the last two places.

@fballem
The language code as set in that system plugin is NOT the URL language code. This is why I posted the htlm result where you can see both. We created that plugin to help search engines.

AFAIK, there are no tricks yet to use the language code as defined in the plugin for the associations badges.

Concerning associations badges, see patch here
#37289

That will certainly solve the last lingering issue. I assume that when the patch is put into production, there will be an update identified on Joomla.

So as we have a pull request, #37289 , can we close this issue like we usually do when we have a pull request? Or is there something remaining which is not solved by that pull request and previous advice?

The bad new could be that the pull request might be delayed until 4.2 because the change is considered to be a new feature.

I'm not sure what a 'pull request' means. If this means that the change will be included in a Joomla update then I would be content to close this issue. I have been able to get my site up and running pretty close to perfect and the pull request would fix the final lingering issue. I'm also okay if the update doesn't occur prior to 4.2, since we are running 4.1 now.

Thanks everyone for all of your help!

A pull request is a proposed code change here on GitHub, like #37289 is.

Closing as having a pull request. Please test #37289 . Thanks in advance.