Translator often encounters bilingual Excel files, which need to be use translated text from it in projects.It is best to add "import entries from Excel files" feature to the translation memory file directly without having to convert Excel file to a TMX fileI'm waiting for this feature to be added in the new Trados releasesThank you.
aazzoma khateeb said:I'm waiting for this feature to be added in the new Trados releases
I very much doubt we will ever see this become a feature because there is little point. Excel allows too much flexibility for a start so this means users would have to make sure that the Excel files were in the format Studio expected. This is of course something we could address by taking the same approach as the Glossary Converter and asking users to define the fields, languages etc. But this is a lot of work for something that isn't needed very often and it easilt solved using looks like the excellent Glossary Converter to get your TMX.
What I'd like to see is the Glossary Converter take things on a step and actually create the SDLTM. That would be brilliant since it could also avoice the UpLift process and produce a usable TM very quickly. But that would require Gerhard Kordmann deciding it was really worthwhile.
if Glossary Converter supports SDLTM, it would be another TM option.
Now. I'm using Bilingual Excel file Type to enrich SDLTM, beside TMX intermediate step1- create a project2- add excel bilingual files
3-update Main project TM / batch tasksthis method is useful also.
Hello PaulI found unsigned sdlpluginto import excel to SDLTM
Great... I imagine that is from Kelly Edward who won't get any of his plugins signed. If it works for you that's great.
Where is that?
It'll be in here somewhere - https://deeptranslation.blogspot.com/
Use at your own risk!
Could not find anything there matching the description
Imort_Excel_SDLTM.zipI will upload itfor studio 2017 only
In principle possible. Main headache is that I would introduce a dependency on Studio, and would have to somehow make the converter compatible with all versions, which is hard enough for MultiTerm. Or build test and maintain multiple versions which also is no fun. Interesting idea, but no promises :-)