• State Verified Answer
  • Replies 24 replies
  • Answers 1 answer
  • Subscribers 77 subscribers
  • Views 20090 views
  • Users 0 members are here
Options
Related

Script for changing segment status

Eva Repolusk-Stoppel

Inspired by Paul's recent blog post, I've just tried for over an hour to create a script to change the segment status. Specifically, I want to be able to assign the status "Translation Approved" and "Translation Rejected" via keyboard shortcuts while I'm in "Translation" mode in the Editor.

I consulted the AHK documentation and watched a couple of tutorials and found that what I'm trying to do should be easy enough - just two mouse clicks, first on "Change Segment Status", then on the respective status. Figuring out the absolute cursor positions on my screen was also easy using "Active Window Info".

So the script below is supposed to assign "Translation Approved" in the maximized Editor window on a 27'' screen when I press Ctrl + Win key + q. But unfortunately, it doesn't. It clicks on "Change Segment Status", but then it stops without clicking on the status. Can anybody see or guess what I've done wrong here?

Thanks in advance!

Eva

;Studio 2017: Change Segment Status > Translation Approved (find absolute mouse cursor position using "Active Window Info" in AHK's program folder)
^#q::click 1346 108
click 1346 218
ExitApp
Rate translation
×
Suggest better translation
×
  • 0 in reply to Eva Repolusk-Stoppel

    Unknown said:
    Therefore, I use different statuses to indicate to the proofreaders the degree to which changes are allowed.

    "Translation Rejected" means "I did it, feel free to improve the text as much as you can."
    "Translated" means "edit with care, because there is some terminology and jargon there, but also some questionable grammar on my part."
    "Translation Approved" means "keep off, it's a full quote, even if you don't like it."

    That's really interesting Eva, I wonder how many other people work in this way.  Coming back to your problem, perhaps you have a good solution now by using AHK to enhance the app.  Shortcuts in the app for the statuses you want and then the move to next segment addition afterwards.  Maybe you could have one shortcut to do this but bring up a choice of the three options you need via AHK that you can quickly select?

    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

  • 0 in reply to Paul

    Unknown said:

     

    Coming back to your problem, perhaps you have a good solution now by using AHK to enhance the app.  Shortcuts in the app for the statuses you want and then the move to next segment addition afterwards.
     

    You can do this by using a tilde, for example, assuming I have Ctrl+Y set up in the app as the shortcut for Change status to Translation Approved:

    ~^y::
    Send {down}
    return

    Using the tilde in the hotkey will send the original functionality of the hotkey and then do whatever else is in the script.
  • 0 in reply to Paul
    I don't really expect anyone else to work this way because it is very inefficient, but neither the client nor I could find somebody with the required subject matter expertise AND the correct language combination. So the idea is that while I'm doing those translations, at the same time, I train the native speaking proofreaders to eventually do the translations. That way they can develop a feeling for how little is actually translated and how much is taken from standards and guidline documents. But that really is a very special situation which is not necessarily representative for other clients.

    I'm pretty happy with my solution now, although I haven't reality tested yet. Of course, Nora is totally right with everything she said about generalizing the script for other users and different hardware, but personally, I don't need that.

    I think only one shortcut with a choice would be possible, but actually involve more pressing of buttons. However, I'm very much waiting for and looking forward to the "highlight color" function I requested on the ideas page and that Daniel Brockmann said is in the making. It will be very helpful, also for other clients, to be able to highlight words and phrases in different colors while translating.

    For example:
    Blue - I was just guessing here, a software engineer has to look up that command for me in the translated GUI
    Green - can a marketing person please figure out which of three different spellings for that function you want?
    Red - I think there is a mistake in the source text, that's why I didn't translate what it said there. I guess it's okay in the target, but you should let the author know so he can fix it.

    etc.