Wordbird for Studio 2019

Hi ,

Do you plan to update your app Wordbird for Studio 2019? That would be great.
Regards,
Angelo

  • Hi Angelo,
    Thanks for asking. I'll look into it as soon as I find the time. From what I've seen so far it seems easy enough if it just involves compiling it against .NET 4.7.
    Kind regards
    Angela

  • Hi Angelo,
    I finally got around to upgrade Wordbird to Studio 2019. It should become available to download within the next days.
    Kind regards
    Angela
  • Hi Angela
    This are great news. I just saw that you published the new version for 2017 and I was sure that the 2019 version would come shortly after.
    Thank you.
    Kind regards,
    Angelo
  • Thanks

    The 2019 and updated 2017 versions are now here: appstore.sdl.com/.../

    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

  • Hi Angela,

    I encountered a problem with Wordbird.

    Sometimes (it does not happen frequently, but it happens) I get a strange message after highlithing something in the source segment and confirming. After deleting the highlight (deleting and reinserting the text in the source segment - in doing so the highlight  is gone) the problem disappears.

    I send you the error attached. Maybe you can have a look at it and investigate the problem?

    Thanks and regards,

    Angelo

    <SDLErrorDetails time="18.09.2018 08:55:09">
      <ErrorMessage>SegmentEditDistanceComputer: diagonalOnly == true but sourceTokens.Count != targetTokens.Count</ErrorMessage>
      <Exception>
        <Type>System.Exception, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089</Type>
        <HelpLink />
        <Source>Sdl.LanguagePlatform.Lingua</Source>
        <HResult>-2146233088</HResult>
        <StackTrace><![CDATA[   at Sdl.LanguagePlatform.Lingua.SegmentEditDistanceComputer.ComputeEditDistanceImpl_Original(IList`1 sourceTokens, IList`1 targetTokens, Boolean computeDiagonalOnly, BuiltinRecognizers disabledAutoSubstitutions, TagAssociations& alignedTags, Boolean diagonalOnly)
       at Sdl.LanguagePlatform.TranslationMemoryImpl.AbstractScorer.ComputeScores(SearchResult searchResult, IAnnotatedSegment docSrcSegment, IAnnotatedSegment docTrgSegment, List`1 documentPlaceables, TuContextData TuContextData, Boolean isDuplicateSearch, FuzzyIndexes usedIndex, Boolean scoreDiagonalOnly)
       at Sdl.LanguagePlatform.TranslationMemoryImpl.Translator.CreateTranslationProposal(TranslationUnit translatedSegment, Segment docSourceSegment, LanguageTools sourceLanguageTools, LanguageTools targetLanguageTools)
       at Sdl.LanguagePlatform.TranslationMemoryTools.TUOperations.CreateTranslationProposal(TranslationUnit translatedSegment, Segment docSourceSegment, LanguageTools sourceLanguageTools, LanguageTools targetLanguageTools, SearchSettings searchSettings)
       at Sdl.TranslationStudio.Editor.Autopropagate.RepetitionTableAutopropagationProvider.GetAutopropagatedMatchResult(ISegmentContainerNode segmentNode, List`1 contextSegmentNodes)
       at Sdl.TranslationStudio.Editor.TranslationEditor.SideBySideDocumentEditingView.AutopropagateSegment(ISegmentContainerNode segment)
       at Sdl.TranslationStudio.Editor.TranslationEditor.SideBySideDocumentEditingView.CheckConditionsAndAutopropagateSegment()
       at Sdl.TranslationStudio.Editor.TranslationEditor.SideBySideDocumentEditingView.ConfirmSegment(Nullable`1 segmentNavigationFilter)
       at Sdl.TranslationStudio.Editor.TranslationEditor.Actions.AbstractConfirmSegmentAction.ExecuteActiveSegment()
       at Sdl.TranslationStudio.Editor.TranslationEditor.Actions.AbstractConfirmSegmentAction.Execute()
       at Sdl.Desktop.Platform.Implementation.CommandBars.ActionService.<>c__DisplayClass30_0.<ExecuteAction>b__0()
       at Sdl.Desktop.Platform.Implementation.Services.Log.Resources(Object message, Action action)
       at Sdl.Desktop.Platform.Implementation.CommandBars.ActionService.ExecuteAction(IAction action, ActionOrigin origin, Boolean allowToggle)
       at Sdl.Desktop.Platform.Implementation.CommandBars.ActionService.ExecuteActionForShortcut(Keys shortcut)
       at Sdl.Desktop.Platform.WinForms.StudioWindowForm.OnKeyDown(KeyEventArgs e)
       at System.Windows.Forms.Control.ProcessKeyEventArgs(Message& m)
       at System.Windows.Forms.Form.ProcessKeyPreview(Message& m)
       at System.Windows.Forms.Control.ProcessKeyPreview(Message& m)
       at System.Windows.Forms.Control.ProcessKeyPreview(Message& m)
       at System.Windows.Forms.Control.ProcessKeyPreview(Message& m)
       at System.Windows.Forms.Control.ProcessKeyPreview(Message& m)
       at System.Windows.Forms.Control.ProcessKeyPreview(Message& m)
       at System.Windows.Forms.Control.ProcessKeyPreview(Message& m)
       at System.Windows.Forms.Control.ProcessKeyPreview(Message& m)
       at System.Windows.Forms.Control.ProcessKeyPreview(Message& m)
       at System.Windows.Forms.Control.ProcessKeyPreview(Message& m)
       at System.Windows.Forms.Control.ProcessKeyPreview(Message& m)
       at System.Windows.Forms.Control.ProcessKeyPreview(Message& m)
       at System.Windows.Forms.Control.ProcessKeyPreview(Message& m)
       at System.Windows.Forms.Control.ProcessKeyPreview(Message& m)
       at System.Windows.Forms.Control.ProcessKeyPreview(Message& m)
       at System.Windows.Forms.Control.ProcessKeyPreview(Message& m)
       at System.Windows.Forms.Control.ProcessKeyPreview(Message& m)
       at System.Windows.Forms.Control.ProcessKeyMessage(Message& m)
       at System.Windows.Forms.Control.WmKeyChar(Message& m)
       at System.Windows.Forms.Control.WndProc(Message& m)
       at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
       at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
       at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)]]></StackTrace>
      </Exception>
      <Environment>
        <ProductName>SDL Trados Studio</ProductName>
        <ProductVersion>15.0.0.0</ProductVersion>
        <EntryAssemblyFileVersion>15.0.1.34200</EntryAssemblyFileVersion>
        <OperatingSystem>Microsoft Windows 10 Pro</OperatingSystem>
        <ServicePack>NULL</ServicePack>
        <OperatingSystemLanguage>1040</OperatingSystemLanguage>
        <CodePage>1252</CodePage>
        <LoggedOnUser>ACL-OFFICE2017\Angelo</LoggedOnUser>
        <DotNetFrameWork>4.0.30319.42000</DotNetFrameWork>
        <ComputerName>ACL-OFFICE2017</ComputerName>
        <ConnectedToNetwork>True</ConnectedToNetwork>
        <PhysicalMemory>16670440 MB</PhysicalMemory>
      </Environment>
    </SDLErrorDetails>

  • Hi Angelo,

    Thanks for that. I'll see what I can do. I can't say that I've seen this before.

    Regards
    Angela
  • Hi Angelo,

    I did some digging but the problem seems highly complex and so far I could not reproduce this error. Hence, I hope you don't mind a couple of questions.

    From what you tell it seems the inserted tags are the problem. Has it ever happened after highlighting parts of the *target* segment? (I've rarely seen the need to highlight something in the source which might be why I've never come across this error.)

    Does it happen also in documents where source editing is enabled (see Project Settings->Project->Allow source editing)?

    And one more: Your unhighlight procedure to fix the problem seems unusual ("deleting and reinserting the text in the source segment - in doing so the highlight is gone"). Have you tried the "No Highlight" option? (I know this didn't work reliably in the past but should do now.)

    Here is my analysis so far:
    From the call stack I can see that the fault is not triggered by my code but by the subsequent confirm/autopropagate action.
    Most baffling is that when I follow the stack it becomes clear that diagonalOnly should never be true.
    My hunch is that I would need to do more to "notify" Trados of a change in the source (which of course might come as a surprise when source editing is not enabled).

    Regards
    Angela
  • Hi Angela

    To answer your questions, I never experienced the problem again after I quit highlighting the source language, therefore I think that the "problem" is connected to the source language. I wanted to highlight exctly the words in the source segment for wich I needed answers from our client, instead of highlighting word in the target language. But it is not necessary.

    Some other infos you required:

    > I have all my projects with source editing enabled.

    > I tried different things: No Highlight was the first options, and the other one that I mentioned I tried after realizing that I got the same error after No Highligt. In the target source the best thing to do, I think, is using the Studio function "Clear Formatting".

    I wanted to ask you could improve a couple of things with a new version:

    1. After clicking on the Higlight option, the first colour you can select is black. Could it be i.e. Yellow? This would allow to use better the key combination, as you would only need to press Enter instead of chosing the colour with the mouse. Or you could give the user the choice to set the color order in the settings (but that requires more work for you, I think :-))

    2. I put the highlight button in the quick access bar. After hitting it the focus is not right and I cannot select the color (see picture):

    Trados Studio interface showing the quick access bar with highlight button added.

    Close-up of the highlight color options in Trados Studio with 'No Highlight' selected.

    Maybe you can do something about it.

    I hope I could be of help. Thank you for your work and your support!

    Have a nice day

    Angelo

    emoji


    Generated Image Alt-Text
    [edited by: Trados AI at 5:34 AM (GMT 0) on 6 Mar 2024]
  • Hi Angelo,

    Reordering the colours is a great idea. Thank you!

    Also thanks for alerting me to the positioning problem. This is not happening in Studio 2017 and as I'm using the same code for 2017 and 2019 it appears something in the .NET Framework has changed. [:@]

    Kind regards
    Angela