From noriko at fedoraproject.org Wed Apr 8 01:00:39 2015 From: noriko at fedoraproject.org (Noriko Mizumoto) Date: Wed, 08 Apr 2015 11:00:39 +1000 Subject: [zanata-users] id.fedoraproject.org login problems Message-ID: <55247DB7.6090008@fedoraproject.org> Hi FYI only. Some of translators including myself have the experience of having the login problems to fedora.zanata.org, and reported to Zanata team. It sometime ago has been explained by Zanata team, if my memory serves correct, that the problem is actually due to fedora openid login thus nothing can be done by Zanata side. The bug has been filed at Fedora Infrastructure, and Infra team is working on it. Thought some of you may have interest on this bug. https://fedorahosted.org/fedora-infrastructure/ticket/4710 noriko From dchen at redhat.com Thu Apr 9 06:19:58 2015 From: dchen at redhat.com (Ding Yi Chen) Date: Thu, 9 Apr 2015 02:19:58 -0400 (EDT) Subject: [zanata-users] zanata-client-3.6.0 for fc22, fc21 is pushed to stable In-Reply-To: <308027250.17397989.1428560297377.JavaMail.zimbra@redhat.com> Message-ID: <873448872.17398174.1428560398377.JavaMail.zimbra@redhat.com> I have pushed zanata-client-3.6.0-1 to stable with fc22, fc21 branches. fc20 will be pushed once it reached Package Update Acceptance Criteria (i.e. 11 April) Regards, -- Ding-Yi Chen Software Engineer Internationalization Group DID: +61 7 3514 8239 Email: dchen at redhat.com Red Hat, Asia-Pacific Pty Ltd Level 1, 193 North Quay Brisbane 4000 Office: +61 7 3514 8100 Fax: +61 7 3514 8199 Website: www.redhat.com Red Hat, Inc. Facebook: Red Hat APAC | Red Hat Japan | Red Hat Korea | JBoss APAC Twitter: Red Hat APAC | Red Hat ANZ LinkedIn: Red Hat APAC | JBoss APAC From sflaniga at redhat.com Thu Apr 9 06:23:32 2015 From: sflaniga at redhat.com (Sean Flanigan) Date: Thu, 09 Apr 2015 16:23:32 +1000 Subject: [zanata-users] [zanata-devel] zanata-client-3.6.0 for fc22, fc21 is pushed to stable In-Reply-To: <873448872.17398174.1428560398377.JavaMail.zimbra@redhat.com> References: <873448872.17398174.1428560398377.JavaMail.zimbra@redhat.com> Message-ID: <55261AE4.8050501@redhat.com> On 2015-04-09 16:19, Ding Yi Chen wrote: > I have pushed zanata-client-3.6.0-1 to stable with fc22, fc21 branches. > > fc20 will be pushed once it reached Package Update Acceptance Criteria > (i.e. 11 April) Thanks, Dean. -- Sean Flanigan Principal Software Engineer Localisation Tools Engineering Red Hat -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 213 bytes Desc: OpenPGP digital signature URL: From noriko at redhat.com Mon Apr 20 02:57:14 2015 From: noriko at redhat.com (Noriko Mizumoto) Date: Mon, 20 Apr 2015 12:57:14 +1000 Subject: [zanata-users] unable to access fedora.zanata.org In-Reply-To: <1444807457.12735398.1428549081718.JavaMail.zimbra@redhat.com> References: <1444807457.12735398.1428549081718.JavaMail.zimbra@redhat.com> Message-ID: <55346B0A.7040102@redhat.com> Hi New maintainer of the doc on fedora.zanata.rog has encountered login problem. "When I visit fedora.zanata.org, I only get an nginx welcome page (see attached screenshot)." Could someone kindly attend this problem? Thanks noriko -------------- next part -------------- A non-text attachment was scrubbed... Name: fzo.png Type: image/png Size: 269466 bytes Desc: not available URL: From siepkes at serviceplanet.nl Wed Apr 22 08:48:45 2015 From: siepkes at serviceplanet.nl (Jasper Siepkes) Date: Wed, 22 Apr 2015 10:48:45 +0200 (CEST) Subject: [zanata-users] Zanata Java properties file workflow Message-ID: <1738638618.6884.1429692525912.JavaMail.open-xchange@sponde.serviceplanet.nl> 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 master utf8properties src/main/strings/ src/main/resources/ 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 From pahuang at redhat.com Thu Apr 23 00:32:04 2015 From: pahuang at redhat.com (Patrick Huang) Date: Wed, 22 Apr 2015 20:32:04 -0400 (EDT) Subject: [zanata-users] Zanata Java properties file workflow In-Reply-To: <1738638618.6884.1429692525912.JavaMail.open-xchange@sponde.serviceplanet.nl> References: <1738638618.6884.1429692525912.JavaMail.open-xchange@sponde.serviceplanet.nl> Message-ID: <1189689785.5152726.1429749124443.JavaMail.zimbra@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" > To: "Zanata User Mailinglist" > 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 > master > utf8properties > > src/main/strings/ > src/main/resources/ > > > 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 > From sflaniga at redhat.com Thu Apr 23 01:26:42 2015 From: sflaniga at redhat.com (Sean Flanigan) Date: Thu, 23 Apr 2015 11:26:42 +1000 Subject: [zanata-users] Zanata Java properties file workflow In-Reply-To: <1738638618.6884.1429692525912.JavaMail.open-xchange@sponde.serviceplanet.nl> References: <1738638618.6884.1429692525912.JavaMail.open-xchange@sponde.serviceplanet.nl> Message-ID: <55384A52.5020604@redhat.com> Hi Jasper, (See below.) On 2015-04-22 18:48, Jasper Siepkes wrote: > 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 > master > utf8properties > > src/main/strings/ > src/main/resources/ The src-dir here (src/main/strings/) doesn't match the directory for Source translation file above (src/main/string/). I'm assuming that's a typo in your email, but you might need to double check your translation file name against the trans-dir setting. > > > 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? Can you supply the output of zanata-cli push (both invocations)? > > Kind regards, > > Jasper > > _______________________________________________ > zanata-users mailing list > zanata-users at redhat.com > https://www.redhat.com/mailman/listinfo/zanata-users > -- Sean Flanigan Principal Software Engineer Localisation Tools Engineering Red Hat -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 213 bytes Desc: OpenPGP digital signature URL: From siepkes at serviceplanet.nl Thu Apr 23 07:30:59 2015 From: siepkes at serviceplanet.nl (Jasper Siepkes) Date: Thu, 23 Apr 2015 09:30:59 +0200 (CEST) Subject: [zanata-users] Zanata Java properties file workflow In-Reply-To: <1189689785.5152726.1429749124443.JavaMail.zimbra@redhat.com> References: <1738638618.6884.1429692525912.JavaMail.open-xchange@sponde.serviceplanet.nl> <1189689785.5152726.1429749124443.JavaMail.zimbra@redhat.com> Message-ID: <749493918.7300.1429774260150.JavaMail.open-xchange@sponde.serviceplanet.nl> 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 : > > 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" > > To: "Zanata User Mailinglist" > > 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 > > master > > utf8properties > > > > src/main/strings/ > > src/main/resources/ > > > > > > 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 > > > From pahuang at redhat.com Fri Apr 24 05:58:23 2015 From: pahuang at redhat.com (Patrick Huang) Date: Fri, 24 Apr 2015 01:58:23 -0400 (EDT) Subject: [zanata-users] Zanata Java properties file workflow In-Reply-To: <749493918.7300.1429774260150.JavaMail.open-xchange@sponde.serviceplanet.nl> References: <1738638618.6884.1429692525912.JavaMail.open-xchange@sponde.serviceplanet.nl> <1189689785.5152726.1429749124443.JavaMail.zimbra@redhat.com> <749493918.7300.1429774260150.JavaMail.open-xchange@sponde.serviceplanet.nl> Message-ID: <1144306946.6203530.1429855103699.JavaMail.zimbra@redhat.com> Hi Jasper, I just did a test case on my local machine and your use case should be supported (and it works for me). My project structure: ./zanata.xml ./src/messages.properties ./resources/messages_en_US.properties content of my zanata.xml: http://localhost:8080/zanata/ jasper master utf8properties src resources en-US After I run: zanata-cli push --push-type both --src-lang en-US I got: [INFO] Loading project config from zanata.xml [INFO] Loading user config from /home/pahuang/.config/zanata.ini [INFO] client API version: 3.4.1, server API version: 3.7.0-SNAPSHOT [WARN] client API version is 3.4.1, but server API version is 3.7.0-SNAPSHOT [INFO] Server: http://localhost:8080/zanata/ [INFO] Project: jasper [INFO] Version: master [INFO] Username: admin [INFO] Project type: utf8properties [INFO] Source language: en-US [INFO] Copy previous translations: true [INFO] Merge type: AUTO [INFO] Enable modules: false [INFO] Include patterns: [INFO] Exclude patterns: [INFO] Case sensitive: true [INFO] Default excludes: true [INFO] Exclude locale filenames: true [INFO] Pushing source and target documents [INFO] Locales to push: [en-US] [INFO] Current directory: /home/pahuang/work/test/jasper [INFO] Source directory (originals): src [INFO] Target base directory (translations): resources [INFO] Found source documents: [INFO] messages [WARN] pushType set to 'Both': existing translations on server may be overwritten/deleted This will overwrite existing documents AND TRANSLATIONS on the server, and delete obsolete documents. Are you sure (y/n)? y [INFO] pushing source doc [name=messages size=2] to server Done in 1 secs [INFO] Pushing target doc [name=messages size=2 client-locale=en-US] to server [locale=en-US] Done in 0 secs [INFO] Running Copy Trans for messages Done in 0 secs The client version I used is 3.4.0 (latest is 3.6.0). Server version is our current master but it shouldn't matter. Make sure when you push translation, you see a log message like "[INFO] Pushing target doc [name=...". If not, you will need to double check your console output and compare then to your project file structure and make sure it is correct. e.g. from my output, [INFO] Current directory: /home/pahuang/work/test/jasper [INFO] Source directory (originals): src [INFO] Target base directory (translations): resources This tells me it would expect to find a translation file at /home/pahuang/work/test/jasper/resources/messages_en_US.properties (combination of current dir and target base dir, then source document name plus locale). If you still couldn't get it to work, you can send me your files (with sensitive information removed) and I can see what I can do. Hope this helps. Regards, Patrick Huang Senior Software Engineer Engineering - Internationalisation Red Hat ----- Original Message ----- > From: "Jasper Siepkes" > To: "Patrick Huang" > Cc: "Zanata User Mailinglist" > Sent: Thursday, April 23, 2015 5:30:59 PM > Subject: Re: [zanata-users] Zanata Java properties file workflow > > 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 : > > > > 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" > > > To: "Zanata User Mailinglist" > > > 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 > > > master > > > utf8properties > > > > > > src/main/strings/ > > > src/main/resources/ > > > > > > > > > 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 > > > > > > > From siepkes at serviceplanet.nl Fri Apr 24 06:49:40 2015 From: siepkes at serviceplanet.nl (Jasper Siepkes) Date: Fri, 24 Apr 2015 08:49:40 +0200 (CEST) Subject: [zanata-users] Zanata Java properties file workflow In-Reply-To: <1144306946.6203530.1429855103699.JavaMail.zimbra@redhat.com> References: <1738638618.6884.1429692525912.JavaMail.open-xchange@sponde.serviceplanet.nl> <1189689785.5152726.1429749124443.JavaMail.zimbra@redhat.com> <749493918.7300.1429774260150.JavaMail.open-xchange@sponde.serviceplanet.nl> <1144306946.6203530.1429855103699.JavaMail.zimbra@redhat.com> Message-ID: <16457984.7748.1429858180525.JavaMail.open-xchange@sponde.serviceplanet.nl> Hi Patrick, Thanks for taking the time to help me! I double checked everything but it still isn't working (maybe i'm missing something). My zanata.xml: ----8<-------------------- https://translate.serviceplanet.nl/ firkraag-ziggo-consumer master utf8properties src/main/strings/ src/main/resources/ nl-NL ----8<-------------------- The source file and previously generated target file: ----8<-------------------- $ ls -las src/main/strings/ total 76 0 drwxrwxr-x 2 siepkes siepkes 40 Apr 23 11:57 . 0 drwxrwxr-x 7 siepkes siepkes 73 Apr 23 11:57 .. 76 -rw-rw-r-- 1 siepkes siepkes 77784 Apr 23 11:57 MessageResources.properties $ ls -als src/main/resources/nl/serviceplanet/firkraag/ziggo/view/messages/ total 76 0 drwxrwxr-x 2 siepkes siepkes 46 Apr 23 11:57 . 0 drwxrwxr-x 3 siepkes siepkes 21 Apr 23 11:57 .. 76 -rw-rw-r-- 1 siepkes siepkes 77715 Apr 23 11:57 MessageResources_nl_NL.properties ----8<-------------------- Running zanata-cli: ----8<-------------------- [siepkes at ws0080 ziggo.consumer]$ ~/Programs/zanata-cli-3.6.0/bin/zanata-cli push --push-type both --src-lang nl-NL [INFO] Loading project config from zanata.xml [INFO] Loading user config from /home/siepkes/.config/zanata.ini [INFO] client API version: 3.4.1, server API version: 3.6.0 [WARN] client API version is 3.4.1, but server API version is 3.6.0 [INFO] Server: https://translate.serviceplanet.nl/ [INFO] Project: firkraag-ziggo-consumer [INFO] Version: master [INFO] Username: siepkes [INFO] Project type: utf8properties [INFO] Source language: nl-NL [INFO] Copy previous translations: true [INFO] Merge type: AUTO [INFO] Enable modules: false [INFO] Include patterns: [INFO] Exclude patterns: [INFO] Case sensitive: true [INFO] Default excludes: true [INFO] Exclude locale filenames: true [INFO] Pushing source and target documents [INFO] Locales to push: [nl-NL] [INFO] Current directory: /home/siepkes/git/sp-projects/firkraag/ziggo.consumer [INFO] Source directory (originals): src/main/strings [INFO] Target base directory (translations): src/main/resources [INFO] Found source documents: [INFO] MessageResources [WARN] pushType set to 'Both': existing translations on server may be overwritten/deleted This will overwrite existing documents AND TRANSLATIONS on the server, and delete obsolete documents. Are you sure (y/n)? y [INFO] pushing source doc [name=MessageResources size=375] to server Done in 0 secs [INFO] Running Copy Trans for MessageResources ----8<-------------------- In the portal the source document shows up but the translation for nl-NL contains no translated values, only keys. The resources files don't really contain any sensitive data, just a lot of text. But I prefer them not lingering around on the nets so i'll send them to you directly. Kind regards, Jasper > Op 24 april 2015 om 7:58 schreef Patrick Huang : > > Hi Jasper, > > I just did a test case on my local machine and your use case should be > supported (and it works for me). > My project structure: > ./zanata.xml > ./src/messages.properties > ./resources/messages_en_US.properties > > content of my zanata.xml: > > > http://localhost:8080/zanata/ > jasper > master > utf8properties > > src > resources > > en-US > > After I run: zanata-cli push --push-type both --src-lang en-US > I got: > [INFO] Loading project config from zanata.xml > [INFO] Loading user config from /home/pahuang/.config/zanata.ini > [INFO] client API version: 3.4.1, server API version: 3.7.0-SNAPSHOT > [WARN] client API version is 3.4.1, but server API version is 3.7.0-SNAPSHOT > [INFO] Server: http://localhost:8080/zanata/ > [INFO] Project: jasper > [INFO] Version: master > [INFO] Username: admin > [INFO] Project type: utf8properties > [INFO] Source language: en-US > [INFO] Copy previous translations: true > [INFO] Merge type: AUTO > [INFO] Enable modules: false > [INFO] Include patterns: > [INFO] Exclude patterns: > [INFO] Case sensitive: true > [INFO] Default excludes: true > [INFO] Exclude locale filenames: true > [INFO] Pushing source and target documents > [INFO] Locales to push: [en-US] > [INFO] Current directory: /home/pahuang/work/test/jasper > [INFO] Source directory (originals): src > [INFO] Target base directory (translations): resources > [INFO] Found source documents: > [INFO] messages > [WARN] pushType set to 'Both': existing translations on server may be > overwritten/deleted > This will overwrite existing documents AND TRANSLATIONS on the server, and > delete obsolete documents. > > Are you sure (y/n)? y > [INFO] pushing source doc [name=messages size=2] to server > Done in 1 secs > [INFO] Pushing target doc [name=messages size=2 client-locale=en-US] to server > [locale=en-US] > Done in 0 secs > [INFO] Running Copy Trans for messages > Done in 0 secs > > The client version I used is 3.4.0 (latest is 3.6.0). Server version is our > current master but it shouldn't matter. Make sure when you push translation, > you see a log message like "[INFO] Pushing target doc [name=...". If not, you > will need to double check your console output and compare then to your project > file structure and make sure it is correct. e.g. from my output, > [INFO] Current directory: /home/pahuang/work/test/jasper > [INFO] Source directory (originals): src > [INFO] Target base directory (translations): resources > This tells me it would expect to find a translation file at > /home/pahuang/work/test/jasper/resources/messages_en_US.properties > (combination of current dir and target base dir, then source document name > plus locale). > > If you still couldn't get it to work, you can send me your files (with > sensitive information removed) and I can see what I can do. Hope this helps. > > Regards, > Patrick Huang > Senior Software Engineer > Engineering - Internationalisation > Red Hat > > ----- Original Message ----- > > From: "Jasper Siepkes" > > To: "Patrick Huang" > > Cc: "Zanata User Mailinglist" > > Sent: Thursday, April 23, 2015 5:30:59 PM > > Subject: Re: [zanata-users] Zanata Java properties file workflow > > > > 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 : > > > > > > 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" > > > > To: "Zanata User Mailinglist" > > > > 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 > > > > master > > > > utf8properties > > > > > > > > src/main/strings/ > > > > src/main/resources/ > > > > > > > > > > > > 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 > > > > > > > > > > > > From pahuang at redhat.com Mon Apr 27 00:37:34 2015 From: pahuang at redhat.com (Patrick Huang) Date: Sun, 26 Apr 2015 20:37:34 -0400 (EDT) Subject: [zanata-users] Zanata Java properties file workflow In-Reply-To: <16457984.7748.1429858180525.JavaMail.open-xchange@sponde.serviceplanet.nl> References: <1738638618.6884.1429692525912.JavaMail.open-xchange@sponde.serviceplanet.nl> <1189689785.5152726.1429749124443.JavaMail.zimbra@redhat.com> <749493918.7300.1429774260150.JavaMail.open-xchange@sponde.serviceplanet.nl> <1144306946.6203530.1429855103699.JavaMail.zimbra@redhat.com> <16457984.7748.1429858180525.JavaMail.open-xchange@sponde.serviceplanet.nl> Message-ID: <1221002755.6965959.1430095054151.JavaMail.zimbra@redhat.com> Hi Jasper, Zanata cli couldn't find your translation file because it will expect it to be at "src/main/resources/MessageResources_nl_NL.properties"(trans-dir, plus source document relative path to src-dir, plus source document name, plus locale, plus file extension). But yours is at "src/main/resources/nl/serviceplanet/firkraag/ziggo/view/messages/MessageResources_nl_NL.properties". Therefore it couldn't find it. There is a in depth example in http://zanata.org/help/cli-configuration/ under "Translation files mapping rules". Not that you need to use file mapping rules but the concept is the same. To fix it you just need to change your in zanata.xml to "src/main/resources/nl/serviceplanet/firkraag/ziggo/view/messages/" assuming it will always go to that directory. If later on you change your package name or structure in your code you will need to update trans-dir as well. Regards Patrick Huang Senior Software Engineer Engineering - Internationalisation Red Hat ----- Original Message ----- > From: "Jasper Siepkes" > To: "Patrick Huang" > Cc: "Zanata User Mailinglist" > Sent: Friday, April 24, 2015 4:49:40 PM > Subject: Re: [zanata-users] Zanata Java properties file workflow > > Hi Patrick, > > Thanks for taking the time to help me! I double checked everything but it > still > isn't working (maybe i'm missing something). > > My zanata.xml: > ----8<-------------------- > > > https://translate.serviceplanet.nl/ > firkraag-ziggo-consumer > master > utf8properties > > src/main/strings/ > src/main/resources/ > > > nl-NL > > > > ----8<-------------------- > > The source file and previously generated target file: > ----8<-------------------- > $ ls -las src/main/strings/ > total 76 > 0 drwxrwxr-x 2 siepkes siepkes 40 Apr 23 11:57 . > 0 drwxrwxr-x 7 siepkes siepkes 73 Apr 23 11:57 .. > 76 -rw-rw-r-- 1 siepkes siepkes 77784 Apr 23 11:57 > MessageResources.properties > > $ ls -als src/main/resources/nl/serviceplanet/firkraag/ziggo/view/messages/ > total 76 > 0 drwxrwxr-x 2 siepkes siepkes 46 Apr 23 11:57 . > 0 drwxrwxr-x 3 siepkes siepkes 21 Apr 23 11:57 .. > 76 -rw-rw-r-- 1 siepkes siepkes 77715 Apr 23 11:57 > MessageResources_nl_NL.properties > ----8<-------------------- > > Running zanata-cli: > ----8<-------------------- > [siepkes at ws0080 ziggo.consumer]$ ~/Programs/zanata-cli-3.6.0/bin/zanata-cli > push > --push-type both --src-lang nl-NL > [INFO] Loading project config from zanata.xml > [INFO] Loading user config from /home/siepkes/.config/zanata.ini > [INFO] client API version: 3.4.1, server API version: 3.6.0 > [WARN] client API version is 3.4.1, but server API version is 3.6.0 > [INFO] Server: https://translate.serviceplanet.nl/ > [INFO] Project: firkraag-ziggo-consumer > [INFO] Version: master > [INFO] Username: siepkes > [INFO] Project type: utf8properties > [INFO] Source language: nl-NL > [INFO] Copy previous translations: true > [INFO] Merge type: AUTO > [INFO] Enable modules: false > [INFO] Include patterns: > [INFO] Exclude patterns: > [INFO] Case sensitive: true > [INFO] Default excludes: true > [INFO] Exclude locale filenames: true > [INFO] Pushing source and target documents > [INFO] Locales to push: [nl-NL] > [INFO] Current directory: > /home/siepkes/git/sp-projects/firkraag/ziggo.consumer > [INFO] Source directory (originals): src/main/strings > [INFO] Target base directory (translations): src/main/resources > [INFO] Found source documents: > [INFO] MessageResources > [WARN] pushType set to 'Both': existing translations on server may be > overwritten/deleted > This will overwrite existing documents AND TRANSLATIONS on the server, and > delete obsolete documents. > > Are you sure (y/n)? y > [INFO] pushing source doc [name=MessageResources size=375] to server > Done in 0 secs > [INFO] Running Copy Trans for MessageResources > ----8<-------------------- > > In the portal the source document shows up but the translation for nl-NL > contains no translated values, only keys. > > The resources files don't really contain any sensitive data, just a lot of > text. > But I prefer them not lingering around on the nets so i'll send them to you > directly. > > Kind regards, > > Jasper > > > Op 24 april 2015 om 7:58 schreef Patrick Huang : > > > > Hi Jasper, > > > > I just did a test case on my local machine and your use case should be > > supported (and it works for me). > > My project structure: > > ./zanata.xml > > ./src/messages.properties > > ./resources/messages_en_US.properties > > > > content of my zanata.xml: > > > > > > http://localhost:8080/zanata/ > > jasper > > master > > utf8properties > > > > src > > resources > > > > en-US > > > > After I run: zanata-cli push --push-type both --src-lang en-US > > I got: > > [INFO] Loading project config from zanata.xml > > [INFO] Loading user config from /home/pahuang/.config/zanata.ini > > [INFO] client API version: 3.4.1, server API version: 3.7.0-SNAPSHOT > > [WARN] client API version is 3.4.1, but server API version is > > 3.7.0-SNAPSHOT > > [INFO] Server: http://localhost:8080/zanata/ > > [INFO] Project: jasper > > [INFO] Version: master > > [INFO] Username: admin > > [INFO] Project type: utf8properties > > [INFO] Source language: en-US > > [INFO] Copy previous translations: true > > [INFO] Merge type: AUTO > > [INFO] Enable modules: false > > [INFO] Include patterns: > > [INFO] Exclude patterns: > > [INFO] Case sensitive: true > > [INFO] Default excludes: true > > [INFO] Exclude locale filenames: true > > [INFO] Pushing source and target documents > > [INFO] Locales to push: [en-US] > > [INFO] Current directory: /home/pahuang/work/test/jasper > > [INFO] Source directory (originals): src > > [INFO] Target base directory (translations): resources > > [INFO] Found source documents: > > [INFO] messages > > [WARN] pushType set to 'Both': existing translations on server may be > > overwritten/deleted > > This will overwrite existing documents AND TRANSLATIONS on the server, and > > delete obsolete documents. > > > > Are you sure (y/n)? y > > [INFO] pushing source doc [name=messages size=2] to server > > Done in 1 secs > > [INFO] Pushing target doc [name=messages size=2 client-locale=en-US] to > > server > > [locale=en-US] > > Done in 0 secs > > [INFO] Running Copy Trans for messages > > Done in 0 secs > > > > The client version I used is 3.4.0 (latest is 3.6.0). Server version is our > > current master but it shouldn't matter. Make sure when you push > > translation, > > you see a log message like "[INFO] Pushing target doc [name=...". If not, > > you > > will need to double check your console output and compare then to your > > project > > file structure and make sure it is correct. e.g. from my output, > > [INFO] Current directory: /home/pahuang/work/test/jasper > > [INFO] Source directory (originals): src > > [INFO] Target base directory (translations): resources > > This tells me it would expect to find a translation file at > > /home/pahuang/work/test/jasper/resources/messages_en_US.properties > > (combination of current dir and target base dir, then source document name > > plus locale). > > > > If you still couldn't get it to work, you can send me your files (with > > sensitive information removed) and I can see what I can do. Hope this > > helps. > > > > Regards, > > Patrick Huang > > Senior Software Engineer > > Engineering - Internationalisation > > Red Hat > > > > ----- Original Message ----- > > > From: "Jasper Siepkes" > > > To: "Patrick Huang" > > > Cc: "Zanata User Mailinglist" > > > Sent: Thursday, April 23, 2015 5:30:59 PM > > > Subject: Re: [zanata-users] Zanata Java properties file workflow > > > > > > 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 : > > > > > > > > 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" > > > > > To: "Zanata User Mailinglist" > > > > > 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 > > > > > master > > > > > utf8properties > > > > > > > > > > src/main/strings/ > > > > > src/main/resources/ > > > > > > > > > > > > > > > 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 > > > > > > > > > > > > > > > > > > > From bkearney at redhat.com Tue Apr 28 13:29:37 2015 From: bkearney at redhat.com (Bryan Kearney) Date: Tue, 28 Apr 2015 09:29:37 -0400 Subject: [zanata-users] po pull is not putting translations into the directories Message-ID: <553F8B41.8040103@redhat.com> I have a project which is project type podir. My directory is set up so that the pot file is in locale and the translation shoudl be in a subdirectory (i.e. ru/ru.po). If I execute "zanata po pull" and it puts the ru.po file in the same directory as the pot file (/locale/ru.po). zanata-python-client-1.3.21-1.fc21.noarch zanata-common-3.3.0-4.fc21.noarch zanata-api-3.4.1-1.fc21.noarch zanata-client-3.6.0-1.fc21.noarch Note.. i can not use the ivy client since I am getting certificate errors again. is there a work around for this? -- bk From sflaniga at redhat.com Wed Apr 29 05:22:38 2015 From: sflaniga at redhat.com (Sean Flanigan) Date: Wed, 29 Apr 2015 15:22:38 +1000 Subject: [zanata-users] po pull is not putting translations into the directories In-Reply-To: <553F8B41.8040103@redhat.com> References: <553F8B41.8040103@redhat.com> Message-ID: <55406A9E.2050104@redhat.com> On 2015-04-28 23:29, Bryan Kearney wrote: > I have a project which is project type podir. My directory is set up so > that the pot file is in locale and the translation shoudl be in a > subdirectory (i.e. ru/ru.po). > > If I execute "zanata po pull" and it puts the ru.po file in the same > directory as the pot file (/locale/ru.po). That does sound like a bug in the python client, assuming that the type has been set to podir correctly (via zanata.xml or command line). I can't remember, does the python client log which project type it found? (I'm more familiar with the Java clients like zanata-ivy.) > zanata-python-client-1.3.21-1.fc21.noarch > zanata-common-3.3.0-4.fc21.noarch > zanata-api-3.4.1-1.fc21.noarch > zanata-client-3.6.0-1.fc21.noarch > > Note.. i can not use the ivy client since I am getting certificate > errors again. is there a work around for this? Are you referring to certificate errors when connecting to a server with a certificate issued by a non-public CA? Such an error would be similar to this: javax.net.ssl.SSLHandshakeException: sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target The best and most secure solution is to install the missing CA certificate into Java's trusted certificate store. Something like this: $ keytool -keystore $keystore -storepass changeit -import -noprompt -alias internalca -file ./internalca.crt - where $keystore is probably /etc/pki/java/cacerts or something like /usr/lib/jvm/java-1.7.0/jre/lib/security/cacerts and internalca.crt is a copy of the CA cert in PEM format. The workaround is to use the command line option --disable-ssl-cert, but of course this is much less secure. -- Sean Flanigan Principal Software Engineer Localisation Tools Engineering Red Hat -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 213 bytes Desc: OpenPGP digital signature URL: From bkearney at redhat.com Wed Apr 29 12:58:18 2015 From: bkearney at redhat.com (Bryan Kearney) Date: Wed, 29 Apr 2015 08:58:18 -0400 Subject: [zanata-users] po pull is not putting translations into the directories In-Reply-To: <55406A9E.2050104@redhat.com> References: <553F8B41.8040103@redhat.com> <55406A9E.2050104@redhat.com> Message-ID: <5540D56A.9050105@redhat.com> On 04/29/2015 01:22 AM, Sean Flanigan wrote: > On 2015-04-28 23:29, Bryan Kearney wrote: >> I have a project which is project type podir. My directory is set up so >> that the pot file is in locale and the translation shoudl be in a >> subdirectory (i.e. ru/ru.po). >> >> If I execute "zanata po pull" and it puts the ru.po file in the same >> directory as the pot file (/locale/ru.po). > > That does sound like a bug in the python client, assuming that the type > has been set to podir correctly (via zanata.xml or command line). I > can't remember, does the python client log which project type it found? > (I'm more familiar with the Java clients like zanata-ivy.) I have opened https://bugzilla.redhat.com/show_bug.cgi?id=1217041. Is there any chance to move to a single CLI? My experience tends to be: "Me: I have issue with ivy client" "Zanata: Use Python client"