Questions about translations in AtoM version 2.10

[ism...@gmail.com]

Hello, we are setting up version 2.10 of AtoM on a new server in order to later migrate all the content from our current version.

We only use two languages, English and Spanish, with Spanish set as the default. There are some untranslated words in the interface, but the translation bar at the bottom does not appear.

I have read in the documentation that this new version uses Weblate to contribute translations, although I am not sure how this affects my AtoM installation.

Could you clarify how to display the translation bar, or alternatively, how to integrate Weblate translations into my platform?

Thank you very much and best regards.

[Hans-Arno Mielsch]

1. The translation bar only appears if the user is entitled by the Administrator to do so: menu Admin/Users in the user's details "Access Control", add User Group "translator" and add Spanish to "Allowed languages for translation".
   Translated content will be saved to one ore more "messages.xml" files in your server instance.
2. Weblate is an alternate way to translate and it is the persistent way, not updating your installation directly, but future installations! 
   Use https://translations.artefactual.com/ to translate and request an update from Sarah/Artefactual before installing again.

[ism...@gmail.com]

Hello, thank you for your reply. I have already checked that I have translator permissions for both Spanish and English, and I do have the messages.xml file, although the translation bar does not appear. In fact, I have reviewed the code in layout.php and _layout_start.php from the arDominionPlugin, and they do not include the translation bar, so I believe there is no option to add it.

Is this something specific to version 2.10 of AtoM? I will consider using Weblate for future updates, although for now—unless you recommend another approach—it seems my only option is to update the XML file manually.

Best regards.

[Hans-Arno Mielsch]

With version 2.10 Bootstrap v2 is not supported anymore: arDominionPlugin will probaly causing problems, you have to switch to arDominionB5Plugin.

[Sarah Romkey]

Hello,

I just want to clarify whether you are trying to translate archival description content or user interface strings or both?

When it comes to the user interface it would be advantageous to use Weblate, because it means that 1. your translations will persist even after you upgrade and 2. it benefits other users in the community. Information on contributing to Weblate translations is here: https://wiki.accesstomemory.org/wiki/Resources/Translation . You don't need to do anything special to have translations from Weblate included in your AtoM site, they come by default- but if there are new translations made between AtoM releases, you need to wait for our next release for those translations to be included. Spanish has pretty good, but not perfect, coverage currently.

For archival descriptions, even if you do not see the translation bar, if you toggle to a language other than the default culture that you installed with and click on Edit in an archival description, you will see that you can still provide the translated content in the way that is described in the documentation. We think there is a bug in AtoM that is preventing the translation bar from appearing when English is toggled, regardless of the default culture. If that turns out to be the case we will file an issue and see what can be done about it in a future release.

Cheers,

Sarah

[ism...@gmail.com]

Hi,  

Actually, the theme my AtoM uses is  arDominionB5Plugin  . Sorry for the mistake. 

Best regards.

[Hans-Arno Mielsch]

Well, I cannot reproduce your issue: even in https://qa-demo.accesstomemory.org/?sf_culture=es it works as designed: as soon I put a user into the translator group, that user will see the translation bar at the time he logs on again (and switches to a foreign language).

Good Luck!

[ism...@gmail.com]

Hi,

My Atom version is 2.10.0 - 197 ¿Could that be the problem?

[Hans-Arno Mielsch]

I don't think so - I am using this feature since version 2.9 without issues.

Some other issues were caused by mistakes done while updating, especially caused by wrong access rights, but the translation bar was quite reliable :-)

[Hans-Arno Mielsch]

While searching in this group I found https://groups.google.com/g/ica-atom-users/c/yO3M72kOAqg/m/pvRJmZC4AgAJ , where Willie did not find a solution for the same problem :-(

But that reminded me to a common mistake I did: ignoring

"Please rebuild the search index if you are adding new languages.

$ php symfony search:populate"

I would do a php symfony cc before that.

Perhaps someone from the development team can check what the display of the translation bar triggers ...

[ism...@gmail.com]

Hello, I had already seen the threads you mentioned. I believe there are more users experiencing this issue, although I’ve been able to verify that the demo you sent me and the one on the AtoM website both display the bar correctly. It’s possible that it’s an installation or configuration problem. I will keep investigating. Thank you and best regards.