Hello Ian,

Unknown said:

Are we expecting to see any changes in segmentation?

No.  There may be the odd thing here and there caused by small changes in filetype differences but there are no major changes to the segmentation engine.

Unknown said:

Can files that have been converted to bilinguals in 2015 be exported in 2017/what filters have been modified?

Probably.  Best thing is to look at the release notes to see which have changed.

Unknown said:

Will we need to recreate TMs/Term bases/ Parsers / projects/packages, etc due to differences between versions?

TMs, Termbases, projects, packages no, although TMs should be optimised if you wish to take advantage of fragment matching.  Parsers... depends on the filetype.  If you customised a filetype that has been upgraded then it would make sense.

Unknown said:

Do logs and reports still have the same base structure?

Yes... although there are additions to some of the reports to help quantify fragment matching for example.

Unknown said:

Quite simply can I just in stall the new version and carry on with all our existing materials/projects, or will I need to tweak/redo some elements?

Quite simply, yes.  But it's always best (in my opinion) to wrap up your projects in the same version you started with and start news ones in the new version.  Then you avoid any possible complications.  But having said this I know plenty of users who have just gone for it and suffered no ill.

Regards

Paul

Hello Ian,

Unknown said:

Are we expecting to see any changes in segmentation?

No.  There may be the odd thing here and there caused by small changes in filetype differences but there are no major changes to the segmentation engine.

Unknown said:

Can files that have been converted to bilinguals in 2015 be exported in 2017/what filters have been modified?

Probably.  Best thing is to look at the release notes to see which have changed.

Unknown said:

Will we need to recreate TMs/Term bases/ Parsers / projects/packages, etc due to differences between versions?

TMs, Termbases, projects, packages no, although TMs should be optimised if you wish to take advantage of fragment matching.  Parsers... depends on the filetype.  If you customised a filetype that has been upgraded then it would make sense.

Unknown said:

Do logs and reports still have the same base structure?

Yes... although there are additions to some of the reports to help quantify fragment matching for example.

Unknown said:

Quite simply can I just in stall the new version and carry on with all our existing materials/projects, or will I need to tweak/redo some elements?

Quite simply, yes.  But it's always best (in my opinion) to wrap up your projects in the same version you started with and start news ones in the new version.  Then you avoid any possible complications.  But having said this I know plenty of users who have just gone for it and suffered no ill.

Regards

Paul