Kelly Edward said:

Trados has very nice tool called "RecordSourceTU" already.

I wish it worked right. Unfortunately it doesn't. With multiple files opened in one tab, it always adds the path/filename of the first file only even when I work on second, third, ... nth file.
Thank you for the script.

I've fixed the error of RecordSourceTU App,
Now, it records fileName correctly when you work with multiple files at the same time. 
-for version2017
-for version2021 

my idea to get a file name is pretty simple

it starts from current "ISegmentContainerNode"
and goes up until to attain "IFileContainerNode"

Where, You can extract the information you wanted "OriginalFilePath"
Done, piece of cake

Kelly Edward

Kelly Edward said:

I've fixed the error of RecordSourceTU App,

Out of curiosity did you submit a pull request with your changes so we can review and incorporate in the official version?  Or you are keeping your improvements to yourself?

I think this way is better one.

Here, I'm attaching the part I've changed from Yours, all of them.
So, Your professional(s) could review it easily, and (s)he could decide what to do (or not).
-say her(him) "Thank You for your efforts" please.

Attached:
modified_Part_All_Of_Them.zip

-ah, its variable names are written in my mother tongue though, it does not matter, it works well regardless of it.

Thanks. 

I think this way is better one.

Here, I'm attaching the part I've changed from Yours, all of them.
So, Your professional(s) could review it easily, and (s)he could decide what to do (or not).
-say her(him) "Thank You for your efforts" please.

Attached:
modified_Part_All_Of_Them.zip

-ah, its variable names are written in my mother tongue though, it does not matter, it works well regardless of it.

Thanks. 

Kelly Edward

Kelly Edward said:

I think this way is better one.

No, it's not a better way.  Github is designed for managing versioning and changes.  Manually working through your code outside of the source is definitely not easier.  All you need to do is create a pull request with your updated code.  That should be easier and we have a proper audit trail.

If you've written some of this in Korean that will also be a problem.

This is my best

Do not try to twist my arms

Regards

No arm twisting here Kelly Edward.  Just pointing out that we need a proper pull request to look at suggested changes and we will only work with code in English.  You don't have to provide your suggested improvements at all.

I did not suggest anything from the beginning.
I have anticipated this uncomfort situation from the beginning.
This happend always.

Bye.