From aeng at redhat.com Tue Sep 5 05:32:32 2017 From: aeng at redhat.com (Alex Eng) Date: Tue, 5 Sep 2017 15:32:32 +1000 Subject: [zanata-users] Zanata.org update - website design Message-ID: Hi, We have updated the design and contents of our home page *http://zanata.org/ * for better user experience. Any feedback is welcome. -- ALEX ENG SENIOR SOFTWARE ENGINEER, team lead globalisation tooling, customer platform Red Hat Asia-Pacific Pty Ltd Brisbane, Australia aeng at redhat.com M: +61423353457 IM: aeng -------------- next part -------------- An HTML attachment was scrubbed... URL: From dchen at redhat.com Mon Sep 11 00:32:17 2017 From: dchen at redhat.com (Ding Yi Chen) Date: Sun, 10 Sep 2017 20:32:17 -0400 (EDT) Subject: [zanata-users] Invalid release: platform-4.2.4 In-Reply-To: <186120726.6860857.1505089499210.JavaMail.zimbra@redhat.com> Message-ID: <1963502036.6861130.1505089937446.JavaMail.zimbra@redhat.com> Hi, We are sorry to announce that, due to our process error, platform-4.2.4 is invalid. We are aware of the issue and are working to fix it as soon as possible. In the meantime, please downgrade to 4.2.1. Regards, -- Ding-Yi CHEN Software Engineer, Globalization Group Red Hat Asia-Pacific Pty Ltd dchen at redhat.com Twitter: @redhatway | Instagram: @redhatinc | Snapchat: @redhatsnaps From sflaniga at redhat.com Mon Sep 11 02:14:46 2017 From: sflaniga at redhat.com (Sean Flanigan) Date: Mon, 11 Sep 2017 12:14:46 +1000 Subject: [zanata-users] [zanata-devel] Invalid release: platform-4.2.4 In-Reply-To: <1963502036.6861130.1505089937446.JavaMail.zimbra@redhat.com> References: <186120726.6860857.1505089499210.JavaMail.zimbra@redhat.com> <1963502036.6861130.1505089937446.JavaMail.zimbra@redhat.com> Message-ID: What actually happened is that the *master* branch (with new, less tested code) was accidentally merged into the *release* branch (older, more stable code). These changes went into the invalid 4.2.4 release. Note that we are now using GitHub's protected branch feature to minimise the chances of this happening again! To fix the *release* branch, we would have to revert 400+ commits, or rewrite the history of the branch (eg git reset to commit 73b1dd29), both unpleasant options with side effects. Then we would have to cherry-pick various fixes into *release* again, fix merge conflicts and do a fair bit of testing. This would also mean that Zanata 4.2.5 would have some older code in it (missing bug-fixes and features) compared to the invalid release 4.2.4. The release testing for Zanata 4.3 is starting soon anyway, so we've decided instead to declare the *release* branch (and Zanata 4.2.5) a lost cause. *If you're running Zanata 4.2.1*, hang on, Zanata 4.3 should be along soon. *If you're running Zanata 4.2.4*, you're really running a pre-release version of Zanata 4.3.0, so you might want to downgrade to 4.2.1 for now. *If you're working on Zanata's codebase*, please don't work from the *release* branch until we have branched for 4.3, probably later this week. Until then, you should probably work with the *master* branch. If you *really* need to do maintenance work on 4.2, please talk to us on the zanata-devel mailing list and we'll try to help. Regards, Sean. On 11 September 2017 at 10:32, Ding Yi Chen wrote: > Hi, > > We are sorry to announce that, due to our process error, platform-4.2.4 is > invalid. > > We are aware of the issue and are working to fix it as soon as possible. > In the meantime, please downgrade to 4.2.1. > > Regards, > > -- > Ding-Yi CHEN > > Software Engineer, Globalization Group > Red Hat Asia-Pacific Pty Ltd > dchen at redhat.com > Twitter: @redhatway | Instagram: @redhatinc | Snapchat: @redhatsnaps > > _______________________________________________ > zanata-devel mailing list > zanata-devel at redhat.com > https://www.redhat.com/mailman/listinfo/zanata-devel > -- Sean Flanigan Principal Software Engineer Globalisation Tools Engineering Red Hat -------------- next part -------------- An HTML attachment was scrubbed... URL: From sbeaver at netgate.com Wed Sep 20 11:48:12 2017 From: sbeaver at netgate.com (Stephen Beaver) Date: Wed, 20 Sep 2017 07:48:12 -0400 Subject: [zanata-users] Unable to download .po files this mornng Message-ID: zanata-cli -e -B pull ? master ? [INFO] Loading project config from zanata.xml [INFO] Loading user config from /Users/xxxx/.config/zanata.ini [INFO] Error stacktraces are turned on. [INFO] client API version: 4.2.4, server API version: 3.9.1 [WARN] client API version is 4.2.4, but server API version is 3.9.1 [INFO] Server: https://translate.zanata.org/ [INFO] Project: xxxxxxx [INFO] Version: 2.4 [INFO] Username: xxxxxx [INFO] Project type: gettext [INFO] Enable modules: false [INFO] Using ETag cache: true [INFO] Purging ETag cache beforehand: false [INFO] Locales to pull: [bg, me-ME, fr, bn-BD, br, bs, si, ka, mai, sk, sl, ga, bn-IN, ca, sq, kk, kn, or, sv, ko, anp, sw, gl, es-MX, srd, de-DE, ta, gu, ky, cs, pt-BR, sr-Latn, xh, es-ES, te, pa, th, es-AR, la, cy, tl, sr-Cyrl, pl, da, he, tr, nds, en-US, hi, ast, zh-CN, lt, hr, lv, ht, hu, hy, ta-IN, uk, id, mk, ml, zh-TW, zh-HK, mn, mr, af, ms, zh-Hant-TW, el, brx, is, eo, it, am, es, et, eu, ar, as, vi, nb, ja, ne, az, fa, pt-PT, ro, nl, en-GB, nn, zh-Hans-CN, fi, ru] [INFO] Encode tab as \t: true [INFO] Current directory: /Users/garga/work/pfsense/pfsense [INFO] Pulling target documents (translations) only [INFO] Target-language base directory (translations): src/usr/local/share/locale [INFO] Minimum accepted translation percentage (message based): 0% [INFO] Create skeletons for untranslated messages/files: false [INFO] Pulling 1 of 1 docs for this module from the server [ERROR] Operation failed: javax.ws.rs.NotFoundException: operation to [https://translate.zanata.org/rest/projects/p/pfsense/iterations/i/2.4/resource?docId=pfSense&ext=gettext&ext=comment] returned 404 (Not Found)::JBWEB000065: HTTP Status 404 -

JBWEB000065: HTTP Status 404 -


JBWEB000309: type JBWEB000067: Status report

JBWEB000068: message

JBWEB000069: description JBWEB000124: The requested resource is not available.


To retry from the last document, please set the following option(s): --from-doc "pfSense" . [ERROR] Execution failed: java.lang.RuntimeException: javax.ws.rs.NotFoundException: operation to [https://translate.zanata.org/rest/projects/p/pfsense/iterations/i/2.4/resource?docId=pfSense&ext=gettext&ext=comment] returned 404 (Not Found)::JBWEB000065: HTTP Status 404 -

JBWEB000065: HTTP Status 404 -


JBWEB000309: type JBWEB000067: Status report

JBWEB000068: message

JBWEB000069: description JBWEB000124: The requested resource is not available.


at org.zanata.client.commands.pull.PullCommand.run(PullCommand.java:280) at org.zanata.client.commands.ConfigurableCommand.runWithActions(ConfigurableCommand.java:110) at org.zanata.client.commands.ArgsUtil.runCommand(ArgsUtil.java:49) at org.zanata.client.ZanataClient.processArgs(ZanataClient.java:182) at org.zanata.client.ZanataClient.main(ZanataClient.java:103) Caused by: javax.ws.rs.client.ResponseProcessingException: javax.ws.rs.NotFoundException: operation to [https://translate.zanata.org/rest/projects/p/pfsense/iterations/i/2.4/resource?docId=pfSense&ext=gettext&ext=comment] returned 404 (Not Found)::JBWEB000065: HTTP Status 404 -

JBWEB000065: HTTP Status 404 -


JBWEB000309: type JBWEB000067: Status report

JBWEB000068: message

JBWEB000069: description JBWEB000124: The requested resource is not available.


at org.jboss.resteasy.client.jaxrs.internal.ClientInvocation.invoke(ClientInvocation.java:455) at org.jboss.resteasy.client.jaxrs.internal.ClientInvocationBuilder.get(ClientInvocationBuilder.java:159) at org.zanata.rest.client.SourceDocResourceClient.getResource(SourceDocResourceClient.java:89) at org.zanata.client.commands.pull.PullCommand.run(PullCommand.java:228) ... 4 more Caused by: javax.ws.rs.NotFoundException: operation to [https://translate.zanata.org/rest/projects/p/pfsense/iterations/i/2.4/resource?docId=pfSense&ext=gettext&ext=comment] returned 404 (Not Found)::JBWEB000065: HTTP Status 404 -

JBWEB000065: HTTP Status 404 -


JBWEB000309: type JBWEB000067: Status report

JBWEB000068: message

JBWEB000069: description JBWEB000124: The requested resource is not available.


at org.zanata.rest.client.ResponseStatusFilter.filter(ResponseStatusFilter.java:75) at org.jboss.resteasy.client.jaxrs.internal.ClientInvocation.invoke(ClientInvocation.java:447) ... 7 more ~/w/p/pfsense ??? zanata-cli -v ? master ? zanata-cli Client version: 4.2.4 Client timestamp: unknown Client SCM describe: unknown API version: 4.2.4 API timestamp: unknown API SCM describe: unknown Steve -- Stephen Beaver | +1 (512) 646-4100;239 | sbeaver at netgate.com | www.netgate.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From info at osmhydrant.org Mon Sep 25 19:19:56 2017 From: info at osmhydrant.org (Robert Koch) Date: Mon, 25 Sep 2017 21:19:56 +0200 Subject: [zanata-users] Change source language Message-ID: <7fda73c8-af66-e13b-8ab7-de23e660583f@osmhydrant.org> Hello, is there an easy way to change the language of the source strings in editor mode? I did not find anything in the documentation at: http://docs.zanata.org/en/ In my case I've got just "keys" sometimes (like meta_description) as translation placeholders. The English translation then contains the "real" source string. In this case I'd like to show the English translation as base source language on the left side of the editor view when translating to German/Spanish/etc. Best regards, Robert From aeng at redhat.com Mon Sep 25 21:36:45 2017 From: aeng at redhat.com (Alex Eng) Date: Tue, 26 Sep 2017 07:36:45 +1000 Subject: [zanata-users] Change source language In-Reply-To: <7fda73c8-af66-e13b-8ab7-de23e660583f@osmhydrant.org> References: <7fda73c8-af66-e13b-8ab7-de23e660583f@osmhydrant.org> Message-ID: Robert, You can configure the editor to show the translations on left column by selecting from the drop down "Show reference translations form" This feature is not available in our Alpha editor. http://docs.zanata.org/en/release/user-guide/editor/editor-view/#settings On Tue, Sep 26, 2017 at 5:19 AM, Robert Koch wrote: > Hello, > > is there an easy way to change the language of the source strings in > editor mode? I did not find anything in the documentation at: > http://docs.zanata.org/en/ > > In my case I've got just "keys" sometimes (like meta_description) as > translation placeholders. The English translation then contains the > "real" source string. In this case I'd like to show the English > translation as base source language on the left side of the editor view > when translating to German/Spanish/etc. > > > Best regards, > Robert > > _______________________________________________ > zanata-users mailing list > zanata-users at redhat.com > https://www.redhat.com/mailman/listinfo/zanata-users > -- ALEX ENG SENIOR SOFTWARE ENGINEER, team lead globalisation tooling, customer platform Red Hat Asia-Pacific Pty Ltd Brisbane, Australia aeng at redhat.com M: +61423353457 IM: aeng -------------- next part -------------- An HTML attachment was scrubbed... URL: From aeng at redhat.com Tue Sep 26 01:15:55 2017 From: aeng at redhat.com (Alex Eng) Date: Tue, 26 Sep 2017 11:15:55 +1000 Subject: [zanata-users] Fwd: Unable to download .po files this mornng In-Reply-To: References: <5A170E01-0B64-47E5-8F3D-F37D1EBED35A@netgate.com> Message-ID: Hi, For anyone that is using Zanata Client version 4.2.4, we have identified an issue in that version that breaks push/pull command when working with Zanata server < 4.2.4 https://translate.zanata.org https://fedora.zanata.org https://translate.jboss.org Please *downgrade to version* *4.2.1 or upgrade to version > 4.2.4* as a workaround. ---------- Forwarded message ---------- From: Alex Eng Date: Thu, Sep 21, 2017 at 8:05 AM Subject: Re: [zanata-users] Unable to download .po files this mornng To: Stephen beaver Stephen, Seems like a client version used is causing the issue. How did you install the zanata-cli? Try version 4.2.1 or 4.3.0-alpha-1 which I tested and it works. On Thu, Sep 21, 2017 at 8:00 AM, Stephen beaver wrote: > My Colleague Renato is a co-maintainer. > > Steve > -- > Als ik kan > > > > On Sep 20, 2017, at 5:58 PM, Alex Eng wrote: > > Hi Stephen, > > Are you a maintainer for this project? https://translate.zan > ata.org/project/view/pfsense > or a translator? > > On Wed, Sep 20, 2017 at 9:48 PM, Stephen Beaver > wrote: > >> zanata-cli -e -B pull >> >> ? master ? >> [INFO] Loading project config from zanata.xml >> [INFO] Loading user config from /Users/xxxx/.config/zanata.ini >> [INFO] Error stacktraces are turned on. >> [INFO] client API version: 4.2.4, server API version: 3.9.1 >> [WARN] client API version is 4.2.4, but server API version is 3.9.1 >> [INFO] Server: https://translate.zanata.org/ >> [INFO] Project: xxxxxxx >> [INFO] Version: 2.4 >> [INFO] Username: xxxxxx >> [INFO] Project type: gettext >> [INFO] Enable modules: false >> [INFO] Using ETag cache: true >> [INFO] Purging ETag cache beforehand: false >> [INFO] Locales to pull: [bg, me-ME, fr, bn-BD, br, bs, si, ka, mai, sk, >> sl, ga, bn-IN, ca, sq, kk, kn, or, sv, ko, anp, sw, gl, es-MX, srd, de-DE, >> ta, gu, ky, cs, pt-BR, sr-Latn, xh, es-ES, te, pa, th, es-AR, la, cy, tl, >> sr-Cyrl, pl, da, he, tr, nds, en-US, hi, ast, zh-CN, lt, hr, lv, ht, hu, >> hy, ta-IN, uk, id, mk, ml, zh-TW, zh-HK, mn, mr, af, ms, zh-Hant-TW, el, >> brx, is, eo, it, am, es, et, eu, ar, as, vi, nb, ja, ne, az, fa, pt-PT, ro, >> nl, en-GB, nn, zh-Hans-CN, fi, ru] >> [INFO] Encode tab as \t: true >> [INFO] Current directory: /Users/garga/work/pfsense/pfsense >> [INFO] Pulling target documents (translations) only >> [INFO] Target-language base directory (translations): >> src/usr/local/share/locale >> [INFO] Minimum accepted translation percentage (message based): 0% >> [INFO] Create skeletons for untranslated messages/files: false >> [INFO] Pulling 1 of 1 docs for this module from the server >> [ERROR] Operation failed: javax.ws.rs.NotFoundException: operation to [ >> https://translate.zanata.org/rest/projects/p/pfsense/iterat >> ions/i/2.4/resource?docId=pfSense&ext=gettext&ext=comment] returned 404 >> (Not Found)::JBWEB000065: HTTP Status 404 - >> >>

JBWEB000065: HTTP Status 404 -


> noshade="noshade">

JBWEB000309: type JBWEB000067: Status >> report

JBWEB000068: message

JBWEB000069: >> description JBWEB000124: The requested resource is not >> available.


>> To retry from the last document, please set the following option(s): >> --from-doc "pfSense" >> . >> [ERROR] Execution failed: >> java.lang.RuntimeException: javax.ws.rs.NotFoundException: operation to [ >> https://translate.zanata.org/rest/projects/p/pfsense/iterat >> ions/i/2.4/resource?docId=pfSense&ext=gettext&ext=comment] returned 404 >> (Not Found)::JBWEB000065: HTTP Status 404 - >> >>

JBWEB000065: HTTP Status 404 -


> noshade="noshade">

JBWEB000309: type JBWEB000067: Status >> report

JBWEB000068: message

JBWEB000069: >> description JBWEB000124: The requested resource is not >> available.


>> at org.zanata.client.commands.pull.PullCommand.run(PullCommand. >> java:280) >> at org.zanata.client.commands.ConfigurableCommand.runWithAction >> s(ConfigurableCommand.java:110) >> at org.zanata.client.commands.ArgsUtil.runCommand(ArgsUtil.java:49) >> at org.zanata.client.ZanataClient.processArgs(ZanataClient.java:182) >> at org.zanata.client.ZanataClient.main(ZanataClient.java:103) >> Caused by: javax.ws.rs.client.ResponseProcessingException: >> javax.ws.rs.NotFoundException: operation to [ >> https://translate.zanata.org/rest/projects/p/pfsense/iterat >> ions/i/2.4/resource?docId=pfSense&ext=gettext&ext=comment] returned 404 >> (Not Found)::JBWEB000065: HTTP Status 404 - >> >>

JBWEB000065: HTTP Status 404 -


> noshade="noshade">

JBWEB000309: type JBWEB000067: Status >> report

JBWEB000068: message

JBWEB000069: >> description JBWEB000124: The requested resource is not >> available.


>> at org.jboss.resteasy.client.jaxrs.internal.ClientInvocation.in >> voke(ClientInvocation.java:455) >> at org.jboss.resteasy.client.jaxrs.internal.ClientInvocationBui >> lder.get(ClientInvocationBuilder.java:159) >> at org.zanata.rest.client.SourceDocResourceClient.getResource(S >> ourceDocResourceClient.java:89) >> at org.zanata.client.commands.pull.PullCommand.run(PullCommand. >> java:228) >> ... 4 more >> Caused by: javax.ws.rs.NotFoundException: operation to [ >> https://translate.zanata.org/rest/projects/p/pfsense/iterat >> ions/i/2.4/resource?docId=pfSense&ext=gettext&ext=comment] returned 404 >> (Not Found)::JBWEB000065: HTTP Status 404 - >> >>

JBWEB000065: HTTP Status 404 -


> noshade="noshade">

JBWEB000309: type JBWEB000067: Status >> report

JBWEB000068: message

JBWEB000069: >> description JBWEB000124: The requested resource is not >> available.


>> at org.zanata.rest.client.ResponseStatusFilter.filter(ResponseS >> tatusFilter.java:75) >> at org.jboss.resteasy.client.jaxrs.internal.ClientInvocation.in >> voke(ClientInvocation.java:447) >> ... 7 more >> ~/w/p/pfsense ??? zanata-cli -v >> >> ? master ? >> zanata-cli >> Client version: 4.2.4 >> Client timestamp: unknown >> Client SCM describe: unknown >> API version: 4.2.4 >> API timestamp: unknown >> API SCM describe: unknown >> >> Steve >> -- >> Stephen Beaver | +1 (512) 646-4100 <(512)%20646-4100>;239 | >> sbeaver at netgate.com | www.netgate.com >> >> >> _______________________________________________ >> zanata-users mailing list >> zanata-users at redhat.com >> https://www.redhat.com/mailman/listinfo/zanata-users >> > > > > -- > > ALEX ENG > > SENIOR SOFTWARE ENGINEER, team lead > > globalisation tooling, customer platform > > Red Hat Asia-Pacific Pty Ltd > > Brisbane, Australia > > aeng at redhat.com M: +61423353457 IM: aeng > > > -- ALEX ENG SENIOR SOFTWARE ENGINEER, team lead globalisation tooling, customer platform Red Hat Asia-Pacific Pty Ltd Brisbane, Australia aeng at redhat.com M: +61423353457 IM: aeng -- ALEX ENG SENIOR SOFTWARE ENGINEER, team lead globalisation tooling, customer platform Red Hat Asia-Pacific Pty Ltd Brisbane, Australia aeng at redhat.com M: +61423353457 IM: aeng -------------- next part -------------- An HTML attachment was scrubbed... URL: From info at osmhydrant.org Tue Sep 26 19:31:37 2017 From: info at osmhydrant.org (Robert Koch) Date: Tue, 26 Sep 2017 21:31:37 +0200 Subject: [zanata-users] Change source language In-Reply-To: References: <7fda73c8-af66-e13b-8ab7-de23e660583f@osmhydrant.org> Message-ID: <89f62459-99c7-2f3d-6443-cb5da819d669@osmhydrant.org> Hello Alex, thanks for your feedback. Without your help I'd be lost. I'm thrilled by this option. Best regards, Robert On 2017-09-25 23:36, Alex Eng wrote: > Robert, > > You can configure the editor to show the translations on left column > by selecting from the drop down "Show reference translations form" > This feature is not available in our Alpha editor. > > http://docs.zanata.org/en/release/user-guide/editor/editor-view/#settings > > On Tue, Sep 26, 2017 at 5:19 AM, Robert Koch > wrote: > > Hello, > > is there an easy way to change the language of the source strings in > editor mode? I did not find anything in the documentation at: > http://docs.zanata.org/en/ > > In my case I've got just "keys" sometimes (like meta_description) as > translation placeholders. The English translation then contains the > "real" source string. In this case I'd like to show the English > translation as base source language on the left side of the editor > view > when translating to German/Spanish/etc. > > > Best regards, > Robert > > _______________________________________________ > zanata-users mailing list > zanata-users at redhat.com > https://www.redhat.com/mailman/listinfo/zanata-users > > > > > > -- > > ALEX ENG > > SENIOR SOFTWARE ENGINEER, team lead > > globalisation tooling, customer platform > > Red Hat Asia-Pacific Pty Ltd > > Brisbane, Australia > > aeng at redhat.com M: +61423353457 > IM: aeng > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: