Hi, but you don't tell me the rational behind the requirement. I just don't get why it's worse to get "cannot translate" than "unknown word". Yours, Per Tunedal
On Fri, Oct 12, 2012, at 07:37, Mikel L. Forcada wrote: > I am not in favour of dropping the requirement either. > Your PMC prez, > Mikel > > On 10/12/12, Francis Tyers <fty...@prompsit.com> wrote: > > El dj 11 de 10 de 2012 a les 22:13 +0200, en/na Per Tunedal va escriure: > >> 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. > > > > It's a GSOC project, if someone takes it up, it would be great, but > > until then I don't see a reason to change the requirements. You can > > always use scripts to trim larger dictionaries as has been explained in > > previous posts. > > > > F. > > > > > > ------------------------------------------------------------------------------ > > 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 > > Apertium-stuff@lists.sourceforge.net > > https://lists.sourceforge.net/lists/listinfo/apertium-stuff > > > > > > -- > Sent from Gmail for mobile | mobile.google.com > > Mikel L. Forcada E-mail: m...@dlsi.ua.es > Departament de Llenguatges Phone: +34-96-590-9776 > i Sistemes Informàtics also +34-96-590-3772. > UNIVERSITAT D'ALACANT Fax: +34-96-590-9326, -3464 > E-03071 ALACANT, Spain. > > URL: http://www.dlsi.ua.es/~mlf > > ------------------------------------------------------------------------------ > 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 > Apertium-stuff@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/apertium-stuff ------------------------------------------------------------------------------ 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 Apertium-stuff@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/apertium-stuff
