in both cases (1. and 2., 3. not exist...) you must apply, by hand, a number of queries for porting to 2.0 ML or leave in monolingual trees in case 2.faglork wrote: Will there be a sort of import/convert function?
Applying SQL queries is not the problem ... question is, will this process be documented? A "conversion manual", so to speak.alby wrote:in both cases (1. and 2., 3. not exist...) you must apply, by hand, a number of queries for porting to 2.0 MLfaglork wrote: Will there be a sort of import/convert function?
I speak for MLE only:faglork wrote: "a number of queries" can be anything - from issuing 10 well-documented sql queries and be done in an hour up to finding out how it may be done and working for two weeks to get it straight ...
Many things can happen in 4-5 monthsfaglork wrote: would you advise to use the CMSMS MLE fork as there will be a safe way for a future transition to CMSMS 2.0?
Right, but it would be nice to have a word from the devs whether the multilanguage system is still in development/will get substantially changed. I think that "in principle" they have a clear idea how to get it to work (would be nice to hear about the basics). If not, well, that's ok, too - at least I can set my timeframes accordingly.alby wrote: Many things can happen in 4-5 months
ML is aready in but in a alpha stage is possible change whatever for new features, back compatible, performance, ......faglork wrote: substantially changed. I think that "in principle" they have a clear idea how to get it to work (would be nice to hear about the basics).
