Skip to content
This repository has been archived by the owner on Nov 9, 2017. It is now read-only.

Commit

Permalink
add src-dir trans-dir section
Browse files Browse the repository at this point in the history
  • Loading branch information
Patrick Huang committed Mar 19, 2015
1 parent 38e5fe8 commit 4f6acdd
Showing 1 changed file with 10 additions and 0 deletions.
10 changes: 10 additions & 0 deletions docs/configuration.md
Expand Up @@ -38,9 +38,19 @@ These steps should be repeated for each project-version before using any zanata-

You can customize `zanata.xml` with command hooks so that other tools will automatically run before or after Zanata commands. Read about command hooks at the [command hook page on the wiki](https://github.com/zanata/zanata-server/wiki/Client-Command-Hooks).

## Source directory and translation directory

To prevent the need to specify the source and translation directories on the command-line, they can be specified in zanata.xml. The source and translation directories are specified in the `<src-dir>` and `<trans-dir>` elements respectively, as shown below. Both paths must be relative to the directory that contains zanata.xml.

```xml
<src-dir>po</src-dir>
<trans-dir>.</trans-dir>
```

## Locale Configuration

***Note:*** Locale configuration in zanata.xml is being phased out, and this configuration will be specified on the server instead. When your project is on a server version that allows locale configuration and you have a client version that supports server locales, you should remove this configuration. Check the details in [feature request 1156236](https://bugzilla.redhat.com/show_bug.cgi?id=1156236).

The `zanata.xml` will contain a list of locales so that the client knows which locales to push and pull to/from the Zanata server. When downloaded from the Zanata server, the list will have the locales as specified by the server itself. It will look something like this:

```xml
Expand Down

0 comments on commit 4f6acdd

Please sign in to comment.