SDL Trados Studio
SDL Trados GroupShare
SDL Trados Business Manager
SDL Trados Live
SDL MultiTerm
SDL Passolo
SDL Speech to Text
SDL Managed Translation - Enterprise
SDL MultiTrans
SDL TMS
SDL WorldServer
Translation Management Connectors
SDL LiveContent S1000D
SDL Contenta S1000D
SDL XPP
SDL Tridion Docs
SDL Tridion Sites
SDL Content Assistant
SDL Machine Translation Cloud
SDL Machine Translation Connectors
SDL Machine Translation Edge
Language Developers
Tridion Developers
Tridion Docs Developers
Xopus Developers
Community Help
SDL User Experience
Language Products - GCS Internal Community
SDL Community Internal Group
SDL Access Customer Portal
SDL Professional Services
SDL Training & Certification
Style Guides
Language Technology Partner Group
SDL Academic Partners
SDL Approved Trainers
SDL Enterprise Technology Partners
XyUser Group
ETUG (European Trados User Group) Public Information
Machine Translation User Group
Nordic SDL Tridion Docs User Group
SDL Tridion UK Meetup
SDL Tridion User Group New England
SDL Tridion West Coast User Group
SDL WorldServer User Group
Tridion Docs Europe & APAC User Group
Tridion User Group Benelux
Tridion User Group Ohio Valley
SDL MultiTerm Ideas
SDL Passolo Ideas
SDL Trados GroupShare Ideas
SDL Trados Studio Ideas
SDL Machine Translation Cloud Ideas
SDL Machine Translation Edge Ideas
SDL Language Cloud TMS Ideas
SDL Language Cloud Terminology Ideas
SDL Language Cloud Online Editor Ideas
SDL Managed Translation - Enterprise Ideas
SDL TMS Ideas
SDL WorldServer Ideas
SDL Tridion Docs Ideas
SDL Tridion Sites Ideas
SDL LiveContent S1000D Ideas
SDL XPP Ideas
Events & Webinars
To SDL Documentation
To SDL Support
What's New in SDL
Detecting language please wait for.......
; You select a SDL Trados Studio TM exported file (.tmx) as a Base(Final/Compiled)_tmx; You select a Folder which has lots, lots of ".tmx"s inside of it
; Then, this Code copies all the TUs from the folder (in the tmxs) into the Base_tmx; In its process, it injects SDL TM fields named "origin_File" which shows its origin tmx file name, for all and every TUs
; It does not touch all the TUs in the Base_tmx (at starting stage). So, you'd better use the empty one (or not) ; You do not have anything to worry about SDL TM fields, it is done all automatically
; Now, you just import a tmx once (the Base_tmx), DONE !!! ;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;; It does NOT make any kind of BackUps. That is your business, not mine.;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
currently it processed "2" tmxs (I do not have thousands of them. Each of them has only one TU within it.)the name of SDL TM fields is "origin_File"it shows briefly only the name of tmx it came from (not Path, should be useless)
details
compile thousands TUs into OneFile.zip
Enjoy..
NIce! Even better as you didn't write in Korean :-)
Thanks.
next timeI could try Chinese, all of themYou know it, nobody cares, including you
I do not careCode works well, that is the point here
Regards
I don’t think that’s true Kelly. Many people take the code and read posts without ever responding. That’s just the nature of communities. I like to read through your code and try to understand it... it’s a good learning experience. I even keep a folder for AHK scripts on my laptop and have many of your scripts in there. But the ones with Korean I usually delete if I can’t figure out what should be in there.