Adendum: to insert a new term *ctrl + F2*

Hello Wolfgang HULLMANN,

Would it be possible for you to post a screen recording, so we can see exactly what is happening and try and replicate this.

The following is a free tool and ideal for this- https://www.screentogif.com/

Thank you for your proposal, Steven, though I'm not quite sure what - apart from my keyboard strokes I described in my initial massage - you may infer from recording the same. Or is there anything I misunderstand as to the usefulness of such recording?
In short, these two actions are carried out in the target segment/editor window although they are destined to be done in the terminology window within Studio, whatever the xcliff file I'm working on.

Wolfgang HULLMANN,

Interesting. I can replicate both. CTRL+Pos1 is usually "go to first position in file", while Pos1 is usually "go to first position of current line". Interestingly, CTRL+End takes you to the last character of a multi-line field in MultiTerm, but CTRL+Pos1 is not captured by the Terminology view and is interpreted by the editor view. This looks like a bug to me.

What behavior would you expect of Shift+Enter in the Terminology View? It does not have an assigned function in MultiTerm.

(I am using the most current versions of Studio 2021 and MultiTerm.)

Daniel

Daniel, I can tell you what really happens when I do Shift+Enter in the Terminology View: again the cursor is activated in the Editor and inserts a conditional line break in the activated target segment. So, the interference between Editor and Terminology view concerns several key strokes. As said, this does *not* apply to MultiTerm itself, which appears to be logical as it is not directly linked to Studio.

A somewhat strange workaround is to place the cursor in the source segment and then do said things in the Terminology View, as no changes can be made to this part of Studio unless "Modify source" has been selected.

Wolfgang HULLMANN

Why would you press Shift+Enter in the terminology view in the first place?

Daniel

For the same reason as in any other text: to separate paragraphs from one another (here: when copying or writing exemple sentences to show usage of a term).

Wolfgang HULLMANN

A simple return will do that. I don't think these fields can distinguish a line break from a paragraph break. That's a feature of a text processor like Word. These fields are plain text fields. A return inserts a cr/lf.

Daniel

No, sorry. A simple return has always - as far as I can think back (to Studio 2015) - served as a command to close the active field and to open/activate a deactivated/closed field (to write/copy somtething into it) within the Term View window as well as in MultiTerm, by the way. That is why a simple return doesn't insert anything. Try it out.

Wolfgang HULLMANN I think this is why asked you to record a video: I can't confirm the behavior you are reporting. MultiTerm has different types of fields, but in those where you could enter several lines (multi line text fields), a simple return will do.

Daniel