Hi,
I suggest more liberal requirements for release of a language
pair/direction:

It would be sufficient if all words in the bilingual dictionary could be
analysed, translated and generated. Drop the requirement that all words
in the source language monolingual dictionary should be translated.

Rational: In that way you prepare for decoupling of the monolingual
dictionaries from the language pairs, see the ideas for Google summer of
code, http://wiki.apertium.org/wiki/Ideas_for_Google_Summer_of_Code:

"Develop a method (scripts) to allow monolingual and bilingual data in
Apertium to be decoupled, leaving each language pair with only the
necessary bilingual data."

In that way it would be easier to maintain the monolingual dictionaries
and all language pairs would immediately profit from a new contribution
to a monolingual dictionary.

Besides, I just feel that it's really silly to drop entries from the
monolingual dictionaries to qualify for a release.

Yours,
Per Tunedal

------------------------------------------------------------------------------
Don't let slow site performance ruin your business. Deploy New Relic APM
Deploy New Relic app performance management and know exactly
what is happening inside your Ruby, Python, PHP, Java, and .NET app
Try New Relic at no cost today and get our sweet Data Nerd shirt too!
http://p.sf.net/sfu/newrelic-dev2dev
_______________________________________________
Apertium-stuff mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/apertium-stuff

Reply via email to