Migrating - Single project scope to Solution scope

Posted by nickniebling on Thu 28 of Nov, 2013 11:43 GMT

We've been using the tool since before Solution scope was introduce (actually I was one of the guys pushing to get this feature).

We never found a good time to migrate from "Single Project Scope" to "Solution Scope". Today we have the ml classes inside each project that needs translation and we don't share strings that has already been translated :-(

I could really use 2 different things - please help me out how to achieve one or both..

1) It would be nice with a migration, so the biggest translation project is moved to "solution scope".

2) It would be nice if I could merge translations between translation projects (without putting translations in global database, as this should only be for confirmed strings)
Example: I got 2 translation projects (single project scoped). The two projects has a subset of strings - no reason for translators of both projects to translate same strings. And the strings not part of the subset might be useful in the future. It could mean the difference between asking translators for a new revision or not.

If I could do both of above, I could also migrate to solution scope. Make 2 solution share the new translation project. Merge strings from the small translation project into the large translation project. Now I have 1 translation project serving both solutions.

Let me know if above is possible today, in near future or if you would like to help us migrate (and receive payment for the work of course).

Yours Faithfully,
Nick Niebling
nn at euroform dot com

Reads: 27971
Link
Posted by Phil on Thu 28 of Nov, 2013 23:11 GMT Germany

This should be possible, but I would certainly recommend committing your work to source control or making a backup before trying it out.

To switch a project to solution scope, open the project properties dialog, select the second tab (Project Database), and then select "Solution Level". That will split the project database into a translation store at solution level, and a project info file at project level.

If the solution-level translation-store already exists, then the Add-In will check for conflicting String IDs. By this I mean a numeric string ID defined at both project and solution level, but for different texts. In this case, it would generate a new String ID in the project.

After this it would copy the translations from the project database into the translation store at solution level.

You would have to repeat this for each project in the solution.

Phil

Link

Posted by nickniebling on Thu 28 of Nov, 2013 23:54 GMT
Thanks a lot - I will try to make this work :-)
Link

Posted by nickniebling on Tue 17 of Dec, 2013 16:06 GMT
No luck with moving to solution scope - I will have to wait and try again after next translation round. A couple of hours consultancy would still help a lot.
Link