Difference between revisions of "Dictionary maintenance"

From Apertium
Jump to navigation Jump to search
m
Line 5: Line 5:
 
There are more and more pairs, for examples 7 pairs with English and the monodix en is copied in every pair.
 
There are more and more pairs, for examples 7 pairs with English and the monodix en is copied in every pair.
   
What happens if developper A and developper B edit both the en monodix, say in en-fr and en-es for example? Answer: another developper has to look on both version, look the diff and try to merge. Most of the time developper A tells developper to wait a few minutes or hours, then he commits and tells to developper B that he may now copy his version and starts working.
+
What happens if developer A and developer B edit both the en [[monodix]], say in en-fr and en-es for example? Answer: another developer has to look on both version, look the diff and try to merge. Most of the time developer A tells developer to wait a few minutes or hours, then he commits and tells to developer B that he may now copy his version and starts working.
   
That is time consuming. For the near future it is manageable, since there are now only a half dozen developpers that regulary go on irc to solve these issue. But in the long-term, it would become harder and harder. Imagine if there are 20 or 50 pairs with English. Imagine that all developpers do not want to wait. There would be different monodix.
+
That is time consuming. For the near future it is manageable, since there are now only a half dozen developers that regulary go on irc to solve these issues. But in the long-term, it would become harder and harder. Imagine if there are 20 or 50 pairs with English. Imagine that all developers do not want to wait. There would be different [[monodix]].
   
 
==Issues==
 
==Issues==

Revision as of 21:35, 20 May 2007

The problem

Problem managing conflict edits for monodix

There are more and more pairs, for examples 7 pairs with English and the monodix en is copied in every pair.

What happens if developer A and developer B edit both the en monodix, say in en-fr and en-es for example? Answer: another developer has to look on both version, look the diff and try to merge. Most of the time developer A tells developer to wait a few minutes or hours, then he commits and tells to developer B that he may now copy his version and starts working.

That is time consuming. For the near future it is manageable, since there are now only a half dozen developers that regulary go on irc to solve these issues. But in the long-term, it would become harder and harder. Imagine if there are 20 or 50 pairs with English. Imagine that all developers do not want to wait. There would be different monodix.

Issues

  • Language specific sections of monodix files.

Ideas to solve