A master termbase can help with the problems of homonyms a bit. The idea is the following:
You have a well maintained, hand crafted termbase that has all the right homonyms as different entries. You now want to merge it with a smaller, new termbase. Normally, you would run into the homonym problems described earlier. By declaring a master termbase, you can preserve homonyms in that one termbase. You do this in the settings dialog. The output file will always be the named <master termbase>_merged.
That means, if you have two entries with the same source term (homonyms), they will remain separate, even if the new termbase has a new translation. How does the Converter know which homonym to chose? It doesn't, so to be on the safe side, it adds the new term to both. Which means that one of them is definitely wrong, but you have to make a compromise here. Again, it's a good idea to do some quality control after merging.
Also, keep in mind that the Converter does not preserve the original termbase as it is. So if you merge with an sdltb master, the output (even if again sdltb) will have lost the field history, for example.
An example may be clearer than the text...
Created with the Personal Edition of HelpNDoc: Generate EPub eBooks with ease