Hello,

Based on your description, it seems like Trados Studio is not recognizing the translatable file in your project. Here are some steps you can take to resolve this issue:

Step 1: Check the File Format

Ensure that the file you're trying to translate is in a format that Trados Studio supports. Trados Studio supports a wide range of file types, including .docx, .xlsx, .pptx, .idml, .html, .xml, .sdlxliff, and many more.

Step 2: Verify the File Location

Make sure the file is located in the correct folder that you're selecting when creating the project. If the file is in a subfolder, Trados Studio might not be able to find it.

Step 3: Restart Trados Studio

Sometimes, a simple restart of the software can resolve minor glitches. Save your current progress, close Trados Studio, and reopen it.

Step 4: Recreate the Project

If the problem persists, the project you're trying to open might be corrupted or damaged and needs to be recreated. During the recreation, you can run the Pre-translate Files batch task using the Translation Memory that probably already contains the previously translated segments. Or you can run the batch task Apply Perfect Match and use the SDLXLIFF files from the target language folder of your original project.

Step 5: Add File Extension Exceptions

If you're using an antivirus or firewall, add file extension exceptions to your list to prevent the problem from reoccurring in the future. The extensions that need to be added are *.sdlppx, *.sdlproj, *.sdlrpx, *.ttp, *.wsxz, *.stppk, *.sdlxliff.

If none of these steps resolve your issue, it might be a more complex problem that requires further investigation.

Best regards,

RWS Community AI

I tried Steps 1 - 3. It's a .docx file, so Step 5 does not apply. Step 4 does not apply since I can't "recreate" a project that doesn't exist yet. I'm trying to start a NEW project.

I did find an error I made. I entered the name of the folder as "Space Travel," when it should have been "Space Travel Project." I fixed that error. 

Now I'm being tortured by another error message that tells me "Please specify an empty or non-existent folder."

First I was told there needed to be at least one translatable file; now I find out there shouldn't be any file in the folder.

I'd appreciate some more help! Thank you!

Kathleen Tunney 

I think I saw a post from you earlier after you discovered you need an empty folder to create a new project in.  Did I dream that or have you resolved this?

No, it's not resolved, and I'm about to bang my head against the desk. :-)

If I make the path D:\Studio 2022\Projects\Space Travel Project, Studio tells me I need a file in there (which I have, but Studio's not seeing it). If I make the path D:\Studio 2022\Projects, thinking Studio perhaps will pick up the project name from the entry for project name I filled out (Space Travel Project), I get the message that Studio wants an empty folder! 

Thanks for looking in here; I'm all ears if you have any ideas which stupid thing I'm doing (or not doing).

Kathleen Tunney 

I just sent you an email.  Join the meeting now and I may be able to help.

I'm very sorry, Paul. Thank you for all your effort. What complicates this is the fact that I'm using a brand new computer which has Windows 11 Professional. I'm coming from a machine where I used Linux for many years. So I'm trying to learn Windows at the same time as learning Trados Studio. It's a hot mess. Sorry.

I'm very sorry, Paul. Thank you for all your effort. What complicates this is the fact that I'm using a brand new computer which has Windows 11 Professional. I'm coming from a machine where I used Linux for many years. So I'm trying to learn Windows at the same time as learning Trados Studio. It's a hot mess. Sorry.

Paul,

The problem was solved in an unexpected way. I came across a suggestion to try System File Checker and sfc scannow. This process repaired some corrupted system files. Then everything worked just fine.

If I hadn't tried this suggestion, I'd still be pulling my hair out. Turns out it wasn't a Trados problem after all! Who knew?

Thanks again, 

Kathleen