9:03 a.m.
Hi,
When I'm trying to compile ovirt-engine-3.5 branch with pulled zanata
source files, I get webadmin compilation errors. And the error message lead
me to the outdated zanata translation
file: org.ovirt.engine.ui.webadmin.ApplicationMessages
The file has a source text called "{0} (VLAN {1})", but recent commit
b068ec755198c27e65f936809104ba5068cd8fd2
has changed the text to "(VLAN {0})"
So is there a way to update the zanata's source text (text on the left) ?
It seems that I don't get any options to update it, I can only update the
target text (text on the right).
thanks.
2:45 p.m.
On Sunday, December 14, 2014 03:03:56 PM plysan wrote:
The zanata source text is generated from default values from the ovirt source
code. Einav should know more about exactly how that is done. You should always
match the translation to the source and not the other way around. So I am not
sure why you are trying to change the source.
4:27 p.m.
Alexander is correct; the source text cannot and should not be changed
directly in Zanata.
in order to update the source (English) text in Zanata, it needs to be
pushed to Zanata from the source code.
generally, we are not updating anything in Zanata for 3.5 anymore, since
we are not planning any additional translation cycles for ovirt 3.5;
however, since we are planning out-of-cycle possible updates for the German
and Italian translation as an exception for 3.5, it *may* also involve
pushing the updated source text to Zanata as part of the process, but this
will not happen any time soon, to my understanding.
I am not sure if you were trying to pull the latest translations from Zanata
and then build ovirt-engine-3.5, or simply tried to build ovirt-engine-3.5
as is;
if you were trying to build ovirt-engine-3.5 as-is and failed, that's bad -
we need to fix that ASAP (however, I am pretty sure that we would have been
notified about this issue already from jenkins / other people / etc.).
I recommend to not attempt pulling the translations from Zanata yourself,
as the pull itself is not enough - need to move some files around, run a few
clean-up scripts, etc. If you still want to pull the translations yourself,
and you are encountering problems as the ones you mentioned above - simply
remove/"fix" the problematic translations *locally on the .properties files
that you pulled from Zanata - NOT in Zanata itself*.
4:35 a.m.
2014-12-15 22:27 GMT+08:00 Einav Cohen <ecohen(a)redhat.com>:
Thanks for your responses.
If I want to make some translation updates in zh_CN, Is it means that the
workflow is first modifying ovirt source code translations and then update
it to zanata ?
But zanata has a user friendly UI and has features that translator likes.
So I think first modifying translations in zanata and then update it to the
source code is better. Just my thoughts :)
thanks.
8:16 a.m.
Hi plysan, I wrongfully thought that you would like to pull updated translations
from Zanata, rather than update the translations yourself (based on updated
source text).
you should definitely update translations via Zanata, not via the source code.
Generally: Source (English) text should be pushed from the code to Zanata,
translations should be updated in Zanata, then pulled from Zanata to the code.
as we are basically already done with 3.5 translations and translation cycles
for 3.6 are still far away, we are not planning to update anything in Zanata
any time soon. however, as I mentioned, since we are planning exceptional out-
of-cycle translation updates (for Italian and German), we may do a push of
updated source text to Zanata some time soon (not in the very near future though).
I prefer to not do any source-pushing to Zanata right now, since AFAIK there is
a heavy translation work that is being done in Italian and German, and I would
like to avoid interrupting that work as much as I can. Once this translation work
will be done, and assuming I will be pushing the updated source text to Zanata
as part of the process of pulling the updated translations, I will update on-list.
2:52 p.m.
On Tuesday, December 16, 2014 10:35:18 AM plysan wrote:
The flow for some new text is the following:
1. The developer writes some new functionality.
2. The developer writes the *English* default message for that functionality.
This includes a key to be used by the translators.
3. Some process takes those new message(s) and puts the *English* translation
and the key into zanata.
4. The translator sees the key AND the English version in zanata and provides
the localized version in zanata.
5. Some process pulls the translation from zanata and puts it into the source
code (In a properties file).
As you can see by the workflow the translator simply translated the English
version of some message in zanata and that then automatically gets into the
source code without the translator having to do anything besides that. Once
you have made the change in zanata it will eventually end up in the project.
The process in step 5 is not automatic.
Now if you want to change a message in a particular locale and immediately see
it, then you have manually modify the properties file for the locale you are
interested in and compile the project.
3767
days inactive
3769
days old
6 comments
3 participants
participants (3)
-
Alexander Wels -
Einav Cohen -
plysan