Description of problem: The German translation of the Manageemnt Engine webUI could benefit from having a native German and technical person looking over it. Things that immediately feel unnatural to me; - Berechnen: is when you calculate something, it's not used to mean "to compute" - Überwachungsportal: all German native technical people I speak to call it 'Monitoring'. Überwachung also has a negative connotation in German. - Unterstützung: is closer to community support or help from colleagues than paid for support. For that Germans tend to use 'Support' Version-Release number of selected component (if applicable): 4.4
Can we change that to an u/s bug (product=ovirt-engine) since no specific customer is attached? AFAIK We do not have any internal resource for the German translations so it was outsourced to a vendor. Yuko, any suggestion on how we can handle the quality of those translations and fix current ones?
Hi Sharon, I can confirm that we do not have any internal resource who can work on German translations. I've also checked and confirmed that some of the translations that are suggested to be replaced were from our former internal German translator(s), so it's not just from the vendor we have engaged. I can think of the following options: 1. create a German glossary listing RHV terms -- this will require help from a Red Hatter who is familiar with this product. We can then provide it to the vendor and ask them to comply with the glossary. Additional funding will be required in order to ask them to update the existing translations. I am not sure how big this effort will be. 2. Invite German spoken Red Hatters who are able to contribute to the translation directly in Zanata. We can do either or both, just as pt-BR. Please let me know what you think.
(In reply to Yuko Katabami from comment #2) > I can think of the following options: > > 1. create a German glossary listing RHV terms -- this will require help from > a Red Hatter who is familiar with this product. We can then provide it to > the vendor and ask them to comply with the glossary. Additional funding will > be required in order to ask them to update the existing translations. I am > not sure how big this effort will be. > > 2. Invite German spoken Red Hatters who are able to contribute to the > translation directly in Zanata. > > We can do either or both, just as pt-BR. > > Please let me know what you think. Yuko, thanks for the info. After discussing that with mskrivan then we think that option (2) is preferable for this case. We do have some German spoken Red Hatters on RHV that we can ask and we can also ask the community for help. Patrick, would you like to help with fixing those specific wrong mentioned German translations yourself? The translation platform used is Zanata and the translations project is hosted here: https://zanata.phx.ovirt.org/iteration/view/ovirt-engine/ovirt-4.4. I can easily open a user for you if needed.
Thank you So much, Sharon.
(In reply to Sharon Gratch from comment #3) > Patrick, would you like to help with fixing those specific wrong mentioned > German translations yourself? Sorry. no.
Dominik, do you plan on handling this for 4.4.4 or should we postpone to 4.4.5?
(In reply to Sharon Gratch from comment #6) > Dominik, do you plan on handling this for 4.4.4 or should we postpone to > 4.4.5? Yes, thanks for the reminder.
Changed: Überwachungsportal -> Monitoringportal Rechnerressourcen -> Compute-Ressourcen Berechnen -> Compute Does this sound better? Where did you saw the "Unterstützung" ?
(In reply to Dominik Holler from comment #8) https://bugzilla.redhat.com/show_bug.cgi?id=1881505#c5
Changed: Überwachungsportal -> Monitoringportal Rechnerressourcen -> Compute-Ressourcen Berechnen -> Compute I did not found the word: "Unterstützung".
Need to pull those new translations to the ovirt-engine code project. @Scott can you please handle this?
Sharon 4.4.4.5 has not been tagged yet, can you please cross check?
(In reply to Sandro Bonazzola from comment #12) > Sharon 4.4.4.5 has not been tagged yet, can you please cross check? Right, it was fixed for 4.4.4.4 already.
Verified on: ovirt-engine-4.4.4.5-0.10.el8ev.noarch
This bugzilla is included in oVirt 4.4.4 release, published on December 21st 2020. Since the problem described in this bug report should be resolved in oVirt 4.4.4 release, it has been closed with a resolution of CURRENT RELEASE. If the solution does not work for you, please open a new bug report.