From ttrinks at redhat.com Thu May 5 08:53:11 2016 From: ttrinks at redhat.com (ttrinks at redhat.com) Date: Thu, 5 May 2016 08:53:11 +0000 (UTC) Subject: [zanata-users] translate.engineering.redhat.com Scheduled Maintenance | 05-May-2016 22:00:00 UTC Message-ID: 2711cfb5-c815-4c47-b256-b0305abd68ea@support.engineering.redhat.com --------------------------------------------------------- ***// SCHEDULED MAINTENANCE REPORT //*** HostName: translate.engineering.redhat.com Priority: Medium Scheduled Date: 05-May-2016 22:00:00 UTC Estimated Time Required: 60 minutes Performed By: ttrinks People/Groups Impacted: Users of Zanata on translate.engineering.redhat.com Services/Sites Impacted: translate.engineering.redhat.com Description: Application upgrade. Impact: Zanata will not be available for the duration of the outage. Sign Off: Marc Raaz ***// SENT FROM CHARNET //*** https://support.engineering.redhat.com/status.jsf Want to escalate an issue find out more here: https://mojo.redhat.com/docs/DOC-1044941 -------------- next part -------------- A non-text attachment was scrubbed... Name: maintenance.ics Type: text/calendar Size: 1645 bytes Desc: not available URL: From ttrinks at redhat.com Thu May 5 21:50:00 2016 From: ttrinks at redhat.com (ttrinks at redhat.com) Date: Thu, 5 May 2016 21:50:00 +0000 (UTC) Subject: [zanata-users] translate.engineering.redhat.com Scheduled Maintenance | 05-May-2016 22:00:00 UTC Message-ID: 2711cfb5-c815-4c47-b256-b0305abd68ea@support.engineering.redhat.com This maintenance will begin in approximately 10 minutes --------------------------------------------------------- --------------------------------------------------------- ***// SCHEDULED MAINTENANCE REPORT //*** HostName: translate.engineering.redhat.com Priority: Medium Scheduled Date: 05-May-2016 22:00:00 UTC Estimated Time Required: 60 minutes Performed By: ttrinks People/Groups Impacted: Users of Zanata on translate.engineering.redhat.com Services/Sites Impacted: translate.engineering.redhat.com Description: Application upgrade. Impact: Zanata will not be available for the duration of the outage. Sign Off: Marc Raaz ***// SENT FROM CHARNET //*** https://support.engineering.redhat.com/status.jsf Want to escalate an issue find out more here: https://mojo.redhat.com/docs/DOC-1044941 From ttrinks at redhat.com Thu May 5 22:48:19 2016 From: ttrinks at redhat.com (ttrinks at redhat.com) Date: Thu, 5 May 2016 22:48:19 +0000 (UTC) Subject: [zanata-users] translate.engineering.redhat.com Scheduled Maintenance | 05-May-2016 22:00:00 UTC In-Reply-To: 2711cfb5-c815-4c47-b256-b0305abd68ea@support.engineering.redhat.com References: 2711cfb5-c815-4c47-b256-b0305abd68ea@support.engineering.redhat.com Message-ID: <483544297.1077.1462488499867.JavaMail.jboss@charnet.host.prod.eng.rdu2.redhat.com> COMPLETED COMMENT ADDED BY ttrinks at 05-May-2016 22:48:19 UTC Outage complete. Zanata has successfully been upgraded. Please report any issues via eng-ops at redhat.com, thanks! --------------------------------------------------------- ***// SCHEDULED MAINTENANCE REPORT //*** HostName: translate.engineering.redhat.com Priority: Medium Scheduled Date: 05-May-2016 22:00:00 UTC Estimated Time Required: 60 minutes Performed By: ttrinks People/Groups Impacted: Users of Zanata on translate.engineering.redhat.com Services/Sites Impacted: translate.engineering.redhat.com Description: Application upgrade. Impact: Zanata will not be available for the duration of the outage. Sign Off: Marc Raaz ***// SENT FROM CHARNET //*** https://support.engineering.redhat.com/status.jsf Want to escalate an issue find out more here: https://mojo.redhat.com/docs/DOC-1044941 From sdickers at redhat.com Fri May 6 19:40:04 2016 From: sdickers at redhat.com (Scott Dickerson) Date: Fri, 6 May 2016 15:40:04 -0400 Subject: [zanata-users] using rules in zanata.xml to replace cli includes argument Message-ID: Hi, In my multi-module maven project I have a bunch of properties files that need to be translated and a bunch that do not. So far, the files to include have been explicitly specified via the includes command line argument (or the same argument in my root pom.xml). My question is, can I replace the includes list with a set of rules in zanata.xml? It would be great to encapsulate all of the zanata configurations in zanata.xml and not have to rely on a shell script or config in pom.xml. The current include list looks like this: moduleA/src/main/resources/another/path/messages.properties, moduleA/src/main/resources/another/path/CommonConstants.properties, moduleB/src/main/resources/path2/SpecificConstants.properties, moduleC/src/main/resources/path3/ConsoleErrors.properites I've tried a few combinations of putting those paths in rule patterns or rule bodies along with the substitution strings. Nothing has really worked so far. Any ideas? Can I do what I'm trying to do? Thank, Scott -- Scott Dickerson Senior Software Engineer RHEV-M Engineering - UX Team Red Hat, Inc -------------- next part -------------- An HTML attachment was scrubbed... URL: From pahuang at redhat.com Mon May 9 23:41:14 2016 From: pahuang at redhat.com (Patrick Huang) Date: Tue, 10 May 2016 09:41:14 +1000 Subject: [zanata-users] using rules in zanata.xml to replace cli includes argument In-Reply-To: References: Message-ID: Hi Scott, Yes you can. Just put your example xml into zanata.xml it should work. moduleA/src/main/resources/another/path/messages.properties, moduleA/src/main/resources/another/path/CommonConstants.properties, moduleB/src/main/resources/path2/SpecificConstants.properties, moduleC/src/main/resources/path3/ConsoleErrors.properites For rules pattern, it's designed to handle translation files. e.g. how to find or where to put a translation file for a given source document. For properties project, you probably don't need to do anything special (translation files most likely will just sit besides its source document. On Sat, May 7, 2016 at 5:40 AM, Scott Dickerson wrote: > Hi, > > In my multi-module maven project I have a bunch of properties files that > need to be translated and a bunch that do not. So far, the files to > include have been explicitly specified via the includes command line > argument (or the same argument in my root pom.xml). > > My question is, can I replace the includes list with a set of rules in > zanata.xml? It would be great to encapsulate all of the zanata > configurations in zanata.xml and not have to rely on a shell script or > config in pom.xml. > > The current include list looks like this: > > > moduleA/src/main/resources/another/path/messages.properties, > > moduleA/src/main/resources/another/path/CommonConstants.properties, > moduleB/src/main/resources/path2/SpecificConstants.properties, > moduleC/src/main/resources/path3/ConsoleErrors.properites > > > I've tried a few combinations of putting those paths in rule patterns or > rule bodies along with the substitution strings. Nothing has really worked > so far. > > Any ideas? Can I do what I'm trying to do? > > Thank, > Scott > > -- > Scott Dickerson > Senior Software Engineer > RHEV-M Engineering - UX Team > Red Hat, Inc > > _______________________________________________ > zanata-users mailing list > zanata-users at redhat.com > https://www.redhat.com/mailman/listinfo/zanata-users > -- Patrick Huang Senior Software Engineer Engineering - Internationalisation Red Hat, Asia-Pacific Pty Ltd Level 1, 193 North Quay Brisbane 4000 Office: +61 7 3514 8278 Fax: +61 7 3514 8199 IRC: pahuang github: github.com/huangp Website: www.redhat.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From pahuang at redhat.com Mon May 9 23:44:06 2016 From: pahuang at redhat.com (Patrick Huang) Date: Tue, 10 May 2016 09:44:06 +1000 Subject: [zanata-users] using rules in zanata.xml to replace cli includes argument In-Reply-To: References: Message-ID: Forgot to mention, you will need newer zanata client to support that. I can't remember which version did we introduce support for in zanata.xml. If it doesn't work for you just upgrade to the latest version. On Tue, May 10, 2016 at 9:41 AM, Patrick Huang wrote: > Hi Scott, > > Yes you can. Just put your example xml into zanata.xml it should work. > > moduleA/src/main/resources/another/path/messages.properties, > > moduleA/src/main/resources/another/path/CommonConstants.properties, > moduleB/src/main/resources/path2/SpecificConstants.properties, > moduleC/src/main/resources/path3/ConsoleErrors.properites > > > For rules pattern, it's designed to handle translation files. e.g. how to > find or where to put a translation file for a given source document. For > properties project, you probably don't need to do anything special > (translation files most likely will just sit besides its source document. > > On Sat, May 7, 2016 at 5:40 AM, Scott Dickerson > wrote: > >> Hi, >> >> In my multi-module maven project I have a bunch of properties files that >> need to be translated and a bunch that do not. So far, the files to >> include have been explicitly specified via the includes command line >> argument (or the same argument in my root pom.xml). >> >> My question is, can I replace the includes list with a set of rules in >> zanata.xml? It would be great to encapsulate all of the zanata >> configurations in zanata.xml and not have to rely on a shell script or >> config in pom.xml. >> >> The current include list looks like this: >> >> >> moduleA/src/main/resources/another/path/messages.properties, >> >> moduleA/src/main/resources/another/path/CommonConstants.properties, >> moduleB/src/main/resources/path2/SpecificConstants.properties, >> moduleC/src/main/resources/path3/ConsoleErrors.properites >> >> >> I've tried a few combinations of putting those paths in rule patterns or >> rule bodies along with the substitution strings. Nothing has really worked >> so far. >> >> Any ideas? Can I do what I'm trying to do? >> >> Thank, >> Scott >> >> -- >> Scott Dickerson >> Senior Software Engineer >> RHEV-M Engineering - UX Team >> Red Hat, Inc >> >> _______________________________________________ >> zanata-users mailing list >> zanata-users at redhat.com >> https://www.redhat.com/mailman/listinfo/zanata-users >> > > > > -- > Patrick Huang > Senior Software Engineer > Engineering - Internationalisation > Red Hat, Asia-Pacific Pty Ltd > Level 1, 193 North Quay > Brisbane 4000 > Office: +61 7 3514 8278 > Fax: +61 7 3514 8199 > IRC: pahuang > github: github.com/huangp > Website: www.redhat.com > -- Patrick Huang Senior Software Engineer Engineering - Internationalisation Red Hat, Asia-Pacific Pty Ltd Level 1, 193 North Quay Brisbane 4000 Office: +61 7 3514 8278 Fax: +61 7 3514 8199 IRC: pahuang github: github.com/huangp Website: www.redhat.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From dchen at redhat.com Tue May 10 00:38:17 2016 From: dchen at redhat.com (Ding Yi Chen) Date: Mon, 9 May 2016 20:38:17 -0400 (EDT) Subject: [zanata-users] using rules in zanata.xml to replace cli includes argument In-Reply-To: References: Message-ID: <1695016954.12775009.1462840697129.JavaMail.zimbra@redhat.com> Hi Scott, You can put something like **/messages.properties,**/CommonConstants.properties,**/SpecificConstants.properties,**/ConsoleErrors.properites ----- Original Message ----- > Hi, > In my multi-module maven project I have a bunch of properties files that need > to be translated and a bunch that do not. So far, the files to include have > been explicitly specified via the includes command line argument (or the > same argument in my root pom.xml). > My question is, can I replace the includes list with a set of rules in > zanata.xml? It would be great to encapsulate all of the zanata > configurations in zanata.xml and not have to rely on a shell script or > config in pom.xml. > The current include list looks like this: > > moduleA/src/main/resources/another/path/messages.properties, > moduleA/src/main/resources/another/path/CommonConstants.properties, > moduleB/src/main/resources/path2/SpecificConstants.properties, > moduleC/src/main/resources/path3/ConsoleErrors.properites > > I've tried a few combinations of putting those paths in rule patterns or rule > bodies along with the substitution strings. Nothing has really worked so > far. > Any ideas? Can I do what I'm trying to do? > Thank, > Scott > -- > Scott Dickerson > Senior Software Engineer > RHEV-M Engineering - UX Team > Red Hat, Inc > _______________________________________________ > zanata-users mailing list > zanata-users at redhat.com > https://www.redhat.com/mailman/listinfo/zanata-users -- Ding-Yi Chen Software Engineer Globalization 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: From Haris.Alijagic at halcom.si Wed May 11 12:53:03 2016 From: Haris.Alijagic at halcom.si (=?iso-8859-2?Q?Haris_Alijagi=E6?=) Date: Wed, 11 May 2016 12:53:03 +0000 Subject: [zanata-users] Zanata REST API documentation Message-ID: Hi, Could you improve the documentation for Zanata rest API a bit? Mainly this part translation Memory is giving me a bit of an issue... For example how should the {slug} parameter look like? An example would be nice. Also right now it only accepts and sends responses in XML.. it would be nice if you could make it so that it can accept and return a json response as well, like with the other resources :). -------------- next part -------------- An HTML attachment was scrubbed... URL: From aeng at redhat.com Wed May 11 22:53:49 2016 From: aeng at redhat.com (Alex Eng) Date: Thu, 12 May 2016 08:53:49 +1000 Subject: [zanata-users] Zanata REST API documentation In-Reply-To: References: Message-ID: Hi Haris, Thanks for the feedback. We will certainly look into improving our documentation. But to answer your question, For {slug} in TM, its a unique string value which is used for a specific collection of imported TM, e.g. "Id" field for when admin create the tm collection. As for Json file format support, can you please file a request in https://zanata.atlassian.net/. We generally use that as our backlog for all requests and bug tracker. --------------------------------------------- Alex Eng Senior Software Engineer Globalisation Tools Engineering DID: +61 3514 8262 Mobile: +614 2335 3457 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 On Wed, May 11, 2016 at 10:53 PM, Haris Alijagi? wrote: > Hi, > > Could you improve the documentation for Zanata rest API a bit? Mainly this > part translation Memory > > is giving me a bit of an issue? For example how should the {slug} > parameter look like? An example would be nice. Also right now it only > accepts and sends responses in XML.. it would be nice if you could make it > so that it can accept and return a json response as well, like with the > other resources J. > > > > _______________________________________________ > zanata-users mailing list > zanata-users at redhat.com > https://www.redhat.com/mailman/listinfo/zanata-users > -------------- next part -------------- An HTML attachment was scrubbed... URL: From pahuang at redhat.com Wed May 11 23:32:34 2016 From: pahuang at redhat.com (Patrick Huang) Date: Thu, 12 May 2016 09:32:34 +1000 Subject: [zanata-users] Zanata REST API documentation In-Reply-To: References: Message-ID: Hi Haris, Alex has explained what is the slug. For the response format, it's XML only because that REST api is returning a specific format called TMX (Translation Memory eXchange) [1]. So the response can be imported into other translation platform and vice versa. I don't know if there is a similar json schema to serve the same purpose. You may want to explain what you want to use the json file for when you file the feature request. [1] https://en.wikipedia.org/wiki/Translation_Memory_eXchange On Thu, May 12, 2016 at 8:53 AM, Alex Eng wrote: > Hi Haris, > > Thanks for the feedback. We will certainly look into improving our > documentation. > > But to answer your question, > For {slug} in TM, its a unique string value which is used for a > specific collection of imported TM, e.g. "Id" field for when admin create > the tm collection. > > As for Json file format support, can you please file a request in > https://zanata.atlassian.net/. > We generally use that as our backlog for all requests and bug tracker. > > > > > --------------------------------------------- > > Alex Eng > Senior Software Engineer > Globalisation Tools Engineering > DID: +61 3514 8262 > Mobile: +614 2335 3457 > > 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 > > On Wed, May 11, 2016 at 10:53 PM, Haris Alijagi? > wrote: > >> Hi, >> >> Could you improve the documentation for Zanata rest API a bit? Mainly >> this part translation Memory >> >> is giving me a bit of an issue? For example how should the {slug} >> parameter look like? An example would be nice. Also right now it only >> accepts and sends responses in XML.. it would be nice if you could make it >> so that it can accept and return a json response as well, like with the >> other resources J. >> >> >> >> _______________________________________________ >> zanata-users mailing list >> zanata-users at redhat.com >> https://www.redhat.com/mailman/listinfo/zanata-users >> > > > _______________________________________________ > zanata-users mailing list > zanata-users at redhat.com > https://www.redhat.com/mailman/listinfo/zanata-users > -- Patrick Huang Senior Software Engineer Engineering - Internationalisation Red Hat, Asia-Pacific Pty Ltd Level 1, 193 North Quay Brisbane 4000 Office: +61 7 3514 8278 Fax: +61 7 3514 8199 IRC: pahuang github: github.com/huangp Website: www.redhat.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From sdickers at redhat.com Fri May 13 14:56:40 2016 From: sdickers at redhat.com (Scott Dickerson) Date: Fri, 13 May 2016 10:56:40 -0400 Subject: [zanata-users] using rules in zanata.xml to replace cli includes argument In-Reply-To: References: Message-ID: Thanks for the info. Works like a charm. What does it take to add that info to the online documents so everyone knows about the include tag in zanata.xml? Scott On Mon, May 9, 2016 at 7:44 PM, Patrick Huang wrote: > Forgot to mention, you will need newer zanata client to support that. I > can't remember which version did we introduce support for in > zanata.xml. If it doesn't work for you just upgrade to the latest version. > > On Tue, May 10, 2016 at 9:41 AM, Patrick Huang wrote: > >> Hi Scott, >> >> Yes you can. Just put your example xml into zanata.xml it should work. >> >> moduleA/src/main/resources/another/path/messages.properties, >> >> moduleA/src/main/resources/another/path/CommonConstants.properties, >> moduleB/src/main/resources/path2/SpecificConstants.properties, >> moduleC/src/main/resources/path3/ConsoleErrors.properites >> >> >> For rules pattern, it's designed to handle translation files. e.g. how to >> find or where to put a translation file for a given source document. For >> properties project, you probably don't need to do anything special >> (translation files most likely will just sit besides its source document. >> >> On Sat, May 7, 2016 at 5:40 AM, Scott Dickerson >> wrote: >> >>> Hi, >>> >>> In my multi-module maven project I have a bunch of properties files that >>> need to be translated and a bunch that do not. So far, the files to >>> include have been explicitly specified via the includes command line >>> argument (or the same argument in my root pom.xml). >>> >>> My question is, can I replace the includes list with a set of rules in >>> zanata.xml? It would be great to encapsulate all of the zanata >>> configurations in zanata.xml and not have to rely on a shell script or >>> config in pom.xml. >>> >>> The current include list looks like this: >>> >>> >>> moduleA/src/main/resources/another/path/messages.properties, >>> >>> moduleA/src/main/resources/another/path/CommonConstants.properties, >>> moduleB/src/main/resources/path2/SpecificConstants.properties, >>> moduleC/src/main/resources/path3/ConsoleErrors.properites >>> >>> >>> I've tried a few combinations of putting those paths in rule patterns or >>> rule bodies along with the substitution strings. Nothing has really worked >>> so far. >>> >>> Any ideas? Can I do what I'm trying to do? >>> >>> Thank, >>> Scott >>> >>> -- >>> Scott Dickerson >>> Senior Software Engineer >>> RHEV-M Engineering - UX Team >>> Red Hat, Inc >>> >>> _______________________________________________ >>> zanata-users mailing list >>> zanata-users at redhat.com >>> https://www.redhat.com/mailman/listinfo/zanata-users >>> >> >> >> >> -- >> Patrick Huang >> Senior Software Engineer >> Engineering - Internationalisation >> Red Hat, Asia-Pacific Pty Ltd >> Level 1, 193 North Quay >> Brisbane 4000 >> Office: +61 7 3514 8278 >> Fax: +61 7 3514 8199 >> IRC: pahuang >> github: github.com/huangp >> Website: www.redhat.com >> > > > > -- > Patrick Huang > Senior Software Engineer > Engineering - Internationalisation > Red Hat, Asia-Pacific Pty Ltd > Level 1, 193 North Quay > Brisbane 4000 > Office: +61 7 3514 8278 > Fax: +61 7 3514 8199 > IRC: pahuang > github: github.com/huangp > Website: www.redhat.com > -- Scott Dickerson Senior Software Engineer RHEV-M Engineering - UX Team Red Hat, Inc -------------- next part -------------- An HTML attachment was scrubbed... URL: From camunoz at redhat.com Sun May 15 23:04:12 2016 From: camunoz at redhat.com (Carlos Munoz) Date: Mon, 16 May 2016 09:04:12 +1000 Subject: [zanata-users] using rules in zanata.xml to replace cli includes argument In-Reply-To: References: Message-ID: Hi Scott, All the documentation for the client is at https://github.com/zanata/zanata-client/tree/master/docs if you feel like contributing ;) That topic specifically should probably go in a section here: https://github.com/zanata/zanata-client/blob/master/docs/configuration.md Regards, Carlos. Carlos A. Munoz Associate Manager, Software Engineering Globalization Red Hat On Sat, May 14, 2016 at 12:56 AM, Scott Dickerson wrote: > Thanks for the info. Works like a charm. > > What does it take to add that info to the online documents so everyone > knows about the include tag in zanata.xml? > > Scott > > > On Mon, May 9, 2016 at 7:44 PM, Patrick Huang wrote: > >> Forgot to mention, you will need newer zanata client to support that. I >> can't remember which version did we introduce support for in >> zanata.xml. If it doesn't work for you just upgrade to the latest version. >> >> On Tue, May 10, 2016 at 9:41 AM, Patrick Huang >> wrote: >> >>> Hi Scott, >>> >>> Yes you can. Just put your example xml into zanata.xml it should work. >>> >>> moduleA/src/main/resources/another/path/messages.properties, >>> >>> moduleA/src/main/resources/another/path/CommonConstants.properties, >>> moduleB/src/main/resources/path2/SpecificConstants.properties, >>> moduleC/src/main/resources/path3/ConsoleErrors.properites >>> >>> >>> For rules pattern, it's designed to handle translation files. e.g. how >>> to find or where to put a translation file for a given source document. For >>> properties project, you probably don't need to do anything special >>> (translation files most likely will just sit besides its source document. >>> >>> On Sat, May 7, 2016 at 5:40 AM, Scott Dickerson >>> wrote: >>> >>>> Hi, >>>> >>>> In my multi-module maven project I have a bunch of properties files >>>> that need to be translated and a bunch that do not. So far, the files to >>>> include have been explicitly specified via the includes command line >>>> argument (or the same argument in my root pom.xml). >>>> >>>> My question is, can I replace the includes list with a set of rules in >>>> zanata.xml? It would be great to encapsulate all of the zanata >>>> configurations in zanata.xml and not have to rely on a shell script or >>>> config in pom.xml. >>>> >>>> The current include list looks like this: >>>> >>>> >>>> moduleA/src/main/resources/another/path/messages.properties, >>>> >>>> moduleA/src/main/resources/another/path/CommonConstants.properties, >>>> moduleB/src/main/resources/path2/SpecificConstants.properties, >>>> moduleC/src/main/resources/path3/ConsoleErrors.properites >>>> >>>> >>>> I've tried a few combinations of putting those paths in rule patterns >>>> or rule bodies along with the substitution strings. Nothing has really >>>> worked so far. >>>> >>>> Any ideas? Can I do what I'm trying to do? >>>> >>>> Thank, >>>> Scott >>>> >>>> -- >>>> Scott Dickerson >>>> Senior Software Engineer >>>> RHEV-M Engineering - UX Team >>>> Red Hat, Inc >>>> >>>> _______________________________________________ >>>> zanata-users mailing list >>>> zanata-users at redhat.com >>>> https://www.redhat.com/mailman/listinfo/zanata-users >>>> >>> >>> >>> >>> -- >>> Patrick Huang >>> Senior Software Engineer >>> Engineering - Internationalisation >>> Red Hat, Asia-Pacific Pty Ltd >>> Level 1, 193 North Quay >>> Brisbane 4000 >>> Office: +61 7 3514 8278 >>> Fax: +61 7 3514 8199 >>> IRC: pahuang >>> github: github.com/huangp >>> Website: www.redhat.com >>> >> >> >> >> -- >> Patrick Huang >> Senior Software Engineer >> Engineering - Internationalisation >> Red Hat, Asia-Pacific Pty Ltd >> Level 1, 193 North Quay >> Brisbane 4000 >> Office: +61 7 3514 8278 >> Fax: +61 7 3514 8199 >> IRC: pahuang >> github: github.com/huangp >> Website: www.redhat.com >> > > > > -- > Scott Dickerson > Senior Software Engineer > RHEV-M Engineering - UX Team > Red Hat, Inc > > _______________________________________________ > zanata-users mailing list > zanata-users at redhat.com > https://www.redhat.com/mailman/listinfo/zanata-users > -------------- next part -------------- An HTML attachment was scrubbed... URL: