[zanata-users] Zanata Java properties file workflow

Jasper Siepkes siepkes at serviceplanet.nl
Thu Apr 23 07:30:59 UTC 2015


Hi Patrick,

The reason is because we (the "programmers") created the source resource file
"MessageResources.properties" (which also happens to be in nl-NL). However all
the text in the application needs to be maintained by other people. The reason
that our source language nl-NL also needs to come from Zanata is that we
programmers make all kinds of horrible spelling and grammar mistakes, even in
our first language. The highest grade I ever got for Dutch was a 6 (out of 10
;-)...

I realize this maybe not standard usage of Zanata but what would be the best way
to proceed? Create an empty source file with only keys and no translation values
and push that to Zanata? The translation upload from our source file would only
be one time then. After which we would just remove all the translation values
from it.

We don't have any trouble with translation files in other languages; The normal
Zanata workflow works fine with that.

Kind regards,

Jasper 

> Op 23 april 2015 om 2:32 schreef Patrick Huang <pahuang at redhat.com>:
> 
> Hi Jasper,
> 
> Glad you like it. 
> 
> Without going into much debugging details, it seems odd that you have a source
> using nl-NL and a target using nl-Nl as well. If they are the same, nothing
> need to be translated. Do you have another sample translation file that is in
> other languages? Meanwhile I will try to see if I can reproduce the issue
> locally.
> 
> Regards,
> Patrick Huang
> Senior Software Engineer
> Engineering - Internationalisation
> Red Hat
> 
> ----- Original Message -----
> > From: "Jasper Siepkes" <siepkes at serviceplanet.nl>
> > To: "Zanata User Mailinglist" <zanata-users at redhat.com>
> > Sent: Wednesday, April 22, 2015 6:48:45 PM
> > Subject: [zanata-users] Zanata Java properties file workflow
> > 
> > Hi all,
> > 
> > I've been playing around with Zanata and I really like it! I've got the hang
> > of
> > most of the basics but one thing eludes me:
> > 
> > Let say I have a "MessageResources.properties" file which I consider the
> > translation source. The base language of this file is Dutch (nl-NL).
> > 
> > So my layout is like this:
> > 
> > Source translation file: src/main/string/MessageResources.properties
> > Sample target translation file:
> > src/main/resources/MessageResources_nl_NL.properties
> > 
> > My zanata.xml is configured as follows:
> > 
> > ----8<-------------------------------
> > https://internal.foo.bar/
> > foo-project
> > <project-version>master</project-version>
> > <project-type>utf8properties</project-type>
> > 
> > <src-dir>src/main/strings/</src-dir>
> > <trans-dir>src/main/resources/</trans-dir>
> > 
> > 
> > nl-NL
> > 
> > ----8<-------------------------------
> > 
> > Now when I run:
> > $ zanata-cli push --src-lang nl-NL
> > $ zanata-cli push --push-type trans --src-lang nl-NL
> > 
> > I would expect that the keys and translations get added to zanata. However
> > all
> > the keys (and document) get added to Zanata but none of the translations are
> > there. Am I making some kind of error in my thinking in the way I should
> > work
> > with Zanata or is this a bug?
> > 
> > Kind regards,
> > 
> > Jasper
> > 
> > _______________________________________________
> > zanata-users mailing list
> > zanata-users at redhat.com
> > https://www.redhat.com/mailman/listinfo/zanata-users
> >

>




More information about the zanata-users mailing list