Hi,

basically all 3 items should be sorted out in next version we plan later this year - at the moment I cannot disclose any more details but the behavior especially when it comes to conflicts and issues while importing will be hugely improved.

Regards

Patrik

Those are good news. What about making the source code public?

I don't think this discussion actually happened yet so I cannot comment:-)

It's basically using the public API but as I said it's up to different people to decide.

I fully agree that SDL XLIFF Converter is a really great tool for doing reviews and hope strongly that it is integrated into SDL Studio.

Hi,

Is the reason you all want this integrated really so it also becomes available as a call through the API?  Or are you referring to this ability from the Studio user point of view?

Just curious, as this is a developers forum and this wasn't clear for me.

Paul

The Studio integration would be mainly for my users.

The open sourcing of the tool would help us make it easier to integrate it into the workflow.

E.g. integrating into our project management tool or as a basic step, into windows explorer.

And it would help to do conversions into other formats, like html.

Obviously, if there would be an api call, we could maybe use the xml export and then convert it. But never looked at the xml export so far.