Hello - we have several thousand tmx files to import, but the Studio TM doesn't display the tmx file name, whether it be the actual name of the file, or a property within the tmx file. Is there a way for this info to be kept and displayed? Many thanks!
Question regarding the import of tmx files into Studio TMs
Yes. You need to create a field on your TM to write in the name of the TMX and then when you import use the filename.
However, if you want this to happen automatically because you have thousands of files then I'm afraid there isn't a way out of the box the do this. It could be done through the API... probably not too difficult. We might have a look at this through the appstore if nobody else does.
A possible workaround for now, I guess, would be to edit the "Created by" values in the TMX files with a batch process (this would be outside of Studio) and then the system fields could be updated with the value you use (the filename).
Another possible workaround woud be use Powershell... Evzen Polenka might have covered something like this with his powershell tools here:
https://github.com/EvzenP/STraSAK/
Unless of course someone has a better idea?
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
Question regarding the import of tmx files into Studio TMs
Yes. You need to create a field on your TM to write in the name of the TMX and then when you import use the filename.
However, if you want this to happen automatically because you have thousands of files then I'm afraid there isn't a way out of the box the do this. It could be done through the API... probably not too difficult. We might have a look at this through the appstore if nobody else does.
A possible workaround for now, I guess, would be to edit the "Created by" values in the TMX files with a batch process (this would be outside of Studio) and then the system fields could be updated with the value you use (the filename).
Another possible workaround woud be use Powershell... Evzen Polenka might have covered something like this with his powershell tools here:
https://github.com/EvzenP/STraSAK/
Unless of course someone has a better idea?
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
I'm afraid that STraSAK doesn't have a feature which could be used for this task.
But the whole task sounds like an XY problem...
It seems to me that the real starting point for the task is somewhere before the thousands of TMX files... simply because I can't think of a "sensible source" of thousands of TMX files...
Like, why and from which source would someone create so many TMXs, that doesn't make much sense to me... it sounds like if someone thought that the only way to create bilingual content from thousands of bilingual files is to export each file to a separate TMX... or something like that.
Which would mean that the ultimate goal could be probably achieved differently, not necessarily the worst possible way (via the separate TMXs).
So, Lucy-Jane Michel, if you don't mind, can you provide a bit more context?
It looks like it could be solved programmatically using EditScript functionality during import to TM, but EditScript is NOT PROPERLY DOCUMENTED ANYWHERE :( :( :(
There is a mention about it in the Studio 2015 (!!!) TM API documentation (http://producthelp.sdl.com/SDK/TranslationMemoryApi/4.0/html/024ab948-758e-4f14-a7c5-e7e8a058b433.htm - check the bottom right of the API schema) and one can find the EditScript class itself documented, but there is not a single word anywhere about how to use it - what the script actually is, how it works, etc.
What's more, this part is completely missing from newer API version documentation, there is a LOT missing in the newer version documentation!
Is SDL ever going to fix this?
Paul, the other day you were wondering why there is so few developers doing something with Studio API for the community... perhaps this is one of the reasons - with such a poor support from SDL, why bother...
Translate
