Hi Samuel,
Not sure if that will answer your question, but let me explain how do i use templates during prep. I do develop automation for large LSP, where we do have hundreds of language combinations for our client:-).

So i do have a master templates, and when they are used i do created this function to change source, target language code:

private static void ModifyProjectTemplate(TradosWorkQueue tradosWorkQueue)
{
XmlDocument doc = new XmlDocument();
doc.XmlResolver = null;
doc.Load(tradosWorkQueue.ProjectTemplate);
XmlNamespaceManager nsmgr = new XmlNamespaceManager(doc.NameTable);
nsmgr.AddNamespace("xsi", "http://www.w3.org/2001/XMLSchema-instance");
nsmgr.AddNamespace("xsd", "http://www.w3.org/2001/XMLSchema");
string xpath1 = "/ProjectTemplate/LanguageDirections/LanguageDirection";

XmlNodeList nodes = doc.SelectNodes(xpath1);
if (nodes.Count > 1)
{
for (int i = nodes.Count - 1; i <= 0; i--)
{
if (i > 0)
{
nodes[i].ParentNode.RemoveChild(nodes[i]);
}
else
{
nodes[i].Attributes["TargetLanguageCode"].Value = tradosWorkQueue.TargetTradosCode;
nodes[i].Attributes["SourceLanguageCode"].Value = tradosWorkQueue.SourceTradosCode;
}
}
}
else
{
XmlNode node = nodes[0];

node.Attributes["TargetLanguageCode"].Value = tradosWorkQueue.TargetTradosCode;
node.Attributes["SourceLanguageCode"].Value = tradosWorkQueue.SourceTradosCode;
}
XmlNode termbasenodes = doc.SelectSingleNode("/ProjectTemplate/TermbaseConfiguration");
termbasenodes.ChildNodes[0].ChildNodes[0].InnerText = tradosWorkQueue.SourceTradosCode;
termbasenodes.ChildNodes[1].ChildNodes[0].InnerText = tradosWorkQueue.TargetTradosCode;
doc.Save(tradosWorkQueue.ProjectTemplate);
}


Then, to clear all template memories i do that:

TranslationProviderConfiguration config = p.GetTranslationProviderConfiguration(trgLanguage);
config.Entries.Clear();

Then i do that to add translation memories:

DataTable dt_memories = analyze_q.DataUtils.RetrieveDataTable(sql);
TranslationProviderCascadeEntry[] tmEntries =
new TranslationProviderCascadeEntry[dt_memories.Rows.Count + 1];
tmEntries[0] = new TranslationProviderCascadeEntry(tm_file, true, true, true, 0);



for (int i = 1; i <= dt_memories.Rows.Count; i++)
{
TradosMemory mem = new TradosMemory();

DataRow row = dt_memories.Rows[i - 1];

mem.MemoryID = int.Parse(row["memory_id"].ToString());
mem.Load();
tmEntries[i] = new TranslationProviderCascadeEntry(mem.MemoryFile, mem.Update.Value,
mem.Search.Value, mem.Concordance.Value, mem.Penalty.Value);
}

for (int i = 0; i < tmEntries.Length; i++)
{


config.OverrideParent = true;
config.Entries.Add(tmEntries[i]);

}



Also, you don't really need to have tm in the template. I'm not sure if this has answered your question, but i hope it did helped you to understand how you can work around templates.

EDIT: Emoticons.... bulbs should be [ i ]

Hi Wojciec,

Thanks for the reply, I understand what you're saying.

My question though, is whether or not you can use TM file(s) within the template, without the State attribute?

And why, after adding the required State attribute, does the SDL Project file (sdlproj), contain a (almost) duplicate TM?

If the API allows you to reference a template, that contains TM file(s), why would it require an attribute that does not get assigned by default?

Unless I am missing something obvious, it seems a bit of an unnecessary workaround.

Thanks.

In your case the problem is caused by the fact that the Batch Analyzer app is also adding the TM that you specify to the project. If this is already in the template then this will result in duplicate entries hence the error from your initial post. If you look at the code in the Batch Analyzer in the file ProjectCreator.cs at line 69 you will see the AddTm method. 

In conclusion you can definitely use TM file(s) within the template. 

Hi Romulus,

Thanks for the reply and explaining the issue.

It looks like it's working well now.

Thanks a million.

Sam