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:
comes with disadvantages.
Same for memoQ xliff files. Maybe the simplest way would be to implement the locked file feature in CT. Sometimes I need to put something into a segment that should not be added to the TM (but without leaving the segment unlocked, unconfirmed or empty).
>Maybe the simplest way would be to implement the locked file feature in CT.
Perhaps. Anyway, it'd be useful to have such a feature in CafeTran (to be able to completely lock segments).
It's extremely quiet in this 'discussion', though the topic must be relevant to more translators, having to deal with pre-translated Studio projects ...
Let me add this question: What to do with locked segments regarding the updating of the memory?
I'm beginning to think that it's wise to not commit locked segments to your clean memory, in order to avoid polluting it with badly, pre-translated but locked content.
How about you?
What's your input on this major topic?
One important observation:
CafeTran treated locked segments in SDLXLIFF and in MQXLIFF projects differently:
treated = treats
Both sdlxliff and mqxliff are not CafeTran projects so the control over whether to lock or unlock a specific segment is in their respective tools by project managers. If they wish to lock some segments, they have a reason for it. I don't think CafeTran (or a translator) should or could tinker with the "locked" property. It would defeat the locking purpose.
Sdlxliff locked segments are skipped by default via Action > Skip > Locked segments.
Igor, thanks for responding. But you are missing a lot of points in my argumentation here.
First. Different treatment of the same phenomenon. Locked segments are displayed/not displayed, depending on the originating CAT tool.
This is not consistent.
Secondly: how to prevent commitment of locked segments to your own memory.
I don't have any problem with PMs locking segments. But I don't want to see them (preferably) at all–so that I don't have to be annoyed by their quality. And if I cannot deactivate the display of them, then at least I don't want to have them imported into my own memory.
This is currently only possible via many work-arounds.
So yes, I'd prefer the MQXLIFF approach. If I'm not mistaken, at one time it used to be so with SDLXLIFF too. Probably some other user requested to make them visible ;).
Tough decision, but one that has to be taken. Hence my request to other users of CafeTran to participate. Before you start coding around again.
I don't think that consistency in display of the locked segments between files from other tools is a such a big issue. You don't need to bother about the locked segments and their addition to your TM if you don't change Action > Skip > Locked segments option. They are jumped over so the memory is not affected by them as you move from segment to segment.
Yes, but I'm in the habit of sending all segments to the memory at the end of the project. Because I use to make modifications to prior segments as I go along and do the QAs only once I've finished the last segment.
Is my workflow so exotic?
Then excluding locked segments from Project to TMX memory conversion sounds like a sensible solution. It should be be available in the next update.
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.