If I could hire a programmer that would give me one extra functionality, something that is not scheduled for this moment, what would I have him do? What if I have a budget for at least a few weeks of work ..
Interwiki links
I hate these things. They are always out of sync. Many people spend a lot of hard work on getting them right while the problem is getting bigger and it is not solved at all. It feels like a waste. When a project grows, it has articles that need to be linked. As more and more wikipedias grow, the number of articles that need updating grow rapidly. Small projects are not easily integrated. It costs a lot of resources.
With a centralised database, we could link an article to another article and by inference it would be known to all the articles that are linked to it. As all the articles are about the same subject, we could check if article names are translations. When they are, it is a basis for linking to the lexicological content of WiktionaryZ ..
Inflection boxes
When a verb, a noun and adjective changes under given rules, it makes sense to have inflection boxes. They are generated using templates on many wiktionaries, but it makes more sense to have some software that allows us to build these boxes. Software that associates inflections of one language to the inflections of other languages for the purpose of translation.
Better support for tools like OmegaT
OmegaT is a CAT-tool, it helps translators with their work. I would do two things to OmegaT, I would have it read directly from a MediaWiki wiki and when the translation is finished, write it to another wiki. I would also have its translation glossary funtction make use of WiktionaryZ..
Yes there would be a quid pro quo, when a translator adds a word to the glossary it would be fed back to WiktionaryZ.
Thanks,
GerardM
PS What would your suggestion be ?
Showing posts with label OmegaT. Show all posts
Showing posts with label OmegaT. Show all posts
Tuesday, March 07, 2006
Wednesday, August 24, 2005
Me, CAT tools en Microsoft
When you are not a translator and when you have no dealings with the translation business, you would not expect that anything that I can do could threaten business interests of Microsoft. I was therefore very suprised when I was informed that my wish for a reference implementation of a translation glossary and my wish to integrate such a functionality in open source CAT tools like OmegaT do just that.
I am actively looking for money to enhance OmegaT. Not because I am likely ever to use it, but because I want quality translations in Ultimate Wiktionary. This reference implementation will do exactly that. In order to make OmegaT less user-feindly, there several little things that can be done. Sabine, defined some quirks that are a barrier for newbies. She also identified that "Trados" compatibility would be really important to introduce many translators to OmegaT.
A friend of mine is working on three annoying things. He is a professional programmer. He will inform us how much time it costs and how much it would cost if 100 translators payed for this. The point that I want to drive home is, that you can either pay for a license or you pay for functionality. When you pay for functionality, it will prove to be much cheaper.
I have my reasons why I want OmegaT to be a success, Microsoft happens to be the monopolist in the translation/localisation business. It is a genuine suprise but when you think about it, it should not be.
Thanks,
GerardM
I am actively looking for money to enhance OmegaT. Not because I am likely ever to use it, but because I want quality translations in Ultimate Wiktionary. This reference implementation will do exactly that. In order to make OmegaT less user-feindly, there several little things that can be done. Sabine, defined some quirks that are a barrier for newbies. She also identified that "Trados" compatibility would be really important to introduce many translators to OmegaT.
A friend of mine is working on three annoying things. He is a professional programmer. He will inform us how much time it costs and how much it would cost if 100 translators payed for this. The point that I want to drive home is, that you can either pay for a license or you pay for functionality. When you pay for functionality, it will prove to be much cheaper.
I have my reasons why I want OmegaT to be a success, Microsoft happens to be the monopolist in the translation/localisation business. It is a genuine suprise but when you think about it, it should not be.
Thanks,
GerardM
Subscribe to:
Posts (Atom)