Forum: CAT Tools Technical Help
Topic: TMLookup
Poster: FarkasAndras
Post title: Yes
[quote]Michael Beijer wrote:
Speaking of multiple databases, it would of course also be great if there was some sort of facility in the program itself that would allow you to pick & mix from multiple databases. For example, I would like to be able to create:
1. Legal.db
2. Education.db
3. IT.db
4. Marketing.db
etc
...and be able to search them all simultaneously (or a selectin of them) from within one copy of TMLookup.
[/quote]
That idea has been around since the first beta. However:
[quote]FarkasAndras wrote:
...an ominous job that is so unappetizing that I've been putting it off since the start of the project. [/quote]
Maybe it's not so bad but it has the potential for annoying complications and cascading changes in the code.
For now, F1-F4/F12 provide a decent workaround. F12 toggles the last two open dbs (active session only), so it's very handy if you can't be bothered to add dbs to the quick access list. The shortcuts may not be in the readme but they can be found in the setup, changelog etc. If you switch databases, your last search is automatically repeated on the new db so you get instant results.
Re: duplicate filtering, maybe I'll look into it. It would be best if you could provoke the issue on a small sample db. The most likely explanation is that there are subtle differences between the entries. Capitalization or whitespace, most likely.
Re: removing old entries, there is no timestamp in the db. Each record (segment) has a rowid, which is essentially a serial number. One could remove older entries based on rowid, but it would be messy to implement and use. If you add a meta (source) field to your entries, you could use the delete hits feature. Switch one of the search columns to the source field, search for the source you want to remove, and delete hits. Test on a sample db first.
Re: tmx editor, I'm not sure. A couple of people have asked for something like this, but I'm not sure what features would make sense. Even if I did this in a separate app (and not in TMLookup), I would almost certainly import the tmx into an sqlite db and discard all the metadata (as is done in TMLookup). That might be an unpleasant surprise to some users. I'm also wary of playing with TMX because my import process is an ugly hack and not a proper xml parser, so some tmxes might be incorrectly imported. The fact that there is a wide array of tools generating TMX files based on various iterations of the standard doesn't help. What features do people want from a TMX editor? Isn't there already an open source tmx editor out there? Or two maybe?
Re: a paid version, that won't happen for a couple of reasons, low interest being only one. There were a couple of occasions when somebody requested a feature that was doable but not trivial, and not a priority for me (for LFA or TML). In those cases I told the guy I would add the feature on the understanding that he will send a small donation afterwards if he is happy with the feature. I usually suggested a range of €20 to €100 or something like that. A couple of people also donated spontaneously. So I made a tiny bit of money but I will never make anything like a meaningful hourly rate on these hobby projects.
Re: autoimport, I have already started fiddling with it. It's not trivial, but I can see there is some interest so I'll probably work on it a little more seriously. It's something I would probably use myself. I used to use it when I still used xbench. I just had a tabbed txt file that was always filled with stuff for the current project.
Topic: TMLookup
Poster: FarkasAndras
Post title: Yes
[quote]Michael Beijer wrote:
Speaking of multiple databases, it would of course also be great if there was some sort of facility in the program itself that would allow you to pick & mix from multiple databases. For example, I would like to be able to create:
1. Legal.db
2. Education.db
3. IT.db
4. Marketing.db
etc
...and be able to search them all simultaneously (or a selectin of them) from within one copy of TMLookup.
[/quote]
That idea has been around since the first beta. However:
[quote]FarkasAndras wrote:
...an ominous job that is so unappetizing that I've been putting it off since the start of the project. [/quote]
Maybe it's not so bad but it has the potential for annoying complications and cascading changes in the code.
For now, F1-F4/F12 provide a decent workaround. F12 toggles the last two open dbs (active session only), so it's very handy if you can't be bothered to add dbs to the quick access list. The shortcuts may not be in the readme but they can be found in the setup, changelog etc. If you switch databases, your last search is automatically repeated on the new db so you get instant results.
Re: duplicate filtering, maybe I'll look into it. It would be best if you could provoke the issue on a small sample db. The most likely explanation is that there are subtle differences between the entries. Capitalization or whitespace, most likely.
Re: removing old entries, there is no timestamp in the db. Each record (segment) has a rowid, which is essentially a serial number. One could remove older entries based on rowid, but it would be messy to implement and use. If you add a meta (source) field to your entries, you could use the delete hits feature. Switch one of the search columns to the source field, search for the source you want to remove, and delete hits. Test on a sample db first.
Re: tmx editor, I'm not sure. A couple of people have asked for something like this, but I'm not sure what features would make sense. Even if I did this in a separate app (and not in TMLookup), I would almost certainly import the tmx into an sqlite db and discard all the metadata (as is done in TMLookup). That might be an unpleasant surprise to some users. I'm also wary of playing with TMX because my import process is an ugly hack and not a proper xml parser, so some tmxes might be incorrectly imported. The fact that there is a wide array of tools generating TMX files based on various iterations of the standard doesn't help. What features do people want from a TMX editor? Isn't there already an open source tmx editor out there? Or two maybe?
Re: a paid version, that won't happen for a couple of reasons, low interest being only one. There were a couple of occasions when somebody requested a feature that was doable but not trivial, and not a priority for me (for LFA or TML). In those cases I told the guy I would add the feature on the understanding that he will send a small donation afterwards if he is happy with the feature. I usually suggested a range of €20 to €100 or something like that. A couple of people also donated spontaneously. So I made a tiny bit of money but I will never make anything like a meaningful hourly rate on these hobby projects.
Re: autoimport, I have already started fiddling with it. It's not trivial, but I can see there is some interest so I'll probably work on it a little more seriously. It's something I would probably use myself. I used to use it when I still used xbench. I just had a tabbed txt file that was always filled with stuff for the current project.