[zanata-users] using rules in zanata.xml to replace cli includes argument

[Scott Dickerson]

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 <pahuang at redhat.com> wrote:

> Forgot to mention, you will need newer zanata client to support that. I
> can't remember which version did we introduce support for <includes> 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 <pahuang at redhat.com> wrote:
>
>> Hi Scott,
>>
>> Yes you can. Just put your example xml into zanata.xml it should work.
>> <includes>
>>           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
>>     </includes>
>>
>> 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 <sdickers at redhat.com>
>> 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:
>>>
>>>     <includes>
>>>           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
>>>     </includes>
>>>
>>> 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: <http://listman.redhat.com/archives/zanata-users/attachments/20160513/edbe7bb9/attachment.htm>