search

globaleaks / globaleaks-whistleblowing-software

GlobaLeaks is a free and open-source whistleblowing software enabling anyone to easily set up and maintain a secure reporting platform.
https://www.globaleaks.org
Other
1.25k stars 275 forks source link

Make it possible to define language-specific ProjectName #3201

Open aetdr opened 2 years ago

aetdr commented 2 years ago

In a multilingual tenant setup, the value of ProjectName can only be defined once and is persistent across translations. We would like to be able to define language-specific values.

evilaliv3 commented 2 years ago

Thank you for your suggestion @aetdr

To implement this we would need first to understand how to handle this condition in general for all the software variables without impacting the already not perfect user experience.

In other words, we would need to understand how to make it possible for users to decide if a setting would need to be applied to every language or if it would have to be different depending on the language.

If you have any suggestion or have in mind a software that enables this please feel free to contribute with your advice.

This exct evaluation is necessary in order to be able to address other tickets like https://github.com/globaleaks/GlobaLeaks/issues/3202 and https://github.com/globaleaks/GlobaLeaks/issues/3195

evilaliv3 commented 2 years ago

Related to: https://github.com/globaleaks/GlobaLeaks/issues/3017

elbill commented 2 years ago

Not being able to define language specific project name also creates issues for us. We end up leaving it blank, that creates some other minor issues. I would suggest to treat this exactly the same with all other fields in a by default multilingual content. Not being multilingual and consistent with other fields creates issues with user experience, not the other way round. The alternative would be to have a single language project name but not to show on the platform or notification messages.