Design a translation tool for Pasco

[willwade]

We want users to be able to translate Pasco trees and have trees translated for them.

A few things to consider:

• We might not have a 1:1 mapping between translations
  • For example, a list of animals in english might list cows, sheep, dogs but in a tree translated too Afrikaans you probably want to list totally different animals like springbok, African penguin.
• Google translate is not considered best practice, its a good starting point but it should be used to recommend translations not make translations.

Output of this issue should be a list of tasks to implement the new architecture.

Original Issue

Not sure this really should live in the app - I really am imagining a small web app that people upload their pasco files to - and it then translates either the main, cue or both from one language to another - and keeps the formatting (indentation/markdown format). This should be pretty straightforward using the google/Microsoft translation tools.

[hosseinzoda]

It's a good idea to use other existing apps for tools around pasco. If we use existing translation tools.
We can endup with a single tree and translations provided in another file.
The existing locale tool running on pasco can be used for translating contents inside nodes.