• State Suggested Answer
  • Replies 14 replies
  • Answers 5 answers
  • Subscribers 432 subscribers
  • Views 13366 views
  • Users 0 members are here
Options
Related

Navigation: Move to Next/Previous Segment

Michael Friedli

Good morning All,

I am using the current version of Studio 2015, but I have been aware of this issue on previous versions too:

My Keyboard Short-cuts are set to the default for:

Move to Next Segment: Ctrl+Down

Move to Previous Segment: Ctrl+Up

However the actual effect of these short-cut keys is consistent with the Up and Down "Go To" arrows in the ribbon, which appear to default to the next unconfirmed segment in either direction.

Is there a "one-at-a-time" step available?

Incidentally, I have always wondered what "Focus Next/Previous Row" is for perhaps it could be changed to a simple one segment up/down move?
Rate translation
×
Suggest better translation
×
Moderator UI
×
  • Get AI Suggestion
Parents
  • 0

    Hello Michael,

    Unknown said:
    Is there a "one-at-a-time" step available?

    I don't really understand this question. The arrows and the shortcuts you mention are exactly the same thing and they are one at a time step.  I can only think I'm completely misunderstanding what you are asking here?

    Unknown said:
    I have always wondered what "Focus Next/Previous Row" is for perhaps it could be changed to a simple one segment up/down move?

    This is to allow you to select segments using only the keyboard.

    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

  • 0 in reply to Paul
    Hi Paul,
    I have checked the GoTo settings - none of the check boxes are enabled, so I assume the behaviour I get is the default
    Ctrl+down (same as ribbon down arrow) goes to the next untranslated segment (skipping confirmed segments)
    Likewise Ctrl+up
    The up/down arrows on their own move a line at a time.
    As far as I can see, when a segment is "focused" it isn't selected, as the one before stays selected (shaded blue).
    What I am looking at, is the keystroke combination that selects the next segment (regardless of which line in a segment the cursor is and regardless of the status of the next segment (draft, confirmed, untranslated etc.) as one does when running through a translation to check it. This would be analogous to clicking in it with the mouse.
    Perhaps I should have said "one segment at a time"...
    As far as I can recall it has always been this way.
    Thanks!
  • 0 in reply to Michael Friedli

    Michael

    What about CTRL-ALT-Enter? This goes to the next segment. And if you prefer Studio to always go to the next segment instead of the "next unconfirmed" - as I do - simply exchange these two shortcuts (CTRL-Enter and CTRL-ALT-Enter) in "File - Options - Keyboard Shortcuts".

    Unknown said:
    As far as I can recall it has always been this way.

    Michael

    No, these settings have not changed since Studio came out (2009).

    Walter
  • 0 in reply to Walter Blaser

    Thank you Walter,

    I think that is what I meant - about settings unchanged.

    I suppose there is no reason not "re-confirm" and move to the next segment (Alt+Enter the way I have it).

    Just for the record, these are my settings:

    The reason for my question was that the "Move to" shortcuts don't say anything about segment status.

    All the best
  • 0 in reply to Michael Friedli

    Unknown said:

    The reason for my question was that the "Move to" shortcuts don't say anything about segment status.

    Michael

    If it is not specified, it means that the segment status does not matter, i.e. "Move to next segment" means exactly what it says, it moves the cursor to the next segment, irrespective of the status this segment has. 

    Sorry, but I am missing what your exact problem is here.

    Walter
  • 0 in reply to Walter Blaser

    Thank you for taking the time to reply Walter

    Unknown said:
    Move to next segment" means exactly what it says, it moves the cursor to the next segment, irrespective of the status this segment has. 

    That is exactly what I would expect and what does not happen when I do it - it jumps to the next unconfirmed segment.

    Unknown said:
    Sorry, but I am missing what your exact problem is here.

    Not really a problem, just trying to understand what is going on.

    Best
  • 0 in reply to Michael Friedli

    Unknown said:
    That is exactly what I would expect and what does not happen when I do it - it jumps to the next unconfirmed segment.

    Hi Michael,

    Have you checked the actual keyboard shortcuts you have for this feature?  Perhaps there is some conflict causing an unusual effect... maybe some 3rd party software you have running at the same time that you could switch off to test again?

    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

  • 0 in reply to Paul
    Hi Paul,
    Thanks for the suggestion, just had a look in Task Manager, I still get this behaviour when Studio is the only app running - the list of background processes is huge, not sure what to look for. It is a Lenovo PC which has quite a lot of their bloatware, but I had exactly the same behaviour on my previous 5-year old Dell machine.
    I just checked in Word, behaviour is normal:
    Ctrl+Down = moves the cursor to the beginning of the next paragraph
    Ctrl+Up = moves the cursor to the beginning of the current paragraph
    In this field (my browser is Firefox):
    Ctrl+Down = moves the cursor to the end of the line
    Ctrl+Up = moves the cursor to the beginning of the line
    I guess it will remain one of life's (and Studio's) many mysteries ;)
    Best
  • 0 in reply to Michael Friedli

    Hi all

    Just checked what happens on my Studio 2015 SR1:

    - CTRL-arrow down and CTRL-arrow up does in fact move to the next unconfirmed segment.

    This seems to be the default behaviour as I have not changed any of these shortcuts.

    I did not mention this before because, frankly, I never use this shortcut.

    Walter
  • 0 in reply to Paul

    It looks to me like you didn't understand Michael's problem. I found this thread because I have exactly the same problem, and Walter, below, has the same problem too. When we're revising our translation, we sometimes want to move to the next segment, since we've read the current segment and are happy with it and don't have any changes to make. 

    (Using Studio 2017) In the list of keyboard shortcuts, there's one called "Move to next segment". It does not say "Move to next unconfirmed segment". So one would expect it to move to the very next segment, irrespective of its status. It does not. It moves to the next unconfirmed segment. Even if you don't create a feature enabling us to move to the next segment, I think at the very least you should rename "Move to next segment" as "Move to next unconfirmed segment".

    This would bring it in line with the distinction made between "Confirm and move to next segment" and "Confirm and move to next unconfirmed segment".

    On a related note, is there a better workflow for revising my translations? In MemoQ, I would set my status to "Reviser 1", then I could include "Confirmed by Translator" as one of the "go to" statuses. In Studio, at the moment, I simply revise the translation a only change the row status if I make a change. But it's not ideal if I don't finish the revision in one go, as I have nothing to tell me which rows I've revised and which I haven't. If I have a particularly long revision, I change all the statuses to draft and confirm them all again as I work through the document. But this isn't ideal either, as it means I don't see which rows I didn't confirm (perhaps because I was trying to solve a query) during my first draft.
  • 0 in reply to Timothy Barton

    Timothy Barton said:
    It looks to me like you didn't understand Michael's problem.

    I don't see where I misunderstood the problem... but as this is 5-yrs old now I don't remember what I experienced when using this feature at the time.

    Having said this I have just tested this in 2021 (I'm not wasting time with 2017 as it's too old anyway) and the behaviour is the same and I can reproduce it.

    Timothy Barton said:
    In the list of keyboard shortcuts, there's one called "Move to next segment". It does not say "Move to next unconfirmed segment". So one would expect it to move to the very next segment, irrespective of its status. It does not. It moves to the next unconfirmed segment. Even if you don't create a feature enabling us to move to the next segment, I think at the very least you should rename "Move to next segment" as "Move to next unconfirmed segment".

    I completely agree with you.  I'll suggest this.

    In the meantime perhaps you can use the solution I use for this using AHK:

    https://community.sdl.com/product-groups/translationproductivity/f/autohotkey/13184/move-from-segment-to-segment

    Timothy Barton said:
    On a related note, is there a better workflow for revising my translations? In MemoQ, I would set my status to "Reviser 1", then I could include "Confirmed by Translator" as one of the "go to" statuses. In Studio, at the moment, I simply revise the translation a only change the row status if I make a change. But it's not ideal if I don't finish the revision in one go, as I have nothing to tell me which rows I've revised and which I haven't.

    Why don't you open the files for revision instead of for translation?  Or even open for sign-off.  Each of these uses a different status  when you confirm so you always know where you got to.  No point trying to "force" Studio to work the way you did in a different tool.  Makes sense to learn how to use this one.

    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

    Thanks. I'm not trying to force Studio to work like in MemoQ. It was just to clarify what I was trying to achieve (a way to distinguish between first draft and second draft). I'll use "open for review" next time.
Reply Children
No Data