Translate
When I finish the project and export the file, the file seems to be mixing both the source and target languages.
When I finish the project and export the file, the file seems to be mixing both the source and target languages.
We're missing some most important information here:
So far I've also tried to restart the computer, removed the project from the list, did a new project, imported the same files, and used the translation memory to redo it but once I finished and exported the error persisted.
So far I've also tried to restart the computer, removed the project from the list, did a new project, imported the same files, and used the translation memory to redo it but once I finished and exported the error persisted.
No surprise there if you didn't change anything about how you set this up. You also need to explain better what you mean by the file contains source and target content. We're still none the wiser about what is really going on here.
Does this happen in every segment or just some segments?
Can you create a sample by editing the SRT file itself?
Are you sure the SRT filetype was used? Sometimes SRT files are not really SRT files and they just have that extension. I think a sample would help rule that problem out.
Paul Filkin | RWS Group
________________________
Design your own training!
You've done the courses and still need to go a little further, or still not clear?
Tell us what you need in our Community Solutions Hub
Problem solved. My husband is a programmer and discovered that the original SRT files had an error in the timestamps. Some time-stamps were missed by SDL.
Example:
10
00:00:40,66 --> 00:00:44,66
tener la certeza de que es tu voluntad revelada
This was a wrong segment because of the timestamps.
The correct way should be:
10
00:00:40,660 --> 00:00:44,660
tener la certeza de que es tu voluntad revelada
In order for SDL to recognize the segment. He made the changes in the original files and now I'm using the translation memory to finish it up, but now everything is fine with the exporting. :)
Thanks for your help.
Thank goodness for programmers! Whilst SRT doesn't really have an official, centralised specification document that is universally accepted the format's conventions have been widely adopted and are documented through various unofficial sources and software documentation. The main takeaways would be these:
HH:MM:SS,mmm format, with three digits for milliseconds.Great troubleshooting!
Paul Filkin | RWS Group
________________________
Design your own training!
You've done the courses and still need to go a little further, or still not clear?
Tell us what you need in our Community Solutions Hub
Thank goodness for programmers! Whilst SRT doesn't really have an official, centralised specification document that is universally accepted the format's conventions have been widely adopted and are documented through various unofficial sources and software documentation. The main takeaways would be these:
HH:MM:SS,mmm format, with three digits for milliseconds.Great troubleshooting!
Paul Filkin | RWS Group
________________________
Design your own training!
You've done the courses and still need to go a little further, or still not clear?
Tell us what you need in our Community Solutions Hub