[Russian oVirt localization] Missing English ApplicationConstants.properties in 3.6
Hello, There is a missing original English .properties file in tar.gz archives for 3.6.* source. The directory is 'frontend/webadmin/modules/webadmin/src/main/resources/org/ovirt/engine/ui/webadmin'. There are only translated properties files but no original English ApplicationConstants.properties. Where can I find it, please? Best regards, Julia Dronova -- С уважением, Дронова Юлия
the following localized files don't exist in the oVirt source: org.ovirt.engine.ui.uicompat.SpiceRedKeys.properties org.ovirt.engine.ui.uicompat.UIConstants.properties org.ovirt.engine.ui.uicompat.UIMessages.properties org.ovirt.engine.ui.common.CommonApplicationConstants.properties org.ovirt.engine.ui.webadmin.ApplicationMessages.properties org.ovirt.engine.ui.webadmin.ApplicationConstants.properties org.ovirt.engine.ui.userportal.ApplicationConstants.properties org.ovirt.engine.ui.userportal.ApplicationMessages.properties the English strings actually reside in GWT Java Constants/Messages files: ./frontend/webadmin/modules/uicompat/src/main/java/org/ovirt/engine/ui/uicompat/SpiceRedKeys.java ./frontend/webadmin/modules/uicompat/src/main/java/org/ovirt/engine/ui/uicompat/UIConstants.java ./frontend/webadmin/modules/uicompat/src/main/java/org/ovirt/engine/ui/uicompat/UIMessages.java ./frontend/webadmin/modules/gwt-common/src/main/java/org/ovirt/engine/ui/common/CommonApplicationConstants.java ./frontend/webadmin/modules/webadmin/src/main/java/org/ovirt/engine/ui/webadmin/ApplicationMessages.java ./frontend/webadmin/modules/webadmin/src/main/java/org/ovirt/engine/ui/webadmin/ApplicationConstants.java ./frontend/webadmin/modules/userportal-gwtp/src/main/java/org/ovirt/engine/ui/userportal/ApplicationConstants.java ./frontend/webadmin/modules/userportal-gwtp/src/main/java/org/ovirt/engine/ui/userportal/ApplicationMessages.java and also: ./frontend/webadmin/modules/gwt-common/src/main/java/org/ovirt/engine/ui/common/CommonApplicationMessages.java (which is the base Interface for both of the ApplicationMessages.java files). ---- Thanks, Einav ----- Original Message -----
From: "Juliette Tux" <juliette.tux@gmail.com> To: Devel@ovirt.org Sent: Monday, December 7, 2015 4:20:28 AM Subject: [ovirt-devel] [Russian oVirt localization] Missing English ApplicationConstants.properties in 3.6
Hello, There is a missing original English .properties file in tar.gz archives for 3.6.* source. The directory is 'frontend/webadmin/modules/webadmin/src/main/resources/org/ovirt/engine/ui/webadmin'. There are only translated properties files but no original English ApplicationConstants.properties. Where can I find it, please? Best regards, Julia Dronova -- С уважением, Дронова Юлия
_______________________________________________ Devel mailing list Devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/devel
Hello,
the following localized files don't exist in the oVirt source The directory 'frontend/webadmin/modules/webadmin/src/main/resources/ org/ovirt/engine/ui/webadmin' contains translated .properties for 8 languages already, which means the translatable files were created somehow and then converted back to properties, right? So what should I do then in order to get ApplicationConstants_ru_RU.properties? This must be an ABC for you ofc, but I would really greatly appreciate your help!
On 7 December 2015 at 20:17, Einav Cohen <ecohen@redhat.com> wrote:
the following localized files don't exist in the oVirt source:
org.ovirt.engine.ui.uicompat.SpiceRedKeys.properties org.ovirt.engine.ui.uicompat.UIConstants.properties org.ovirt.engine.ui.uicompat.UIMessages.properties org.ovirt.engine.ui.common.CommonApplicationConstants.properties org.ovirt.engine.ui.webadmin.ApplicationMessages.properties org.ovirt.engine.ui.webadmin.ApplicationConstants.properties org.ovirt.engine.ui.userportal.ApplicationConstants.properties org.ovirt.engine.ui.userportal.ApplicationMessages.properties
the English strings actually reside in GWT Java Constants/Messages files:
./frontend/webadmin/modules/uicompat/src/main/java/org/ovirt/engine/ui/uicompat/SpiceRedKeys.java
./frontend/webadmin/modules/uicompat/src/main/java/org/ovirt/engine/ui/uicompat/UIConstants.java
./frontend/webadmin/modules/uicompat/src/main/java/org/ovirt/engine/ui/uicompat/UIMessages.java
./frontend/webadmin/modules/gwt-common/src/main/java/org/ovirt/engine/ui/common/CommonApplicationConstants.java
./frontend/webadmin/modules/webadmin/src/main/java/org/ovirt/engine/ui/webadmin/ApplicationMessages.java
./frontend/webadmin/modules/webadmin/src/main/java/org/ovirt/engine/ui/webadmin/ApplicationConstants.java
./frontend/webadmin/modules/userportal-gwtp/src/main/java/org/ovirt/engine/ui/userportal/ApplicationConstants.java
./frontend/webadmin/modules/userportal-gwtp/src/main/java/org/ovirt/engine/ui/userportal/ApplicationMessages.java
and also:
./frontend/webadmin/modules/gwt-common/src/main/java/org/ovirt/engine/ui/common/CommonApplicationMessages.java (which is the base Interface for both of the ApplicationMessages.java files).
---- Thanks, Einav
----- Original Message -----
From: "Juliette Tux" <juliette.tux@gmail.com> To: Devel@ovirt.org Sent: Monday, December 7, 2015 4:20:28 AM Subject: [ovirt-devel] [Russian oVirt localization] Missing English ApplicationConstants.properties in 3.6
Hello, There is a missing original English .properties file in tar.gz archives for 3.6.* source. The directory is
'frontend/webadmin/modules/webadmin/src/main/resources/org/ovirt/engine/ui/webadmin'.
There are only translated properties files but no original English ApplicationConstants.properties. Where can I find it, please? Best regards, Julia Dronova -- С уважением, Дронова Юлия
_______________________________________________ Devel mailing list Devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/devel
-- С уважением, Дронова Юлия
Hi Juliette, You were originally asking about the "original *English* .properties files". As I mentioned - these (*English* .properties files) do not exist in the oVirt source code as .properties files - but as Java files. All of the *non-English* .properties files (including the 8 ones that you have mentioned) were auto-generated by pulling translations from Zanata's oVirt project [1] (you mentioned that you are already familiar with Zanata, IIRC). So in order to create *_ru_RU.properties files, Russian translations for oVirt need to be uploaded to Zanata's 'oVirt' project first. If you need technical assistance with uploading Russian translations (in any format) to the oVirt Zanata project - please consult the Zanata team via the zanata-users@redhat.com mailing list. Once Russian translations are uploaded to Zanata, I can take care of pulling them into *_ru_RU.properties files within the oVirt code - that shouldn't be a problem. ---- Thanks, Einav [1] https://translate.zanata.org/zanata/project/view/ovirt ----- Original Message -----
From: "Juliette Tux" <juliette.tux@gmail.com> To: "Einav Cohen" <ecohen@redhat.com> Cc: Devel@ovirt.org Sent: Tuesday, December 8, 2015 4:45:01 AM Subject: Re: [ovirt-devel] [Russian oVirt localization] Missing English ApplicationConstants.properties in 3.6
Hello,
the following localized files don't exist in the oVirt source The directory 'frontend/webadmin/modules/webadmin/src/main/resources/ org/ovirt/engine/ui/webadmin' contains translated .properties for 8 languages already, which means the translatable files were created somehow and then converted back to properties, right? So what should I do then in order to get ApplicationConstants_ru_RU.properties? This must be an ABC for you ofc, but I would really greatly appreciate your help!
On 7 December 2015 at 20:17, Einav Cohen <ecohen@redhat.com> wrote:
the following localized files don't exist in the oVirt source:
org.ovirt.engine.ui.uicompat.SpiceRedKeys.properties org.ovirt.engine.ui.uicompat.UIConstants.properties org.ovirt.engine.ui.uicompat.UIMessages.properties org.ovirt.engine.ui.common.CommonApplicationConstants.properties org.ovirt.engine.ui.webadmin.ApplicationMessages.properties org.ovirt.engine.ui.webadmin.ApplicationConstants.properties org.ovirt.engine.ui.userportal.ApplicationConstants.properties org.ovirt.engine.ui.userportal.ApplicationMessages.properties
the English strings actually reside in GWT Java Constants/Messages files:
./frontend/webadmin/modules/uicompat/src/main/java/org/ovirt/engine/ui/uicompat/SpiceRedKeys.java
./frontend/webadmin/modules/uicompat/src/main/java/org/ovirt/engine/ui/uicompat/UIConstants.java
./frontend/webadmin/modules/uicompat/src/main/java/org/ovirt/engine/ui/uicompat/UIMessages.java
./frontend/webadmin/modules/gwt-common/src/main/java/org/ovirt/engine/ui/common/CommonApplicationConstants.java
./frontend/webadmin/modules/webadmin/src/main/java/org/ovirt/engine/ui/webadmin/ApplicationMessages.java
./frontend/webadmin/modules/webadmin/src/main/java/org/ovirt/engine/ui/webadmin/ApplicationConstants.java
./frontend/webadmin/modules/userportal-gwtp/src/main/java/org/ovirt/engine/ui/userportal/ApplicationConstants.java
./frontend/webadmin/modules/userportal-gwtp/src/main/java/org/ovirt/engine/ui/userportal/ApplicationMessages.java
and also:
./frontend/webadmin/modules/gwt-common/src/main/java/org/ovirt/engine/ui/common/CommonApplicationMessages.java (which is the base Interface for both of the ApplicationMessages.java files).
---- Thanks, Einav
----- Original Message -----
From: "Juliette Tux" <juliette.tux@gmail.com> To: Devel@ovirt.org Sent: Monday, December 7, 2015 4:20:28 AM Subject: [ovirt-devel] [Russian oVirt localization] Missing English ApplicationConstants.properties in 3.6
Hello, There is a missing original English .properties file in tar.gz archives for 3.6.* source. The directory is
'frontend/webadmin/modules/webadmin/src/main/resources/org/ovirt/engine/ui/webadmin'.
There are only translated properties files but no original English ApplicationConstants.properties. Where can I find it, please? Best regards, Julia Dronova -- С уважением, Дронова Юлия
_______________________________________________ Devel mailing list Devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/devel
-- С уважением, Дронова Юлия
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
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
Hi Einav, Hi all, proper .properties files do exist in the source code. I thought that was some kind of omission or error. 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 -- С уважением, Дронова Юлия
----- Original Message -----
From: "Juliette Tux" <juliette.tux@gmail.com> To: "Einav Cohen" <ecohen@redhat.com> Cc: Devel@ovirt.org Sent: Tuesday, December 8, 2015 5:46:17 PM Subject: Re: [ovirt-devel] [Russian oVirt localization] Missing English ApplicationConstants.properties in 3.6
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.
Hi Juliette, the default English texts are currently located in Java files, for example: frontend/webadmin/modules/webadmin/src/main/java/org/ovirt/engine/ui/webadmin/ApplicationConstants.java with values expressed via Java annotation (like DefaultStringValue): @DefaultStringValue("oVirt Engine Web Administration") String applicationTitle(); This is definitely not a good practice so in oVirt 4.0 we'll put these default English texts into properties files as you'd normally expect, for example: frontend/webadmin/modules/webadmin/src/main/resources/org/ovirt/engine/ui/webadmin/ApplicationConstants.properties Also, we'll modify the UI i18n implementation so that you don't need to re-build Engine (re-compile GWT UI) in order to see changes you've done to any of properties files.
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
For now, please refer to Java files containing default English texts as mentioned by Einav (these currently substitute properties files you are looking for). In oVirt 4.0 we'll have default properties files in place.
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, t his 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.
AFAIK, we're using Zanata to help manage (lots of) i18n properties files which are then pulled into oVirt code base in controlled translation cycles, so Zanata acts as repository of translations.
Best regards, Julia Dronova
-- С уважением, Дронова Юлия
_______________________________________________ Devel mailing list Devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/devel
Hello Vojtech,
In oVirt 4.0 we'll have default properties files in place. we'll modify the UI i18n implementation so that you don't need to re-build Engine (re-compile GWT UI) in order to see changes you've done to any of properties files. Oh, these are really good news. Thanks a lot for your support and positive devs feedback!
Best regards, Julia Dronova On 9 December 2015 at 18:35, Vojtech Szocs <vszocs@redhat.com> wrote:
From: "Juliette Tux" <juliette.tux@gmail.com> To: "Einav Cohen" <ecohen@redhat.com> Cc: Devel@ovirt.org Sent: Tuesday, December 8, 2015 5:46:17 PM Subject: Re: [ovirt-devel] [Russian oVirt localization] Missing English ApplicationConstants.properties in 3.6
Hi Einav, Hi all,
As I mentioned - these (*English* .properties files) do not exist in
----- Original Message ----- 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.
Hi Juliette,
the default English texts are currently located in Java files, for example:
frontend/webadmin/modules/webadmin/src/main/java/org/ovirt/engine/ui/webadmin/ApplicationConstants.java
with values expressed via Java annotation (like DefaultStringValue):
@DefaultStringValue("oVirt Engine Web Administration") String applicationTitle();
This is definitely not a good practice so in oVirt 4.0 we'll put these default English texts into properties files as you'd normally expect, for example:
frontend/webadmin/modules/webadmin/src/main/resources/org/ovirt/engine/ui/webadmin/ApplicationConstants.properties
Also, we'll modify the UI i18n implementation so that you don't need to re-build Engine (re-compile GWT UI) in order to see changes you've done to any of properties files.
in order to create *_ru_RU.properties files, Russian translations for
need to be uploaded to Zanata's 'oVirt' project first. In most cases in order to create Russian properties I use prop2po and
oVirt 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
For now, please refer to Java files containing default English texts as mentioned by Einav (these currently substitute properties files you are looking for). In oVirt 4.0 we'll have default properties files in place.
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}" 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, t his 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
"${type}\u3092${action}\u3067\u304D\u307E\u305B\u3093\u3002\u30C7\u30D5\u30A9\u30EB\u30C8\u306E 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.
AFAIK, we're using Zanata to help manage (lots of) i18n properties files which are then pulled into oVirt code base in controlled translation cycles, so Zanata acts as repository of translations.
Best regards, Julia Dronova
-- С уважением, Дронова Юлия
_______________________________________________ Devel mailing list Devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/devel
-- С уважением, Дронова Юлия
----- Original Message -----
From: "Juliette Tux" <juliette.tux@gmail.com> Cc: Devel@ovirt.org Sent: Wednesday, December 9, 2015 4:46:34 PM Subject: Re: [ovirt-devel] [Russian oVirt localization] Missing English ApplicationConstants.properties in 3.6
Hello Vojtech,
In oVirt 4.0 we'll have default properties files in place. we'll modify the UI i18n implementation so that you don't need to re-build Engine (re-compile GWT UI) in order to see changes you've done to any of properties files. Oh, these are really good news. Thanks a lot for your support and positive devs feedback!
You are welcome :-) there's a lot of space for improvement in our i18n implementation which we didn't address yet, but we will get to it :P
Best regards, Julia Dronova
On 9 December 2015 at 18:35, Vojtech Szocs < vszocs@redhat.com > wrote:
----- Original Message -----
From: "Juliette Tux" < juliette.tux@gmail.com > To: "Einav Cohen" < ecohen@redhat.com > Cc: Devel@ovirt.org Sent: Tuesday, December 8, 2015 5:46:17 PM Subject: Re: [ovirt-devel] [Russian oVirt localization] Missing English ApplicationConstants.properties in 3.6
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.
Hi Juliette,
the default English texts are currently located in Java files, for example:
frontend/webadmin/modules/webadmin/src/main/java/org/ovirt/engine/ui/webadmin/ApplicationConstants.java
with values expressed via Java annotation (like DefaultStringValue):
@DefaultStringValue("oVirt Engine Web Administration") String applicationTitle();
This is definitely not a good practice so in oVirt 4.0 we'll put these default English texts into properties files as you'd normally expect, for example:
frontend/webadmin/modules/webadmin/src/main/resources/org/ovirt/engine/ui/webadmin/ApplicationConstants.properties
Also, we'll modify the UI i18n implementation so that you don't need to re-build Engine (re-compile GWT UI) in order to see changes you've done to any of properties files.
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
For now, please refer to Java files containing default English texts as mentioned by Einav (these currently substitute properties files you are looking for). In oVirt 4.0 we'll have default properties files in place.
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, t his 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.
AFAIK, we're using Zanata to help manage (lots of) i18n properties files which are then pulled into oVirt code base in controlled translation cycles, so Zanata acts as repository of translations.
Best regards, Julia Dronova
-- С уважением, Дронова Юлия
_______________________________________________ Devel mailing list Devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/devel
-- С уважением, Дронова Юлия
_______________________________________________ Devel mailing list Devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/devel
participants (3)
-
Einav Cohen -
Juliette Tux -
Vojtech Szocs