• Replies 6 replies
  • Subscribers 362 subscribers
  • Views 4856 views
  • Users 0 members are here
Options
Related

Wishlist for the SDL XLIFF Converter for Microsoft Office

Remy Blaettler

First, the SDL XLIFF Converter for Microsoft Office is genius. I think  it's one of the most used tools in our company. But since we need it so much there are a few things that could be improved.

The simplest thing that you could do would be to open source it and lets us hack away at it. I think it would also make for a great example application.

If this is not possible for whatever reason, here are some things to improve:

  • Change the App Title, people often use the 2009 by accident and there is no easy way to notice this.
  • Add some debug logging. We have one PC where the import does not work, but there is no error message or any other logging to see what is going on.
  • Add context menu integration (Right click on file -> convert)

I also heard that there are plans to integrate it further with Trados? That would of course help too.
Rate translation
×
Suggest better translation
×
Parents Reply Children
  • in reply to Paul Filkin

    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.