Multilingual documentation

Just sitting here talking to Knut, and it would seem that Google translation may be good enough for a first pass of the translation.

Now, a few issues arise from this.

Management of the pom to generate the documentation, may become a major problem. Currently, we need quite a bit of XML for each language. The more languages we add, the bigger problem this is going to be.

Knut and I would like to suggest to the community to fork off each language into a seperate branch. This will allow better ownership by each individual language " community" and will simplify the process of actually getting the documentation. It really may not be necessary for everyone to have every language, but rather the languages that they are actually interested in.

Comments?

Regards,
Jason

···

Jason P. Pickering
email: jason.p.pickering@gmail.com
tel:+260968395190

Just to add a bit:

Because of the identified need to have separate image files for each language in the manuals, we have to make sure the checkout and build processes don’t become unnecessarily burdensome. Most people would only be interested in one or two languages.

However, we have to consider the integrated help function - I suppose we want to build DHIS2 with all “help languages”, which will be much smaller, since the images are not included.

So what would be a good way to achieve both the goals above at the same time - ideally also without too complex pom.xml (Maven 1.x allowed for scripting such as foreach loops through Jelly, something similar may be possible with Antrun or Beanshell in Maven 2??).

Knut

···

On Thu, Mar 25, 2010 at 9:55 AM, Jason Pickering jason.p.pickering@gmail.com wrote:

Just sitting here talking to Knut, and it would seem that Google translation may be good enough for a first pass of the translation.

Now, a few issues arise from this.

Management of the pom to generate the documentation, may become a major problem. Currently, we need quite a bit of XML for each language. The more languages we add, the bigger problem this is going to be.

Knut and I would like to suggest to the community to fork off each language into a seperate branch. This will allow better ownership by each individual language " community" and will simplify the process of actually getting the documentation. It really may not be necessary for everyone to have every language, but rather the languages that they are actually interested in.

Comments?

Regards,
Jason

Jason P. Pickering
email: jason.p.pickering@gmail.com

tel:+260968395190


Mailing list: https://launchpad.net/~dhis2-devs

Post to : dhis2-devs@lists.launchpad.net

Unsubscribe : https://launchpad.net/~dhis2-devs

More help : https://help.launchpad.net/ListHelp


Cheers,
Knut Staring