I would like to export multiple SDLTM files to TMX files in one go, and apply at the same time a particular filter so that I get only specific translation units in the TMX files.
Did you come across a plug-in or any other solution?
I haven't seen such a plugin. But I think you might find the "upgrade" path helpful here as you'll at least get this into less steps.
Not ideal... but perhaps helpful if you didn't think of this already.
Thanks for the workaround, but if you have to do that once, then yes it works.
Thing is that we would like to do that every time we deliver a project to the client, 2-3 times per week. So if you have 10 TMs of ~300MB each, it's huge effort.
Anyway, thanks again.
have you thought about using project TMs instead of expecting from a main TM? Perhaps that would be easier?
Of course we are using project TMs in our projects.
The problem is not in the workaround you provided us with, but in the fact that we have to do the upgrade + merge + export 5-10 times per week, once we deliver a project to our client. So it's time consuming anyway.
I'm wondering if export using a filter definition file (i.e. the *.sdltm.filters file which can be exported from Studio) would be okay.
Because it looks like I could quite easily implement such enhancement into STraSAK: https://github.com/EvzenP/STraSAK.It already contains batch export to TMX, so adding the filtering capability looks like pretty simple task...
today I have delved into SDL TM Filter file
amazingly, it is so perfect one
which means... too complex to use
nobody is going to use that filter like that - in theory, it could combine hundreds of criteria, wow..
And, most importantly, SDL do not support TM export using that file - I could be wrong, like I said today is the first day of using it.
So, my conclusion is..
Looks like impossible as you wished
but, If your criteria is brief one (which means, 3 criteria or less)
you could achieve your goal by making filter function from the scratch.
Easier Said Than Done .
Good Luck To You
krupa adrian said:And, most importantly, SDL do not support TM export using that file
I believe it should be possible. The FilterExpressionParser class has a Parse method, which should be able to parse the expression stored in the exported filter file.I believe this is the way to go.
However, I wasn't able to initialize the FilterExpressionParser instance actually "bound" to the actual TM fields definitions, so that the Parse method doesn't fail with "unknown fields" error.Will continue trying later...I'm not a developer, so it's not very straightforward to me.