Hi Vedran,
I am a bit baffled by this, and will follow up with our team - but I have to say, we are still having issues getting
Weblate (our new translation platform, since we moved from Transifex) working as we want, and our team is still trying to resolve several issues to improve the translation experience.
I decided to use the first example in your screenshot, "Location information," for testing. I did a search in Weblate and was not able to find the string, which is strange. However, I can see
in the code here that it appears to be properly wrapped in the i18n code to make it a string for translation, and I was also able to find the spot in the Croatian translation file - there are two spots:
There are no translations in the file currently included in AtoM's 2.5 release - however, this may not include all the recent work you've done in Weblate anyway.
I know that you figured out
in this thread how to import a translation file into AtoM. One possibility would be to edit that file locally, add any missing strings, and then add it back into AtoM. You will want to clear the application cache, restart services such as PHP-FPM, and re-index your site for the changes to show up after local edits.
Another option would be to use the translation bar at the bottom of the page - here is a screenshot of me finding the relevant string in the French interface and updating the current translation:
Unfortunately, for both of these solutions, the changes will only be stored locally - meaning you will need to repeat them in the future if you upgrade. However, hopefully a combination of the two approaches will allow you to accomplish what you need for now.
I will check in with our team and try to determine why "Location information" is not displaying as a string in Weblate. If we can figure that out, then you should be able to translate it in Weblate and avoid having to make local changes in the future.
Regarding terms found in taxonomies and menu elements - these may need to be translated via the AtoM user interface. They are terms in the database, so you can navigate to the related taxonomy, find the term, flip the user interface to Croatian, and add a translation. Here is another example of me doing so with the French term for "Transfer" (used in the Accession acquisition type taxonomy):
Note that the source English term is shown in yellow above the edit field, for reference. You can simply add your translation directly to the term name edit field, and save.
The same process can be followed for menu nodes. Navigate to Admin > Menus, find the menu node that you want to edit, click on it, flip in your translation language, and then add the translated label in the edit field:
In the future, it would be great to be able to get these database fixture terms into Weblate to make it easier for volunteers to submit translations. However, we first need to focus on resolving the current issues with Weblate before addressing this!
In the meantime, if I learn something new about why I was unable to find the "Location information" string in Weblate, I will let you know.
Cheers,