Hi Octavio,

Yes, I'd agree with you that the solution in Studio is a bit cumbersome.  The way it worked in SDLX and obviously TMS made a lot more sense in this regard.  You don't actually need a TM though, you can use a Language Resource Template to act as a template for future TMs but the very fact you need to use the TM for segmentation (created based on your template anyway) on your files as opposed to the Language Resource Template is where it loses its value I think.  Worth noting of course that if you just keep empty TMs for this purpose then it may provide a bit of a workaround as they would be fulfilling the same purpose.  You could create custom tasks in Studio to just prepare the project based on the TM rules rather than the SRX rules, but don't pretranslate or analyse.

Maybe you can address this programatically?  There is a thread started by another customer who is constructing a way to use the SRX rules from WorldServer (I think):

Maybe this would be a helpful approach for you?

Regards

Paul

Hello Octavio,

Unknown said:

The sad part there is that I would have to create one per language, right?

Yes.  This is a design decision, which occasionally comes under scrutiny, as you do need separate templates for each language instead of being able to create a single set of rules that could be applied to all TMs.  I'd like to see an improved, or rather more flexible, approach here too.

Let us know if you do tackle the API and find a way to resolve this in a more practical way?

Regards

Paul