We have Italian in oVirt 'master'. Do we want Italian in RHEV (4.0) as well?
Thank you Moran. @Einav, do we need more acks before we can commence our side of work, or is it ready to go?
(In reply to Yuko Katabami from comment #7) > Thank you Moran. > > @Einav, do we need more acks before we can commence our side of work, or is > it ready to go? we have PM ack, so we are ready to go. thanks.
(In reply to Einav Cohen from comment #8) > (In reply to Yuko Katabami from comment #7) > > Thank you Moran. > > > > @Einav, do we need more acks before we can commence our side of work, or is > > it ready to go? > > we have PM ack, so we are ready to go. thanks. reminding - this is for RHEV 4.0, for which we haven't even started translation planning yet; so no actual work needs to be performed right now, but the translation-resources planning definitely needs to take Italian translation into consideration. thanks.
Hi Einav, Since the oVirt project has such a large workload, I thought that it would be better to start reviwing the current strings in the master version and complete untranslated strings before 4.0 translation cycles begins. It allows our Italian translator more time to work on it. What do you think?
(In reply to Yuko Katabami from comment #10) > Hi Einav, > > Since the oVirt project has such a large workload, I thought that it would > be better to start reviwing the current strings in the master version and > complete untranslated strings before 4.0 translation cycles begins. > It allows our Italian translator more time to work on it. > > What do you think? absolutely. feel free to review/complete translations for Italian on the 'master' version in your own time - it should definitely save you time and resources once we get to the actual translation cycles for RHEV 4.0.
Sandro, can you check the user portal as well? it's actually more interesting than the admin portal (from my perspective).
Checked a 4.0.2.4-0.1.el7ev environment and confirmed that Italian is available, including landing page and the new Dashboard tab. Moving the status to VERIFIED.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://rhn.redhat.com/errata/RHEA-2016-1743.html