This site uses cookies.
Some of these cookies are essential to the operation of the site,
while others help to improve your experience by providing insights into how the site is being used.
For more information, please see the ProZ.com privacy policy.
Using Studio on TTX file with a configuration file (.ini)
Thread poster: Daniel Weston
Daniel Weston United States Local time: 10:32 French to English + ...
Feb 1, 2011
I received a project today to be translated using TagEditor in conjunction with a configuration file (.ini). I'd really like to use Studio instead of TagEditor. I know it is possible to use Studio on TTX files but I don't have any experience using .ini files. Is it possible to use the .ini file in Studio? If so, where can I find information on how to do it? If I have to, I can use TagEditor but this brings up another question. How do I incorporate the .ini file when using TagEditor?
<... See more
I received a project today to be translated using TagEditor in conjunction with a configuration file (.ini). I'd really like to use Studio instead of TagEditor. I know it is possible to use Studio on TTX files but I don't have any experience using .ini files. Is it possible to use the .ini file in Studio? If so, where can I find information on how to do it? If I have to, I can use TagEditor but this brings up another question. How do I incorporate the .ini file when using TagEditor?
Any guidance would be most humbly appreciated!
***UPDATE - I seem to have found another post that addresses this issue. The only question I still have is "will the ttx file that I create to send back to the client comply with the original specs?"
The contents of this post will automatically be included in the ticket generated. Please add any additional comments or explanation (optional)
Gillian Searl United Kingdom Local time: 18:32 German to English
You can check afterwards
Feb 1, 2011
Open the TTX in Studio (ignoring the INI), translate in Studio, export finished translation to TTX. Open TagEditor and go through the whole thing using the INI file. If there are any problems you should pick them up at this stage.
Subject:
Comment:
The contents of this post will automatically be included in the ticket generated. Please add any additional comments or explanation (optional)
Jerzy Czopik Germany Local time: 19:32 Member (2003) Polish to German + ...
Studio reads TTX - and this is "Standard"
Feb 1, 2011
So what Studio will produce will be TTX, exactly the same as the one you imported.
No ini necessary for that. First when saving the target format this ini will be used.
With other word, when you deliver the TTX to the customer he will not notice, if it was translated in TagEditor or Studio unless he opens the file in Notepad and reads the file heading.
Subject:
Comment:
The contents of this post will automatically be included in the ticket generated. Please add any additional comments or explanation (optional)
Daniel Weston United States Local time: 10:32 French to English + ...
TOPIC STARTER
Thanks
Feb 1, 2011
Thanks Jerzy and Gillian,
I was just concerned becuase they were very specific about using the ini file that they provided, stating that their post production would be compromised if I didn't use TagEditor with it!
Subject:
Comment:
The contents of this post will automatically be included in the ticket generated. Please add any additional comments or explanation (optional)
Jerzy Czopik Germany Local time: 19:32 Member (2003) Polish to German + ...
Do a test
Feb 1, 2011
Translate some few lines of the TTX in Studio, then save it as target (Save as target in Studio will deliver the TTX, NOT the real target text).
Send it to the customer asking them to test if evertyhing is OK.
As reason you can simply tell them, that you wanna be sure everything goes fine before you really start working on the project . As they have so specific ini it is not a bad idea to test to make sure your systems... See more
Translate some few lines of the TTX in Studio, then save it as target (Save as target in Studio will deliver the TTX, NOT the real target text).
Send it to the customer asking them to test if evertyhing is OK.
As reason you can simply tell them, that you wanna be sure everything goes fine before you really start working on the project . As they have so specific ini it is not a bad idea to test to make sure your systems are really compatible. ▲ Collapse
Subject:
Comment:
The contents of this post will automatically be included in the ticket generated. Please add any additional comments or explanation (optional)
Daniel Weston United States Local time: 10:32 French to English + ...
TOPIC STARTER
Thanks Jerzy
Feb 1, 2011
That is an excellent idea - thank you for the suggestion!
Subject:
Comment:
The contents of this post will automatically be included in the ticket generated. Please add any additional comments or explanation (optional)
Selcuk Akyuz Türkiye Local time: 21:32 English to Turkish + ...
I am not a Trados user but
Feb 1, 2011
I guess the procedure should be different than described above.
I would first open the ttx file in TagEditor with the ini file provided, and then translate against an empty TM to populate all segments (copy source to target). Now your ttx file is ready for translation with Studio (or any other CAT tool).
[Edited at 2011-02-01 11:38 GMT]
Subject:
Comment:
The contents of this post will automatically be included in the ticket generated. Please add any additional comments or explanation (optional)
Pastey is an innovative desktop application that bridges the gap between human expertise and artificial intelligence. With intuitive keyboard shortcuts, Pastey transforms your source text into AI-powered draft translations.
The leading translation software used by over 270,000 translators.
Designed with your feedback in mind, Trados Studio 2022 delivers an unrivalled, powerful desktop
and cloud solution, empowering you to work in the most efficient and cost-effective way.