• State Verified Answer
  • Replies 13 replies
  • Answers 2 answers
  • Subscribers 435 subscribers
  • Views 7012 views
  • Users 0 members are here
Options
Related

Project file "Last Changed" Time-Stamp is not correct

Shyam Gupta

Hello experts,

In the "detailed view" under the "List of project files" in Trados, the "Last changed" time-stamp for individual files doesn't seem to be correct.

For example, I have a project with 37 files, I worked on some of them on the 16.03.2017 and on some I worked on the 16th as well as on the 17.03.2017.

But the "Last changed" time-stamp on files which I definitely also edited on the 17.03.2017 is showing the wrong date and time (e.g. 16.03.2017 12:29:09).

 

How is the "Last changed" time-stamp updated in Trados?

I hope that it is "just" a time-stamp update issue and has no effect on the file contents update.

Kindly advice if I need to change any settings in Trados for correct time stamp.

 

By the way, I am using SDL Trados 2017.

Thanks and best regards

Shyam Gupta

 

 
Rate translation
×
Suggest better translation
×
Moderator UI
×
  • Get AI Suggestion
Parents
  • 0
    Hello Shyam,

    I'm not really sure what to suggest here... this isn't just the first time I've heard of this, it's also the first time I've ever seen anyone mention this view! This is clutching at straws really but maybe double check you saved your changes? Also keep an eye on it from now on and see whether you can identify when this timestamp is not refreshed.

    Can you also try opening one of the file where the timestamp has not changed and make a change,s ave it, see if the timestamp is updated?

    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
    Hello Paul,
    I reconfirmed as you sugeested.
    I opened an already existing and translated project file (with timestamp 16.03.2017 12:29.09),
    - added some random (dummy) text as change
    - executed "Save" (Speichern)
    - executed "Save target text under" (Zieltext speichern unter)
    - "Closed" (Schließen) file

    Alas, the timestamp in the detailed view is still 16.03.2017 12:29:09

    I reopened the file, the changes which I had made previously were right there. This means that the changes were made and saved correctly. Only the timestamp was not updated.

    As a double check, I removed the changes made above for test purposes, saved, closed the file. After reopening the file, one could see that the changes were gone as expected, but the timestamp remains unchanged.

    Paul, as long as the file contents are updated, I am not so much worried about the timestamp because I am an independent freelancer.
    But for someone working in a team or for an agency, this might be a problem.

    Having said that, I am not ruling out that there might be someting wrong with my Trados 2017 settings. But I don't know where to look for?

    Any advice from your side would be most welcome.

    Thanks and best regards
    Shyam
  • 0 in reply to Shyam Gupta
    Can you check the suggestion from Evzen too. After make the change and saving it please close Studio and restart it. If that doesn't help I wonder if this is a permissions thing? Try starting Studio as admin, so right-click and run as admin. See if this makes a difference?

    I don't think this is a general thing, at least at the moment the knowledge I have is it's 50:50 ;-) Works for me, not for you!

    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
    Hello Paul,

    Sorry, I had forgotten to mention in my last reply that I have also tried what Evezen had suggested.
    Anyway, I have repeated that but closing, reopening Studio doesn't seem to make any difference.

    I have now also tried - as you sueggested - working with Studio as Admin, but the result is the same.
    The timestamp is simply not budging!

    Unless you have another proposal, I might have to ask the customer on Monday to find out if their source files have something special.

    Thanks and best regards
    Shyam
  • 0 in reply to Shyam Gupta
    I doubt this has anything to do with the files. Can you try reinstalling Studio as administrator? So right-click and run the installer as admin.

    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
    I doubt this is a permission thing, otherwise it wouldn't save the changes in the first place, would it?
    I'm wondering if the actual PHYSICAL FILES change their timestamps or not... because this is a filesystem-driven operation, it has nothing to do with Studio. So... if the physical files are correctly timestamped, but the change does not propagate to Studio view, that would be one thing. And if the physical files are not properly timestamped (but still containing the changes), that would be a real mystery...
  • 0 in reply to Paul
    Hello Paul,

    As per your suggestion, I removed the project from the list, closed Studio, renamed (to disable) and reinstalled it as adminstrator.
    Logged-in the project again in Studio, opned file(s), stored, and closed files - the timestamp remains unchanged!

    My observation: The timestamp for all 37 project files is - but for a difference of 2 seconds- absolutly same.
    That timestamp matches the time when Jerzy Czopic hepled me with resetting the Studio on the 16.03.2017. The 2 seconds time difference between different files is probably the time it took the system to load the 37 project files.

    As a cross check, I have created another project today (18.03.2017 13:30.56) with three dummy MS-Word fies and loaded. The timestamp of all three is same. which is ok to start with.
    But even after editing, storing, closing the files, the timestamp remain unchanged to the last seconds digit.
    I tried the same after 10 minutes (within the same hour) and then after some time (in the next hour) - the timestamp remains unchanged.

    So, you are absolutely right, the problem has nothing to do with the customer's file.
    However, it seems to me that the term "Last Changed" in detailed summary might be misleading. It probably is the the timestamp when the file(s) were first loaded with the project and never changes thereafter.

    If it is working for you but not for me then it could be that there is an undocumented difference in Studio features depending upon the license type. I am using Single user, Studio 2017 freelancer license.
    Did you confirm on your side also using a similar license ?

    Looking forward to your advice.

    Thanks and best regards
    Shyam
  • 0 in reply to Shyam Gupta
    While I have never checked the timestamp within Studio, I've been seeing this with target files recently. After generating the target file and immediately going to the folder where it was saved, the file won't show at the top of the list when sorting by Date Modified, and I usually have to find it by name.

    For Word files, for example, if I simply open the file in Word and then close it, the timestamp gets updated. I hadn't given this much thought, as it doesn't cause any major problems beyond being a minor inconvenience, but I found this thread interesting, and will start monitoring when this happens. I know it doesn't happen all the time, but I definitely know it happens on both the Professional and the Freelance version of Studio, as I use both and have seen it happen with both. It's also probably not filetype-related, as I had this happen as recently as last night with an xlf file, and see it often with Word files.
  • 0 in reply to Nora Díaz
    Looks like it has something to do with the multiple different NTFS timestamps (see superuser.com/.../how-can-i-display-all-8-ntfs-timestamps).
    This needs to be clarified by developement - which timestamp exactly they manipulate when saving files and which they read to display in the view. (And it could be also some glitch in the underlying .NET Framework)
  • 0 in reply to Evzen Polenka
    Hello Paul,
    just curious to know about the Status of the issue from SDL side.
    Is this issue now being followed up internally with the SDL engineering team or...

    Would be thankful to you for a Brief update please.
    Best regards
    Shyam
Reply Children