Hi Matheus,
I will pass this information on to our Maintainers team for them to investigate. However, in at least some cases I can see in your screenshots, it is a known issue that we cannot easily resolve.
There are a number of strings that exist in the database, but need to be present when a user first installs AtoM - this includes any default taxonomy terms for example, but also some other core terms. We call these fixtures - they are stored directly in the code, and when AtoM is first installed, part of the installation procedure then "seeds" the database by writing these fixtures to the relevant tables.
Fixtures are available in our translation platform for users to translate. However, the known issue is in making new fixture translations available to upgrading users. See:
When a user upgrades, they first install a new AtoM instance normally - during which, any new fixture translations get added to the (currently empty) database. However, THEN the upgrading user completely overwrites these database updates when they load their own backup from the older version - meaning the newer translations are lost.
This is at least part of what is happening with some of the strings in the demo site. We have been using and upgrading that demo data since the early ICA-AtoM days. Many new fixture translations have since been added, but we cannot easily get them into the demo data until this issue is resolved.
There are also other known internationalization (i18n) issues - you will see a number of other issue tickets linked to the one above, and there are
many more issues here. There is much we still hope to do to improve translation support and i18n in AtoM. As a small project without consistent funding, we constantly have to balance these goals against the many other maintenance priorities we have for the application.
Nevertheless, I will pass this feedback on to the Maintainer team, so they are aware of the issues and the interest in prioritizing fixes related to it. In the meantime, if your group would be interested in potentially sponsoring an analysis project so our team can dedicate some time to investigating, prioritizing, and preparing a plan to address i18n issues, feel free to
contact Artefactual to discuss options.
In the short term - if you are using AtoM to teach, then I would strongly suggest that you consider hosting your own teaching instance. If you wait until the upcoming 2.8 release, install fresh, and then create your own demo data set inside the new installation, you will avoid many of these issues and have more control over the environment anyway!
Cheers,