[FIXES #7126] multi word iso category strings will not get translated

[gannebamm]

fixed custom_translation.py errors and rebuild the translation files. Only the german .po file was compiled to .mo. The new translation strings must be translated by the respective native speakers.

Checklist

Reviewing is a process done by project maintainers, mostly on a volunteer basis. We try to keep the overhead as small as possible and appreciate if you help us to do so by completing the following items. Feel free to ask in a comment if you have troubles with any of them.

For all pull requests:

• Confirm you have read the contribution guidelines
• You have sent a Contribution Licence Agreement (CLA) as necessary (not required for small changes, e.g., fixing typos in the documentation)
• Make sure the first PR targets the master branch, eventual backports will be managed later. This can be ignored if the PR is fixing an issue that only happens in a specific branch, but not in newer ones.

The following are required only for core and extension modules (they are welcomed, but not required, for contrib modules):

• There is a ticket in https://github.com/GeoNode/geonode/issues describing the issue/improvement/feature (a notable exemption is, changes not visible to end-users)
• The issue connected to the PR must have Labels and Milestone assigned
• PR for bug fixes and small new features are presented as a single commit
• Commit message must be in the form "[Fixes #<issue_number>] Title of the Issue"
• New unit tests have been added covering the changes, unless there is an explanation on why the tests are not necessary/implemented
• This PR passes all existing unit tests (test results will be reported by travis-ci after opening this PR)
• This PR passes the QA checks: flake8 geonode
• Commits changing the settings, UI, existing user workflows, or adding new functionality, need to include documentation updates
• Commits adding new texts do use gettext and have updated .po / .mo files (without location infos)

Submitting the PR does not require you to check all items, but by the time it gets merged, they should be either satisfied or inapplicable.

[gannebamm]

@afabiani @t-book maybe we shall get the major languages covered in this PR? Like Italian, Spanish and French? I am not proficient in any of those, sorry.

And (to pad myself on the back): Look how nice and clean the .po diffs will be displayed since #7019 is merged 😄

[afabiani]

@gannebamm I agree... I can help only with Italian though :(

[t-book]

@gannebamm agree! Learning Spanish is on my Todo List. for a long time. Unfortunately, until now I can only help with german.

[dpadron]

I could collaborate with the Spanish translation. Can you tell me the steps to follow?

[gannebamm]

I could collaborate with the Spanish translation. Can you tell me the steps to follow?

You can download the django.po file for spanisch localisation and upload it again somewhere. I will cover the rest.
Please use this file of this pull requests (not Master branch)
geonode/locale/es/LC_MESSAGES/django.po

[codecov]

Codecov Report

Merging #7130 (a57528b) into master (c1007fc) will increase coverage by 0.01%.
The diff coverage is 100.00%.

❗ Current head a57528b differs from pull request most recent head e51fd3e. Consider uploading reports for the commit e51fd3e to get more accurate results

@@            Coverage Diff             @@
##           master    #7130      +/-   ##
==========================================
+ Coverage   59.07%   59.08%   +0.01%     
==========================================
  Files         565      565              
  Lines       39827    39840      +13     
  Branches     5282     5282              
==========================================
+ Hits        23527    23540      +13     
  Misses      14935    14935              
  Partials     1365     1365              

[afabiani]

@gannebamm I guess you will need to push also the *.mo files in order to see the translations on GeoNode.

[audetrobergem]

@gannebamm Here are the French translation files. I corrected some mistakes and added translations where there were none. I also corrected the isotopic categories. Let me know if there is anything that is not working. Cheers!
geonode_french_translation.zip

[github-actions]

The backport to 3.1.x failed:

The process 'git' failed with exit code 1

To backport manually, run these commands in your terminal:

# Fetch latest updates from GitHub
git fetch
# Create a new working tree
git worktree add .worktrees/backport-3.1.x 3.1.x
# Navigate to the new working tree
cd .worktrees/backport-3.1.x
# Create a new branch
git switch --create backport-7130-to-3.1.x
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick b5c81a49b1ac8b4264c0e5b553c00f4d9a3061c3
# Push it to GitHub
git push --set-upstream origin backport-7130-to-3.1.x
# Go back to the original working tree
cd ../..
# Delete the working tree
git worktree remove .worktrees/backport-3.1.x

Then, create a pull request where the base branch is 3.1.x and the compare/head branch is backport-7130-to-3.1.x.

[github-actions]

The backport to 3.2.x failed:

The process 'git' failed with exit code 1

To backport manually, run these commands in your terminal:

# Fetch latest updates from GitHub
git fetch
# Create a new working tree
git worktree add .worktrees/backport-3.2.x 3.2.x
# Navigate to the new working tree
cd .worktrees/backport-3.2.x
# Create a new branch
git switch --create backport-7130-to-3.2.x
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick b5c81a49b1ac8b4264c0e5b553c00f4d9a3061c3
# Push it to GitHub
git push --set-upstream origin backport-7130-to-3.2.x
# Go back to the original working tree
cd ../..
# Delete the working tree
git worktree remove .worktrees/backport-3.2.x

Then, create a pull request where the base branch is 3.2.x and the compare/head branch is backport-7130-to-3.2.x.

[gannebamm]

@afabiani Thanks, for taking care of this! Sorry that I 'staled' this PR. I was on vacation and lost track of some of my open work here.