<div dir="ltr">Hello Vojtech,<br><div><br></div><div>> <span style="font-size:12.8000001907349px">In oVirt 4.0 we'll have default properties files in place.</span></div><div><span style="font-size:12.8000001907349px">> </span><span style="font-size:12.8000001907349px">we'll modify the UI i18n implementation so that you don't need </span><span style="font-size:12.8000001907349px">to re-build Engine (re-compile GWT UI) in order to see changes you've</span></div><span style="font-size:12.8000001907349px">done to any of properties files.</span><div><span style="font-size:12.8000001907349px">Oh, these are really good news. </span>Thanks a lot for your support and positive devs feedback!</div><div><br></div><div>Best regards,<br>Julia Dronova</div></div><div class="gmail_extra"><br><div class="gmail_quote">On 9 December 2015 at 18:35, Vojtech Szocs <span dir="ltr"><<a href="mailto:vszocs@redhat.com" target="_blank">vszocs@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class=""><br>
<br>
----- Original Message -----<br>
> From: "Juliette Tux" <<a href="mailto:juliette.tux@gmail.com">juliette.tux@gmail.com</a>><br>
> To: "Einav Cohen" <<a href="mailto:ecohen@redhat.com">ecohen@redhat.com</a>><br>
> Cc: <a href="mailto:Devel@ovirt.org">Devel@ovirt.org</a><br>
</span><span class="">> Sent: Tuesday, December 8, 2015 5:46:17 PM<br>
> Subject: Re: [ovirt-devel] [Russian oVirt localization] Missing English ApplicationConstants.properties in 3.6<br>
><br>
</span><span class="">> Hi Einav,<br>
> Hi all,<br>
><br>
> > As I mentioned - these (*English* .properties files) do not exist in the<br>
> > oVirt source code as .properties files - but as Java files.<br>
> Ok i got it, but I supposed this was not intentionally since in most cases<br>
> proper .properties files do exist in the source code. I thought that was<br>
> some kind of omission or error.<br>
<br>
</span>Hi Juliette,<br>
<br>
the default English texts are currently located in Java files, for example:<br>
<br>
frontend/webadmin/modules/webadmin/src/main/java/org/ovirt/engine/ui/webadmin/ApplicationConstants.java<br>
<br>
with values expressed via Java annotation (like DefaultStringValue):<br>
<br>
@DefaultStringValue("oVirt Engine Web Administration")<br>
String applicationTitle();<br>
<br>
This is definitely not a good practice so in oVirt 4.0 we'll put these<br>
default English texts into properties files as you'd normally expect,<br>
for example:<br>
<br>
frontend/webadmin/modules/webadmin/src/main/resources/org/ovirt/engine/ui/webadmin/ApplicationConstants.properties<br>
<br>
Also, we'll modify the UI i18n implementation so that you don't need<br>
to re-build Engine (re-compile GWT UI) in order to see changes you've<br>
done to any of properties files.<br>
<span class=""><br>
><br>
> > in order to create *_ru_RU.properties files, Russian translations for oVirt<br>
> > need to be uploaded to Zanata's 'oVirt' project first.<br>
> In most cases in order to create Russian properties I use prop2po and po2prop<br>
> utilities and it takes 1 minute to create good and properly unicoded<br>
> translated .properties file ready to be tested in the oVirt interface. We<br>
> are able here to test the translations directly from oVirt in order to<br>
> improve the translation first before uploading to the community resources.<br>
> But with omitted .properties the translator's work tends to be extremely<br>
> hard.<br>
><br>
> > If you need technical assistance with uploading Russian translations (in<br>
> > any format) to the oVirt Zanata project<br>
> Well, I do not. I needed technical assistance with locating missed<br>
> .properties files<br>
<br>
</span>For now, please refer to Java files containing default English texts as<br>
mentioned by Einav (these currently substitute properties files you are<br>
looking for). In oVirt 4.0 we'll have default properties files in place.<br>
<span class=""><br>
><br>
> > were auto-generated by pulling translations from Zanata's oVirt project<br>
> I see. Please note that those files have non-unicode characters like, for<br>
> example in German: "nicht l\u00F6schen" and "\n\u2013 W\u00E4hlen Sie unter<br>
> \u00BBEinmal", "ausf\u00FChren\u00AB" and so on. Since I'm dealing with<br>
> Russian language with no Latin characters at all, the whole files will be<br>
> looking like that I guess. Like Japanese files:<br>
> "${type}\u3092${action}\u3067\u304D\u307E\u305B\u3093\u3002\u30C7\u30D5\u30A9\u30EB\u30C8\u306E<br>
> ${type}" This makes the local translator's work VERY hard. Ofc this is not<br>
> your problem and I'll be asked again to write to Zanata mailing list which<br>
> in this case I'll certainly do.<br>
><br>
</span>> In general, t his vendor lock-in to Zanata looks very disturbing to me as a<br>
<span class="">> Open Source translator. I've been working for years locally in Lokalize,<br>
> freely using the gettext and other utilities and committing my translations<br>
> to KDE and Gnome svn/git without any problem. Now this Zanata lock-in is<br>
> VERY wrong and I still hope those .properties are missing in the source code<br>
> just because of some error.<br>
<br>
</span>AFAIK, we're using Zanata to help manage (lots of) i18n properties<br>
files which are then pulled into oVirt code base in controlled<br>
translation cycles, so Zanata acts as repository of translations.<br>
<span class="im HOEnZb"><br>
><br>
> Best regards,<br>
> Julia Dronova<br>
><br>
><br>
> --<br>
> С уважением, Дронова Юлия<br>
><br>
</span><div class="HOEnZb"><div class="h5">> _______________________________________________<br>
> Devel mailing list<br>
> <a href="mailto:Devel@ovirt.org">Devel@ovirt.org</a><br>
> <a href="http://lists.ovirt.org/mailman/listinfo/devel" rel="noreferrer" target="_blank">http://lists.ovirt.org/mailman/listinfo/devel</a><br>
</div></div></blockquote></div><br><br clear="all"><div><br></div>-- <br><div class="gmail_signature">С уважением, Дронова Юлия</div>
</div>