• State Suggested Answer
  • Replies 2 replies
  • Answers 1 answer
  • Subscribers 432 subscribers
  • Views 1697 views
  • Users 0 members are here
Options
Related

Numbers being automatically substituted in target segment in Translation Results window is very confusing.

Lieven Lannoo

Hi,

I don't think this was the case in Studio 2014 (never used 2015), but numbers are now being automatically substituted in the target segment in the Translation Results window. It's great that Studio automatically replaces elements such as numbers in the main window, but it's very confusing if the same thing happens in the Translation Results window. It seems to me to make more sense for the original source and target segments to be displayed in the Translation Results window. Now, those source and target segments don't match anymore...

When Studio then doesn't get the decimal and thousand separators right, I always want to edit the target segment in the TM, only to notice that that target segment is actually correct, as shown in the screenshot.   

I'm not sure why this was changed, but it would seem to me to make more sense just to show the original source and target segments (as-is) in the Translation Results window.

Best regards,

Lieven
Rate translation
×
Suggest better translation
×
Moderator UI
×
  • Get AI Suggestion
Parents
  • 0

    Hello Lieven,

    I didn't understand this at first but now I get it (click for a better view):

    On reflection I'm with you.  I think changing just the target and not the source in the TM results pane does seem a little confusing.  I think I preferred it as it was in 2014... although I didn't even realise this had changed until you pointed it out!  I tested 2015 and this was the same as in 2014 so this is a new thing.

    I'll raise this and see whether it was actually intentional or we need to fix something.

    Thanks for posting your find.

    Regards

    Paul

    Paul Filkin | RWS Group

    ________________________
    Design your own training!
    You've done the courses and still need to go a little further, or still not clear? 
    Tell us what you need in our Community Solutions Hub

  • Former Member
    0 Former Member in reply to Paul
    Oh, I would like to put in my input! I was testing 2017 as well and noticed this. But I thought it was part of the fuzzy repair function. I personally didn't like it, and agree with Lieven's suggestion to leave the TM results as it is in the TM. The decimal commas was also 'hit and miss' when it did it correctly. I couldn't find any consistency or reason why it worked on one, but not the other. In fact, it would do decimal comma/point within the same segment.
    Great question! I thought it was just me!
    Best, Mindy
Reply
  • Former Member
    0 Former Member in reply to Paul
    Oh, I would like to put in my input! I was testing 2017 as well and noticed this. But I thought it was part of the fuzzy repair function. I personally didn't like it, and agree with Lieven's suggestion to leave the TM results as it is in the TM. The decimal commas was also 'hit and miss' when it did it correctly. I couldn't find any consistency or reason why it worked on one, but not the other. In fact, it would do decimal comma/point within the same segment.
    Great question! I thought it was just me!
    Best, Mindy
Children
No Data