Brief background: our majority language project has had a bit of a rocky history. The four Gospels were printed in 2010 after something over a decade of work. Since then, ten other books have been completed, with two more almost ready.
A decision has been made to revise the Gospels: we now have a cohesive team of MTTs (as opposed to one main translator and others who came and went from the Gospels project), and they have a lot more experience. We also have the challenge of eschewing high literary language (pardon the irony), yet avoiding the translation sounding like a particular dialect – the Gospels didn’t always achieve the latter.
Anyway, I can see two options:
- To make a daughter project, and revise the Gospels there;
- To archive the current Gospels (where we’re still tweaking footnotes, etc. for electronic publishing purposes – mainly apps and the DBL) to a new project, and revise the Gospels in the main project.
My question is: which route would others recommend? (1) has the advantage that there are tick-boxes (checkboxes) to help the translators/revisers to keep track of what they’ve revised to their satisfaction; (2) has the advantage that the revision will share the spellchecking, morphological and Biblical terms data of the rest of the project. And it seems logical to keep the latest version of the whole translation in one project, with an archive (maybe more than one in future) for earlier versions of parts on the Bible.
I wish we could have the best of both worlds! Is there a way to do (1) and have two projects share the same spelling/morpho/Biblical terms data?
Or, is there a way to get tick-boxes in a Standard (non-Daughter) Project? This could be useful in a number of other, more common situations: preparing Draft 2 from Draft 1, you could keep track of which verses you’ve checked and are satisfied with, for example.