... and I got this error, trying to extend the xml filetype...

??

Sébastien

Hi,

it's issue which emerged very recently - we are working on this and will get back to you when it's sorted.

Patrik

Hi,

While we are working on a permanent solution with a future cumulative update (slated for January) find attached an updated pluginconfig.xml file that should allow you to access the API. Notes:

- This is for development purposes only at this stage - i.e. we would like to enable the developers to start using the public APIs (there was one missing in this config file) for creating plug-ins and customisations
- With the CU in January the entire chain of users will then also be able to start using apps or plug-ins that will be created using the APIs, as they will all get the updated pluginconfig.xml file through the CU
- If you require testing apps on user's machines in the meantime, feel free to patch in the XML file as per the instructions in this post.

To install the file, first rename the same file in c:\Program Files (x86)\SDL\SDL Trados Studio\Studio3\pluginconfig.xml so you have a backup. Then copy the attached file to the same location. This requires admin rights as it is in the Studio3 installation folder.

Let me know if you have any questions on the above.

Thanks
Daniel

Hello Patrik and Daniel,

I am not sure if both answers were destinated to me and my case. I installed the pluginconfig.xml file, but it didn't help. It's about another assembly. Are you working on this issue too? Or am I trying something which is not "allowed"?

Thank you

Sébastien

HI,

sorry, I didn't looked into the message properly - in your case you are referencing XML filter assembly - you should not do that. The filter extension mechanism doesn't need the filter you are extending referenced.

Regards

Patrik

Hi Patrik and Daniel,

as far as I understand, it is not possible with IFileTypeComponentBuilderAdapter to extend the generic XML filter and set up custom XML parser rules programmatically. Is this correct?

A solution that I see is to derive from AbstractXmlFilterComponentBuilder directly and override GetParser(). With that, it would be possible to set up the parser rules by overriding XmlParser.GetParserSettingsObject.

However, when I try that, I get the same error message ("SDL assembly reference not public").

Is there another way to develop a filter that is based on the existing XML filter?

Kind regards,

Christopher

Hi,

if you are referring to the issue with the Sdl.FileTypeSupport.Framework.Core.Settings assembly (you did not attached more details so I expect you do) that should be fixed in CU3

Regards

Patrik

Hi Patrik,

what I want to do:

Develop a new file filter that extends the existing Studio XML filter.

My questions is, how to set up the XML parser rules for this new filter?

My idea is to derive from AbstractXmlFilterComponentBuilder and set the parser rules by overriding XmlParser.GetParserSettingsObject. However, for this I would need to add assembly references to SDL.FileTypeSupport.Native.Xml_1_2.dll and SDL.FileTypeSupport.Native.Xml.FilterSettings_1_2.dll. As far as I understand this is not possible because these assemblies are not part of the public API.

Is there another option to set up the parser rules programmatically?

Thanks

Christopher

Hi Patrik,

what I want to do:

Develop a new file filter that extends the existing Studio XML filter.

My questions is, how to set up the XML parser rules for this new filter?

My idea is to derive from AbstractXmlFilterComponentBuilder and set the parser rules by overriding XmlParser.GetParserSettingsObject. However, for this I would need to add assembly references to SDL.FileTypeSupport.Native.Xml_1_2.dll and SDL.FileTypeSupport.Native.Xml.FilterSettings_1_2.dll. As far as I understand this is not possible because these assemblies are not part of the public API.

Is there another option to set up the parser rules programmatically?

Thanks

Christopher

If you create new unique FileTypeID in your extension a new filter instance will be created in the Studio UI - you should then be able to specify your settings there.

Patrik

I solved it by extending "XML v 1.2.0.0" instead of "XML Any v 1.2.0.0".  Now I see the UI to specify the parser settings.

Thanks,

Christopher