Forum: CAT Tools Technical Help
Topic: TMLookup
Poster: Michael Beijer
Post title: :)
[quote]FarkasAndras wrote:
[quote]Michael Beijer wrote:
(1) I would love to be able to just point TMLookup at a specific folder of TMXs, and have it automatically index all TMXs contained therein. If I were then to delete certain TMXs from the folder, and re-run TMLookup, it would automatically remove the deleted TMXs from its index. Basically, what LogiTerm (which costs $795.00) can do. That would be amazing.
[/quote]
That shouldn't be all that hard. I have already considered some sort of auto-import feature, although that was for one file (current project DB). I guess I could implement it as file/folder (whichever is specified in the setup file) that is auto-imported on startup. It would either be reimported on every startup or when the user deletes the auto-generated db file. Probably the latter. Making sure that languages don't get mixed up is a bit of an issue, esp. if there are different TMXes and TXTs/XLSes mixed together.
One reason why it got put off before is that it would make most sense after implementing multi-db support. However, with one-button db switching, which is already implemented, it could work reasonably well even without multi-db support. Currently, F1-F4 switches between user-defined DBs. The current project DB could just be assigned to F5.[/quote]
That would be very cool!
[quote][quote]Michael Beijer wrote:
(2) My second big feature request relates to pretranslation. I would love to be able to use TMLookup to Pretranslate files, producing a TMX. Another of LogiTerm's tricks.
Michael[/quote]
I don't think that's likely. What's the idea? Read a translatable file sentence by sentence and export matching segments from the db into a "project TM" tmx? In any case, this would require a fuzzy matching algorithm to be useful, and TMLookup doesn't have one. It's not likely that it will get one in the future, either. [/quote]
Yes, pretty much that.
However, no biggie if you don't add it, because I can already achieve this in CafeTran, using my TMLookup .db, which is already great. Basically, I maintain a very big TMLookup .db, of ALL my TMXs, and can pretranslate documents in CafeTran by telling CafeTran to use my TMluukup .db as its database for pretranslation. To do so I use CafeTran's special Total Recall system, which produces a TMX (of my pretranslated doc) as you described.
Michael
PS: I don't want to jinx things, but I think there would be sufficient interest to warrant a paid version of TMLookup. Throw in a few TMX editing features, and you would have quite an amazing, and unique tool. Hell, while your're at it (ho ho ho), you could of course als integrate LFAligner, to create ... the Ultimate TMX Tool for Translators: LFAligner + TMlookup + TMX Editor/Cleaner/Maintainer ;-)
[Edited at 2015-12-22 23:27 GMT]