Forum: CAT Tools Technical Help
Topic: TMLookup
Poster: Michael Beijer
Post title: sorry, I got confused (we have a 1-month old baby in the house!)
[quote]
Michael Beijer wrote:
If I test your assertion that dupes are identified based on the columns shown in TMLookup (the moment I have some, yes, there's that word again, time), would you consider:
(1) Adding a function where are all TUs imported from TMXs include the creationdate, and
(2) Changing the dupe deleter to (delete all oldest and) leave the latest instance?
[/quote]
[quote]
FarkasAndras wrote:
Re: Michael, nice try for a bargain but I don't particulary [i]need[/i] the dedupe feature to be tested :)
[/quote]
It was worth a try ;)
[quote]
(1) would be a bit of a pain to implement and it would increase the db size and complexity a bit. Very unlikely. I guess you could do it by converting your tmx to a tabbed file that includes the timestamp and importing it as a separate language. [/quote]
OK!
[quote]
(2) requires me to change exactly two characters in the code (MIN to MAX). I can do it and it will be in the next version, which might ship next week or next year. In most cases it won't matter because, well, they are dupes anyway i.e. the relevant content is the same. [/quote]
Hmm, I seem to have confused a few things.
Let me explain what I am trying to achieve by way of an example:
a TU ("hallo kat = ×") changes over time:
time: nl = en
mon.: hallo kat = hello cat
Tue.: hallo kat = hello pussycat
Wed.: hallo kat = hello feline friend
I want the dupe deleter in TMLookup to always remove all but the last version, so delete Mon. and Tue. in my example and leave only Wed.
Can it do this?
[Edited at 2015-06-05 14:03 GMT]
Topic: TMLookup
Poster: Michael Beijer
Post title: sorry, I got confused (we have a 1-month old baby in the house!)
[quote]
Michael Beijer wrote:
If I test your assertion that dupes are identified based on the columns shown in TMLookup (the moment I have some, yes, there's that word again, time), would you consider:
(1) Adding a function where are all TUs imported from TMXs include the creationdate, and
(2) Changing the dupe deleter to (delete all oldest and) leave the latest instance?
[/quote]
[quote]
FarkasAndras wrote:
Re: Michael, nice try for a bargain but I don't particulary [i]need[/i] the dedupe feature to be tested :)
[/quote]
It was worth a try ;)
[quote]
(1) would be a bit of a pain to implement and it would increase the db size and complexity a bit. Very unlikely. I guess you could do it by converting your tmx to a tabbed file that includes the timestamp and importing it as a separate language. [/quote]
OK!
[quote]
(2) requires me to change exactly two characters in the code (MIN to MAX). I can do it and it will be in the next version, which might ship next week or next year. In most cases it won't matter because, well, they are dupes anyway i.e. the relevant content is the same. [/quote]
Hmm, I seem to have confused a few things.
Let me explain what I am trying to achieve by way of an example:
a TU ("hallo kat = ×") changes over time:
time: nl = en
mon.: hallo kat = hello cat
Tue.: hallo kat = hello pussycat
Wed.: hallo kat = hello feline friend
I want the dupe deleter in TMLookup to always remove all but the last version, so delete Mon. and Tue. in my example and leave only Wed.
Can it do this?
[Edited at 2015-06-05 14:03 GMT]