Hello Dan,

Unknown said:

Can we have the people responsible on here so that I have somebody other than Paul to whom l can give a piece of my mind?

Looks like you struck out and got me... although you can rest assured that posting it in here means you have got the attention of the right people (if I'm not ;-))

Unknown said:

As usual I was asked to select five languages and as usual I found myself asking why. Why can't the software pick out the five languages I had selected for 2015 and 2014 and offer me a choice, a button saying "Use existing languages?"?

I certainly agree with you here and we should be asking when you start the installation process if you are upgrading and if you want to use the same languages you used before... or something like this as part of an upgrade/migration process.  That on its own doesn't sound too complicated to me, although I'd prefer to see a more comprehensive approach that would definitely not be trivial work.  I know the focus next year is likely to be on the "little" things like this so maybe your timing is right.  We'll see.

Unknown said:

I want functionality that directly improves my efficiency and part of that is a streamlined interface that requires me to make as few clicks as possible. I have seen no progress on that front in Studio over two generations of product. The five languages issue is an excellent example.

I don't really agree with you here Dan.  Not completely anyway.  You are referring to a one off task when you install the product or some updates... not exactly something that affects you daily.  Irritating at worst I agree, but hardly affecting users more than that.  On the other hand I think the improvements in the interface and through the opportunities afforded by the APIs we have seen many ways to work that save considerable time for all sorts of things.

Unknown said:

Another is creation of termbases: why can't I just have the option of a one-click process that creates a new termbase immediately and without having to deal with the lumbering time-sink that is Multiterm? One button in the Studio interface saying "Create based on existing termbase". I click on it, it pops up a list right under the cursor of the ten most recently used termbases, saying "Select termbase to use as template". I click on my main termbase. Done, new termbase created.

A prime example would be the glossary plugin.  Have you tried that?  Almost a one click termbase creation if you want it.  Scroll down a bit in this article:

https://multifarious.filkin.com/2015/12/09/feature-rich/

Having said that... how often do you create a completely new termbase?  You can also do that anyway from within Studio even if it does use the MultiTerm Wizard.  It is a bit clicky and seems to stop at unnecessary windows as well as not having a finish button if you know you don't want to change the definition.

Unknown said:

There is more to productivity than flashy new suggestion technology. You've spent some time on the shiny new toys in 2017 and yes, I like those too, but you really need to spend some time on the boring functions that are the bread and butter of translation. You need to LOOK at how freelancers, as well as LSPs, use the software in daily life.

Of course we know this Dan.  We have run workshops with Freelancers, LSPs, Corporates in the past to gather feedback for the tools.  In fact last month we did this again in great details covering the needs of new users and more experienced users to help guide what we do in 2017 and onwards.  Some of the people on this forum might even be able to share their views of those workshops if they read this.

Unknown said:

Printing isn't sexy, but when you want to proof-read a translation on paper with a deadline looming, being immediately able to print only the segments that you need is a huge benefit. I find myself tempted to skip a vital QA step because Studio makes it so hard to isolate and print 30 segments out of 700. That's a serious issue for me. SDL clearly couldn't care less.

I'd agree here too.  You can workaround this easily enough if you are familiar with some of the tools like the SDLXLIFF Toolkit for example, or if you export to Excel and just filter out what you don't need to see, but it would clearly be better to have an export to Word feature that could just take segments you wanted based on some condition.  Probably not hard to do either... would be a neat batch task.

Unknown said:

Your market position is not secure and, by failing to address longstanding issues like these, you are allowing goodwill to erode.

I think we all know where you're coming from Dan.  Your usecases are one thing, not everything, but an important thing that we do need to consider.  It's hard to be all things to all men, but we are conscious of these requirements and have put in place an environment where it's possible for any developer to tackle many of these small things in isolation.  It also means we can address things in core development using the same mechanism, sometimes as an app and sometimes within the product.  I know you might say having to use apps is not right... but I would wholeheartedly disagree with that.  The ability to use apps is one thing that sets us apart, and I noted that even Kilgray are starting to mention their limited features to support this sort of thing, and will probably focus more in this themselves, because you really can't keep adding in features for everyone as the tool soon becomes more complicated than easy to use.  Frankly I don't find memoQ any easier to use at all and I've been using it since version 4.  What I have seen is increasing complexity as the interface has become more and more cluttered, partly because of features that might be better of being optional.

But your points are all noted.

Thank you.

Paul

Hello Dan,

Unknown said:

Can we have the people responsible on here so that I have somebody other than Paul to whom l can give a piece of my mind?

Looks like you struck out and got me... although you can rest assured that posting it in here means you have got the attention of the right people (if I'm not ;-))

Unknown said:

As usual I was asked to select five languages and as usual I found myself asking why. Why can't the software pick out the five languages I had selected for 2015 and 2014 and offer me a choice, a button saying "Use existing languages?"?

I certainly agree with you here and we should be asking when you start the installation process if you are upgrading and if you want to use the same languages you used before... or something like this as part of an upgrade/migration process.  That on its own doesn't sound too complicated to me, although I'd prefer to see a more comprehensive approach that would definitely not be trivial work.  I know the focus next year is likely to be on the "little" things like this so maybe your timing is right.  We'll see.

Unknown said:

I want functionality that directly improves my efficiency and part of that is a streamlined interface that requires me to make as few clicks as possible. I have seen no progress on that front in Studio over two generations of product. The five languages issue is an excellent example.

I don't really agree with you here Dan.  Not completely anyway.  You are referring to a one off task when you install the product or some updates... not exactly something that affects you daily.  Irritating at worst I agree, but hardly affecting users more than that.  On the other hand I think the improvements in the interface and through the opportunities afforded by the APIs we have seen many ways to work that save considerable time for all sorts of things.

Unknown said:

Another is creation of termbases: why can't I just have the option of a one-click process that creates a new termbase immediately and without having to deal with the lumbering time-sink that is Multiterm? One button in the Studio interface saying "Create based on existing termbase". I click on it, it pops up a list right under the cursor of the ten most recently used termbases, saying "Select termbase to use as template". I click on my main termbase. Done, new termbase created.

A prime example would be the glossary plugin.  Have you tried that?  Almost a one click termbase creation if you want it.  Scroll down a bit in this article:

https://multifarious.filkin.com/2015/12/09/feature-rich/

Having said that... how often do you create a completely new termbase?  You can also do that anyway from within Studio even if it does use the MultiTerm Wizard.  It is a bit clicky and seems to stop at unnecessary windows as well as not having a finish button if you know you don't want to change the definition.

Unknown said:

There is more to productivity than flashy new suggestion technology. You've spent some time on the shiny new toys in 2017 and yes, I like those too, but you really need to spend some time on the boring functions that are the bread and butter of translation. You need to LOOK at how freelancers, as well as LSPs, use the software in daily life.

Of course we know this Dan.  We have run workshops with Freelancers, LSPs, Corporates in the past to gather feedback for the tools.  In fact last month we did this again in great details covering the needs of new users and more experienced users to help guide what we do in 2017 and onwards.  Some of the people on this forum might even be able to share their views of those workshops if they read this.

Unknown said:

Printing isn't sexy, but when you want to proof-read a translation on paper with a deadline looming, being immediately able to print only the segments that you need is a huge benefit. I find myself tempted to skip a vital QA step because Studio makes it so hard to isolate and print 30 segments out of 700. That's a serious issue for me. SDL clearly couldn't care less.

I'd agree here too.  You can workaround this easily enough if you are familiar with some of the tools like the SDLXLIFF Toolkit for example, or if you export to Excel and just filter out what you don't need to see, but it would clearly be better to have an export to Word feature that could just take segments you wanted based on some condition.  Probably not hard to do either... would be a neat batch task.

Unknown said:

Your market position is not secure and, by failing to address longstanding issues like these, you are allowing goodwill to erode.

I think we all know where you're coming from Dan.  Your usecases are one thing, not everything, but an important thing that we do need to consider.  It's hard to be all things to all men, but we are conscious of these requirements and have put in place an environment where it's possible for any developer to tackle many of these small things in isolation.  It also means we can address things in core development using the same mechanism, sometimes as an app and sometimes within the product.  I know you might say having to use apps is not right... but I would wholeheartedly disagree with that.  The ability to use apps is one thing that sets us apart, and I noted that even Kilgray are starting to mention their limited features to support this sort of thing, and will probably focus more in this themselves, because you really can't keep adding in features for everyone as the tool soon becomes more complicated than easy to use.  Frankly I don't find memoQ any easier to use at all and I've been using it since version 4.  What I have seen is increasing complexity as the interface has become more and more cluttered, partly because of features that might be better of being optional.

But your points are all noted.

Thank you.

Paul