Probability score: 0.4  

Question improvement suggestion: Provide more details about the specific requirements for translating .razor and .cs files, such as whether the client has specific formatting or content needs.  

In the meantime, based on the information you have provided, here is a suggested answer to your question:  

Hello Aurélie,  

Step 1: Understand that Trados Studio is primarily designed for translating common file types like .docx, .pptx, and .xliff. Unfortunately, it does not natively support .razor and .cs files, which are typically used for web applications and C# programming, respectively.  

Step 2: If your client requires translation of these file types, you may need to consider alternative methods. One option is to convert these files into a format that Trados Studio can handle, such as plain text or XML.  

Step 3: You could also explore using a custom file type configuration in Trados Studio, but this may require some technical expertise to set up correctly.  

Step 4: If the translation involves a significant amount of code or technical content, it might be beneficial to consult with RWS Professional Services for a tailored solution.  

I hope this answer addressed your question. If not, please reject the answer, add the question improvement suggestion information, and click the RWS Community AI checkbox on the right to try again.  

RWS Community AI

 Aurélie Machut 

.razor and .cs files are not XML-based.

• .cs files: These are C# source code files.  They contain C# syntax, not XML.

• .razor files: These are Razor component files used in Blazor/ASP.NET Core.  They mix HTML markup with C# code, but again, not XML.

They are not usually translated.  They are implementation files in a software project.  If you see text in them (labels, messages, UI strings), best practice is to extract those into resource files (.resx) or another localisation framework.  Translating the .razor or .cs files directly could break the build.

So if your client is asking you to translate them I would ask your client what specifically they want translated in the file so you know exactly what can be translated and what should not.  Only then will you be able to see whether you can handle them with some regex based filetype perhaps.  But as I mentioned... it would be better for your client to extract translatable content into proper resource files.

Hello Paul , thanks for your quick answer. I’ll check that with my client. 

Doing some research, I was wondering if Passolo could help. What do you think?

Thanks, Aurélie 

 Aurélie Machut 

Passolo is not designed to handle .razor or .cs files directly.

• These files are source code. Translating them in Passolo would risk corrupting the logic.
• The intended workflow is to externalise localisable strings into resource files (.resx in .NET projects). Passolo has a .NET parser that works with .resx, .dll, or .exe resources and is well-suited for that. But if you get proper resources files you could handle them in Trados Studio anyway.
• Any text left directly inside .razor or .cs is not meant for translation. Developers should move it into resources before localisation

Hello Paul , this answers my question, thanks!