I would be nice to have the TR import routine running in the background, although (I suppose the TR function would be disabled during this, as importing e.g. a 100 K or 120 K segments TM into TR (about 100 MB)) takes quite a time, and – maybe I am mistaken – the TR function (as long as not activated) does not interfere with the rest of the program.
Anyway, would be nice to have a "You can keep on working while TR imports the TM" hint, though I know this is against the "keep it super-concise" rule of CT.
Will it be possible to use the TR feature during import? I would try this, but I really do not want to crash my TR database. It should be possible to have two accesses to the same DB in two different tables, shouldn't it?
> Will it be possible to use the TR feature during import?
Yes, it needs to be tested thoroughly.
> "keep it super-concise" rule of CT.
I like that expression. The super borders on hyper. :)
> And is it possible to use TR during import?
Yes, you can search keep translating and searching TR tables. However, recalling and importing data at the same time is not possible. I think it can be done only in the server-based databases (like MySQL and MariaDB), which can be used with CT instead of the default SQLite.