I actually wrote my Bachelor's thesis about using Omegawiki to help interface translation. The result was shortly put that it is not worth the hassle.
Basically it would be lot of effort for very little gain:
- OmegaWiki doesn't currently contain nearly any of the DefinedMeanings we need
- Even when it does, they have definitions in less than ten languages by average, usually including those languages which need it least.
- OmegaWiki lacks pretty much all high level term management functions (splitting, merging, changing terms)
- Proper integration would be a lot of work. Message annotation is slow and difficult and OmegaWiki is not helping us in this process.
- If we basically need to build our own terminology from scratch, why make it complicated and use OmegaWiki, which is not integrated in twn in any way
Agreed with all you write.
I've been looking into several projects and programs doing what we do here, i.e. the "translation" part of localizing software. Only OmegaT works with glossaries, but I do not know about any free glossaries related to the kind of terminology we need, so that needs research.
We must perspectively look into building or own glossaries. Good is that they can be very specific. I doubt :-) references to usage contexts such as "Mediawiki extension 'Socialprofile'" would be accepted in more general wordbook projects. They are however in Ambaradan, and maybe in Omegawiki, should we choose to automatically share collected data.
Let's see, what I am going to find, while doing some glossary related tests and research anyways in the future. I shall report.