Preparing for Brazilian

[alemorvan]

We have to prepare mkdocs for Brazilian language. This time, language code will be with 5 letters code.

I think, it will come from crowdin with pt-BR (uppercase).

Please check if crowdin can support both 2 letters codes and 5 letters codes.

Antoine.

[vercel[bot]]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
rockylinux-docs	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Apr 20, 2023 3:11pm

[alemorvan]

@NeilHanlon please check MM (~localization) for explaination. Thx!

[sspencerwire]

@NeilHanlon please check MM (~localization) for explaination. Thx!

@NeilHanlon @alemorvan Turns out that this will not work the way it is entered. Mkdocs explodes. It needs to be "pt_BR" rather than "pt-BR" the mapping has been fixed in Crowdin, but we need to correct this PR before merging:

INFO     -  Building documentation...
ERROR    -  Config value: 'plugins'. Error: Plugin 'i18n' value: 'languages'. Error: Language code values must be either ISO-639-1 lower
            case or represented with they territory/region/county codes, received 'pt-BR' expected forms examples: 'en' or 'en_US'.
Aborted with 1 Configuration Errors!

When entered in the mkdocs.yml file as "pt_BR" it loads fine.

[sspencerwire]

This works in my local copy of mkdocs so it should now be ready to merge. @ressonix can you merge this change for us?

[NeilHanlon]

Yeah this looks good to me. I can merge but I would like @rocky-linux/web-leads to review so everyone knows what's up :)