• State Verified Answer
  • Replies 25 replies
  • Answers 3 answers
  • Subscribers 434 subscribers
  • Views 9304 views
  • Users 0 members are here
Options
Related

Problems with TermExcelerator plugin

Pascal Zotto

 Hi,

On my search for a faster termbase tool (when adding them to a termbase) I already used RyS one which is very fast but lacks very important term list overview without mouse clicks so I just installed TermExcelerator, but there seem to be a few bugs.

(settings are per project not globally)

When I restart Trados standard termbank switches from Excel-file (TermExtractor) to the first Multiterm termbase in the list.

I also cannot add any term via “Quick add new term”, it’s greyed out and the shortcut does not do anything.
If I try adding it the slow way, I get an error: The sequence does not contain any matching Element. (freely translated from German: Die Sequenz enthält kein übereinstimmendes Element.)
also since I added this addin, whenever I double click a word on the left in the editor I get this error: An element with the same key has already been added. (freely translated from German: Ein Element mit dem gleichen Schlüssel wurde bereits hinzugefügt.)

Any ideas?

regards,
Pascal
Rate translation
×
Suggest better translation
×
Moderator UI
×
  • Get AI Suggestion
Parents
  • 0

    meanwhile most errors are gone, without me changing anything oO and Quick add works but I cannot add another translation for an existing term via Quick add: I then get this error: The index was outside the bounds of the array. It must not be negative and smaller than the collection. Parameter name: index (freely translated from German: Der Index lag außerhalb des Bereichs. Er darf nicht negativ und kleiner sein als die Sammlung. Parametername: Index.)
    I can add another translation for an existing term via Termbase Viewer though.

    I still must reset the Excel termbase as standard after a restart of Trados.
Reply
  • 0

    meanwhile most errors are gone, without me changing anything oO and Quick add works but I cannot add another translation for an existing term via Quick add: I then get this error: The index was outside the bounds of the array. It must not be negative and smaller than the collection. Parameter name: index (freely translated from German: Der Index lag außerhalb des Bereichs. Er darf nicht negativ und kleiner sein als die Sammlung. Parametername: Index.)
    I can add another translation for an existing term via Termbase Viewer though.

    I still must reset the Excel termbase as standard after a restart of Trados.
Children
  • 0 in reply to Pascal Zotto
    Hi

    I'm not sure what to suggest. I don't have any of these problems with the plugin. Even my settings can be retained globally. Can you share the full error stack you are seeing? Just attach it to your post and the forum will render it nicely.

    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

  • 0 in reply to Paul

    Hi ,

    Here comes the error stack when trying to add a synonym to an existing term via quick add term.

     

    Fullscreen sdlerror-2018918-16h52m7s.sdlerror.xml Download 
    <SDLErrorDetails time="18.09.2018 16:52:15">
  <ErrorMessage>Der Index lag außerhalb des Bereichs. Er darf nicht negativ und kleiner als die Sammlung sein.
Parametername: index</ErrorMessage>
  <Exception>
    <Type>System.ArgumentOutOfRangeException, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089</Type>
    <ParamName>index</ParamName>
    <HelpLink />
    <Source>Sdl.Community.ExcelTerminology</Source>
    <HResult>-2146233086</HResult>
    <StackTrace><![CDATA[   bei Sdl.Community.ExcelTerminology.Ui.TermsList.AddAndEdit(IEntry entry, ExcelDataGrid excelDataGrid)
   bei System.Action`2.Invoke(T1 arg1, T2 arg2)
   bei Sdl.Community.ExcelTerminology.TerminologyProviderViewerWinFormsUIExcel.AddAndEditTerm(IEntry term, String source, String target)
   bei Sdl.TranslationStudio.Editor.Terminology.TermbaseViewer.TermBaseViewPartX.TerminologyProviderViewerAddAndEditTerm(ITerminologyProvider termbase, ITermHit term, String source, String target)
   bei Sdl.TranslationStudio.Editor.Terminology.TermbaseViewer.TermBaseViewPartX.AddAndEditTerm(ITerminologyProvider termbase, ITermHit term, String source, String target)
   bei Sdl.TranslationStudio.Editor.Terminology.EditorTermbaseUtils.AddTerm(IEditorService editorService, ITranslatableDocument translatableDocument, String sourceText, String targetText)
   bei Sdl.TranslationStudio.Editor.Terminology.Actions.AbstractAddNewTermAction.AddTerm()
   bei Sdl.TranslationStudio.Editor.Terminology.Actions.QuickAddNewTerm.Execute()
   bei Sdl.Desktop.Platform.Implementation.CommandBars.StaticAction.Execute()
   bei Sdl.Desktop.Platform.Implementation.CommandBars.ActionService.<>c__DisplayClass30_0.<ExecuteAction>b__0()
   bei Sdl.Desktop.Platform.Implementation.Services.Log.Resources(Object message, Action action)
   bei Sdl.Desktop.Platform.Implementation.CommandBars.ActionService.ExecuteAction(IAction action, ActionOrigin origin, Boolean allowToggle)
   bei Sdl.Desktop.Platform.Implementation.CommandBars.ActionService.ExecuteActionForShortcut(Keys shortcut)
   bei Sdl.Desktop.Platform.WinForms.StudioWindowForm.OnKeyDown(KeyEventArgs e)
   bei System.Windows.Forms.Control.ProcessKeyEventArgs(Message& m)
   bei System.Windows.Forms.Form.ProcessKeyPreview(Message& m)
   bei System.Windows.Forms.Control.ProcessKeyPreview(Message& m)
   bei System.Windows.Forms.Control.ProcessKeyPreview(Message& m)
   bei System.Windows.Forms.Control.ProcessKeyPreview(Message& m)
   bei System.Windows.Forms.Control.ProcessKeyPreview(Message& m)
   bei System.Windows.Forms.Control.ProcessKeyPreview(Message& m)
   bei System.Windows.Forms.Control.ProcessKeyPreview(Message& m)
   bei System.Windows.Forms.Control.ProcessKeyPreview(Message& m)
   bei System.Windows.Forms.Control.ProcessKeyPreview(Message& m)
   bei System.Windows.Forms.Control.ProcessKeyPreview(Message& m)
   bei System.Windows.Forms.Control.ProcessKeyPreview(Message& m)
   bei System.Windows.Forms.Control.ProcessKeyPreview(Message& m)
   bei System.Windows.Forms.Control.ProcessKeyPreview(Message& m)
   bei System.Windows.Forms.Control.ProcessKeyPreview(Message& m)
   bei System.Windows.Forms.Control.ProcessKeyPreview(Message& m)
   bei System.Windows.Forms.Control.ProcessKeyPreview(Message& m)
   bei System.Windows.Forms.Control.ProcessKeyPreview(Message& m)
   bei System.Windows.Forms.Control.ProcessKeyMessage(Message& m)
   bei System.Windows.Forms.Control.WmKeyChar(Message& m)
   bei System.Windows.Forms.Control.WndProc(Message& m)
   bei System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
   bei System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
   bei System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)]]></StackTrace>
  </Exception>
  <Environment>
    <ProductName>SDL Trados Studio</ProductName>
    <ProductVersion>14.0.0.0</ProductVersion>
    <EntryAssemblyFileVersion>14.1.10012.29730</EntryAssemblyFileVersion>
    <OperatingSystem>Microsoft Windows 10 Pro</OperatingSystem>
    <ServicePack>NULL</ServicePack>
    <OperatingSystemLanguage>1031</OperatingSystemLanguage>
    <CodePage>1252</CodePage>
    <LoggedOnUser>TRANSLATING-IT\Translating-IT</LoggedOnUser>
    <DotNetFrameWork>4.0.30319.42000</DotNetFrameWork>
    <ComputerName>TRANSLATING-IT</ComputerName>
    <ConnectedToNetwork>True</ConnectedToNetwork>
    <PhysicalMemory>16740688 MB</PhysicalMemory>
  </Environment>
</SDLErrorDetails>

    regards,

    Pascal
  • 0 in reply to Pascal Zotto
    Hi ,

    I just tested together with the plugin and we couldn't reproduce the issue. Could you please send me the excel file you are using? Also please tell me the steps to reproduce this with your file?

    Kind regards,

    Andrea Ghisa
  • 0 in reply to Andrea-Melinda Ghisa

    Hi ,

     

    Here is one of them.

    Stepe to reproduce the error: Add a term and add another term for the same source term.

    Trados 2017 with latest updates installed and set to German. 2 other MT termbases added to project.

    language settings for termbases: English (United States) and Luxembourgish (Luxembourg)

     

    regards,

    Pascal

     

    Büro EN_US-LB_LU.xlsx
  • 0 in reply to Pascal Zotto
    Thank you for the file. I'll investigate the issue and come back to you with an update.

    Kind regards,

    Andrea Ghisa
  • 0 in reply to Andrea-Melinda Ghisa
    Hi and ,

    any update to this one as I did not get any reply to my last mails?

    these problems still persist:

    - When I restart Trados or switch to another project the standard termbank (the one to be updated) switches from Excel-file (TermExcelerator) to the first Multiterm termbase in the list.

    - Added terms do not show up immediately in list but only after switching to another segment.

    regards,
    Pascal
  • 0 in reply to Pascal Zotto
    Hi

    Many apologies for not getting back to you on this. I'd like to blame xmas but it was September! I have logged this under SDLCOM-165 in our tracking system and we'll try to plan some time in to look at this in the near future.

    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

  • 0 in reply to Pascal Zotto
    Hi ,

    Sorry for the late reply. We released a new version of the plugin on the AppStore. Could you please see if in this version the issue you found is fixed?

    Kind regards,
    Andrea Ghisa