On 05/08/2014 09:09 AM, Ovirt User wrote: Einav can share details on how to translate in zanata if you want to help create an italian translation

On May 8, 2014 11:01 PM, "Einav Cohen" <ecohen(a)redhat.com&gt; wrote: I'm interested in helping with italian translation too. In the mean time I created an account on zanata using my FAS account and asked to join the Italian translators team. Gianluca

you need to request that from one of the maintainers of the oVirt Zanata project: http://i.imgur.com/K36FrPQ.png luckily for you, I am one of them :) Italian is now added.

every version in Zanata tracks the translation for a different ovirt-engine code-branch: the 'master' version in Zanata is tracking the translation for the 'master' branch in ovirt-engine's code repo. therefore the 'master' version should *always* be kept up-to-date with regards to translations. the 'ovirt-3.4' version in Zanata is tracking the translation for the 'ovirt- engine-3.4' branch. AFAIK, the ovirt-engine-3.4.1 code was already branched out of ovirt-engine-3.4, therefore we will need to create an 'ovirt-3.4.1' version in Zanata if we would like to track translations specifically for ovirt 3.4.1 (the 'ovirt-engine-3.4' code branch is now the baseline for ovirt-engine-3.4.2, AFAIK). we are typically not updating translations for versions that were already GA'd (3.4), therefore I recommend to concentrate at this point only on the 'master' version (which is currently tracking the ovirt-engine-3.5 translations, practically). once we will branch the ovirt-engine-3.5 code out of the 'master' code branch, I will create an 'ovirt-3.5' version in Zanata, to track the ovirt-engine-3.5 translations. the 'master' version will remain the translation tracker for the 'master' code branch [which would practically become the baseline for the next ovirt-engine planned release (ovirt-3.6?)]. from that point on, translations which we want to land in ovirt-3.5 will need to be updated in both the 'master' version and the 'ovirt-3.5' version in Zanata (very similar to code patches: once we branch out, if we want a certain piece of code to land in ovirt-3.5, we will need to fix it in 'master' as well as in the 'ovirt-engine-3.5' branch). again, doing translations specifically for 3.4.1 is problematic, as I explained above; I recommend working on a 'master'-based environment. in order to apply your translations, a regular ovirt environment is not enough - you will need a development environment, since the GUI code needs to be re-compiled with the new locale to make that new locale available in the GUI.

you can leave it untranslated or copy-paste the English string into the Italian translation - the result should be the same (English string displayed in GUI). It is recommended to copy the translation rather than leaving it untranslated, since leaving it untranslated will affect the statistics of the translation completeness (i.e. even if the translation is actually 100% complete, it will not be shown as 100% if strings were left untranslated, even deliberately). if you will leave the translation blank but mark it as 'translated' (so statistics are not affected), there is a good chance that the GUI will simply display a blank text as the translation, rather than the English text, so need to be careful with that. missing translations will result in displaying the corresponding English string instead.

[apologies for the extremely late response] we never discussed this before, I assume that a language should be at least in ~70/75% completion in order to justify its introduction into the product (need ack/nack from others on that number?) right now Italian stands on 1.22% translation completion in the 'master' version of the 'oVirt' project in Zanata, so I don't think that it justifies introducing it into oVirt at the moment. Gianluca: do you have an ETA for completion of at least ~70/75% of the Italian translation? if it would be early enough, we can definitely consider adding it to oVirt 3.5 (we obviously missed the ovirt-3.5 alpha milestones, but we can try and introduce it in later ovirt-3.5 milestones).

sounds good, Gianluca - we will follow up on next Wednesday. thanks.

Hi Gianluca, Thank you for working hard on completing the translation - it is highly appreciated! according to [1], ovirt-3.5.0 beta is planned for 2014-06-26 (which is ~1 week from now), however I am not sure if this is a build date or a release date (I assume it is a build date, as it is the same time in which we plan to branch 'ovirt-engine-3.5' out of 'master' - maybe @Sandro/Eyal can confirm that). RC Build is currently planned for 2014-07-16. GA is currently planned for 2014-08-04. I am planning to pull translations from Zanata towards the end of this month (hopefully in time for the beta, but not necessarily - maybe it will land only in the RC build eventually), and then do another pull at the end of July [probably not in time for the RC build, so may land eventually only in ovirt-3.5.1 or similar]. do you think that we will be able to have a ~70% Italian translation completion by mid/towards-the-end-of July? if so, we can work on adding Italian to the locale drop-down in the GUI "now" (i.e. in the upcoming days/week), however we may need to take it out of the GUI drop-down eventually if we won't meet the "~70% Italian translation completion by mid/towards-the-end-of July" goal. let me know what you think. ---- Thanks, Einav [1] http://wiki.ovirt.org/OVirt_3.5_release-management ----- Original Message -----

Il 19/06/2014 15:24, Einav Cohen ha scritto: Beta will be composed on 2014-06-26 using the last nightly snapshot available. If it won't pass basic sanity test a new build may be required but it will be highly appreciated that maintainers ensure their packages works the day before the repository composition. The branch will be created from the git hash of the build passing basic sanity test. -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com