[ovirt-devel] [Russian oVirt localization] Missing English ApplicationConstants.properties in 3.6

[Juliette Tux]

Hi Einav,
Hi all,

> As I mentioned - these (*English* .properties files) do not exist in the
oVirt source code as .properties files - but as Java files.
Ok i got it, but I supposed this was not intentionally since in most cases
proper  .properties files do exist in the source code. I thought that was
some kind of omission or error.

> in order to create *_ru_RU.properties files, Russian translations for
oVirt need to be uploaded to Zanata's 'oVirt' project first.
In most cases in order to create Russian properties I use prop2po and
po2prop utilities and it takes 1 minute to create good and properly
unicoded translated .properties file ready to be tested in the oVirt
interface. We are able here to test the translations directly from oVirt in
order to improve the translation first before uploading to the community
resources. But with omitted .properties the translator's work tends to be
extremely hard.

> If you need technical assistance with uploading Russian translations (in
any format) to the oVirt Zanata project
Well, I do not. I needed technical assistance with locating missed
.properties files

> were auto-generated by pulling translations from Zanata's oVirt project
I see. Please note that those files have non-unicode characters like, for
example in German: "nicht l\u00F6schen"  and "\n\u2013 W\u00E4hlen Sie
unter \u00BBEinmal", "ausf\u00FChren\u00AB" and so on. Since I'm dealing
with Russian language with no Latin characters at all, the whole files will
be looking like that I guess. Like Japanese files:
"${type}\u3092${action}\u3067\u304D\u307E\u305B\u3093\u3002\u30C7\u30D5\u30A9\u30EB\u30C8\u306E
${type}" This makes the local translator's work VERY hard. Ofc this is not
your problem and I'll be asked again to write to Zanata mailing list which
in this case I'll certainly do.

In general, this vendor lock-in to Zanata looks very disturbing to me as a
Open Source translator. I've been working for years locally in Lokalize,
freely using the gettext and other utilities and committing my translations
to KDE and Gnome svn/git without any problem. Now this Zanata lock-in is
VERY wrong and I still hope those .properties are missing in the source
code just because of some error.

Best regards,
Julia Dronova


-- 
С уважением, Дронова Юлия
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ovirt.org/pipermail/devel/attachments/20151208/bbc071c1/attachment-0001.html>