• State Verified Answer
  • Replies 7 replies
  • Answers 1 answer
  • Subscribers 433 subscribers
  • Views 2047 views
  • Users 0 members are here
Options
Related

XTM file type plugin causes problems when opening XLF files!!!

Sameh Elsharkawy

See details attached please.

Fullscreen sdlerror-2020723-13h49m56s.sdlerror.xml Download 
<SDLErrorDetails time="7/23/2020 1:50:00 PM">
  <ErrorMessage>Value cannot be null.
Parameter name: headerNode</ErrorMessage>
  <Exception>
    <Type>System.ArgumentNullException, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089</Type>
    <ParamName>headerNode</ParamName>
    <HelpLink />
    <Source>Xtm.Common.Xlf</Source>
    <HResult>-2147467261</HResult>
    <StackTrace><![CDATA[   at Xtm.Common.Xlf.XlfReaderNodeCreator.CreateHeader(XmlNode headerNode, IXlfFileLoader xlfFileLoader)
   at Xtm.Common.Xlf.XlfReaderNodeCreator.<CreateFiles>d__6.MoveNext()
   at Xtm.Plugin.SDLStudio.Xliff.XtmXliffParser.ParseNext()
   at Sdl.FileTypeSupport.Framework.Integration.FileExtractor.ParseNext()
   at Sdl.FileTypeSupport.Framework.Integration.MultiFileConverter.ParseNext()
   at Sdl.FileTypeSupport.Framework.Integration.MultiFileConverter.Parse()
   at Sdl.ProjectApi.AutomaticTasks.Conversion.ConversionTask.ProcessFile(IExecutingTaskFile executingTaskFile)
   at Sdl.ProjectApi.AutomaticTasks.AbstractFileLevelAutomaticTaskImplementation.Execute()]]></StackTrace>
  </Exception>
  <Environment>
    <ProductName>SDL Trados Studio</ProductName>
    <ProductVersion>15.0.0.0</ProductVersion>
    <EntryAssemblyFileVersion>15.2.6.2831</EntryAssemblyFileVersion>
    <OperatingSystem>Microsoft Windows 10 Pro</OperatingSystem>
    <ServicePack>NULL</ServicePack>
    <OperatingSystemLanguage>1033</OperatingSystemLanguage>
    <CodePage>1256</CodePage>
    <LoggedOnUser>ADMINSAM\Ahmed</LoggedOnUser>
    <DotNetFrameWork>4.0.30319.42000</DotNetFrameWork>
    <ComputerName>ADMINSAM</ComputerName>
    <ConnectedToNetwork>True</ConnectedToNetwork>
    <PhysicalMemory>50276084 MB</PhysicalMemory>
  </Environment>
</SDLErrorDetails>

You simply can not prepare XLF files if this plugin is installed.
Rate translation
×
Suggest better translation
×
Moderator UI
×
  • Get AI Suggestion
Parents
  • 0

    upon removing the XTM file type plugin, I am able to prepare the file normally! Who is responsible please to help fix this issue? I assume SDL has collaboration with the plugin's creators, so when we report a problem like this, it is for SDL's best interest, but instead, I got a message saying that what I am reporting is nonsense and I should double-check!!!! Where did I bring this plugin from then? It must have been created by one of the Plugins vendors collaborating with SDL.
  • 0 in reply to Sameh Elsharkawy

    Sameh Elsharkawy said:
    Who is responsible please to help fix this issue?

    The developer of the plugin.  Where did you get the plugin from?  It is not available from the SDL AppStore.

    Sameh Elsharkawy said:
    I assume SDL has collaboration with the plugin's creators

    Don't assume anything. The beauty of the APIs is that developers can build things without ever speaking to SDL at all.

    Sameh Elsharkawy said:
    when we report a problem like this, it is for SDL's best interest

    If we have some responsibility for the plugin then I'd agree.  But if you install plugins that we have not approved then where do we become responsible for them?

    Sameh Elsharkawy said:
    Where did I bring this plugin from then? It must have been created by one of the Plugins vendors collaborating with SDL.

    Wrong.  Anyone can create plugins... it's completely open.  Developers do not need to collaborate with us at all... all they need is a copy of Studio.  If they wish to publish it on the appstore then it's a different story.

    I suggest you start by contacting someone from XTM and perhaps they can help you.

    Sameh Elsharkawy said:
    I got a message saying that what I am reporting is nonsense and I should double-check!!!!

    If you read that message carefully Sameh you'll see that I was referring to the fact you said you were using Studio defaults and you only provided the error stack.  You then showed me this screenshot after I spent time trying to see where the problem might be coming from:

    Screenshot showing Trados Studio interface with an arrow pointing to a custom filetype named 'XLIFF2' indicating it is not a default setting.

    It's clear from here that you are not using default settings because the XLF file is being picked up by a custom filetype that is not part of Studio and nor is it available on the SDL AppStore.  This is why it was nonsense, and it is.  I thought you would know better.

    Clearly there is a culture difference here because I don't see anything wrong in me saying your claim is nonsense when I know you well enough.

    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

    emoji


    Generated Image Alt-Text
    [edited by: Trados AI at 9:57 PM (GMT 0) on 28 Feb 2024]
Reply
  • 0 in reply to Sameh Elsharkawy

    Sameh Elsharkawy said:
    Who is responsible please to help fix this issue?

    The developer of the plugin.  Where did you get the plugin from?  It is not available from the SDL AppStore.

    Sameh Elsharkawy said:
    I assume SDL has collaboration with the plugin's creators

    Don't assume anything. The beauty of the APIs is that developers can build things without ever speaking to SDL at all.

    Sameh Elsharkawy said:
    when we report a problem like this, it is for SDL's best interest

    If we have some responsibility for the plugin then I'd agree.  But if you install plugins that we have not approved then where do we become responsible for them?

    Sameh Elsharkawy said:
    Where did I bring this plugin from then? It must have been created by one of the Plugins vendors collaborating with SDL.

    Wrong.  Anyone can create plugins... it's completely open.  Developers do not need to collaborate with us at all... all they need is a copy of Studio.  If they wish to publish it on the appstore then it's a different story.

    I suggest you start by contacting someone from XTM and perhaps they can help you.

    Sameh Elsharkawy said:
    I got a message saying that what I am reporting is nonsense and I should double-check!!!!

    If you read that message carefully Sameh you'll see that I was referring to the fact you said you were using Studio defaults and you only provided the error stack.  You then showed me this screenshot after I spent time trying to see where the problem might be coming from:

    Screenshot showing Trados Studio interface with an arrow pointing to a custom filetype named 'XLIFF2' indicating it is not a default setting.

    It's clear from here that you are not using default settings because the XLF file is being picked up by a custom filetype that is not part of Studio and nor is it available on the SDL AppStore.  This is why it was nonsense, and it is.  I thought you would know better.

    Clearly there is a culture difference here because I don't see anything wrong in me saying your claim is nonsense when I know you well enough.

    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

    emoji


    Generated Image Alt-Text
    [edited by: Trados AI at 9:57 PM (GMT 0) on 28 Feb 2024]
Children
No Data