• State Suggested Answer
  • Replies 3 replies
  • Answers 1 answer
  • Subscribers 433 subscribers
  • Views 1975 views
  • Users 0 members are here
Options
Related

TRANSLATING SPECIFIC TXT FILES IN STUDIO 2019

Frederic Garcia

Dear All,

I hope someone will be able to help me.

We translate some specific TXT files for one of our customer, they look like this:

Screenshot of a TXT file opened in Trados Studio 2017 with columns separated by triple slashes. Column 2 is correctly displayed for translation.

The customer cannot send the files for translation in another format. It is an export from their tool.

"(///)" are separators for the different columns of the file.

So as to translate the text contained in column 2, we were used to creating a specific filetype in Studio 2017 and it worked perfectly (only the content of column 2 was displayed in Studio).

Here is the process:

Options > Filetypes > Create a new filetype > Simple delimited text.

Then we specified a specific generic expression (for instance, "CLIENT.txt" to be applied too to the file names for translation) and we indicated in the Format window the followings parameters:

Separators: (///)

Column to be translated : 2

Column for source text : 2

Minimum number of columns : 1

And the files opened perfectly in Studio 2017, see below:

Screenshot of Trados Studio 2019 showing a side-by-side comparison of source and target text. The text is correctly aligned with column 2 highlighted for translation.

Now in Studio 2019, if I make the same steps (creation of a filetype using the same process or import of the setting from Studio 2017), the file do not open correctly and I do not know why, see below:

Screenshot of a TXT file opened in Trados Studio 2019 with misaligned columns. The text from column 2 is not isolated for translation, indicating an error in file type settings.

Let me know if you have any suggestion for me to translate these TXT files correctly in Studio 2019!

Rachel

Generated Image Alt-Text
[edited by: Trados AI at 5:36 AM (GMT 0) on 29 Feb 2024]
emoji
Rate translation
×
Suggest better translation
×
Moderator UI
×
  • Get AI Suggestion
Parents
  • 0

    @

    A few things to check.

    1.  In 2017 under Files view you can clarify what the name of the file type it is that you are using.
    Mine is just an example

    Trados Studio Files view showing a file named 'NumVer3.docx.sdlxliff' with file type identifier 'SDLXLIFF 1.01.0.0.0'.
    Please ensure it is this file type that you are exporting then importing.

    2. The in  2019 under Files view please clarify what the file type name is as I assume it may not be what you see in 2017.
    Which the leads me to point number 3

    3. In 2019, ensure that this file type is correct listed under File - Options - File Types and that no overlapping/duplicate extensions are taking priority
    In my case I have 2 txt file types and it could be the wrong one is being used at the time of file processing
    FYI: The one on top will always take priority

    Trados Studio File Types options showing a list with 'Tab Delimited Text', 'Text', 'Java Resources', and 'Portable Object' file types.

    4. Which takes me to my last point, how are your files being opened?
    Via Single Document or via a project template?

    If via a project template you will need to take care that point 2 is reviewed carefully and your template in 2019 may not have the correct file type support.

    I trust these 4  points will help you source the root issue. If not please update post so I can help further

    Lyds 

     

    Oana Nagy | Developer Experience | QA Engineer | RWS Group

    emoji


    Generated Image Alt-Text
    [edited by: Trados AI at 5:37 AM (GMT 0) on 29 Feb 2024]
  • 0 in reply to Oana Nagy

    Dear Lyds,

    Thank you so much for your help!

    I carefully checked each one of your points, and it occurs that Studio 2019 considered my files as Plain Text v1.0.0.0 and not as Copy of Delimited Text v2.0.0.0, despite the fact that I had created a proper filetype and put it on top of the list.

    I unckecked all TXT filetypes but mine, and my files for translation could not open (because Studio did non consider them as of the same type of my filetype).

    Therefore, I created a new filetype again, leaving all other TXT filetypes unchecked, but this time, I did not name my filetype extension as "CLIENT.txt", I kept ".txt" only and my files for translation opened correctly!

    Everything is ok now.

    Thank you again Lyds!

    Best regards,

    Rachel (through "Frederic Garcia" account)
    emoji
  • 0 in reply to Frederic Garcia

    Glad I could help Hugging

     

    Oana Nagy | Developer Experience | QA Engineer | RWS Group

    emoji
Reply Children
No Data