Stelios Mathioulakis 

Perhaps you can explain what you are trying to achieve? I confirmed with Patrick Andrew Hartnett that we have manipulated SDLXLIFF in our appstore projects before to support unusual workflows, but always by using the FileTypeSupport.Framework to read and write the SDLXLIFF files.

We persist meta-data, such as the back-translation with the TranslationOrigin in our Trados Transcreate application.  We included this to facilitate automation in the workflow as there are detached procedures in the workflow.

If this is the sort of thing that would help then search for "back-translation" in the source code of this project:

https://github.com/RWS/Sdl-Community/tree/master/SDLTranscreate

Stelios Mathioulakis 

Perhaps you can explain what you are trying to achieve? I confirmed with Patrick Andrew Hartnett that we have manipulated SDLXLIFF in our appstore projects before to support unusual workflows, but always by using the FileTypeSupport.Framework to read and write the SDLXLIFF files.

We persist meta-data, such as the back-translation with the TranslationOrigin in our Trados Transcreate application.  We included this to facilitate automation in the workflow as there are detached procedures in the workflow.

If this is the sort of thing that would help then search for "back-translation" in the source code of this project:

https://github.com/RWS/Sdl-Community/tree/master/SDLTranscreate

I want to inject Folia namespace elements inside an sdl xliff, in the extension point that I mentioned before.

Stelios Mathioulakis 

Well... we already established this isn't supported as Patrik advised.  I just wondered if there was another way to achieve your ultimate aim for wanting to do this.  But if you don't explain we'll never know!