Nicolas Racine 

It might be helpful to understand why you need to do this as there might be a another way to approach your need... however, why not create standard projects instead of using the single document approach?  If you use project templates these are really quick and will do all the things you seem to need (analysis etc.) in one go.  So it is a bit of a misnome that the single document approach is faster if you want to do anymore more than just look at the file in the editor and maybe translate with the same TM all the time.

But to answer your question specifically... no you cannot do that in the software.  But you could write a small script using PowerShell perhaps to allow you to select your project and then remove the suffix from your reports.  That would be faster at least.

Thank you for the reply.

I need to keep the original name because I am sending the analysis file to a translation portal that needs the file name IN the analysis file to be the same as the translated file.

The thing that bugs me the most is that a colleague that works in Studio 2022 does not have that problem. There is no adding languages at the end of the file name. This is why I thought There would be an option somewhere to do it.

I'll look into customizing a template. Thanks for the tip.

Best

Thank you for the reply.

I need to keep the original name because I am sending the analysis file to a translation portal that needs the file name IN the analysis file to be the same as the translated file.

The thing that bugs me the most is that a colleague that works in Studio 2022 does not have that problem. There is no adding languages at the end of the file name. This is why I thought There would be an option somewhere to do it.

I'll look into customizing a template. Thanks for the tip.

Best

Nicolas Racine 

Nicolas Racine said:

The thing that bugs me the most is that a colleague that works in Studio 2022 does not have that problem.

Are you sure he/she is also using the translate single document approach?

Yes. I saw it with my own eyes. The only explanation that makes sense is that RWS change the handling of file name in Studio 2024.

I looked into using a custom template. Maybe I haven't looked enough, but I did not see an option to use the original folder as location folder. You have to specify a path. That's a deal breaker for me.

Nicolas Racine 

Well... you raised my curiosity so I tested in 2024 and then an older version of Studio (2022 in fact...):

The only differences are the guids which I'd expect.  The file names are all exactly the same.

So then I created a proper project instead:

Exactly what you're looking for.  So I do think your colleague must have been using a standard Studio project and not a single file project.  I believe this naming convention has been there since Studio 2009.

Nicolas Racine 

Nicolas Racine said:

I did not see an option to use the original folder as location folder. You have to specify a path.

True... but I wouldn't see this as a dealbreaker.  I think it all depends on how you work.  For example, if you copy the path to the folder where your source file is before you start it's a trivial exercise:

You also get the benefits of doing all your files in one project when you do get them.  You could even change the path in the project template if that is helpful at all?  Although probably not as useful as the path copy... which I have seen many Project Managers and Localization Engineers doing all the time when they have to spend all day creating projects:

I don't know what to tell you... I saw her do it. I'll check back on Monday.

Yeah, I know about all that.

The thing is I am not a freelancer. I work for a big company. Every file I translate can be saved on one of about 25 different paths on a server. To me, copy-pasting the file path for each project is much more annoying than changing the file name in the analysis report, so that's a dealbreaker.

Thanks for trying, though, I appreciate it!