Generated SDLTBs crash

Dear,

We are having problems with the SDLTB files we have created with the MultiTerm API.

The SDL Trados GUI (both 2009 and 2011) crash when we view entries in the SDLTB's we create ourselves.

Termbases are created using createTermbase("test_ja", "", "2009Definition for Test_JA.xdt.xml", "testexportxml1.xml"); Entries are added using tbNew.newEntry(content,  false).

Reading the sdltb with the MultiTerm API seems to work but the SDL Trados Desktop GUI crashes. You'll find a screenshot of v2011 crash in reportcrash20120709SDLTrados.zip together with the XDT and XML (entry content).

You can reproduce by loading our SDLTB.

Can you tell us what we are missing/ How we can prevent this?

Thanks and kind regards

reportcrash20120709SDLTrados.zip
Parents
  • Thomas,

     

     This from an SDL Architect...

    I can confirm I also have problems with the provided  termbases, but not why so far. I don't know the code used to create the data, the function mentioned in the report is none of ours.  I tried creating a termbase and importing the provided data myself and it looks OK. Maybe a look at the code I used is helpful.

     

     

    // Create and open local termbase repository

    Sdl.MultiTerm.TMO.Interop.Application _Mt = new Sdl.MultiTerm.TMO.Interop.Application();

    TermbaseRepository tr = _Mt.LocalRepository;

    tr.Connect("", "");

    // Create new file based termbase

    Termbase tb = _Mt.LocalRepository.Termbases.New("tempTermbase", "programmatically created",

       @"D:\Data\2009Definition for Test_JA.xdt",

       @"D:\Data\New Termbase.sdltb");

    // inject file paths into import definition (alternatively create an import definition in the wizard

    // with the files filled in)

    string tmpPath = System.Environment.GetEnvironmentVariable("TEMP") + "\\tmpImportDefinition.xml";

    _Tb.ImportDefinitions["Default import definition"].Save(tmpPath);

    XmlDocument doc = new XmlDocument();

    doc.Load(tmpPath);

    XmlNode node = doc.SelectSingleNode("//XMLFile");

    node.InnerXml = @"D:\Data\testexportxml1.xml";

    node = doc.SelectSingleNode("//ErrorFile");

    node.InnerXml = @"D:\Data\testexportxml1.xml.import.log";

    doc.Save(tmpPath);

    // use modified definition for import

    ImportDefinition modified = _Tb.ImportDefinitions.Add("tmpImport", "", tmpPath);

    modified.ProcessImport(MtTaskType.mtScript);

    // clean up

    modified.Delete();

    System.IO.File.Delete(tmpPath);

    tr.Disconnect();

    Paul Filkin | RWS Group

    ________________________
    Design your own training!

    You've done the courses and still need to go a little further, or still not clear? 
    Tell us what you need in our Community Solutions Hub

  • Update from an SDL Architect...

    It looks like the termbase was created correctly, but the import: tbNew.newEntry(content,  false).  seems to have been passed the content of "testexportxml1.xml" as a parameter. This file is an export of the complete termbase, but Entries.New (the function probably used inside newEntry) takes the xml for a single entry. The format is briefly described in the sdk help, or you can export a single entry from the desktop client as a template:note that in that case you need to remove the <concept> group.

    Paul Filkin | RWS Group

    ________________________
    Design your own training!

    You've done the courses and still need to go a little further, or still not clear? 
    Tell us what you need in our Community Solutions Hub

Reply
  • Update from an SDL Architect...

    It looks like the termbase was created correctly, but the import: tbNew.newEntry(content,  false).  seems to have been passed the content of "testexportxml1.xml" as a parameter. This file is an export of the complete termbase, but Entries.New (the function probably used inside newEntry) takes the xml for a single entry. The format is briefly described in the sdk help, or you can export a single entry from the desktop client as a template:note that in that case you need to remove the <concept> group.

    Paul Filkin | RWS Group

    ________________________
    Design your own training!

    You've done the courses and still need to go a little further, or still not clear? 
    Tell us what you need in our Community Solutions Hub

Children
No Data