Daniel McCosh

I believe this changed around a year ago and seems to be the way we work in 2019.  I'd forgotten about this as I rarely work with specific language pairs unless I'm testing something, but I'd agree with you that this isn't too helpful. I can't find anything in the release notes about this but Daniel Brockmann may be able to shed some light on this one and whether the old way of working in earlier versions will come back?

Hi - our usage analytics have told us that the vast majority of our users now work with the all language pairs view (which also accomodates single language pairs) and so in Studio 2019 we wanted to maximise the space for that UI rather than always showing the very rare exceptions on the main screen above. Perhaps down the line we could make this smarter and have a hyperlink to the changed language pairs, you could perhaps log an idea around that so we can track it for future? Thanks, Daniel

Thank you Paul and Daniel Brockmann for clarifying this. I agree that the current behavior is less confusing for the majority of users. I ran into this while standing in for an agency PM, I don't usually deal with so many languages.