Go through all the 25 released language pairs in our SVN and note down their date of last release[1] and how many dictionary entries and rules the released package has.

Then go to SVN and look at the module for the released pair and find out how many dictionary entries and rules it has.[2] Put this into a CSV spreadsheet and email the mailing list. Example spreadsheet:

language_pair,version,date,dict_l1,dict_l2,dict_l1_l2,rules_l1_l2,rules_l2_l1,svn_lastchanged,dict_l1,dict_l2,dict_l1_l2,rules_l1_l2,rules_l2_l1

apertium-mk-bg,0.2.0,2010-10-26,8745,8580,8811,33,25,2010-11-03,8745,8580,8811,33,25

Why? Our release cycle is very slow, and often we get pairs in trunk which have substantial improvements but have not been released.

1. https://sourceforge.net/projects/apertium/files/

2. Here are some tips on how to caclulate the numbers you will need for the spreadsheet:

fran@eki:/tmp/apertium-mk-bg-0.2.0$ cat apertium-mk-bg.mk.dix | grep '<e lm' | wc -l
8745

fran@eki:/tmp/apertium-mk-bg-0.2.0$ cat apertium-mk-bg.bg.dix | grep '<e lm' | wc -l
8580

fran@eki:/tmp/apertium-mk-bg-0.2.0$ cat apertium-mk-bg.mk-bg.dix | grep '<l' | wc -l
8811

fran@eki:/tmp/apertium-mk-bg-0.2.0$ cat apertium-mk-bg.mk-bg.t*x | grep '<rul' | wc -l
33

fran@eki:/tmp/apertium-mk-bg-0.2.0$ cat apertium-mk-bg.bg-mk.t*x | grep '<rul' | wc -l
25

fran@eki:~/source/apertium/trunk/apertium-mk-bg$ svn info | grep 'Last Changed Date'
Last Changed Date: 2010-11-03 09:40:47 +0000 (dc, 03 nov 2010)