Hello Paul,

when a translator places the cursor in the target segment of a "new" TU, he gets a CM match. The problem is that when he looks onto the reference window above the TU he sees a reference to, yes, the file he is working on. Since the TU has already been translated in an older document, he would expect to get a reference to that document to bolster his confidence in using that solution. Instead he has to copy the source text and via DtSearch find where the TU was originally translated. I have verified the translation and import of the older file, so we are at a loss why Studio doesn´t reveal where the solution originates from. This calls for extra research on the behalf of the translator, which should be unneccesary. Will attempt to put in a screenshot of older translated file as well.

Yes, it is, I wonder though if users can tweak their settings so as to overwrite original project settings? Where does one find these settings?

Hi Reynir Gunnlaugsson 

Many apologies for not noticing your earlier post in April!

Unknown said:

Yes, it is, I wonder though if users can tweak their settings so as to overwrite original project settings? Where does one find these settings?

Yes they can, and there's even an app to support this:

http://appstore.sdl.com/language/app/apply-studio-project-template/391/

However, I doubt this is the cause of your problem.  I'm wondering if you need to allow multiple values in your field holding the filename.  If you don't then when the translator confirms something in his own translation the field will be updated with the value of the current document.  perhaps this is the source of your problem?

Hello Paul,

as far as I can see, the memory already has that option picked.

The worrying part is that no relevant history of previous usage is portrayed. And why does concordance search not provide any results either?

Is there any merit to rumours saying that Studio does not handle well memories larger than approximately 400.000 segments ?