Start a new topic

DISCUSS: Locked segments in Studio projects

Perhaps we can discuss the modified handling of locked segments in Studio projects.

Is everybody happy with the current implementation?

Personally, especially for working in garbage projects, I'd like the be able to F/R in locked segments too, so that there would be needed a switch 'Deactivate locking', or so.

I now have to deal with projects that are partially pre-translated by the client and that contain lots of typos etc. -- of course in locked segments.

How to deal with them?

In the past, I could just replace them. Open the project in Studio, remove all target segments (incl. the locked once) and deliver the client a project that contained corrected locked segments--without them paying for them ;).

This is no longer possible.

Again, I can see the big advantages of CafeTran not handling locked segments. And I don't put my head under the table so I have seen the requests for it. But as our great soccer player JC (not the one with the beard, from Nazareth) always said:

Every advantage,

comes with disadvantages.


I haven’t tested this yet, but I was wondering if it perhaps is better to replace locked=“true” with locked=“false” or locked=“”, in order to be able to restore the locked attribute, once you’ve finished the project in CafeTran.

You see, Mario?

...Nobody else here in need for a feature to unlock segments in Studio projects?

Add me to the list.

1 person likes this

Maybe you should post it more prominently in the Requests section.

Nobody else here in need for a feature to unlock segments in Studio projects?

Ah, OK, thanks, my mistake, I assumed the grey colour indicated locked segments.


Yes, there is a red "L" displayed in the segments grid.

Ah, ok, that may well be it. So is there a marker for locked segments in CT?


Perhaps they are not set locked, but just pre-translated with 100% exact matches by you client? Try Skip > Checked segments to see if they are omitted.

I'm just translating a Studio project in CT, and the lock doesn't seem to work - grey segments (which I assume means thes are locked?) are treated just like any other segment.
(Action -> Skip -> Locked segmetns is ticked).

This is verry inconvenient when you're pounding through a file at top speed and belatedly realise that you've edited locked segments (which I'm a) not paid for and b) isn't what the customer wants).
I don't understand why this is possible. Surely that's the point of locked segments?


the possibility to lock segments in CT would be great, a good solution for the auto propagation problem, for example. It would also be great if we could hide/filter out the locked segments (locked by PMs) in Studio projects. When revising the file I would be glad to be able to hide all segments I don't need to look at, sometimes pages and pages of locked segments and you have to find the segments you have translated in the middle of those. Is there a solution or a workaround?


There currently is a strange behaviour. It used to be better some months ago.

Now: when I click on a locked segment, that is on the small grey square with the segment number, CafeTran takes me to another segment. I cannot enter the segment, not even when Skip > Locked is disabled.

There's absolutely no way to change the locked segments. In the past I was able to do this and used it a lot. I cannot change the content via direct editing nor via F/R.

Two things:

I had the Action>Skip>Locked segments active. This means that segments are being searched, but not clickable in the grid to load the segment into the target editor (and if I am not mistaken, there is no visible indication for this, only after filtering at least a bit). If you are not figuring out what is going on, you might get nuts. This means I am able to edit locked segments (Action>Skip>Locked segments inactive), but segments are going to the TM, or I am unable to edit locked segments (Action>Skip>Locked segments active), while segments are kept away from the TM. Perhaps it would make sense to assign a shortcut to do a faster switch (or a button).

There might be different reasons to lock a segment. However, when the client tells me that term A should be replaced by term B and a whole bulk of segments with term A is locked, I have a problem with mqxliff files (if unable to do this in memoQ).
Nice, but indeed having a "locked segment" feature in CT would be nice. I am thinking of the following use cases:
files with single segments that shall remain in the source language, while making them invisible in Word is no option (too few segments, other file format than Word) - examples are localzations where some titles, button names etc. remain in the source language, adresses and/or departement/function names such as "Head of development".
working in a project with many repetitions, where single repeated segments need different translation and where switching off auto-propagate is not an option

What about this?


Then excluding locked segments from Project to TMX memory conversion sounds like a sensible solution. It should be be available in the next update.

1 person likes this
Login to post a comment