Keep getting this error:
OK, enough playing around. Got to switch all this nonsense off and make some actual money for a few hours.
I was wondering what Michael was doing - I always wonder what on earth he's doing - and then I realised he's using the TM_Lookup database, rather than the CT database.
A few remarks on databases may be useful.
7. You can recall more than 1 table...
... and assign different priorities to the resulting TMs. I don't know if you can do that with fields (rather than tables), like context General and context Automative, for example.
8. To search for phrases in a table, use quotes.
Two more articles on Total Recall which explain the storage and retrieval of the segments to the working memory:
Am I right when I say
Terima kasih, terima kasih, terima kasih.
OK, I have a question, which came about in connection with a discussion that is currently going on over at Proz about the new Lift technology, and Total Recall.
It basically boils down to this: how does subsegment matching in CafeTran relate to, or work in 9if it does), Total Recall?
Hans (van den Broek) and I have been trying to understand it in the forum discussion above. Hans says that since the TR database is SQLite, it cannot apply fuzziness in its operations. I am not sure, or at any rate, don't have a clue.
If you look at my post titled " here’s an example of what I mean (CafeTran LIFTing)" (which is here: http://www.proz.com/forum/sdl_trados_support/289937-lift_technology_is_it_on_its_way-page3.html), you'll see that there seems to be some subsegment matching (and hence fuzziness) in my example screenshots. However, how is this possible?
Sorry if my question is not very well posed. I'm a bit short on time, as usual.