[ovirt-users] How to update zanata's source text ?

[plysan]

2014-12-16 20:52 GMT+08:00 Alexander Wels <awels at redhat.com>:
>
> On Tuesday, December 16, 2014 10:35:18 AM plysan wrote:
> > 2014-12-15 22:27 GMT+08:00 Einav Cohen <ecohen at redhat.com>:
> > > > ----- Original Message -----
> > > > From: "Alexander Wels" <awels at redhat.com>
> > > > Sent: Monday, December 15, 2014 7:45:41 AM
> > > >
> > > > On Sunday, December 14, 2014 03:03:56 PM plysan wrote:
> > > > > 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.
> > > >
> > > > 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.
> > >
> > > 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*.
> >
> > 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 :)
> >
>
> 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.
>

Thanks for your answer, I think for now I'll just update to the zanata
project and compile it myself :P

>
> > thanks.
> >
> > > > _______________________________________________
> > > > Users mailing list
> > > > Users at ovirt.org
> > > > http://lists.ovirt.org/mailman/listinfo/users
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ovirt.org/pipermail/users/attachments/20141217/9ab1377f/attachment-0001.html>