tomw wrote:I think that assuming this test goes well (which I am confident it will) we will create a solution and host it at the Church. Ideally I would love to get the community involved in creating the solution as well. However we do have some other software that we use in our existing translation department that we would need to interface with.
The way I see it, we would need 4 levels of translations. Some of these levels may not be used as much as others but here they are:
MediaWiki seems to be suited to this. You would either need some creative templates, or you could create a special wiki area and markup that would magically do the required replacement.
A good starting place is:
Unfortunately, while LDSOSS uses MediaWiki, it does not seem current enough to like the templates (specifically Template:array) that are needed.
I might get some time to set up a sandbox, but I can't open it to the world. I'll try to get the templates built, and maybe play with custom markup or wikis. If we can get the templates set up, then comes the word lists. Documents are pretty easy after that, assuming the templates are structured correctly.
I think with a proper template system, it would not be hard to scrape the translation off the page.
What do you mean by "publish" in 1,2? If a translation is available on a public wiki site in a partial state, is that 'published'? For 3, would we vote on a translation, or just wait till it was stable? Would the wiki even be considered an official source for completed translations?
I really don't think a forum works well for this task. It makes much more sense to put it in a hierarchical structure with the original language document at the root, and the translations as children. As language translations are added, they are simply added as new children to the original document.
I'll keep hashing on this till I find something I like.
LDSOSS. Wikimedia, and the Wikipedia project are not endorsed by The Church.