Vous êtes sur la page 1sur 346

From bogus@does.not.exist.

com Sat Nov 1 02:59:31 2014


From: bogus@does.not.exist.com ()
Date: Sat Nov 1 03:54:16 2014
Subject: No subject
Message-ID: <mailman.1.1414814056.14999.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sat Nov 1 02:59:31 2014
From: bogus@does.not.exist.com ()
Date: Sat Nov 1 03:54:19 2014
Subject: No subject
Message-ID: <mailman.2.1414814059.14999.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sat Nov 1 02:59:31 2014
From: bogus@does.not.exist.com ()
Date: Sat Nov 1 03:54:19 2014
Subject: No subject
Message-ID: <mailman.3.1414814059.14999.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sat Nov 1 02:59:31 2014
From: bogus@does.not.exist.com ()
Date: Sat Nov 1 03:54:20 2014
Subject: No subject
Message-ID: <mailman.4.1414814060.14999.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sat Nov 1 02:59:31 2014
From: bogus@does.not.exist.com ()
Date: Sat Nov 1 03:54:20 2014
Subject: No subject
Message-ID: <mailman.5.1414814060.14999.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sat Nov 1 02:59:31 2014
From: bogus@does.not.exist.com ()
Date: Sat Nov 1 03:54:20 2014
Subject: No subject
Message-ID: <mailman.6.1414814060.14999.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sat Nov 1 02:59:31 2014
From: bogus@does.not.exist.com ()
Date: Sat Nov 1 03:54:21 2014
Subject: No subject
Message-ID: <mailman.7.1414814061.14999.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sat Nov 1 02:59:31 2014
From: bogus@does.not.exist.com ()
Date: Sat Nov 1 03:54:21 2014
Subject: No subject
Message-ID: <mailman.8.1414814061.14999.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sat Nov 1 02:59:31 2014
From: bogus@does.not.exist.com ()
Date: Sat Nov 1 03:54:22 2014
Subject: No subject
Message-ID: <mailman.9.1414814062.14999.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sat Nov 1 02:59:31 2014
From: bogus@does.not.exist.com ()
Date: Sat Nov 1 03:54:24 2014
Subject: No subject
Message-ID: <mailman.10.1414814064.14999.htk-users@eng.cam.ac.uk>

From bogus@does.not.exist.com Sat Nov 1 02:59:31 2014


From: bogus@does.not.exist.com ()
Date: Sat Nov 1 03:54:24 2014
Subject: No subject
Message-ID: <mailman.11.1414814064.14999.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sat Nov 1 02:59:31 2014
From: bogus@does.not.exist.com ()
Date: Sat Nov 1 03:54:26 2014
Subject: No subject
Message-ID: <mailman.12.1414814066.14999.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sat Nov 1 02:59:31 2014
From: bogus@does.not.exist.com ()
Date: Sat Nov 1 03:54:27 2014
Subject: No subject
Message-ID: <mailman.13.1414814067.14999.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sat Nov 1 02:59:31 2014
From: bogus@does.not.exist.com ()
Date: Sat Nov 1 03:54:27 2014
Subject: No subject
Message-ID: <mailman.14.1414814067.14999.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sat Nov 1 02:59:31 2014
From: bogus@does.not.exist.com ()
Date: Sat Nov 1 03:54:28 2014
Subject: No subject
Message-ID: <mailman.15.1414814068.14999.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sat Nov 1 02:59:31 2014
From: bogus@does.not.exist.com ()
Date: Sat Nov 1 03:54:28 2014
Subject: No subject
Message-ID: <mailman.16.1414814068.14999.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sat Nov 1 02:59:31 2014
From: bogus@does.not.exist.com ()
Date: Sat Nov 1 03:54:29 2014
Subject: No subject
Message-ID: <mailman.17.1414814068.14999.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sat Nov 1 02:59:31 2014
From: bogus@does.not.exist.com ()
Date: Sat Nov 1 03:54:29 2014
Subject: No subject
Message-ID: <mailman.18.1414814069.14999.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sat Nov 1 02:59:31 2014
From: bogus@does.not.exist.com ()
Date: Sat Nov 1 03:54:32 2014
Subject: No subject
Message-ID: <mailman.19.1414814072.14999.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sat Nov 1 02:59:31 2014
From: bogus@does.not.exist.com ()
Date: Sat Nov 1 03:54:33 2014
Subject: No subject
Message-ID: <mailman.20.1414814073.14999.htk-users@eng.cam.ac.uk>

From bogus@does.not.exist.com Sat Nov 1 02:59:31 2014


From: bogus@does.not.exist.com ()
Date: Sat Nov 1 03:54:39 2014
Subject: No subject
Message-ID: <mailman.21.1414814079.14999.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sat Nov 1 02:59:31 2014
From: bogus@does.not.exist.com ()
Date: Sat Nov 1 03:54:42 2014
Subject: No subject
Message-ID: <mailman.22.1414814082.14999.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sat Nov 1 02:59:31 2014
From: bogus@does.not.exist.com ()
Date: Sat Nov 1 03:54:43 2014
Subject: No subject
Message-ID: <mailman.23.1414814083.14999.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sat Nov 1 02:59:31 2014
From: bogus@does.not.exist.com ()
Date: Sat Nov 1 03:54:44 2014
Subject: No subject
Message-ID: <mailman.24.1414814084.14999.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sat Nov 1 02:59:31 2014
From: bogus@does.not.exist.com ()
Date: Sat Nov 1 03:55:00 2014
Subject: No subject
Message-ID: <mailman.25.1414814100.14999.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sat Nov 1 02:59:31 2014
From: bogus@does.not.exist.com ()
Date: Sat Nov 1 03:55:02 2014
Subject: No subject
Message-ID: <mailman.26.1414814102.14999.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sat Nov 1 02:59:31 2014
From: bogus@does.not.exist.com ()
Date: Sat Nov 1 03:55:04 2014
Subject: No subject
Message-ID: <mailman.27.1414814104.14999.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sat Nov 1 02:59:31 2014
From: bogus@does.not.exist.com ()
Date: Sat Nov 1 03:55:04 2014
Subject: No subject
Message-ID: <mailman.28.1414814104.14999.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sat Nov 1 02:59:31 2014
From: bogus@does.not.exist.com ()
Date: Sat Nov 1 03:55:04 2014
Subject: No subject
Message-ID: <mailman.29.1414814104.14999.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sat Nov 1 02:59:31 2014
From: bogus@does.not.exist.com ()
Date: Sat Nov 1 03:55:10 2014
Subject: No subject
Message-ID: <mailman.30.1414814110.14999.htk-users@eng.cam.ac.uk>

From bogus@does.not.exist.com Sat Nov 1 02:59:31 2014


From: bogus@does.not.exist.com ()
Date: Sat Nov 1 03:55:13 2014
Subject: No subject
Message-ID: <mailman.31.1414814113.14999.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sat Nov 1 02:59:31 2014
From: bogus@does.not.exist.com ()
Date: Sat Nov 1 03:55:17 2014
Subject: No subject
Message-ID: <mailman.32.1414814117.14999.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sat Nov 1 02:59:31 2014
From: bogus@does.not.exist.com ()
Date: Sat Nov 1 03:55:19 2014
Subject: No subject
Message-ID: <mailman.33.1414814119.14999.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sat Nov 1 02:59:31 2014
From: bogus@does.not.exist.com ()
Date: Sat Nov 1 03:55:19 2014
Subject: No subject
Message-ID: <mailman.34.1414814119.14999.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sat Nov 1 02:59:31 2014
From: bogus@does.not.exist.com ()
Date: Sat Nov 1 03:55:19 2014
Subject: No subject
Message-ID: <mailman.35.1414814119.14999.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sat Nov 1 02:59:31 2014
From: bogus@does.not.exist.com ()
Date: Sat Nov 1 03:55:20 2014
Subject: No subject
Message-ID: <mailman.36.1414814120.14999.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sat Nov 1 02:59:31 2014
From: bogus@does.not.exist.com ()
Date: Sat Nov 1 03:55:20 2014
Subject: No subject
Message-ID: <mailman.37.1414814120.14999.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sat Nov 1 02:59:31 2014
From: bogus@does.not.exist.com ()
Date: Sat Nov 1 03:55:22 2014
Subject: No subject
Message-ID: <mailman.38.1414814122.14999.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sat Nov 1 02:59:31 2014
From: bogus@does.not.exist.com ()
Date: Sat Nov 1 03:55:22 2014
Subject: No subject
Message-ID: <mailman.39.1414814122.14999.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sat Nov 1 02:59:31 2014
From: bogus@does.not.exist.com ()
Date: Sat Nov 1 03:55:22 2014
Subject: No subject
Message-ID: <mailman.40.1414814122.14999.htk-users@eng.cam.ac.uk>

From bogus@does.not.exist.com Sat Nov 1 02:59:31 2014


From: bogus@does.not.exist.com ()
Date: Sat Nov 1 03:55:27 2014
Subject: No subject
Message-ID: <mailman.41.1414814126.14999.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sat Nov 1 02:59:31 2014
From: bogus@does.not.exist.com ()
Date: Sat Nov 1 03:55:30 2014
Subject: No subject
Message-ID: <mailman.42.1414814130.14999.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sat Nov 1 02:59:31 2014
From: bogus@does.not.exist.com ()
Date: Sat Nov 1 03:55:32 2014
Subject: No subject
Message-ID: <mailman.43.1414814132.14999.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sat Nov 1 02:59:31 2014
From: bogus@does.not.exist.com ()
Date: Sat Nov 1 03:55:32 2014
Subject: No subject
Message-ID: <mailman.44.1414814132.14999.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sat Nov 1 02:59:31 2014
From: bogus@does.not.exist.com ()
Date: Sat Nov 1 03:55:34 2014
Subject: No subject
Message-ID: <mailman.45.1414814134.14999.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sat Nov 1 02:59:31 2014
From: bogus@does.not.exist.com ()
Date: Sat Nov 1 03:55:37 2014
Subject: No subject
Message-ID: <mailman.46.1414814137.14999.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sat Nov 1 02:59:31 2014
From: bogus@does.not.exist.com ()
Date: Sat Nov 1 03:55:39 2014
Subject: No subject
Message-ID: <mailman.47.1414814139.14999.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sat Nov 1 02:59:31 2014
From: bogus@does.not.exist.com ()
Date: Sat Nov 1 03:55:40 2014
Subject: No subject
Message-ID: <mailman.48.1414814140.14999.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sat Nov 1 02:59:31 2014
From: bogus@does.not.exist.com ()
Date: Sat Nov 1 03:55:44 2014
Subject: No subject
Message-ID: <mailman.49.1414814144.14999.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sat Nov 1 02:59:31 2014
From: bogus@does.not.exist.com ()
Date: Sat Nov 1 03:55:47 2014
Subject: No subject
Message-ID: <mailman.50.1414814147.14999.htk-users@eng.cam.ac.uk>

From bogus@does.not.exist.com Sat Nov 1 02:59:31 2014


From: bogus@does.not.exist.com ()
Date: Sat Nov 1 03:55:49 2014
Subject: No subject
Message-ID: <mailman.51.1414814149.14999.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sat Nov 1 02:59:31 2014
From: bogus@does.not.exist.com ()
Date: Sat Nov 1 03:55:52 2014
Subject: No subject
Message-ID: <mailman.52.1414814152.14999.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sat Nov 1 02:59:31 2014
From: bogus@does.not.exist.com ()
Date: Sat Nov 1 03:55:54 2014
Subject: No subject
Message-ID: <mailman.53.1414814154.14999.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sat Nov 1 02:59:31 2014
From: bogus@does.not.exist.com ()
Date: Sat Nov 1 03:55:57 2014
Subject: No subject
Message-ID: <mailman.54.1414814157.14999.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sat Nov 1 02:59:31 2014
From: bogus@does.not.exist.com ()
Date: Sat Nov 1 03:56:01 2014
Subject: No subject
Message-ID: <mailman.55.1414814161.14999.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sat Nov 1 02:59:31 2014
From: bogus@does.not.exist.com ()
Date: Sat Nov 1 03:56:04 2014
Subject: No subject
Message-ID: <mailman.56.1414814164.14999.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sat Nov 1 02:59:31 2014
From: bogus@does.not.exist.com ()
Date: Sat Nov 1 03:56:07 2014
Subject: No subject
Message-ID: <mailman.57.1414814167.14999.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sat Nov 1 02:59:31 2014
From: bogus@does.not.exist.com ()
Date: Sat Nov 1 03:56:09 2014
Subject: No subject
Message-ID: <mailman.58.1414814169.14999.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sat Nov 1 02:59:31 2014
From: bogus@does.not.exist.com ()
Date: Sat Nov 1 03:56:10 2014
Subject: No subject
Message-ID: <mailman.59.1414814170.14999.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sat Nov 1 02:59:31 2014
From: bogus@does.not.exist.com ()
Date: Sat Nov 1 03:56:11 2014
Subject: No subject
Message-ID: <mailman.60.1414814171.14999.htk-users@eng.cam.ac.uk>

From bogus@does.not.exist.com Sat Nov 1 02:59:31 2014


From: bogus@does.not.exist.com ()
Date: Sat Nov 1 03:56:12 2014
Subject: No subject
Message-ID: <mailman.61.1414814172.14999.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sat Nov 1 02:59:31 2014
From: bogus@does.not.exist.com ()
Date: Sat Nov 1 03:56:12 2014
Subject: No subject
Message-ID: <mailman.62.1414814172.14999.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sat Nov 1 02:59:31 2014
From: bogus@does.not.exist.com ()
Date: Sat Nov 1 03:56:13 2014
Subject: No subject
Message-ID: <mailman.63.1414814173.14999.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sat Nov 1 02:59:31 2014
From: bogus@does.not.exist.com ()
Date: Sat Nov 1 03:56:13 2014
Subject: No subject
Message-ID: <mailman.64.1414814173.14999.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sat Nov 1 02:59:31 2014
From: bogus@does.not.exist.com ()
Date: Sat Nov 1 03:56:14 2014
Subject: No subject
Message-ID: <mailman.65.1414814174.14999.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sat Nov 1 02:59:31 2014
From: bogus@does.not.exist.com ()
Date: Sat Nov 1 03:56:14 2014
Subject: No subject
Message-ID: <mailman.66.1414814174.14999.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sat Nov 1 02:59:31 2014
From: bogus@does.not.exist.com ()
Date: Sat Nov 1 03:56:14 2014
Subject: No subject
Message-ID: <mailman.67.1414814174.14999.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sat Nov 1 02:59:31 2014
From: bogus@does.not.exist.com ()
Date: Sat Nov 1 03:56:17 2014
Subject: No subject
Message-ID: <mailman.68.1414814177.14999.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sat Nov 1 02:59:31 2014
From: bogus@does.not.exist.com ()
Date: Sat Nov 1 03:56:17 2014
Subject: No subject
Message-ID: <mailman.69.1414814177.14999.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sat Nov 1 02:59:31 2014
From: bogus@does.not.exist.com ()
Date: Sat Nov 1 03:56:21 2014
Subject: No subject
Message-ID: <mailman.70.1414814181.14999.htk-users@eng.cam.ac.uk>

From bogus@does.not.exist.com Sat Nov 1 02:59:31 2014


From: bogus@does.not.exist.com ()
Date: Sat Nov 1 03:56:21 2014
Subject: No subject
Message-ID: <mailman.71.1414814181.14999.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sat Nov 1 02:59:31 2014
From: bogus@does.not.exist.com ()
Date: Sat Nov 1 03:56:21 2014
Subject: No subject
Message-ID: <mailman.72.1414814181.14999.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sat Nov 1 02:59:31 2014
From: bogus@does.not.exist.com ()
Date: Sat Nov 1 03:56:22 2014
Subject: No subject
Message-ID: <mailman.73.1414814182.14999.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sat Nov 1 02:59:31 2014
From: bogus@does.not.exist.com ()
Date: Sat Nov 1 03:56:22 2014
Subject: No subject
Message-ID: <mailman.74.1414814182.14999.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sat Nov 1 02:59:31 2014
From: bogus@does.not.exist.com ()
Date: Sat Nov 1 03:56:23 2014
Subject: No subject
Message-ID: <mailman.75.1414814183.14999.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sat Nov 1 02:59:31 2014
From: bogus@does.not.exist.com ()
Date: Sat Nov 1 03:56:23 2014
Subject: No subject
Message-ID: <mailman.76.1414814183.14999.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sat Nov 1 02:59:31 2014
From: bogus@does.not.exist.com ()
Date: Sat Nov 1 03:56:23 2014
Subject: No subject
Message-ID: <mailman.77.1414814183.14999.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sat Nov 1 02:59:31 2014
From: bogus@does.not.exist.com ()
Date: Sat Nov 1 03:56:24 2014
Subject: No subject
Message-ID: <mailman.78.1414814184.14999.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sat Nov 1 02:59:31 2014
From: bogus@does.not.exist.com ()
Date: Sat Nov 1 03:56:25 2014
Subject: No subject
Message-ID: <mailman.79.1414814185.14999.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sat Nov 1 02:59:31 2014
From: bogus@does.not.exist.com ()
Date: Sat Nov 1 03:56:25 2014
Subject: No subject
Message-ID: <mailman.80.1414814185.14999.htk-users@eng.cam.ac.uk>

From bogus@does.not.exist.com Sat Nov 1 02:59:31 2014


From: bogus@does.not.exist.com ()
Date: Sat Nov 1 03:56:25 2014
Subject: No subject
Message-ID: <mailman.81.1414814185.14999.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sat Nov 1 02:59:31 2014
From: bogus@does.not.exist.com ()
Date: Sat Nov 1 03:56:26 2014
Subject: No subject
Message-ID: <mailman.82.1414814186.14999.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sat Nov 1 02:59:31 2014
From: bogus@does.not.exist.com ()
Date: Sat Nov 1 03:56:26 2014
Subject: No subject
Message-ID: <mailman.83.1414814186.14999.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sat Nov 1 02:59:31 2014
From: bogus@does.not.exist.com ()
Date: Sat Nov 1 03:56:27 2014
Subject: No subject
Message-ID: <mailman.84.1414814187.14999.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sat Nov 1 02:59:31 2014
From: bogus@does.not.exist.com ()
Date: Sat Nov 1 03:56:28 2014
Subject: No subject
Message-ID: <mailman.85.1414814188.14999.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sat Nov 1 02:59:31 2014
From: bogus@does.not.exist.com ()
Date: Sat Nov 1 03:56:30 2014
Subject: No subject
Message-ID: <mailman.86.1414814190.14999.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sat Nov 1 02:59:31 2014
From: bogus@does.not.exist.com ()
Date: Sat Nov 1 03:56:30 2014
Subject: No subject
Message-ID: <mailman.87.1414814190.14999.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sat Nov 1 02:59:31 2014
From: bogus@does.not.exist.com ()
Date: Sat Nov 1 03:56:31 2014
Subject: No subject
Message-ID: <mailman.88.1414814191.14999.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sat Nov 1 02:59:31 2014
From: bogus@does.not.exist.com ()
Date: Sat Nov 1 03:56:32 2014
Subject: No subject
Message-ID: <mailman.89.1414814192.14999.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sat Nov 1 02:59:31 2014
From: bogus@does.not.exist.com ()
Date: Sat Nov 1 03:56:33 2014
Subject: No subject
Message-ID: <mailman.91.1414814193.14999.htk-users@eng.cam.ac.uk>

From bogus@does.not.exist.com Sat Nov 1 02:59:31 2014


From: bogus@does.not.exist.com ()
Date: Sat Nov 1 03:56:41 2014
Subject: No subject
Message-ID: <mailman.92.1414814201.14999.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sat Nov 1 02:59:31 2014
From: bogus@does.not.exist.com ()
Date: Sat Nov 1 03:56:44 2014
Subject: No subject
Message-ID: <mailman.93.1414814204.14999.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sat Nov 1 02:59:31 2014
From: bogus@does.not.exist.com ()
Date: Sat Nov 1 03:56:48 2014
Subject: No subject
Message-ID: <mailman.94.1414814207.14999.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sat Nov 1 02:59:31 2014
From: bogus@does.not.exist.com ()
Date: Sat Nov 1 03:56:51 2014
Subject: No subject
Message-ID: <mailman.95.1414814211.14999.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sat Nov 1 02:59:31 2014
From: bogus@does.not.exist.com ()
Date: Sat Nov 1 03:56:54 2014
Subject: No subject
Message-ID: <mailman.96.1414814214.14999.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sat Nov 1 02:59:31 2014
From: bogus@does.not.exist.com ()
Date: Sat Nov 1 03:57:02 2014
Subject: No subject
Message-ID: <mailman.97.1414814222.14999.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sat Nov 1 02:59:31 2014
From: bogus@does.not.exist.com ()
Date: Sat Nov 1 03:57:05 2014
Subject: No subject
Message-ID: <mailman.98.1414814225.14999.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sat Nov 1 02:59:31 2014
From: bogus@does.not.exist.com ()
Date: Sat Nov 1 03:57:10 2014
Subject: No subject
Message-ID: <mailman.99.1414814230.14999.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sat Nov 1 02:59:31 2014
From: bogus@does.not.exist.com ()
Date: Sat Nov 1 03:57:11 2014
Subject: No subject
Message-ID: <mailman.100.1414814231.14999.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sat Nov 1 02:59:31 2014
From: bogus@does.not.exist.com ()
Date: Sat Nov 1 03:57:12 2014
Subject: No subject
Message-ID: <mailman.101.1414814231.14999.htk-users@eng.cam.ac.uk>

From bogus@does.not.exist.com Sat Nov 1 02:59:31 2014


From: bogus@does.not.exist.com ()
Date: Sat Nov 1 03:57:12 2014
Subject: No subject
Message-ID: <mailman.102.1414814232.14999.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sat Nov 1 02:59:31 2014
From: bogus@does.not.exist.com ()
Date: Sat Nov 1 03:57:13 2014
Subject: No subject
Message-ID: <mailman.103.1414814233.14999.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sun Nov 2 02:54:21 2014
From: bogus@does.not.exist.com ()
Date: Sun Nov 2 03:47:44 2014
Subject: No subject
Message-ID: <mailman.1.1414900064.26491.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sun Nov 2 02:54:21 2014
From: bogus@does.not.exist.com ()
Date: Sun Nov 2 03:47:49 2014
Subject: No subject
Message-ID: <mailman.2.1414900069.26491.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sun Nov 2 02:54:21 2014
From: bogus@does.not.exist.com ()
Date: Sun Nov 2 03:47:49 2014
Subject: No subject
Message-ID: <mailman.3.1414900069.26491.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sun Nov 2 02:54:21 2014
From: bogus@does.not.exist.com ()
Date: Sun Nov 2 03:47:50 2014
Subject: No subject
Message-ID: <mailman.4.1414900070.26491.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sun Nov 2 02:54:21 2014
From: bogus@does.not.exist.com ()
Date: Sun Nov 2 03:47:50 2014
Subject: No subject
Message-ID: <mailman.5.1414900070.26491.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sun Nov 2 02:54:21 2014
From: bogus@does.not.exist.com ()
Date: Sun Nov 2 03:47:50 2014
Subject: No subject
Message-ID: <mailman.6.1414900070.26491.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sun Nov 2 02:54:21 2014
From: bogus@does.not.exist.com ()
Date: Sun Nov 2 03:47:51 2014
Subject: No subject
Message-ID: <mailman.7.1414900071.26491.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sun Nov 2 02:54:21 2014
From: bogus@does.not.exist.com ()
Date: Sun Nov 2 03:47:51 2014
Subject: No subject
Message-ID: <mailman.8.1414900071.26491.htk-users@eng.cam.ac.uk>

From bogus@does.not.exist.com Sun Nov 2 02:54:21 2014


From: bogus@does.not.exist.com ()
Date: Sun Nov 2 03:47:51 2014
Subject: No subject
Message-ID: <mailman.9.1414900071.26491.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sun Nov 2 02:54:21 2014
From: bogus@does.not.exist.com ()
Date: Sun Nov 2 03:47:54 2014
Subject: No subject
Message-ID: <mailman.10.1414900074.26491.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sun Nov 2 02:54:21 2014
From: bogus@does.not.exist.com ()
Date: Sun Nov 2 03:47:54 2014
Subject: No subject
Message-ID: <mailman.11.1414900074.26491.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sun Nov 2 02:54:21 2014
From: bogus@does.not.exist.com ()
Date: Sun Nov 2 03:47:56 2014
Subject: No subject
Message-ID: <mailman.12.1414900076.26491.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sun Nov 2 02:54:21 2014
From: bogus@does.not.exist.com ()
Date: Sun Nov 2 03:47:56 2014
Subject: No subject
Message-ID: <mailman.13.1414900076.26491.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sun Nov 2 02:54:21 2014
From: bogus@does.not.exist.com ()
Date: Sun Nov 2 03:47:56 2014
Subject: No subject
Message-ID: <mailman.14.1414900076.26491.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sun Nov 2 02:54:21 2014
From: bogus@does.not.exist.com ()
Date: Sun Nov 2 03:47:57 2014
Subject: No subject
Message-ID: <mailman.15.1414900077.26491.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sun Nov 2 02:54:21 2014
From: bogus@does.not.exist.com ()
Date: Sun Nov 2 03:48:03 2014
Subject: No subject
Message-ID: <mailman.16.1414900083.26491.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sun Nov 2 02:54:21 2014
From: bogus@does.not.exist.com ()
Date: Sun Nov 2 03:48:08 2014
Subject: No subject
Message-ID: <mailman.17.1414900088.26491.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sun Nov 2 02:54:21 2014
From: bogus@does.not.exist.com ()
Date: Sun Nov 2 03:48:09 2014
Subject: No subject
Message-ID: <mailman.18.1414900089.26491.htk-users@eng.cam.ac.uk>

From bogus@does.not.exist.com Sun Nov 2 02:54:21 2014


From: bogus@does.not.exist.com ()
Date: Sun Nov 2 03:48:14 2014
Subject: No subject
Message-ID: <mailman.19.1414900094.26491.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sun Nov 2 02:54:21 2014
From: bogus@does.not.exist.com ()
Date: Sun Nov 2 03:48:18 2014
Subject: No subject
Message-ID: <mailman.20.1414900098.26491.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sun Nov 2 02:54:21 2014
From: bogus@does.not.exist.com ()
Date: Sun Nov 2 03:48:25 2014
Subject: No subject
Message-ID: <mailman.21.1414900105.26491.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sun Nov 2 02:54:21 2014
From: bogus@does.not.exist.com ()
Date: Sun Nov 2 03:48:30 2014
Subject: No subject
Message-ID: <mailman.22.1414900110.26491.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sun Nov 2 02:54:21 2014
From: bogus@does.not.exist.com ()
Date: Sun Nov 2 03:48:31 2014
Subject: No subject
Message-ID: <mailman.23.1414900111.26491.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sun Nov 2 02:54:21 2014
From: bogus@does.not.exist.com ()
Date: Sun Nov 2 03:48:33 2014
Subject: No subject
Message-ID: <mailman.24.1414900113.26491.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sun Nov 2 02:54:21 2014
From: bogus@does.not.exist.com ()
Date: Sun Nov 2 03:48:35 2014
Subject: No subject
Message-ID: <mailman.25.1414900115.26491.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sun Nov 2 02:54:21 2014
From: bogus@does.not.exist.com ()
Date: Sun Nov 2 03:48:35 2014
Subject: No subject
Message-ID: <mailman.26.1414900115.26491.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sun Nov 2 02:54:21 2014
From: bogus@does.not.exist.com ()
Date: Sun Nov 2 03:48:35 2014
Subject: No subject
Message-ID: <mailman.27.1414900115.26491.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sun Nov 2 02:54:21 2014
From: bogus@does.not.exist.com ()
Date: Sun Nov 2 03:48:36 2014
Subject: No subject
Message-ID: <mailman.28.1414900116.26491.htk-users@eng.cam.ac.uk>

From bogus@does.not.exist.com Sun Nov 2 02:54:21 2014


From: bogus@does.not.exist.com ()
Date: Sun Nov 2 03:48:36 2014
Subject: No subject
Message-ID: <mailman.29.1414900116.26491.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sun Nov 2 02:54:21 2014
From: bogus@does.not.exist.com ()
Date: Sun Nov 2 03:48:42 2014
Subject: No subject
Message-ID: <mailman.30.1414900122.26491.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sun Nov 2 02:54:21 2014
From: bogus@does.not.exist.com ()
Date: Sun Nov 2 03:48:53 2014
Subject: No subject
Message-ID: <mailman.31.1414900133.26491.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sun Nov 2 02:54:21 2014
From: bogus@does.not.exist.com ()
Date: Sun Nov 2 03:48:55 2014
Subject: No subject
Message-ID: <mailman.32.1414900135.26491.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sun Nov 2 02:54:21 2014
From: bogus@does.not.exist.com ()
Date: Sun Nov 2 03:49:04 2014
Subject: No subject
Message-ID: <mailman.33.1414900144.26491.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sun Nov 2 02:54:21 2014
From: bogus@does.not.exist.com ()
Date: Sun Nov 2 03:49:07 2014
Subject: No subject
Message-ID: <mailman.34.1414900147.26491.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sun Nov 2 02:54:21 2014
From: bogus@does.not.exist.com ()
Date: Sun Nov 2 03:49:10 2014
Subject: No subject
Message-ID: <mailman.35.1414900150.26491.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sun Nov 2 02:54:21 2014
From: bogus@does.not.exist.com ()
Date: Sun Nov 2 03:49:12 2014
Subject: No subject
Message-ID: <mailman.36.1414900152.26491.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sun Nov 2 02:54:21 2014
From: bogus@does.not.exist.com ()
Date: Sun Nov 2 03:49:15 2014
Subject: No subject
Message-ID: <mailman.37.1414900155.26491.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sun Nov 2 02:54:21 2014
From: bogus@does.not.exist.com ()
Date: Sun Nov 2 03:49:17 2014
Subject: No subject
Message-ID: <mailman.38.1414900157.26491.htk-users@eng.cam.ac.uk>

From bogus@does.not.exist.com Sun Nov 2 02:54:21 2014


From: bogus@does.not.exist.com ()
Date: Sun Nov 2 03:49:17 2014
Subject: No subject
Message-ID: <mailman.39.1414900157.26491.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sun Nov 2 02:54:21 2014
From: bogus@does.not.exist.com ()
Date: Sun Nov 2 03:49:18 2014
Subject: No subject
Message-ID: <mailman.40.1414900158.26491.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sun Nov 2 02:54:21 2014
From: bogus@does.not.exist.com ()
Date: Sun Nov 2 03:49:21 2014
Subject: No subject
Message-ID: <mailman.41.1414900161.26491.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sun Nov 2 02:54:21 2014
From: bogus@does.not.exist.com ()
Date: Sun Nov 2 03:49:21 2014
Subject: No subject
Message-ID: <mailman.42.1414900161.26491.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sun Nov 2 02:54:21 2014
From: bogus@does.not.exist.com ()
Date: Sun Nov 2 03:49:21 2014
Subject: No subject
Message-ID: <mailman.43.1414900161.26491.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sun Nov 2 02:54:21 2014
From: bogus@does.not.exist.com ()
Date: Sun Nov 2 03:49:22 2014
Subject: No subject
Message-ID: <mailman.44.1414900162.26491.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sun Nov 2 02:54:21 2014
From: bogus@does.not.exist.com ()
Date: Sun Nov 2 03:49:23 2014
Subject: No subject
Message-ID: <mailman.45.1414900163.26491.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sun Nov 2 02:54:21 2014
From: bogus@does.not.exist.com ()
Date: Sun Nov 2 03:49:24 2014
Subject: No subject
Message-ID: <mailman.46.1414900164.26491.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sun Nov 2 02:54:21 2014
From: bogus@does.not.exist.com ()
Date: Sun Nov 2 03:49:24 2014
Subject: No subject
Message-ID: <mailman.47.1414900164.26491.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sun Nov 2 02:54:21 2014
From: bogus@does.not.exist.com ()
Date: Sun Nov 2 03:49:25 2014
Subject: No subject
Message-ID: <mailman.48.1414900165.26491.htk-users@eng.cam.ac.uk>

From bogus@does.not.exist.com Sun Nov 2 02:54:21 2014


From: bogus@does.not.exist.com ()
Date: Sun Nov 2 03:49:26 2014
Subject: No subject
Message-ID: <mailman.49.1414900166.26491.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sun Nov 2 02:54:21 2014
From: bogus@does.not.exist.com ()
Date: Sun Nov 2 03:49:27 2014
Subject: No subject
Message-ID: <mailman.50.1414900167.26491.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sun Nov 2 02:54:21 2014
From: bogus@does.not.exist.com ()
Date: Sun Nov 2 03:49:27 2014
Subject: No subject
Message-ID: <mailman.51.1414900167.26491.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sun Nov 2 02:54:21 2014
From: bogus@does.not.exist.com ()
Date: Sun Nov 2 03:49:28 2014
Subject: No subject
Message-ID: <mailman.52.1414900168.26491.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sun Nov 2 02:54:21 2014
From: bogus@does.not.exist.com ()
Date: Sun Nov 2 03:49:28 2014
Subject: No subject
Message-ID: <mailman.53.1414900168.26491.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sun Nov 2 02:54:21 2014
From: bogus@does.not.exist.com ()
Date: Sun Nov 2 03:49:28 2014
Subject: No subject
Message-ID: <mailman.54.1414900168.26491.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sun Nov 2 02:54:21 2014
From: bogus@does.not.exist.com ()
Date: Sun Nov 2 03:49:29 2014
Subject: No subject
Message-ID: <mailman.55.1414900169.26491.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sun Nov 2 02:54:21 2014
From: bogus@does.not.exist.com ()
Date: Sun Nov 2 03:49:29 2014
Subject: No subject
Message-ID: <mailman.56.1414900169.26491.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sun Nov 2 02:54:21 2014
From: bogus@does.not.exist.com ()
Date: Sun Nov 2 03:49:29 2014
Subject: No subject
Message-ID: <mailman.57.1414900169.26491.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sun Nov 2 02:54:21 2014
From: bogus@does.not.exist.com ()
Date: Sun Nov 2 03:49:30 2014
Subject: No subject
Message-ID: <mailman.58.1414900170.26491.htk-users@eng.cam.ac.uk>

From bogus@does.not.exist.com Sun Nov 2 02:54:21 2014


From: bogus@does.not.exist.com ()
Date: Sun Nov 2 03:49:30 2014
Subject: No subject
Message-ID: <mailman.59.1414900170.26491.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sun Nov 2 02:54:21 2014
From: bogus@does.not.exist.com ()
Date: Sun Nov 2 03:49:30 2014
Subject: No subject
Message-ID: <mailman.60.1414900170.26491.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sun Nov 2 02:54:21 2014
From: bogus@does.not.exist.com ()
Date: Sun Nov 2 03:49:31 2014
Subject: No subject
Message-ID: <mailman.61.1414900171.26491.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sun Nov 2 02:54:21 2014
From: bogus@does.not.exist.com ()
Date: Sun Nov 2 03:49:31 2014
Subject: No subject
Message-ID: <mailman.62.1414900171.26491.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sun Nov 2 02:54:21 2014
From: bogus@does.not.exist.com ()
Date: Sun Nov 2 03:49:31 2014
Subject: No subject
Message-ID: <mailman.63.1414900171.26491.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sun Nov 2 02:54:21 2014
From: bogus@does.not.exist.com ()
Date: Sun Nov 2 03:49:31 2014
Subject: No subject
Message-ID: <mailman.64.1414900171.26491.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sun Nov 2 02:54:21 2014
From: bogus@does.not.exist.com ()
Date: Sun Nov 2 03:49:32 2014
Subject: No subject
Message-ID: <mailman.65.1414900172.26491.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sun Nov 2 02:54:21 2014
From: bogus@does.not.exist.com ()
Date: Sun Nov 2 03:49:32 2014
Subject: No subject
Message-ID: <mailman.66.1414900172.26491.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sun Nov 2 02:54:21 2014
From: bogus@does.not.exist.com ()
Date: Sun Nov 2 03:49:33 2014
Subject: No subject
Message-ID: <mailman.67.1414900172.26491.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sun Nov 2 02:54:21 2014
From: bogus@does.not.exist.com ()
Date: Sun Nov 2 03:49:33 2014
Subject: No subject
Message-ID: <mailman.68.1414900173.26491.htk-users@eng.cam.ac.uk>

From bogus@does.not.exist.com Sun Nov 2 02:54:21 2014


From: bogus@does.not.exist.com ()
Date: Sun Nov 2 03:49:34 2014
Subject: No subject
Message-ID: <mailman.69.1414900174.26491.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sun Nov 2 02:54:21 2014
From: bogus@does.not.exist.com ()
Date: Sun Nov 2 03:49:35 2014
Subject: No subject
Message-ID: <mailman.70.1414900175.26491.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sun Nov 2 02:54:21 2014
From: bogus@does.not.exist.com ()
Date: Sun Nov 2 03:49:39 2014
Subject: No subject
Message-ID: <mailman.71.1414900179.26491.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sun Nov 2 02:54:21 2014
From: bogus@does.not.exist.com ()
Date: Sun Nov 2 03:49:42 2014
Subject: No subject
Message-ID: <mailman.72.1414900182.26491.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sun Nov 2 02:54:21 2014
From: bogus@does.not.exist.com ()
Date: Sun Nov 2 03:49:45 2014
Subject: No subject
Message-ID: <mailman.73.1414900185.26491.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sun Nov 2 02:54:21 2014
From: bogus@does.not.exist.com ()
Date: Sun Nov 2 03:49:50 2014
Subject: No subject
Message-ID: <mailman.74.1414900190.26491.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sun Nov 2 02:54:21 2014
From: bogus@does.not.exist.com ()
Date: Sun Nov 2 03:49:52 2014
Subject: No subject
Message-ID: <mailman.75.1414900192.26491.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sun Nov 2 02:54:21 2014
From: bogus@does.not.exist.com ()
Date: Sun Nov 2 03:49:52 2014
Subject: No subject
Message-ID: <mailman.76.1414900192.26491.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sun Nov 2 02:54:21 2014
From: bogus@does.not.exist.com ()
Date: Sun Nov 2 03:49:53 2014
Subject: No subject
Message-ID: <mailman.77.1414900193.26491.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sun Nov 2 02:54:21 2014
From: bogus@does.not.exist.com ()
Date: Sun Nov 2 03:49:53 2014
Subject: No subject
Message-ID: <mailman.78.1414900193.26491.htk-users@eng.cam.ac.uk>

From bogus@does.not.exist.com Sun Nov 2 02:54:21 2014


From: bogus@does.not.exist.com ()
Date: Sun Nov 2 03:49:54 2014
Subject: No subject
Message-ID: <mailman.79.1414900194.26491.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sun Nov 2 02:54:21 2014
From: bogus@does.not.exist.com ()
Date: Sun Nov 2 03:49:54 2014
Subject: No subject
Message-ID: <mailman.80.1414900194.26491.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sun Nov 2 02:54:21 2014
From: bogus@does.not.exist.com ()
Date: Sun Nov 2 03:49:54 2014
Subject: No subject
Message-ID: <mailman.81.1414900194.26491.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sun Nov 2 02:54:21 2014
From: bogus@does.not.exist.com ()
Date: Sun Nov 2 03:49:55 2014
Subject: No subject
Message-ID: <mailman.82.1414900195.26491.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sun Nov 2 02:54:21 2014
From: bogus@does.not.exist.com ()
Date: Sun Nov 2 03:49:55 2014
Subject: No subject
Message-ID: <mailman.83.1414900195.26491.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sun Nov 2 02:54:21 2014
From: bogus@does.not.exist.com ()
Date: Sun Nov 2 03:49:56 2014
Subject: No subject
Message-ID: <mailman.84.1414900196.26491.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sun Nov 2 02:54:21 2014
From: bogus@does.not.exist.com ()
Date: Sun Nov 2 03:50:00 2014
Subject: No subject
Message-ID: <mailman.85.1414900200.26491.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sun Nov 2 02:54:21 2014
From: bogus@does.not.exist.com ()
Date: Sun Nov 2 03:50:06 2014
Subject: No subject
Message-ID: <mailman.86.1414900206.26491.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sun Nov 2 02:54:21 2014
From: bogus@does.not.exist.com ()
Date: Sun Nov 2 03:50:09 2014
Subject: No subject
Message-ID: <mailman.87.1414900209.26491.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sun Nov 2 02:54:21 2014
From: bogus@does.not.exist.com ()
Date: Sun Nov 2 03:50:12 2014
Subject: No subject
Message-ID: <mailman.88.1414900212.26491.htk-users@eng.cam.ac.uk>

From bogus@does.not.exist.com Sun Nov 2 02:54:21 2014


From: bogus@does.not.exist.com ()
Date: Sun Nov 2 03:50:16 2014
Subject: No subject
Message-ID: <mailman.89.1414900216.26491.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sun Nov 2 02:54:21 2014
From: bogus@does.not.exist.com ()
Date: Sun Nov 2 03:50:19 2014
Subject: No subject
Message-ID: <mailman.91.1414900219.26491.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sun Nov 2 02:54:21 2014
From: bogus@does.not.exist.com ()
Date: Sun Nov 2 03:50:22 2014
Subject: No subject
Message-ID: <mailman.92.1414900222.26491.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sun Nov 2 02:54:21 2014
From: bogus@does.not.exist.com ()
Date: Sun Nov 2 03:50:25 2014
Subject: No subject
Message-ID: <mailman.93.1414900225.26491.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sun Nov 2 02:54:21 2014
From: bogus@does.not.exist.com ()
Date: Sun Nov 2 03:50:29 2014
Subject: No subject
Message-ID: <mailman.94.1414900229.26491.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sun Nov 2 02:54:21 2014
From: bogus@does.not.exist.com ()
Date: Sun Nov 2 03:50:29 2014
Subject: No subject
Message-ID: <mailman.95.1414900229.26491.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sun Nov 2 02:54:21 2014
From: bogus@does.not.exist.com ()
Date: Sun Nov 2 03:50:30 2014
Subject: No subject
Message-ID: <mailman.96.1414900230.26491.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sun Nov 2 02:54:21 2014
From: bogus@does.not.exist.com ()
Date: Sun Nov 2 03:50:32 2014
Subject: No subject
Message-ID: <mailman.97.1414900232.26491.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sun Nov 2 02:54:21 2014
From: bogus@does.not.exist.com ()
Date: Sun Nov 2 03:50:33 2014
Subject: No subject
Message-ID: <mailman.98.1414900233.26491.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sun Nov 2 02:54:21 2014
From: bogus@does.not.exist.com ()
Date: Sun Nov 2 03:50:35 2014
Subject: No subject
Message-ID: <mailman.99.1414900235.26491.htk-users@eng.cam.ac.uk>

From bogus@does.not.exist.com Sun Nov 2 02:54:21 2014


From: bogus@does.not.exist.com ()
Date: Sun Nov 2 03:50:35 2014
Subject: No subject
Message-ID: <mailman.100.1414900235.26491.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sun Nov 2 02:54:21 2014
From: bogus@does.not.exist.com ()
Date: Sun Nov 2 03:50:36 2014
Subject: No subject
Message-ID: <mailman.101.1414900236.26491.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sun Nov 2 02:54:21 2014
From: bogus@does.not.exist.com ()
Date: Sun Nov 2 03:50:37 2014
Subject: No subject
Message-ID: <mailman.102.1414900237.26491.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sun Nov 2 02:54:21 2014
From: bogus@does.not.exist.com ()
Date: Sun Nov 2 03:50:39 2014
Subject: No subject
Message-ID: <mailman.103.1414900239.26491.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Mon Nov 3 02:50:36 2014
From: bogus@does.not.exist.com ()
Date: Mon Nov 3 03:41:26 2014
Subject: No subject
Message-ID: <mailman.1.1414986086.6321.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Mon Nov 3 02:50:36 2014
From: bogus@does.not.exist.com ()
Date: Mon Nov 3 03:41:29 2014
Subject: No subject
Message-ID: <mailman.2.1414986089.6321.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Mon Nov 3 02:50:36 2014
From: bogus@does.not.exist.com ()
Date: Mon Nov 3 03:41:29 2014
Subject: No subject
Message-ID: <mailman.3.1414986089.6321.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Mon Nov 3 02:50:36 2014
From: bogus@does.not.exist.com ()
Date: Mon Nov 3 03:41:30 2014
Subject: No subject
Message-ID: <mailman.4.1414986090.6321.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Mon Nov 3 02:50:36 2014
From: bogus@does.not.exist.com ()
Date: Mon Nov 3 03:41:31 2014
Subject: No subject
Message-ID: <mailman.5.1414986090.6321.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Mon Nov 3 02:50:36 2014
From: bogus@does.not.exist.com ()
Date: Mon Nov 3 03:41:31 2014
Subject: No subject
Message-ID: <mailman.6.1414986091.6321.htk-users@eng.cam.ac.uk>

From bogus@does.not.exist.com Mon Nov 3 02:50:36 2014


From: bogus@does.not.exist.com ()
Date: Mon Nov 3 03:41:31 2014
Subject: No subject
Message-ID: <mailman.7.1414986091.6321.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Mon Nov 3 02:50:36 2014
From: bogus@does.not.exist.com ()
Date: Mon Nov 3 03:41:32 2014
Subject: No subject
Message-ID: <mailman.8.1414986092.6321.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Mon Nov 3 02:50:36 2014
From: bogus@does.not.exist.com ()
Date: Mon Nov 3 03:41:32 2014
Subject: No subject
Message-ID: <mailman.9.1414986092.6321.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Mon Nov 3 02:50:36 2014
From: bogus@does.not.exist.com ()
Date: Mon Nov 3 03:41:35 2014
Subject: No subject
Message-ID: <mailman.10.1414986095.6321.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Mon Nov 3 02:50:36 2014
From: bogus@does.not.exist.com ()
Date: Mon Nov 3 03:41:35 2014
Subject: No subject
Message-ID: <mailman.11.1414986095.6321.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Mon Nov 3 02:50:36 2014
From: bogus@does.not.exist.com ()
Date: Mon Nov 3 03:41:37 2014
Subject: No subject
Message-ID: <mailman.12.1414986097.6321.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Mon Nov 3 02:50:36 2014
From: bogus@does.not.exist.com ()
Date: Mon Nov 3 03:41:37 2014
Subject: No subject
Message-ID: <mailman.13.1414986097.6321.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Mon Nov 3 02:50:36 2014
From: bogus@does.not.exist.com ()
Date: Mon Nov 3 03:41:38 2014
Subject: No subject
Message-ID: <mailman.14.1414986098.6321.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Mon Nov 3 02:50:36 2014
From: bogus@does.not.exist.com ()
Date: Mon Nov 3 03:41:39 2014
Subject: No subject
Message-ID: <mailman.15.1414986099.6321.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Mon Nov 3 02:50:36 2014
From: bogus@does.not.exist.com ()
Date: Mon Nov 3 03:41:39 2014
Subject: No subject
Message-ID: <mailman.16.1414986099.6321.htk-users@eng.cam.ac.uk>

From bogus@does.not.exist.com Mon Nov 3 02:50:36 2014


From: bogus@does.not.exist.com ()
Date: Mon Nov 3 03:41:39 2014
Subject: No subject
Message-ID: <mailman.17.1414986099.6321.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Mon Nov 3 02:50:36 2014
From: bogus@does.not.exist.com ()
Date: Mon Nov 3 03:41:46 2014
Subject: No subject
Message-ID: <mailman.18.1414986106.6321.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Mon Nov 3 02:50:36 2014
From: bogus@does.not.exist.com ()
Date: Mon Nov 3 03:41:52 2014
Subject: No subject
Message-ID: <mailman.19.1414986112.6321.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Mon Nov 3 02:50:36 2014
From: bogus@does.not.exist.com ()
Date: Mon Nov 3 03:41:55 2014
Subject: No subject
Message-ID: <mailman.20.1414986115.6321.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Mon Nov 3 02:50:36 2014
From: bogus@does.not.exist.com ()
Date: Mon Nov 3 03:42:02 2014
Subject: No subject
Message-ID: <mailman.21.1414986122.6321.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Mon Nov 3 02:50:36 2014
From: bogus@does.not.exist.com ()
Date: Mon Nov 3 03:42:07 2014
Subject: No subject
Message-ID: <mailman.22.1414986127.6321.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Mon Nov 3 02:50:36 2014
From: bogus@does.not.exist.com ()
Date: Mon Nov 3 03:42:10 2014
Subject: No subject
Message-ID: <mailman.23.1414986130.6321.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Mon Nov 3 02:50:36 2014
From: bogus@does.not.exist.com ()
Date: Mon Nov 3 03:42:15 2014
Subject: No subject
Message-ID: <mailman.24.1414986135.6321.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Mon Nov 3 02:50:36 2014
From: bogus@does.not.exist.com ()
Date: Mon Nov 3 03:42:20 2014
Subject: No subject
Message-ID: <mailman.25.1414986140.6321.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Mon Nov 3 02:50:36 2014
From: bogus@does.not.exist.com ()
Date: Mon Nov 3 03:42:21 2014
Subject: No subject
Message-ID: <mailman.26.1414986141.6321.htk-users@eng.cam.ac.uk>

From bogus@does.not.exist.com Mon Nov 3 02:50:36 2014


From: bogus@does.not.exist.com ()
Date: Mon Nov 3 03:42:21 2014
Subject: No subject
Message-ID: <mailman.27.1414986141.6321.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Mon Nov 3 02:50:36 2014
From: bogus@does.not.exist.com ()
Date: Mon Nov 3 03:42:22 2014
Subject: No subject
Message-ID: <mailman.28.1414986142.6321.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Mon Nov 3 02:50:36 2014
From: bogus@does.not.exist.com ()
Date: Mon Nov 3 03:42:22 2014
Subject: No subject
Message-ID: <mailman.29.1414986142.6321.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Mon Nov 3 02:50:36 2014
From: bogus@does.not.exist.com ()
Date: Mon Nov 3 03:42:25 2014
Subject: No subject
Message-ID: <mailman.30.1414986145.6321.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Mon Nov 3 02:50:36 2014
From: bogus@does.not.exist.com ()
Date: Mon Nov 3 03:42:25 2014
Subject: No subject
Message-ID: <mailman.31.1414986145.6321.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Mon Nov 3 02:50:36 2014
From: bogus@does.not.exist.com ()
Date: Mon Nov 3 03:42:26 2014
Subject: No subject
Message-ID: <mailman.32.1414986146.6321.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Mon Nov 3 02:50:36 2014
From: bogus@does.not.exist.com ()
Date: Mon Nov 3 03:42:27 2014
Subject: No subject
Message-ID: <mailman.33.1414986147.6321.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Mon Nov 3 02:50:36 2014
From: bogus@does.not.exist.com ()
Date: Mon Nov 3 03:42:28 2014
Subject: No subject
Message-ID: <mailman.34.1414986148.6321.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Mon Nov 3 02:50:36 2014
From: bogus@does.not.exist.com ()
Date: Mon Nov 3 03:42:28 2014
Subject: No subject
Message-ID: <mailman.35.1414986148.6321.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Mon Nov 3 02:50:36 2014
From: bogus@does.not.exist.com ()
Date: Mon Nov 3 03:42:28 2014
Subject: No subject
Message-ID: <mailman.36.1414986148.6321.htk-users@eng.cam.ac.uk>

From bogus@does.not.exist.com Mon Nov 3 02:50:36 2014


From: bogus@does.not.exist.com ()
Date: Mon Nov 3 03:42:29 2014
Subject: No subject
Message-ID: <mailman.37.1414986149.6321.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Mon Nov 3 02:50:36 2014
From: bogus@does.not.exist.com ()
Date: Mon Nov 3 03:42:31 2014
Subject: No subject
Message-ID: <mailman.38.1414986151.6321.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Mon Nov 3 02:50:36 2014
From: bogus@does.not.exist.com ()
Date: Mon Nov 3 03:42:31 2014
Subject: No subject
Message-ID: <mailman.39.1414986151.6321.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Mon Nov 3 02:50:36 2014
From: bogus@does.not.exist.com ()
Date: Mon Nov 3 03:42:32 2014
Subject: No subject
Message-ID: <mailman.40.1414986152.6321.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Mon Nov 3 02:50:36 2014
From: bogus@does.not.exist.com ()
Date: Mon Nov 3 03:42:34 2014
Subject: No subject
Message-ID: <mailman.41.1414986154.6321.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Mon Nov 3 02:50:36 2014
From: bogus@does.not.exist.com ()
Date: Mon Nov 3 03:42:35 2014
Subject: No subject
Message-ID: <mailman.42.1414986155.6321.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Mon Nov 3 02:50:36 2014
From: bogus@does.not.exist.com ()
Date: Mon Nov 3 03:42:36 2014
Subject: No subject
Message-ID: <mailman.43.1414986156.6321.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Mon Nov 3 02:50:36 2014
From: bogus@does.not.exist.com ()
Date: Mon Nov 3 03:42:36 2014
Subject: No subject
Message-ID: <mailman.44.1414986156.6321.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Mon Nov 3 02:50:36 2014
From: bogus@does.not.exist.com ()
Date: Mon Nov 3 03:42:37 2014
Subject: No subject
Message-ID: <mailman.45.1414986157.6321.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Mon Nov 3 02:50:36 2014
From: bogus@does.not.exist.com ()
Date: Mon Nov 3 03:42:37 2014
Subject: No subject
Message-ID: <mailman.46.1414986157.6321.htk-users@eng.cam.ac.uk>

From bogus@does.not.exist.com Mon Nov 3 02:50:36 2014


From: bogus@does.not.exist.com ()
Date: Mon Nov 3 03:42:37 2014
Subject: No subject
Message-ID: <mailman.47.1414986157.6321.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Mon Nov 3 02:50:36 2014
From: bogus@does.not.exist.com ()
Date: Mon Nov 3 03:42:38 2014
Subject: No subject
Message-ID: <mailman.48.1414986158.6321.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Mon Nov 3 02:50:36 2014
From: bogus@does.not.exist.com ()
Date: Mon Nov 3 03:42:39 2014
Subject: No subject
Message-ID: <mailman.49.1414986159.6321.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Mon Nov 3 02:50:36 2014
From: bogus@does.not.exist.com ()
Date: Mon Nov 3 03:42:40 2014
Subject: No subject
Message-ID: <mailman.50.1414986160.6321.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Mon Nov 3 02:50:36 2014
From: bogus@does.not.exist.com ()
Date: Mon Nov 3 03:42:41 2014
Subject: No subject
Message-ID: <mailman.51.1414986161.6321.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Mon Nov 3 02:50:36 2014
From: bogus@does.not.exist.com ()
Date: Mon Nov 3 03:42:42 2014
Subject: No subject
Message-ID: <mailman.52.1414986162.6321.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Mon Nov 3 02:50:36 2014
From: bogus@does.not.exist.com ()
Date: Mon Nov 3 03:42:42 2014
Subject: No subject
Message-ID: <mailman.53.1414986162.6321.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Mon Nov 3 02:50:36 2014
From: bogus@does.not.exist.com ()
Date: Mon Nov 3 03:42:42 2014
Subject: No subject
Message-ID: <mailman.54.1414986162.6321.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Mon Nov 3 02:50:36 2014
From: bogus@does.not.exist.com ()
Date: Mon Nov 3 03:42:43 2014
Subject: No subject
Message-ID: <mailman.55.1414986163.6321.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Mon Nov 3 02:50:36 2014
From: bogus@does.not.exist.com ()
Date: Mon Nov 3 03:42:43 2014
Subject: No subject
Message-ID: <mailman.56.1414986163.6321.htk-users@eng.cam.ac.uk>

From bogus@does.not.exist.com Mon Nov 3 02:50:36 2014


From: bogus@does.not.exist.com ()
Date: Mon Nov 3 03:42:44 2014
Subject: No subject
Message-ID: <mailman.57.1414986163.6321.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Mon Nov 3 02:50:36 2014
From: bogus@does.not.exist.com ()
Date: Mon Nov 3 03:42:44 2014
Subject: No subject
Message-ID: <mailman.58.1414986164.6321.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Mon Nov 3 02:50:36 2014
From: bogus@does.not.exist.com ()
Date: Mon Nov 3 03:42:44 2014
Subject: No subject
Message-ID: <mailman.59.1414986164.6321.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Mon Nov 3 02:50:36 2014
From: bogus@does.not.exist.com ()
Date: Mon Nov 3 03:42:45 2014
Subject: No subject
Message-ID: <mailman.60.1414986165.6321.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Mon Nov 3 02:50:36 2014
From: bogus@does.not.exist.com ()
Date: Mon Nov 3 03:42:46 2014
Subject: No subject
Message-ID: <mailman.61.1414986166.6321.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Mon Nov 3 02:50:36 2014
From: bogus@does.not.exist.com ()
Date: Mon Nov 3 03:42:46 2014
Subject: No subject
Message-ID: <mailman.62.1414986166.6321.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Mon Nov 3 02:50:36 2014
From: bogus@does.not.exist.com ()
Date: Mon Nov 3 03:42:46 2014
Subject: No subject
Message-ID: <mailman.63.1414986166.6321.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Mon Nov 3 02:50:36 2014
From: bogus@does.not.exist.com ()
Date: Mon Nov 3 03:42:47 2014
Subject: No subject
Message-ID: <mailman.64.1414986167.6321.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Mon Nov 3 02:50:36 2014
From: bogus@does.not.exist.com ()
Date: Mon Nov 3 03:42:47 2014
Subject: No subject
Message-ID: <mailman.65.1414986167.6321.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Mon Nov 3 02:50:36 2014
From: bogus@does.not.exist.com ()
Date: Mon Nov 3 03:42:48 2014
Subject: No subject
Message-ID: <mailman.66.1414986168.6321.htk-users@eng.cam.ac.uk>

From bogus@does.not.exist.com Mon Nov 3 02:50:36 2014


From: bogus@does.not.exist.com ()
Date: Mon Nov 3 03:42:48 2014
Subject: No subject
Message-ID: <mailman.67.1414986168.6321.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Mon Nov 3 02:50:36 2014
From: bogus@does.not.exist.com ()
Date: Mon Nov 3 03:42:48 2014
Subject: No subject
Message-ID: <mailman.68.1414986168.6321.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Mon Nov 3 02:50:36 2014
From: bogus@does.not.exist.com ()
Date: Mon Nov 3 03:42:49 2014
Subject: No subject
Message-ID: <mailman.69.1414986169.6321.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Mon Nov 3 02:50:36 2014
From: bogus@does.not.exist.com ()
Date: Mon Nov 3 03:42:50 2014
Subject: No subject
Message-ID: <mailman.70.1414986170.6321.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Mon Nov 3 02:50:36 2014
From: bogus@does.not.exist.com ()
Date: Mon Nov 3 03:42:51 2014
Subject: No subject
Message-ID: <mailman.71.1414986171.6321.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Mon Nov 3 02:50:36 2014
From: bogus@does.not.exist.com ()
Date: Mon Nov 3 03:42:54 2014
Subject: No subject
Message-ID: <mailman.72.1414986174.6321.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Mon Nov 3 02:50:36 2014
From: bogus@does.not.exist.com ()
Date: Mon Nov 3 03:42:58 2014
Subject: No subject
Message-ID: <mailman.73.1414986178.6321.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Mon Nov 3 02:50:36 2014
From: bogus@does.not.exist.com ()
Date: Mon Nov 3 03:43:02 2014
Subject: No subject
Message-ID: <mailman.74.1414986182.6321.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Mon Nov 3 02:50:36 2014
From: bogus@does.not.exist.com ()
Date: Mon Nov 3 03:43:05 2014
Subject: No subject
Message-ID: <mailman.75.1414986185.6321.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Mon Nov 3 02:50:36 2014
From: bogus@does.not.exist.com ()
Date: Mon Nov 3 03:43:06 2014
Subject: No subject
Message-ID: <mailman.76.1414986186.6321.htk-users@eng.cam.ac.uk>

From bogus@does.not.exist.com Mon Nov 3 02:50:36 2014


From: bogus@does.not.exist.com ()
Date: Mon Nov 3 03:43:06 2014
Subject: No subject
Message-ID: <mailman.77.1414986186.6321.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Mon Nov 3 02:50:36 2014
From: bogus@does.not.exist.com ()
Date: Mon Nov 3 03:43:07 2014
Subject: No subject
Message-ID: <mailman.78.1414986187.6321.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Mon Nov 3 02:50:36 2014
From: bogus@does.not.exist.com ()
Date: Mon Nov 3 03:43:07 2014
Subject: No subject
Message-ID: <mailman.79.1414986187.6321.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Mon Nov 3 02:50:36 2014
From: bogus@does.not.exist.com ()
Date: Mon Nov 3 03:43:08 2014
Subject: No subject
Message-ID: <mailman.80.1414986188.6321.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Mon Nov 3 02:50:36 2014
From: bogus@does.not.exist.com ()
Date: Mon Nov 3 03:43:08 2014
Subject: No subject
Message-ID: <mailman.81.1414986188.6321.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Mon Nov 3 02:50:36 2014
From: bogus@does.not.exist.com ()
Date: Mon Nov 3 03:43:08 2014
Subject: No subject
Message-ID: <mailman.82.1414986188.6321.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Mon Nov 3 02:50:36 2014
From: bogus@does.not.exist.com ()
Date: Mon Nov 3 03:43:09 2014
Subject: No subject
Message-ID: <mailman.83.1414986189.6321.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Mon Nov 3 02:50:36 2014
From: bogus@does.not.exist.com ()
Date: Mon Nov 3 03:43:10 2014
Subject: No subject
Message-ID: <mailman.84.1414986190.6321.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Mon Nov 3 02:50:36 2014
From: bogus@does.not.exist.com ()
Date: Mon Nov 3 03:43:11 2014
Subject: No subject
Message-ID: <mailman.85.1414986191.6321.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Mon Nov 3 02:50:36 2014
From: bogus@does.not.exist.com ()
Date: Mon Nov 3 03:43:12 2014
Subject: No subject
Message-ID: <mailman.86.1414986192.6321.htk-users@eng.cam.ac.uk>

From bogus@does.not.exist.com Mon Nov 3 02:50:36 2014


From: bogus@does.not.exist.com ()
Date: Mon Nov 3 03:43:13 2014
Subject: No subject
Message-ID: <mailman.87.1414986193.6321.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Mon Nov 3 02:50:36 2014
From: bogus@does.not.exist.com ()
Date: Mon Nov 3 03:43:14 2014
Subject: No subject
Message-ID: <mailman.88.1414986194.6321.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Mon Nov 3 02:50:36 2014
From: bogus@does.not.exist.com ()
Date: Mon Nov 3 03:43:15 2014
Subject: No subject
Message-ID: <mailman.89.1414986195.6321.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Mon Nov 3 02:50:36 2014
From: bogus@does.not.exist.com ()
Date: Mon Nov 3 03:43:18 2014
Subject: No subject
Message-ID: <mailman.91.1414986198.6321.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Mon Nov 3 02:50:36 2014
From: bogus@does.not.exist.com ()
Date: Mon Nov 3 03:43:29 2014
Subject: No subject
Message-ID: <mailman.92.1414986209.6321.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Mon Nov 3 02:50:36 2014
From: bogus@does.not.exist.com ()
Date: Mon Nov 3 03:43:38 2014
Subject: No subject
Message-ID: <mailman.93.1414986218.6321.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Mon Nov 3 02:50:36 2014
From: bogus@does.not.exist.com ()
Date: Mon Nov 3 03:43:42 2014
Subject: No subject
Message-ID: <mailman.94.1414986222.6321.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Mon Nov 3 02:50:36 2014
From: bogus@does.not.exist.com ()
Date: Mon Nov 3 03:43:45 2014
Subject: No subject
Message-ID: <mailman.95.1414986225.6321.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Mon Nov 3 02:50:36 2014
From: bogus@does.not.exist.com ()
Date: Mon Nov 3 03:43:46 2014
Subject: No subject
Message-ID: <mailman.96.1414986226.6321.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Mon Nov 3 02:50:36 2014
From: bogus@does.not.exist.com ()
Date: Mon Nov 3 03:43:48 2014
Subject: No subject
Message-ID: <mailman.97.1414986228.6321.htk-users@eng.cam.ac.uk>

From bogus@does.not.exist.com Mon Nov 3 02:50:36 2014


From: bogus@does.not.exist.com ()
Date: Mon Nov 3 03:43:49 2014
Subject: No subject
Message-ID: <mailman.98.1414986229.6321.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Mon Nov 3 02:50:36 2014
From: bogus@does.not.exist.com ()
Date: Mon Nov 3 03:43:51 2014
Subject: No subject
Message-ID: <mailman.99.1414986231.6321.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Mon Nov 3 02:50:36 2014
From: bogus@does.not.exist.com ()
Date: Mon Nov 3 03:43:52 2014
Subject: No subject
Message-ID: <mailman.100.1414986232.6321.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Mon Nov 3 02:50:36 2014
From: bogus@does.not.exist.com ()
Date: Mon Nov 3 03:43:52 2014
Subject: No subject
Message-ID: <mailman.101.1414986232.6321.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Mon Nov 3 02:50:36 2014
From: bogus@does.not.exist.com ()
Date: Mon Nov 3 03:43:53 2014
Subject: No subject
Message-ID: <mailman.102.1414986233.6321.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Mon Nov 3 02:50:36 2014
From: bogus@does.not.exist.com ()
Date: Mon Nov 3 03:43:54 2014
Subject: No subject
Message-ID: <mailman.103.1414986234.6321.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Tue Nov 4 02:54:20 2014
From: bogus@does.not.exist.com ()
Date: Tue Nov 4 04:25:56 2014
Subject: No subject
Message-ID: <mailman.1.1415075156.20686.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Tue Nov 4 02:54:20 2014
From: bogus@does.not.exist.com ()
Date: Tue Nov 4 04:25:59 2014
Subject: No subject
Message-ID: <mailman.2.1415075159.20686.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Tue Nov 4 02:54:20 2014
From: bogus@does.not.exist.com ()
Date: Tue Nov 4 04:25:59 2014
Subject: No subject
Message-ID: <mailman.3.1415075159.20686.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Tue Nov 4 02:54:20 2014
From: bogus@does.not.exist.com ()
Date: Tue Nov 4 04:26:00 2014
Subject: No subject
Message-ID: <mailman.4.1415075160.20686.htk-users@eng.cam.ac.uk>

From bogus@does.not.exist.com Tue Nov 4 02:54:20 2014


From: bogus@does.not.exist.com ()
Date: Tue Nov 4 04:26:01 2014
Subject: No subject
Message-ID: <mailman.5.1415075161.20686.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Tue Nov 4 02:54:20 2014
From: bogus@does.not.exist.com ()
Date: Tue Nov 4 04:26:04 2014
Subject: No subject
Message-ID: <mailman.6.1415075164.20686.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Tue Nov 4 02:54:20 2014
From: bogus@does.not.exist.com ()
Date: Tue Nov 4 04:26:06 2014
Subject: No subject
Message-ID: <mailman.7.1415075165.20686.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Tue Nov 4 02:54:20 2014
From: bogus@does.not.exist.com ()
Date: Tue Nov 4 04:26:08 2014
Subject: No subject
Message-ID: <mailman.8.1415075168.20686.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Tue Nov 4 02:54:20 2014
From: bogus@does.not.exist.com ()
Date: Tue Nov 4 04:26:11 2014
Subject: No subject
Message-ID: <mailman.9.1415075171.20686.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Tue Nov 4 02:54:20 2014
From: bogus@does.not.exist.com ()
Date: Tue Nov 4 04:26:16 2014
Subject: No subject
Message-ID: <mailman.10.1415075176.20686.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Tue Nov 4 02:54:20 2014
From: bogus@does.not.exist.com ()
Date: Tue Nov 4 04:26:20 2014
Subject: No subject
Message-ID: <mailman.11.1415075180.20686.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Tue Nov 4 02:54:20 2014
From: bogus@does.not.exist.com ()
Date: Tue Nov 4 04:26:25 2014
Subject: No subject
Message-ID: <mailman.12.1415075184.20686.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Tue Nov 4 02:54:20 2014
From: bogus@does.not.exist.com ()
Date: Tue Nov 4 04:26:38 2014
Subject: No subject
Message-ID: <mailman.13.1415075197.20686.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Tue Nov 4 02:54:20 2014
From: bogus@does.not.exist.com ()
Date: Tue Nov 4 04:26:58 2014
Subject: No subject
Message-ID: <mailman.14.1415075218.20686.htk-users@eng.cam.ac.uk>

From bogus@does.not.exist.com Tue Nov 4 02:54:20 2014


From: bogus@does.not.exist.com ()
Date: Tue Nov 4 04:27:06 2014
Subject: No subject
Message-ID: <mailman.15.1415075226.20686.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Tue Nov 4 02:54:20 2014
From: bogus@does.not.exist.com ()
Date: Tue Nov 4 04:27:07 2014
Subject: No subject
Message-ID: <mailman.16.1415075227.20686.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Tue Nov 4 02:54:20 2014
From: bogus@does.not.exist.com ()
Date: Tue Nov 4 04:27:08 2014
Subject: No subject
Message-ID: <mailman.17.1415075228.20686.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Tue Nov 4 02:54:20 2014
From: bogus@does.not.exist.com ()
Date: Tue Nov 4 04:27:08 2014
Subject: No subject
Message-ID: <mailman.18.1415075228.20686.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Tue Nov 4 02:54:20 2014
From: bogus@does.not.exist.com ()
Date: Tue Nov 4 04:27:10 2014
Subject: No subject
Message-ID: <mailman.19.1415075230.20686.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Tue Nov 4 02:54:20 2014
From: bogus@does.not.exist.com ()
Date: Tue Nov 4 04:27:11 2014
Subject: No subject
Message-ID: <mailman.20.1415075231.20686.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Tue Nov 4 02:54:20 2014
From: bogus@does.not.exist.com ()
Date: Tue Nov 4 04:27:13 2014
Subject: No subject
Message-ID: <mailman.21.1415075233.20686.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Tue Nov 4 02:54:20 2014
From: bogus@does.not.exist.com ()
Date: Tue Nov 4 04:27:15 2014
Subject: No subject
Message-ID: <mailman.22.1415075235.20686.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Tue Nov 4 02:54:20 2014
From: bogus@does.not.exist.com ()
Date: Tue Nov 4 04:27:16 2014
Subject: No subject
Message-ID: <mailman.23.1415075236.20686.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Tue Nov 4 02:54:20 2014
From: bogus@does.not.exist.com ()
Date: Tue Nov 4 04:27:18 2014
Subject: No subject
Message-ID: <mailman.24.1415075238.20686.htk-users@eng.cam.ac.uk>

From bogus@does.not.exist.com Tue Nov 4 02:54:20 2014


From: bogus@does.not.exist.com ()
Date: Tue Nov 4 04:27:20 2014
Subject: No subject
Message-ID: <mailman.25.1415075240.20686.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Tue Nov 4 02:54:20 2014
From: bogus@does.not.exist.com ()
Date: Tue Nov 4 04:27:20 2014
Subject: No subject
Message-ID: <mailman.26.1415075240.20686.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Tue Nov 4 02:54:20 2014
From: bogus@does.not.exist.com ()
Date: Tue Nov 4 04:27:21 2014
Subject: No subject
Message-ID: <mailman.27.1415075241.20686.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Tue Nov 4 02:54:20 2014
From: bogus@does.not.exist.com ()
Date: Tue Nov 4 04:27:22 2014
Subject: No subject
Message-ID: <mailman.28.1415075242.20686.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Tue Nov 4 02:54:20 2014
From: bogus@does.not.exist.com ()
Date: Tue Nov 4 04:27:22 2014
Subject: No subject
Message-ID: <mailman.29.1415075242.20686.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Tue Nov 4 02:54:20 2014
From: bogus@does.not.exist.com ()
Date: Tue Nov 4 04:27:26 2014
Subject: No subject
Message-ID: <mailman.30.1415075246.20686.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Tue Nov 4 02:54:20 2014
From: bogus@does.not.exist.com ()
Date: Tue Nov 4 04:27:26 2014
Subject: No subject
Message-ID: <mailman.31.1415075246.20686.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Tue Nov 4 02:54:20 2014
From: bogus@does.not.exist.com ()
Date: Tue Nov 4 04:27:28 2014
Subject: No subject
Message-ID: <mailman.32.1415075248.20686.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Tue Nov 4 02:54:20 2014
From: bogus@does.not.exist.com ()
Date: Tue Nov 4 04:27:28 2014
Subject: No subject
Message-ID: <mailman.33.1415075248.20686.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Tue Nov 4 02:54:20 2014
From: bogus@does.not.exist.com ()
Date: Tue Nov 4 04:27:29 2014
Subject: No subject
Message-ID: <mailman.34.1415075249.20686.htk-users@eng.cam.ac.uk>

From bogus@does.not.exist.com Tue Nov 4 02:54:20 2014


From: bogus@does.not.exist.com ()
Date: Tue Nov 4 04:27:30 2014
Subject: No subject
Message-ID: <mailman.35.1415075250.20686.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Tue Nov 4 02:54:20 2014
From: bogus@does.not.exist.com ()
Date: Tue Nov 4 04:27:30 2014
Subject: No subject
Message-ID: <mailman.36.1415075250.20686.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Tue Nov 4 02:54:20 2014
From: bogus@does.not.exist.com ()
Date: Tue Nov 4 04:27:30 2014
Subject: No subject
Message-ID: <mailman.37.1415075250.20686.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Tue Nov 4 02:54:20 2014
From: bogus@does.not.exist.com ()
Date: Tue Nov 4 04:27:32 2014
Subject: No subject
Message-ID: <mailman.38.1415075252.20686.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Tue Nov 4 02:54:20 2014
From: bogus@does.not.exist.com ()
Date: Tue Nov 4 04:27:32 2014
Subject: No subject
Message-ID: <mailman.39.1415075252.20686.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Tue Nov 4 02:54:20 2014
From: bogus@does.not.exist.com ()
Date: Tue Nov 4 04:27:32 2014
Subject: No subject
Message-ID: <mailman.40.1415075252.20686.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Tue Nov 4 02:54:20 2014
From: bogus@does.not.exist.com ()
Date: Tue Nov 4 04:27:35 2014
Subject: No subject
Message-ID: <mailman.41.1415075255.20686.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Tue Nov 4 02:54:20 2014
From: bogus@does.not.exist.com ()
Date: Tue Nov 4 04:27:36 2014
Subject: No subject
Message-ID: <mailman.42.1415075256.20686.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Tue Nov 4 02:54:20 2014
From: bogus@does.not.exist.com ()
Date: Tue Nov 4 04:27:36 2014
Subject: No subject
Message-ID: <mailman.43.1415075256.20686.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Tue Nov 4 02:54:20 2014
From: bogus@does.not.exist.com ()
Date: Tue Nov 4 04:27:37 2014
Subject: No subject
Message-ID: <mailman.44.1415075257.20686.htk-users@eng.cam.ac.uk>

From bogus@does.not.exist.com Tue Nov 4 02:54:20 2014


From: bogus@does.not.exist.com ()
Date: Tue Nov 4 04:27:37 2014
Subject: No subject
Message-ID: <mailman.45.1415075257.20686.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Tue Nov 4 02:54:20 2014
From: bogus@does.not.exist.com ()
Date: Tue Nov 4 04:27:38 2014
Subject: No subject
Message-ID: <mailman.46.1415075258.20686.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Tue Nov 4 02:54:20 2014
From: bogus@does.not.exist.com ()
Date: Tue Nov 4 04:27:38 2014
Subject: No subject
Message-ID: <mailman.47.1415075258.20686.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Tue Nov 4 02:54:20 2014
From: bogus@does.not.exist.com ()
Date: Tue Nov 4 04:27:38 2014
Subject: No subject
Message-ID: <mailman.48.1415075258.20686.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Tue Nov 4 02:54:20 2014
From: bogus@does.not.exist.com ()
Date: Tue Nov 4 04:27:41 2014
Subject: No subject
Message-ID: <mailman.49.1415075261.20686.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Tue Nov 4 02:54:20 2014
From: bogus@does.not.exist.com ()
Date: Tue Nov 4 04:27:41 2014
Subject: No subject
Message-ID: <mailman.50.1415075261.20686.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Tue Nov 4 02:54:20 2014
From: bogus@does.not.exist.com ()
Date: Tue Nov 4 04:27:45 2014
Subject: No subject
Message-ID: <mailman.51.1415075265.20686.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Tue Nov 4 02:54:20 2014
From: bogus@does.not.exist.com ()
Date: Tue Nov 4 04:27:45 2014
Subject: No subject
Message-ID: <mailman.52.1415075265.20686.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Tue Nov 4 02:54:20 2014
From: bogus@does.not.exist.com ()
Date: Tue Nov 4 04:27:47 2014
Subject: No subject
Message-ID: <mailman.53.1415075267.20686.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Tue Nov 4 02:54:20 2014
From: bogus@does.not.exist.com ()
Date: Tue Nov 4 04:27:51 2014
Subject: No subject
Message-ID: <mailman.54.1415075270.20686.htk-users@eng.cam.ac.uk>

From bogus@does.not.exist.com Tue Nov 4 02:54:20 2014


From: bogus@does.not.exist.com ()
Date: Tue Nov 4 04:27:54 2014
Subject: No subject
Message-ID: <mailman.55.1415075274.20686.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Tue Nov 4 02:54:20 2014
From: bogus@does.not.exist.com ()
Date: Tue Nov 4 04:27:58 2014
Subject: No subject
Message-ID: <mailman.56.1415075278.20686.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Tue Nov 4 02:54:20 2014
From: bogus@does.not.exist.com ()
Date: Tue Nov 4 04:28:02 2014
Subject: No subject
Message-ID: <mailman.57.1415075281.20686.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Tue Nov 4 02:54:20 2014
From: bogus@does.not.exist.com ()
Date: Tue Nov 4 04:28:03 2014
Subject: No subject
Message-ID: <mailman.58.1415075283.20686.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Tue Nov 4 02:54:20 2014
From: bogus@does.not.exist.com ()
Date: Tue Nov 4 04:28:03 2014
Subject: No subject
Message-ID: <mailman.59.1415075283.20686.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Tue Nov 4 02:54:20 2014
From: bogus@does.not.exist.com ()
Date: Tue Nov 4 04:28:04 2014
Subject: No subject
Message-ID: <mailman.60.1415075284.20686.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Tue Nov 4 02:54:20 2014
From: bogus@does.not.exist.com ()
Date: Tue Nov 4 04:28:05 2014
Subject: No subject
Message-ID: <mailman.61.1415075285.20686.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Tue Nov 4 02:54:20 2014
From: bogus@does.not.exist.com ()
Date: Tue Nov 4 04:28:08 2014
Subject: No subject
Message-ID: <mailman.62.1415075288.20686.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Tue Nov 4 02:54:20 2014
From: bogus@does.not.exist.com ()
Date: Tue Nov 4 04:28:09 2014
Subject: No subject
Message-ID: <mailman.63.1415075289.20686.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Tue Nov 4 02:54:20 2014
From: bogus@does.not.exist.com ()
Date: Tue Nov 4 04:28:20 2014
Subject: No subject
Message-ID: <mailman.64.1415075300.20686.htk-users@eng.cam.ac.uk>

From bogus@does.not.exist.com Tue Nov 4 02:54:20 2014


From: bogus@does.not.exist.com ()
Date: Tue Nov 4 04:28:24 2014
Subject: No subject
Message-ID: <mailman.65.1415075304.20686.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Tue Nov 4 02:54:20 2014
From: bogus@does.not.exist.com ()
Date: Tue Nov 4 04:28:25 2014
Subject: No subject
Message-ID: <mailman.66.1415075305.20686.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Tue Nov 4 02:54:20 2014
From: bogus@does.not.exist.com ()
Date: Tue Nov 4 04:28:29 2014
Subject: No subject
Message-ID: <mailman.67.1415075308.20686.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Tue Nov 4 02:54:20 2014
From: bogus@does.not.exist.com ()
Date: Tue Nov 4 04:28:33 2014
Subject: No subject
Message-ID: <mailman.68.1415075313.20686.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Tue Nov 4 02:54:20 2014
From: bogus@does.not.exist.com ()
Date: Tue Nov 4 04:28:36 2014
Subject: No subject
Message-ID: <mailman.69.1415075316.20686.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Tue Nov 4 02:54:20 2014
From: bogus@does.not.exist.com ()
Date: Tue Nov 4 04:28:38 2014
Subject: No subject
Message-ID: <mailman.70.1415075318.20686.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Tue Nov 4 02:54:20 2014
From: bogus@does.not.exist.com ()
Date: Tue Nov 4 04:28:43 2014
Subject: No subject
Message-ID: <mailman.71.1415075323.20686.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Tue Nov 4 02:54:20 2014
From: bogus@does.not.exist.com ()
Date: Tue Nov 4 04:28:45 2014
Subject: No subject
Message-ID: <mailman.72.1415075325.20686.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Tue Nov 4 02:54:20 2014
From: bogus@does.not.exist.com ()
Date: Tue Nov 4 04:28:48 2014
Subject: No subject
Message-ID: <mailman.73.1415075327.20686.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Tue Nov 4 02:54:20 2014
From: bogus@does.not.exist.com ()
Date: Tue Nov 4 04:28:50 2014
Subject: No subject
Message-ID: <mailman.74.1415075330.20686.htk-users@eng.cam.ac.uk>

From bogus@does.not.exist.com Tue Nov 4 02:54:20 2014


From: bogus@does.not.exist.com ()
Date: Tue Nov 4 04:28:52 2014
Subject: No subject
Message-ID: <mailman.75.1415075332.20686.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Tue Nov 4 02:54:20 2014
From: bogus@does.not.exist.com ()
Date: Tue Nov 4 04:28:54 2014
Subject: No subject
Message-ID: <mailman.76.1415075334.20686.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Tue Nov 4 02:54:20 2014
From: bogus@does.not.exist.com ()
Date: Tue Nov 4 04:28:55 2014
Subject: No subject
Message-ID: <mailman.77.1415075335.20686.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Tue Nov 4 02:54:20 2014
From: bogus@does.not.exist.com ()
Date: Tue Nov 4 04:28:56 2014
Subject: No subject
Message-ID: <mailman.78.1415075336.20686.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Tue Nov 4 02:54:20 2014
From: bogus@does.not.exist.com ()
Date: Tue Nov 4 04:28:57 2014
Subject: No subject
Message-ID: <mailman.79.1415075337.20686.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Tue Nov 4 02:54:20 2014
From: bogus@does.not.exist.com ()
Date: Tue Nov 4 04:28:58 2014
Subject: No subject
Message-ID: <mailman.80.1415075338.20686.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Tue Nov 4 02:54:20 2014
From: bogus@does.not.exist.com ()
Date: Tue Nov 4 04:29:00 2014
Subject: No subject
Message-ID: <mailman.81.1415075340.20686.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Tue Nov 4 02:54:20 2014
From: bogus@does.not.exist.com ()
Date: Tue Nov 4 04:29:02 2014
Subject: No subject
Message-ID: <mailman.82.1415075342.20686.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Tue Nov 4 02:54:20 2014
From: bogus@does.not.exist.com ()
Date: Tue Nov 4 04:29:03 2014
Subject: No subject
Message-ID: <mailman.83.1415075343.20686.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Tue Nov 4 02:54:20 2014
From: bogus@does.not.exist.com ()
Date: Tue Nov 4 04:29:04 2014
Subject: No subject
Message-ID: <mailman.84.1415075344.20686.htk-users@eng.cam.ac.uk>

From bogus@does.not.exist.com Tue Nov 4 02:54:20 2014


From: bogus@does.not.exist.com ()
Date: Tue Nov 4 04:29:05 2014
Subject: No subject
Message-ID: <mailman.85.1415075345.20686.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Tue Nov 4 02:54:20 2014
From: bogus@does.not.exist.com ()
Date: Tue Nov 4 04:29:06 2014
Subject: No subject
Message-ID: <mailman.86.1415075346.20686.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Tue Nov 4 02:54:20 2014
From: bogus@does.not.exist.com ()
Date: Tue Nov 4 04:29:07 2014
Subject: No subject
Message-ID: <mailman.87.1415075347.20686.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Tue Nov 4 02:54:20 2014
From: bogus@does.not.exist.com ()
Date: Tue Nov 4 04:29:07 2014
Subject: No subject
Message-ID: <mailman.88.1415075347.20686.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Tue Nov 4 02:54:20 2014
From: bogus@does.not.exist.com ()
Date: Tue Nov 4 04:29:08 2014
Subject: No subject
Message-ID: <mailman.89.1415075348.20686.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Tue Nov 4 02:54:20 2014
From: bogus@does.not.exist.com ()
Date: Tue Nov 4 04:29:09 2014
Subject: No subject
Message-ID: <mailman.91.1415075349.20686.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Tue Nov 4 02:54:20 2014
From: bogus@does.not.exist.com ()
Date: Tue Nov 4 04:29:11 2014
Subject: No subject
Message-ID: <mailman.92.1415075351.20686.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Tue Nov 4 02:54:20 2014
From: bogus@does.not.exist.com ()
Date: Tue Nov 4 04:29:12 2014
Subject: No subject
Message-ID: <mailman.93.1415075352.20686.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Tue Nov 4 02:54:20 2014
From: bogus@does.not.exist.com ()
Date: Tue Nov 4 04:29:13 2014
Subject: No subject
Message-ID: <mailman.94.1415075353.20686.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Tue Nov 4 02:54:20 2014
From: bogus@does.not.exist.com ()
Date: Tue Nov 4 04:29:14 2014
Subject: No subject
Message-ID: <mailman.95.1415075354.20686.htk-users@eng.cam.ac.uk>

From bogus@does.not.exist.com Tue Nov 4 02:54:20 2014


From: bogus@does.not.exist.com ()
Date: Tue Nov 4 04:29:15 2014
Subject: No subject
Message-ID: <mailman.96.1415075355.20686.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Tue Nov 4 02:54:20 2014
From: bogus@does.not.exist.com ()
Date: Tue Nov 4 04:29:16 2014
Subject: No subject
Message-ID: <mailman.97.1415075356.20686.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Tue Nov 4 02:54:20 2014
From: bogus@does.not.exist.com ()
Date: Tue Nov 4 04:29:17 2014
Subject: No subject
Message-ID: <mailman.98.1415075357.20686.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Tue Nov 4 02:54:20 2014
From: bogus@does.not.exist.com ()
Date: Tue Nov 4 04:29:19 2014
Subject: No subject
Message-ID: <mailman.99.1415075359.20686.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Tue Nov 4 02:54:20 2014
From: bogus@does.not.exist.com ()
Date: Tue Nov 4 04:29:20 2014
Subject: No subject
Message-ID: <mailman.100.1415075360.20686.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Tue Nov 4 02:54:20 2014
From: bogus@does.not.exist.com ()
Date: Tue Nov 4 04:29:20 2014
Subject: No subject
Message-ID: <mailman.101.1415075360.20686.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Tue Nov 4 02:54:20 2014
From: bogus@does.not.exist.com ()
Date: Tue Nov 4 04:29:22 2014
Subject: No subject
Message-ID: <mailman.102.1415075362.20686.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Tue Nov 4 02:54:20 2014
From: bogus@does.not.exist.com ()
Date: Tue Nov 4 04:29:23 2014
Subject: No subject
Message-ID: <mailman.103.1415075363.20686.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 5 02:50:55 2014
From: bogus@does.not.exist.com ()
Date: Wed Nov 5 03:56:44 2014
Subject: No subject
Message-ID: <mailman.1.1415159804.3666.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 5 02:50:55 2014
From: bogus@does.not.exist.com ()
Date: Wed Nov 5 03:56:55 2014
Subject: No subject
Message-ID: <mailman.2.1415159815.3666.htk-users@eng.cam.ac.uk>

From bogus@does.not.exist.com Wed Nov 5 02:50:55 2014


From: bogus@does.not.exist.com ()
Date: Wed Nov 5 03:56:57 2014
Subject: No subject
Message-ID: <mailman.3.1415159817.3666.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 5 02:50:55 2014
From: bogus@does.not.exist.com ()
Date: Wed Nov 5 03:56:58 2014
Subject: No subject
Message-ID: <mailman.4.1415159818.3666.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 5 02:50:55 2014
From: bogus@does.not.exist.com ()
Date: Wed Nov 5 03:56:58 2014
Subject: No subject
Message-ID: <mailman.5.1415159818.3666.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 5 02:50:55 2014
From: bogus@does.not.exist.com ()
Date: Wed Nov 5 03:56:59 2014
Subject: No subject
Message-ID: <mailman.6.1415159819.3666.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 5 02:50:55 2014
From: bogus@does.not.exist.com ()
Date: Wed Nov 5 03:57:00 2014
Subject: No subject
Message-ID: <mailman.7.1415159820.3666.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 5 02:50:55 2014
From: bogus@does.not.exist.com ()
Date: Wed Nov 5 03:57:00 2014
Subject: No subject
Message-ID: <mailman.8.1415159820.3666.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 5 02:50:55 2014
From: bogus@does.not.exist.com ()
Date: Wed Nov 5 03:57:01 2014
Subject: No subject
Message-ID: <mailman.9.1415159821.3666.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 5 02:50:55 2014
From: bogus@does.not.exist.com ()
Date: Wed Nov 5 03:57:04 2014
Subject: No subject
Message-ID: <mailman.10.1415159823.3666.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 5 02:50:55 2014
From: bogus@does.not.exist.com ()
Date: Wed Nov 5 03:57:04 2014
Subject: No subject
Message-ID: <mailman.11.1415159824.3666.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 5 02:50:55 2014
From: bogus@does.not.exist.com ()
Date: Wed Nov 5 03:57:06 2014
Subject: No subject
Message-ID: <mailman.12.1415159826.3666.htk-users@eng.cam.ac.uk>

From bogus@does.not.exist.com Wed Nov 5 02:50:55 2014


From: bogus@does.not.exist.com ()
Date: Wed Nov 5 03:57:06 2014
Subject: No subject
Message-ID: <mailman.13.1415159826.3666.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 5 02:50:55 2014
From: bogus@does.not.exist.com ()
Date: Wed Nov 5 03:57:07 2014
Subject: No subject
Message-ID: <mailman.14.1415159827.3666.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 5 02:50:55 2014
From: bogus@does.not.exist.com ()
Date: Wed Nov 5 03:57:08 2014
Subject: No subject
Message-ID: <mailman.15.1415159828.3666.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 5 02:50:55 2014
From: bogus@does.not.exist.com ()
Date: Wed Nov 5 03:57:08 2014
Subject: No subject
Message-ID: <mailman.16.1415159828.3666.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 5 02:50:55 2014
From: bogus@does.not.exist.com ()
Date: Wed Nov 5 03:57:08 2014
Subject: No subject
Message-ID: <mailman.17.1415159828.3666.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 5 02:50:55 2014
From: bogus@does.not.exist.com ()
Date: Wed Nov 5 03:57:09 2014
Subject: No subject
Message-ID: <mailman.18.1415159829.3666.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 5 02:50:55 2014
From: bogus@does.not.exist.com ()
Date: Wed Nov 5 03:57:11 2014
Subject: No subject
Message-ID: <mailman.19.1415159831.3666.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 5 02:50:55 2014
From: bogus@does.not.exist.com ()
Date: Wed Nov 5 03:57:11 2014
Subject: No subject
Message-ID: <mailman.20.1415159831.3666.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 5 02:50:55 2014
From: bogus@does.not.exist.com ()
Date: Wed Nov 5 03:57:16 2014
Subject: No subject
Message-ID: <mailman.21.1415159836.3666.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 5 02:50:55 2014
From: bogus@does.not.exist.com ()
Date: Wed Nov 5 03:57:21 2014
Subject: No subject
Message-ID: <mailman.22.1415159841.3666.htk-users@eng.cam.ac.uk>

From bogus@does.not.exist.com Wed Nov 5 02:50:55 2014


From: bogus@does.not.exist.com ()
Date: Wed Nov 5 03:57:25 2014
Subject: No subject
Message-ID: <mailman.23.1415159845.3666.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 5 02:50:55 2014
From: bogus@does.not.exist.com ()
Date: Wed Nov 5 03:57:30 2014
Subject: No subject
Message-ID: <mailman.24.1415159850.3666.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 5 02:50:55 2014
From: bogus@does.not.exist.com ()
Date: Wed Nov 5 03:57:36 2014
Subject: No subject
Message-ID: <mailman.25.1415159856.3666.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 5 02:50:55 2014
From: bogus@does.not.exist.com ()
Date: Wed Nov 5 03:57:39 2014
Subject: No subject
Message-ID: <mailman.26.1415159859.3666.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 5 02:50:55 2014
From: bogus@does.not.exist.com ()
Date: Wed Nov 5 03:57:40 2014
Subject: No subject
Message-ID: <mailman.27.1415159860.3666.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 5 02:50:55 2014
From: bogus@does.not.exist.com ()
Date: Wed Nov 5 03:57:41 2014
Subject: No subject
Message-ID: <mailman.28.1415159861.3666.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 5 02:50:55 2014
From: bogus@does.not.exist.com ()
Date: Wed Nov 5 03:57:41 2014
Subject: No subject
Message-ID: <mailman.29.1415159861.3666.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 5 02:50:55 2014
From: bogus@does.not.exist.com ()
Date: Wed Nov 5 03:57:44 2014
Subject: No subject
Message-ID: <mailman.30.1415159864.3666.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 5 02:50:55 2014
From: bogus@does.not.exist.com ()
Date: Wed Nov 5 03:57:45 2014
Subject: No subject
Message-ID: <mailman.31.1415159864.3666.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 5 02:50:55 2014
From: bogus@does.not.exist.com ()
Date: Wed Nov 5 03:57:45 2014
Subject: No subject
Message-ID: <mailman.32.1415159865.3666.htk-users@eng.cam.ac.uk>

From bogus@does.not.exist.com Wed Nov 5 02:50:55 2014


From: bogus@does.not.exist.com ()
Date: Wed Nov 5 03:57:45 2014
Subject: No subject
Message-ID: <mailman.33.1415159865.3666.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 5 02:50:55 2014
From: bogus@does.not.exist.com ()
Date: Wed Nov 5 03:57:46 2014
Subject: No subject
Message-ID: <mailman.34.1415159866.3666.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 5 02:50:55 2014
From: bogus@does.not.exist.com ()
Date: Wed Nov 5 03:57:46 2014
Subject: No subject
Message-ID: <mailman.35.1415159866.3666.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 5 02:50:55 2014
From: bogus@does.not.exist.com ()
Date: Wed Nov 5 03:57:46 2014
Subject: No subject
Message-ID: <mailman.36.1415159866.3666.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 5 02:50:55 2014
From: bogus@does.not.exist.com ()
Date: Wed Nov 5 03:57:47 2014
Subject: No subject
Message-ID: <mailman.37.1415159867.3666.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 5 02:50:55 2014
From: bogus@does.not.exist.com ()
Date: Wed Nov 5 03:57:47 2014
Subject: No subject
Message-ID: <mailman.38.1415159867.3666.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 5 02:50:55 2014
From: bogus@does.not.exist.com ()
Date: Wed Nov 5 03:57:48 2014
Subject: No subject
Message-ID: <mailman.39.1415159868.3666.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 5 02:50:55 2014
From: bogus@does.not.exist.com ()
Date: Wed Nov 5 03:57:48 2014
Subject: No subject
Message-ID: <mailman.40.1415159868.3666.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 5 02:50:55 2014
From: bogus@does.not.exist.com ()
Date: Wed Nov 5 03:57:51 2014
Subject: No subject
Message-ID: <mailman.41.1415159871.3666.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 5 02:50:55 2014
From: bogus@does.not.exist.com ()
Date: Wed Nov 5 03:57:52 2014
Subject: No subject
Message-ID: <mailman.42.1415159872.3666.htk-users@eng.cam.ac.uk>

From bogus@does.not.exist.com Wed Nov 5 02:50:55 2014


From: bogus@does.not.exist.com ()
Date: Wed Nov 5 03:57:53 2014
Subject: No subject
Message-ID: <mailman.43.1415159873.3666.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 5 02:50:55 2014
From: bogus@does.not.exist.com ()
Date: Wed Nov 5 03:57:53 2014
Subject: No subject
Message-ID: <mailman.44.1415159873.3666.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 5 02:50:55 2014
From: bogus@does.not.exist.com ()
Date: Wed Nov 5 03:57:54 2014
Subject: No subject
Message-ID: <mailman.45.1415159874.3666.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 5 02:50:55 2014
From: bogus@does.not.exist.com ()
Date: Wed Nov 5 03:57:54 2014
Subject: No subject
Message-ID: <mailman.46.1415159874.3666.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 5 02:50:55 2014
From: bogus@does.not.exist.com ()
Date: Wed Nov 5 03:57:55 2014
Subject: No subject
Message-ID: <mailman.47.1415159875.3666.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 5 02:50:55 2014
From: bogus@does.not.exist.com ()
Date: Wed Nov 5 03:57:55 2014
Subject: No subject
Message-ID: <mailman.48.1415159875.3666.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 5 02:50:55 2014
From: bogus@does.not.exist.com ()
Date: Wed Nov 5 03:57:57 2014
Subject: No subject
Message-ID: <mailman.49.1415159877.3666.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 5 02:50:55 2014
From: bogus@does.not.exist.com ()
Date: Wed Nov 5 03:57:57 2014
Subject: No subject
Message-ID: <mailman.50.1415159877.3666.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 5 02:50:55 2014
From: bogus@does.not.exist.com ()
Date: Wed Nov 5 03:57:57 2014
Subject: No subject
Message-ID: <mailman.51.1415159877.3666.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 5 02:50:55 2014
From: bogus@does.not.exist.com ()
Date: Wed Nov 5 03:57:58 2014
Subject: No subject
Message-ID: <mailman.52.1415159878.3666.htk-users@eng.cam.ac.uk>

From bogus@does.not.exist.com Wed Nov 5 02:50:55 2014


From: bogus@does.not.exist.com ()
Date: Wed Nov 5 03:57:59 2014
Subject: No subject
Message-ID: <mailman.53.1415159879.3666.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 5 02:50:55 2014
From: bogus@does.not.exist.com ()
Date: Wed Nov 5 03:58:00 2014
Subject: No subject
Message-ID: <mailman.54.1415159880.3666.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 5 02:50:55 2014
From: bogus@does.not.exist.com ()
Date: Wed Nov 5 03:58:00 2014
Subject: No subject
Message-ID: <mailman.55.1415159880.3666.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 5 02:50:55 2014
From: bogus@does.not.exist.com ()
Date: Wed Nov 5 03:58:01 2014
Subject: No subject
Message-ID: <mailman.56.1415159881.3666.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 5 02:50:55 2014
From: bogus@does.not.exist.com ()
Date: Wed Nov 5 03:58:01 2014
Subject: No subject
Message-ID: <mailman.57.1415159881.3666.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 5 02:50:55 2014
From: bogus@does.not.exist.com ()
Date: Wed Nov 5 03:58:01 2014
Subject: No subject
Message-ID: <mailman.58.1415159881.3666.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 5 02:50:55 2014
From: bogus@does.not.exist.com ()
Date: Wed Nov 5 03:58:02 2014
Subject: No subject
Message-ID: <mailman.59.1415159882.3666.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 5 02:50:55 2014
From: bogus@does.not.exist.com ()
Date: Wed Nov 5 03:58:02 2014
Subject: No subject
Message-ID: <mailman.60.1415159882.3666.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 5 02:50:55 2014
From: bogus@does.not.exist.com ()
Date: Wed Nov 5 03:58:04 2014
Subject: No subject
Message-ID: <mailman.61.1415159884.3666.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 5 02:50:55 2014
From: bogus@does.not.exist.com ()
Date: Wed Nov 5 03:58:05 2014
Subject: No subject
Message-ID: <mailman.62.1415159885.3666.htk-users@eng.cam.ac.uk>

From bogus@does.not.exist.com Wed Nov 5 02:50:55 2014


From: bogus@does.not.exist.com ()
Date: Wed Nov 5 03:58:05 2014
Subject: No subject
Message-ID: <mailman.63.1415159885.3666.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 5 02:50:55 2014
From: bogus@does.not.exist.com ()
Date: Wed Nov 5 03:58:05 2014
Subject: No subject
Message-ID: <mailman.64.1415159885.3666.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 5 02:50:55 2014
From: bogus@does.not.exist.com ()
Date: Wed Nov 5 03:58:06 2014
Subject: No subject
Message-ID: <mailman.65.1415159886.3666.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 5 02:50:55 2014
From: bogus@does.not.exist.com ()
Date: Wed Nov 5 03:58:06 2014
Subject: No subject
Message-ID: <mailman.66.1415159886.3666.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 5 02:50:55 2014
From: bogus@does.not.exist.com ()
Date: Wed Nov 5 03:58:07 2014
Subject: No subject
Message-ID: <mailman.67.1415159887.3666.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 5 02:50:55 2014
From: bogus@does.not.exist.com ()
Date: Wed Nov 5 03:58:07 2014
Subject: No subject
Message-ID: <mailman.68.1415159887.3666.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 5 02:50:55 2014
From: bogus@does.not.exist.com ()
Date: Wed Nov 5 03:58:08 2014
Subject: No subject
Message-ID: <mailman.69.1415159888.3666.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 5 02:50:55 2014
From: bogus@does.not.exist.com ()
Date: Wed Nov 5 03:58:20 2014
Subject: No subject
Message-ID: <mailman.70.1415159900.3666.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 5 02:50:55 2014
From: bogus@does.not.exist.com ()
Date: Wed Nov 5 03:58:24 2014
Subject: No subject
Message-ID: <mailman.71.1415159903.3666.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 5 02:50:55 2014
From: bogus@does.not.exist.com ()
Date: Wed Nov 5 03:58:28 2014
Subject: No subject
Message-ID: <mailman.72.1415159907.3666.htk-users@eng.cam.ac.uk>

From bogus@does.not.exist.com Wed Nov 5 02:50:55 2014


From: bogus@does.not.exist.com ()
Date: Wed Nov 5 03:58:29 2014
Subject: No subject
Message-ID: <mailman.73.1415159909.3666.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 5 02:50:55 2014
From: bogus@does.not.exist.com ()
Date: Wed Nov 5 03:58:29 2014
Subject: No subject
Message-ID: <mailman.74.1415159909.3666.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 5 02:50:55 2014
From: bogus@does.not.exist.com ()
Date: Wed Nov 5 03:58:30 2014
Subject: No subject
Message-ID: <mailman.75.1415159910.3666.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 5 02:50:55 2014
From: bogus@does.not.exist.com ()
Date: Wed Nov 5 03:58:30 2014
Subject: No subject
Message-ID: <mailman.76.1415159910.3666.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 5 02:50:55 2014
From: bogus@does.not.exist.com ()
Date: Wed Nov 5 03:58:30 2014
Subject: No subject
Message-ID: <mailman.77.1415159910.3666.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 5 02:50:55 2014
From: bogus@does.not.exist.com ()
Date: Wed Nov 5 03:58:31 2014
Subject: No subject
Message-ID: <mailman.78.1415159911.3666.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 5 02:50:55 2014
From: bogus@does.not.exist.com ()
Date: Wed Nov 5 03:58:31 2014
Subject: No subject
Message-ID: <mailman.79.1415159911.3666.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 5 02:50:55 2014
From: bogus@does.not.exist.com ()
Date: Wed Nov 5 03:58:31 2014
Subject: No subject
Message-ID: <mailman.80.1415159911.3666.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 5 02:50:55 2014
From: bogus@does.not.exist.com ()
Date: Wed Nov 5 03:58:32 2014
Subject: No subject
Message-ID: <mailman.81.1415159912.3666.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 5 02:50:55 2014
From: bogus@does.not.exist.com ()
Date: Wed Nov 5 03:58:32 2014
Subject: No subject
Message-ID: <mailman.82.1415159912.3666.htk-users@eng.cam.ac.uk>

From bogus@does.not.exist.com Wed Nov 5 02:50:55 2014


From: bogus@does.not.exist.com ()
Date: Wed Nov 5 03:58:33 2014
Subject: No subject
Message-ID: <mailman.83.1415159913.3666.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 5 02:50:55 2014
From: bogus@does.not.exist.com ()
Date: Wed Nov 5 03:58:33 2014
Subject: No subject
Message-ID: <mailman.84.1415159913.3666.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 5 02:50:55 2014
From: bogus@does.not.exist.com ()
Date: Wed Nov 5 03:58:34 2014
Subject: No subject
Message-ID: <mailman.85.1415159914.3666.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 5 02:50:55 2014
From: bogus@does.not.exist.com ()
Date: Wed Nov 5 03:58:36 2014
Subject: No subject
Message-ID: <mailman.86.1415159916.3666.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 5 02:50:55 2014
From: bogus@does.not.exist.com ()
Date: Wed Nov 5 03:58:37 2014
Subject: No subject
Message-ID: <mailman.87.1415159917.3666.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 5 02:50:55 2014
From: bogus@does.not.exist.com ()
Date: Wed Nov 5 03:58:37 2014
Subject: No subject
Message-ID: <mailman.88.1415159917.3666.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 5 02:50:55 2014
From: bogus@does.not.exist.com ()
Date: Wed Nov 5 03:58:38 2014
Subject: No subject
Message-ID: <mailman.89.1415159918.3666.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 5 02:50:55 2014
From: bogus@does.not.exist.com ()
Date: Wed Nov 5 03:58:39 2014
Subject: No subject
Message-ID: <mailman.91.1415159919.3666.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 5 02:50:55 2014
From: bogus@does.not.exist.com ()
Date: Wed Nov 5 03:58:41 2014
Subject: No subject
Message-ID: <mailman.92.1415159921.3666.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 5 02:50:55 2014
From: bogus@does.not.exist.com ()
Date: Wed Nov 5 03:58:41 2014
Subject: No subject
Message-ID: <mailman.93.1415159921.3666.htk-users@eng.cam.ac.uk>

From bogus@does.not.exist.com Wed Nov 5 02:50:55 2014


From: bogus@does.not.exist.com ()
Date: Wed Nov 5 03:58:43 2014
Subject: No subject
Message-ID: <mailman.94.1415159923.3666.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 5 02:50:55 2014
From: bogus@does.not.exist.com ()
Date: Wed Nov 5 03:58:44 2014
Subject: No subject
Message-ID: <mailman.95.1415159924.3666.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 5 02:50:55 2014
From: bogus@does.not.exist.com ()
Date: Wed Nov 5 03:58:45 2014
Subject: No subject
Message-ID: <mailman.96.1415159925.3666.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 5 02:50:55 2014
From: bogus@does.not.exist.com ()
Date: Wed Nov 5 03:58:56 2014
Subject: No subject
Message-ID: <mailman.97.1415159936.3666.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 5 02:50:55 2014
From: bogus@does.not.exist.com ()
Date: Wed Nov 5 03:58:59 2014
Subject: No subject
Message-ID: <mailman.98.1415159939.3666.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 5 02:50:55 2014
From: bogus@does.not.exist.com ()
Date: Wed Nov 5 03:59:04 2014
Subject: No subject
Message-ID: <mailman.99.1415159944.3666.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 5 02:50:55 2014
From: bogus@does.not.exist.com ()
Date: Wed Nov 5 03:59:08 2014
Subject: No subject
Message-ID: <mailman.100.1415159948.3666.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 5 02:50:55 2014
From: bogus@does.not.exist.com ()
Date: Wed Nov 5 03:59:11 2014
Subject: No subject
Message-ID: <mailman.101.1415159951.3666.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 5 02:50:55 2014
From: bogus@does.not.exist.com ()
Date: Wed Nov 5 03:59:17 2014
Subject: No subject
Message-ID: <mailman.102.1415159957.3666.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 5 02:50:55 2014
From: bogus@does.not.exist.com ()
Date: Wed Nov 5 03:59:20 2014
Subject: No subject
Message-ID: <mailman.103.1415159960.3666.htk-users@eng.cam.ac.uk>

From tonyr at cantabResearch.com Tue Nov 4 20:04:46 2014


From: tonyr at cantabResearch.com (Tony Robinson)
Date: Wed Nov 5 04:16:44 2014
Subject: [HTK-Users] HTK license agreement
In-Reply-To: <545241EC02000049000E3077@pta-emo.csir.co.za>
References: <545241EC02000049000E3077@pta-emo.csir.co.za>
Message-ID: <5459315E.9030409@cantabResearch.com>
I just saw this post - I hope I haven't also missed any replies.
It's been a while since I read the HTK licence, but from memory and past
commercial practices I believe that what you are proposing is entirely
acceptable according to the HTK licence.
In fact I think www.speechmatics.com uses HVite in exactly this way to
do some final tidying up of the large vocabulary speech recognition output.
Tony
On 30/10/14 11:49, Georg Schlunz wrote:
> Good day
>
> Regarding the HTK license, as specified at http://htk.eng.cam.ac.uk/docs/licen
se.shtml , I would like to know whether the following scenario is permitted:
>
> The HTK software (including HVite) sits on a server in-house in our organisati
on, as per license sections 2.1 and 2.3.
> The HTK software (including HVite) is never distributed to a commercial (or no
n-commercial) party, as per license section 2.2.
>
> We have written our own server-client software, where:
> a) the client records speech and sends the audio file to the server, which pas
ses it on to HVite (the server software and HTK sit on the same in-house machine
)
> b) HVite decodes the audio into text
> c) the server replies to the client with the decoded text and the client proce
sses the text somehow
>
> Naturally, the client software contains no HTK code; it only processes data pr
oduced by HTK.
>
> Therefore, may this client software and decoding SERVICE be sold commercially
(as long as we agree to license sections 2.4 and 2.5)?
>
> Thank you
> Georg Schlunz
>
-- ** Cantab is hiring: www.cantabResearch.com/openings ** -Dr A J Robinson, Founder, Cantab Research Ltd
Phone direct: 01223 778240 office: 01223 794497
Company reg no GB 05697423, VAT reg no 925606030
51 Canterbury Street, Cambridge, CB4 3QG, UK
From bogus@does.not.exist.com Thu Nov 6 02:55:14 2014
From: bogus@does.not.exist.com ()
Date: Thu Nov 6 04:01:01 2014
Subject: No subject
Message-ID: <mailman.1.1415246461.21045.htk-users@eng.cam.ac.uk>

From bogus@does.not.exist.com Thu Nov 6 02:55:14 2014


From: bogus@does.not.exist.com ()
Date: Thu Nov 6 04:01:09 2014
Subject: No subject
Message-ID: <mailman.2.1415246469.21045.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 6 02:55:14 2014
From: bogus@does.not.exist.com ()
Date: Thu Nov 6 04:01:12 2014
Subject: No subject
Message-ID: <mailman.3.1415246472.21045.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 6 02:55:14 2014
From: bogus@does.not.exist.com ()
Date: Thu Nov 6 04:01:15 2014
Subject: No subject
Message-ID: <mailman.4.1415246475.21045.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 6 02:55:14 2014
From: bogus@does.not.exist.com ()
Date: Thu Nov 6 04:01:18 2014
Subject: No subject
Message-ID: <mailman.5.1415246478.21045.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 6 02:55:14 2014
From: bogus@does.not.exist.com ()
Date: Thu Nov 6 04:01:20 2014
Subject: No subject
Message-ID: <mailman.6.1415246480.21045.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 6 02:55:14 2014
From: bogus@does.not.exist.com ()
Date: Thu Nov 6 04:01:24 2014
Subject: No subject
Message-ID: <mailman.7.1415246484.21045.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 6 02:55:14 2014
From: bogus@does.not.exist.com ()
Date: Thu Nov 6 04:01:27 2014
Subject: No subject
Message-ID: <mailman.8.1415246486.21045.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 6 02:55:14 2014
From: bogus@does.not.exist.com ()
Date: Thu Nov 6 04:01:29 2014
Subject: No subject
Message-ID: <mailman.9.1415246489.21045.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 6 02:55:14 2014
From: bogus@does.not.exist.com ()
Date: Thu Nov 6 04:01:31 2014
Subject: No subject
Message-ID: <mailman.10.1415246491.21045.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 6 02:55:14 2014
From: bogus@does.not.exist.com ()
Date: Thu Nov 6 04:01:31 2014
Subject: No subject
Message-ID: <mailman.11.1415246491.21045.htk-users@eng.cam.ac.uk>

From bogus@does.not.exist.com Thu Nov 6 02:55:14 2014


From: bogus@does.not.exist.com ()
Date: Thu Nov 6 04:01:33 2014
Subject: No subject
Message-ID: <mailman.12.1415246493.21045.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 6 02:55:14 2014
From: bogus@does.not.exist.com ()
Date: Thu Nov 6 04:01:34 2014
Subject: No subject
Message-ID: <mailman.13.1415246494.21045.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 6 02:55:14 2014
From: bogus@does.not.exist.com ()
Date: Thu Nov 6 04:01:34 2014
Subject: No subject
Message-ID: <mailman.14.1415246494.21045.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 6 02:55:14 2014
From: bogus@does.not.exist.com ()
Date: Thu Nov 6 04:01:34 2014
Subject: No subject
Message-ID: <mailman.15.1415246494.21045.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 6 02:55:14 2014
From: bogus@does.not.exist.com ()
Date: Thu Nov 6 04:01:35 2014
Subject: No subject
Message-ID: <mailman.16.1415246495.21045.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 6 02:55:14 2014
From: bogus@does.not.exist.com ()
Date: Thu Nov 6 04:01:35 2014
Subject: No subject
Message-ID: <mailman.17.1415246495.21045.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 6 02:55:14 2014
From: bogus@does.not.exist.com ()
Date: Thu Nov 6 04:01:35 2014
Subject: No subject
Message-ID: <mailman.18.1415246495.21045.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 6 02:55:14 2014
From: bogus@does.not.exist.com ()
Date: Thu Nov 6 04:01:38 2014
Subject: No subject
Message-ID: <mailman.19.1415246498.21045.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 6 02:55:14 2014
From: bogus@does.not.exist.com ()
Date: Thu Nov 6 04:01:38 2014
Subject: No subject
Message-ID: <mailman.20.1415246498.21045.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 6 02:55:14 2014
From: bogus@does.not.exist.com ()
Date: Thu Nov 6 04:01:40 2014
Subject: No subject
Message-ID: <mailman.21.1415246500.21045.htk-users@eng.cam.ac.uk>

From bogus@does.not.exist.com Thu Nov 6 02:55:14 2014


From: bogus@does.not.exist.com ()
Date: Thu Nov 6 04:01:42 2014
Subject: No subject
Message-ID: <mailman.22.1415246502.21045.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 6 02:55:14 2014
From: bogus@does.not.exist.com ()
Date: Thu Nov 6 04:01:43 2014
Subject: No subject
Message-ID: <mailman.23.1415246503.21045.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 6 02:55:14 2014
From: bogus@does.not.exist.com ()
Date: Thu Nov 6 04:01:45 2014
Subject: No subject
Message-ID: <mailman.24.1415246505.21045.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 6 02:55:14 2014
From: bogus@does.not.exist.com ()
Date: Thu Nov 6 04:01:46 2014
Subject: No subject
Message-ID: <mailman.25.1415246506.21045.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 6 02:55:14 2014
From: bogus@does.not.exist.com ()
Date: Thu Nov 6 04:01:46 2014
Subject: No subject
Message-ID: <mailman.26.1415246506.21045.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 6 02:55:14 2014
From: bogus@does.not.exist.com ()
Date: Thu Nov 6 04:01:47 2014
Subject: No subject
Message-ID: <mailman.27.1415246507.21045.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 6 02:55:14 2014
From: bogus@does.not.exist.com ()
Date: Thu Nov 6 04:01:47 2014
Subject: No subject
Message-ID: <mailman.28.1415246507.21045.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 6 02:55:14 2014
From: bogus@does.not.exist.com ()
Date: Thu Nov 6 04:01:48 2014
Subject: No subject
Message-ID: <mailman.29.1415246508.21045.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 6 02:55:14 2014
From: bogus@does.not.exist.com ()
Date: Thu Nov 6 04:01:51 2014
Subject: No subject
Message-ID: <mailman.30.1415246511.21045.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 6 02:55:14 2014
From: bogus@does.not.exist.com ()
Date: Thu Nov 6 04:01:51 2014
Subject: No subject
Message-ID: <mailman.31.1415246511.21045.htk-users@eng.cam.ac.uk>

From bogus@does.not.exist.com Thu Nov 6 02:55:14 2014


From: bogus@does.not.exist.com ()
Date: Thu Nov 6 04:01:52 2014
Subject: No subject
Message-ID: <mailman.32.1415246512.21045.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 6 02:55:14 2014
From: bogus@does.not.exist.com ()
Date: Thu Nov 6 04:01:52 2014
Subject: No subject
Message-ID: <mailman.33.1415246512.21045.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 6 02:55:14 2014
From: bogus@does.not.exist.com ()
Date: Thu Nov 6 04:01:52 2014
Subject: No subject
Message-ID: <mailman.34.1415246512.21045.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 6 02:55:14 2014
From: bogus@does.not.exist.com ()
Date: Thu Nov 6 04:01:53 2014
Subject: No subject
Message-ID: <mailman.35.1415246513.21045.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 6 02:55:14 2014
From: bogus@does.not.exist.com ()
Date: Thu Nov 6 04:01:53 2014
Subject: No subject
Message-ID: <mailman.36.1415246513.21045.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 6 02:55:14 2014
From: bogus@does.not.exist.com ()
Date: Thu Nov 6 04:01:53 2014
Subject: No subject
Message-ID: <mailman.37.1415246513.21045.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 6 02:55:14 2014
From: bogus@does.not.exist.com ()
Date: Thu Nov 6 04:01:56 2014
Subject: No subject
Message-ID: <mailman.38.1415246516.21045.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 6 02:55:14 2014
From: bogus@does.not.exist.com ()
Date: Thu Nov 6 04:01:58 2014
Subject: No subject
Message-ID: <mailman.39.1415246518.21045.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 6 02:55:14 2014
From: bogus@does.not.exist.com ()
Date: Thu Nov 6 04:01:59 2014
Subject: No subject
Message-ID: <mailman.40.1415246519.21045.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 6 02:55:14 2014
From: bogus@does.not.exist.com ()
Date: Thu Nov 6 04:02:01 2014
Subject: No subject
Message-ID: <mailman.41.1415246521.21045.htk-users@eng.cam.ac.uk>

From bogus@does.not.exist.com Thu Nov 6 02:55:14 2014


From: bogus@does.not.exist.com ()
Date: Thu Nov 6 04:02:01 2014
Subject: No subject
Message-ID: <mailman.42.1415246521.21045.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 6 02:55:14 2014
From: bogus@does.not.exist.com ()
Date: Thu Nov 6 04:02:02 2014
Subject: No subject
Message-ID: <mailman.43.1415246522.21045.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 6 02:55:14 2014
From: bogus@does.not.exist.com ()
Date: Thu Nov 6 04:02:03 2014
Subject: No subject
Message-ID: <mailman.44.1415246523.21045.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 6 02:55:14 2014
From: bogus@does.not.exist.com ()
Date: Thu Nov 6 04:02:03 2014
Subject: No subject
Message-ID: <mailman.45.1415246523.21045.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 6 02:55:14 2014
From: bogus@does.not.exist.com ()
Date: Thu Nov 6 04:02:04 2014
Subject: No subject
Message-ID: <mailman.46.1415246524.21045.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 6 02:55:14 2014
From: bogus@does.not.exist.com ()
Date: Thu Nov 6 04:02:05 2014
Subject: No subject
Message-ID: <mailman.47.1415246525.21045.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 6 02:55:14 2014
From: bogus@does.not.exist.com ()
Date: Thu Nov 6 04:02:06 2014
Subject: No subject
Message-ID: <mailman.48.1415246526.21045.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 6 02:55:14 2014
From: bogus@does.not.exist.com ()
Date: Thu Nov 6 04:02:20 2014
Subject: No subject
Message-ID: <mailman.49.1415246540.21045.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 6 02:55:14 2014
From: bogus@does.not.exist.com ()
Date: Thu Nov 6 04:02:23 2014
Subject: No subject
Message-ID: <mailman.50.1415246543.21045.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 6 02:55:14 2014
From: bogus@does.not.exist.com ()
Date: Thu Nov 6 04:02:26 2014
Subject: No subject
Message-ID: <mailman.51.1415246546.21045.htk-users@eng.cam.ac.uk>

From bogus@does.not.exist.com Thu Nov 6 02:55:14 2014


From: bogus@does.not.exist.com ()
Date: Thu Nov 6 04:02:29 2014
Subject: No subject
Message-ID: <mailman.52.1415246549.21045.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 6 02:55:14 2014
From: bogus@does.not.exist.com ()
Date: Thu Nov 6 04:02:32 2014
Subject: No subject
Message-ID: <mailman.53.1415246552.21045.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 6 02:55:14 2014
From: bogus@does.not.exist.com ()
Date: Thu Nov 6 04:02:35 2014
Subject: No subject
Message-ID: <mailman.54.1415246555.21045.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 6 02:55:14 2014
From: bogus@does.not.exist.com ()
Date: Thu Nov 6 04:02:38 2014
Subject: No subject
Message-ID: <mailman.55.1415246558.21045.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 6 02:55:14 2014
From: bogus@does.not.exist.com ()
Date: Thu Nov 6 04:02:40 2014
Subject: No subject
Message-ID: <mailman.56.1415246560.21045.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 6 02:55:14 2014
From: bogus@does.not.exist.com ()
Date: Thu Nov 6 04:02:42 2014
Subject: No subject
Message-ID: <mailman.57.1415246562.21045.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 6 02:55:14 2014
From: bogus@does.not.exist.com ()
Date: Thu Nov 6 04:02:42 2014
Subject: No subject
Message-ID: <mailman.58.1415246562.21045.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 6 02:55:14 2014
From: bogus@does.not.exist.com ()
Date: Thu Nov 6 04:02:43 2014
Subject: No subject
Message-ID: <mailman.59.1415246563.21045.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 6 02:55:14 2014
From: bogus@does.not.exist.com ()
Date: Thu Nov 6 04:02:43 2014
Subject: No subject
Message-ID: <mailman.60.1415246563.21045.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 6 02:55:14 2014
From: bogus@does.not.exist.com ()
Date: Thu Nov 6 04:02:43 2014
Subject: No subject
Message-ID: <mailman.61.1415246563.21045.htk-users@eng.cam.ac.uk>

From bogus@does.not.exist.com Thu Nov 6 02:55:14 2014


From: bogus@does.not.exist.com ()
Date: Thu Nov 6 04:02:44 2014
Subject: No subject
Message-ID: <mailman.62.1415246564.21045.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 6 02:55:14 2014
From: bogus@does.not.exist.com ()
Date: Thu Nov 6 04:02:44 2014
Subject: No subject
Message-ID: <mailman.63.1415246564.21045.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 6 02:55:14 2014
From: bogus@does.not.exist.com ()
Date: Thu Nov 6 04:02:45 2014
Subject: No subject
Message-ID: <mailman.64.1415246565.21045.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 6 02:55:14 2014
From: bogus@does.not.exist.com ()
Date: Thu Nov 6 04:02:45 2014
Subject: No subject
Message-ID: <mailman.65.1415246565.21045.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 6 02:55:14 2014
From: bogus@does.not.exist.com ()
Date: Thu Nov 6 04:02:46 2014
Subject: No subject
Message-ID: <mailman.66.1415246566.21045.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 6 02:55:14 2014
From: bogus@does.not.exist.com ()
Date: Thu Nov 6 04:02:46 2014
Subject: No subject
Message-ID: <mailman.67.1415246566.21045.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 6 02:55:14 2014
From: bogus@does.not.exist.com ()
Date: Thu Nov 6 04:02:46 2014
Subject: No subject
Message-ID: <mailman.68.1415246566.21045.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 6 02:55:14 2014
From: bogus@does.not.exist.com ()
Date: Thu Nov 6 04:02:47 2014
Subject: No subject
Message-ID: <mailman.69.1415246567.21045.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 6 02:55:14 2014
From: bogus@does.not.exist.com ()
Date: Thu Nov 6 04:02:49 2014
Subject: No subject
Message-ID: <mailman.70.1415246569.21045.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 6 02:55:14 2014
From: bogus@does.not.exist.com ()
Date: Thu Nov 6 04:02:50 2014
Subject: No subject
Message-ID: <mailman.71.1415246570.21045.htk-users@eng.cam.ac.uk>

From bogus@does.not.exist.com Thu Nov 6 02:55:14 2014


From: bogus@does.not.exist.com ()
Date: Thu Nov 6 04:02:50 2014
Subject: No subject
Message-ID: <mailman.72.1415246570.21045.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 6 02:55:14 2014
From: bogus@does.not.exist.com ()
Date: Thu Nov 6 04:02:51 2014
Subject: No subject
Message-ID: <mailman.73.1415246571.21045.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 6 02:55:14 2014
From: bogus@does.not.exist.com ()
Date: Thu Nov 6 04:02:51 2014
Subject: No subject
Message-ID: <mailman.74.1415246571.21045.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 6 02:55:14 2014
From: bogus@does.not.exist.com ()
Date: Thu Nov 6 04:02:51 2014
Subject: No subject
Message-ID: <mailman.75.1415246571.21045.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 6 02:55:14 2014
From: bogus@does.not.exist.com ()
Date: Thu Nov 6 04:02:52 2014
Subject: No subject
Message-ID: <mailman.76.1415246572.21045.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 6 02:55:14 2014
From: bogus@does.not.exist.com ()
Date: Thu Nov 6 04:02:52 2014
Subject: No subject
Message-ID: <mailman.77.1415246572.21045.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 6 02:55:14 2014
From: bogus@does.not.exist.com ()
Date: Thu Nov 6 04:02:52 2014
Subject: No subject
Message-ID: <mailman.78.1415246572.21045.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 6 02:55:14 2014
From: bogus@does.not.exist.com ()
Date: Thu Nov 6 04:02:53 2014
Subject: No subject
Message-ID: <mailman.79.1415246573.21045.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 6 02:55:14 2014
From: bogus@does.not.exist.com ()
Date: Thu Nov 6 04:02:54 2014
Subject: No subject
Message-ID: <mailman.80.1415246574.21045.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 6 02:55:14 2014
From: bogus@does.not.exist.com ()
Date: Thu Nov 6 04:02:54 2014
Subject: No subject
Message-ID: <mailman.81.1415246574.21045.htk-users@eng.cam.ac.uk>

From bogus@does.not.exist.com Thu Nov 6 02:55:14 2014


From: bogus@does.not.exist.com ()
Date: Thu Nov 6 04:02:54 2014
Subject: No subject
Message-ID: <mailman.82.1415246574.21045.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 6 02:55:14 2014
From: bogus@does.not.exist.com ()
Date: Thu Nov 6 04:02:55 2014
Subject: No subject
Message-ID: <mailman.83.1415246575.21045.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 6 02:55:14 2014
From: bogus@does.not.exist.com ()
Date: Thu Nov 6 04:02:56 2014
Subject: No subject
Message-ID: <mailman.84.1415246576.21045.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 6 02:55:14 2014
From: bogus@does.not.exist.com ()
Date: Thu Nov 6 04:02:57 2014
Subject: No subject
Message-ID: <mailman.85.1415246577.21045.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 6 02:55:14 2014
From: bogus@does.not.exist.com ()
Date: Thu Nov 6 04:02:58 2014
Subject: No subject
Message-ID: <mailman.86.1415246578.21045.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 6 02:55:14 2014
From: bogus@does.not.exist.com ()
Date: Thu Nov 6 04:02:59 2014
Subject: No subject
Message-ID: <mailman.87.1415246579.21045.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 6 02:55:14 2014
From: bogus@does.not.exist.com ()
Date: Thu Nov 6 04:03:00 2014
Subject: No subject
Message-ID: <mailman.88.1415246580.21045.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 6 02:55:14 2014
From: bogus@does.not.exist.com ()
Date: Thu Nov 6 04:03:02 2014
Subject: No subject
Message-ID: <mailman.89.1415246582.21045.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 6 02:55:14 2014
From: bogus@does.not.exist.com ()
Date: Thu Nov 6 04:03:04 2014
Subject: No subject
Message-ID: <mailman.91.1415246584.21045.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 6 02:55:14 2014
From: bogus@does.not.exist.com ()
Date: Thu Nov 6 04:03:21 2014
Subject: No subject
Message-ID: <mailman.92.1415246601.21045.htk-users@eng.cam.ac.uk>

From bogus@does.not.exist.com Thu Nov 6 02:55:14 2014


From: bogus@does.not.exist.com ()
Date: Thu Nov 6 04:03:24 2014
Subject: No subject
Message-ID: <mailman.93.1415246604.21045.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 6 02:55:14 2014
From: bogus@does.not.exist.com ()
Date: Thu Nov 6 04:03:28 2014
Subject: No subject
Message-ID: <mailman.94.1415246608.21045.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 6 02:55:14 2014
From: bogus@does.not.exist.com ()
Date: Thu Nov 6 04:03:31 2014
Subject: No subject
Message-ID: <mailman.95.1415246611.21045.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 6 02:55:14 2014
From: bogus@does.not.exist.com ()
Date: Thu Nov 6 04:03:35 2014
Subject: No subject
Message-ID: <mailman.96.1415246615.21045.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 6 02:55:14 2014
From: bogus@does.not.exist.com ()
Date: Thu Nov 6 04:03:40 2014
Subject: No subject
Message-ID: <mailman.97.1415246619.21045.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 6 02:55:14 2014
From: bogus@does.not.exist.com ()
Date: Thu Nov 6 04:03:43 2014
Subject: No subject
Message-ID: <mailman.98.1415246622.21045.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 6 02:55:14 2014
From: bogus@does.not.exist.com ()
Date: Thu Nov 6 04:03:47 2014
Subject: No subject
Message-ID: <mailman.99.1415246627.21045.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 6 02:55:14 2014
From: bogus@does.not.exist.com ()
Date: Thu Nov 6 04:03:51 2014
Subject: No subject
Message-ID: <mailman.100.1415246631.21045.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 6 02:55:14 2014
From: bogus@does.not.exist.com ()
Date: Thu Nov 6 04:03:53 2014
Subject: No subject
Message-ID: <mailman.101.1415246633.21045.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 6 02:55:14 2014
From: bogus@does.not.exist.com ()
Date: Thu Nov 6 04:03:54 2014
Subject: No subject
Message-ID: <mailman.102.1415246634.21045.htk-users@eng.cam.ac.uk>

From bogus@does.not.exist.com Thu Nov 6 02:55:14 2014


From: bogus@does.not.exist.com ()
Date: Thu Nov 6 04:03:55 2014
Subject: No subject
Message-ID: <mailman.103.1415246635.21045.htk-users@eng.cam.ac.uk>
From tonyr at cantabResearch.com Tue Nov 4 20:04:46 2014
From: tonyr at cantabResearch.com (Tony Robinson)
Date: Thu Nov 6 04:20:40 2014
Subject: [HTK-Users] HTK license agreement
In-Reply-To: <545241EC02000049000E3077@pta-emo.csir.co.za>
References: <545241EC02000049000E3077@pta-emo.csir.co.za>
Message-ID: <5459315E.9030409@cantabResearch.com>
I just saw this post - I hope I haven't also missed any replies.
It's been a while since I read the HTK licence, but from memory and past
commercial practices I believe that what you are proposing is entirely
acceptable according to the HTK licence.
In fact I think www.speechmatics.com uses HVite in exactly this way to
do some final tidying up of the large vocabulary speech recognition output.
Tony
On 30/10/14 11:49, Georg Schlunz wrote:
> Good day
>
> Regarding the HTK license, as specified at http://htk.eng.cam.ac.uk/docs/licen
se.shtml , I would like to know whether the following scenario is permitted:
>
> The HTK software (including HVite) sits on a server in-house in our organisati
on, as per license sections 2.1 and 2.3.
> The HTK software (including HVite) is never distributed to a commercial (or no
n-commercial) party, as per license section 2.2.
>
> We have written our own server-client software, where:
> a) the client records speech and sends the audio file to the server, which pas
ses it on to HVite (the server software and HTK sit on the same in-house machine
)
> b) HVite decodes the audio into text
> c) the server replies to the client with the decoded text and the client proce
sses the text somehow
>
> Naturally, the client software contains no HTK code; it only processes data pr
oduced by HTK.
>
> Therefore, may this client software and decoding SERVICE be sold commercially
(as long as we agree to license sections 2.4 and 2.5)?
>
> Thank you
> Georg Schlunz
>
-- ** Cantab is hiring: www.cantabResearch.com/openings ** -Dr A J Robinson, Founder, Cantab Research Ltd
Phone direct: 01223 778240 office: 01223 794497
Company reg no GB 05697423, VAT reg no 925606030

51 Canterbury Street, Cambridge, CB4 3QG, UK


From bogus@does.not.exist.com Fri Nov 7 02:50:35 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 7 03:59:35 2014
Subject: No subject
Message-ID: <mailman.1.1415332774.2343.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 7 02:50:35 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 7 03:59:41 2014
Subject: No subject
Message-ID: <mailman.2.1415332781.2343.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 7 02:50:35 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 7 03:59:42 2014
Subject: No subject
Message-ID: <mailman.3.1415332782.2343.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 7 02:50:35 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 7 03:59:42 2014
Subject: No subject
Message-ID: <mailman.4.1415332782.2343.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 7 02:50:35 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 7 03:59:43 2014
Subject: No subject
Message-ID: <mailman.5.1415332783.2343.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 7 02:50:35 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 7 03:59:44 2014
Subject: No subject
Message-ID: <mailman.6.1415332784.2343.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 7 02:50:35 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 7 03:59:45 2014
Subject: No subject
Message-ID: <mailman.7.1415332785.2343.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 7 02:50:35 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 7 03:59:45 2014
Subject: No subject
Message-ID: <mailman.8.1415332785.2343.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 7 02:50:35 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 7 03:59:46 2014
Subject: No subject
Message-ID: <mailman.9.1415332786.2343.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 7 02:50:35 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 7 03:59:53 2014
Subject: No subject

Message-ID: <mailman.10.1415332793.2343.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 7 02:50:35 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 7 03:59:56 2014
Subject: No subject
Message-ID: <mailman.11.1415332796.2343.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 7 02:50:35 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 7 04:00:01 2014
Subject: No subject
Message-ID: <mailman.12.1415332801.2343.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 7 02:50:35 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 7 04:00:07 2014
Subject: No subject
Message-ID: <mailman.13.1415332805.2343.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 7 02:50:35 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 7 04:00:10 2014
Subject: No subject
Message-ID: <mailman.14.1415332810.2343.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 7 02:50:35 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 7 04:00:12 2014
Subject: No subject
Message-ID: <mailman.15.1415332812.2343.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 7 02:50:35 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 7 04:00:15 2014
Subject: No subject
Message-ID: <mailman.16.1415332815.2343.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 7 02:50:35 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 7 04:00:17 2014
Subject: No subject
Message-ID: <mailman.17.1415332817.2343.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 7 02:50:35 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 7 04:00:19 2014
Subject: No subject
Message-ID: <mailman.18.1415332819.2343.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 7 02:50:35 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 7 04:00:27 2014
Subject: No subject
Message-ID: <mailman.19.1415332827.2343.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 7 02:50:35 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 7 04:00:29 2014
Subject: No subject

Message-ID: <mailman.20.1415332829.2343.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 7 02:50:35 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 7 04:00:33 2014
Subject: No subject
Message-ID: <mailman.21.1415332833.2343.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 7 02:50:35 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 7 04:00:36 2014
Subject: No subject
Message-ID: <mailman.22.1415332836.2343.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 7 02:50:35 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 7 04:00:36 2014
Subject: No subject
Message-ID: <mailman.23.1415332836.2343.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 7 02:50:35 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 7 04:00:39 2014
Subject: No subject
Message-ID: <mailman.24.1415332839.2343.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 7 02:50:35 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 7 04:00:41 2014
Subject: No subject
Message-ID: <mailman.25.1415332841.2343.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 7 02:50:35 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 7 04:00:42 2014
Subject: No subject
Message-ID: <mailman.26.1415332842.2343.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 7 02:50:35 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 7 04:00:42 2014
Subject: No subject
Message-ID: <mailman.27.1415332842.2343.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 7 02:50:35 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 7 04:00:43 2014
Subject: No subject
Message-ID: <mailman.28.1415332843.2343.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 7 02:50:35 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 7 04:00:43 2014
Subject: No subject
Message-ID: <mailman.29.1415332843.2343.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 7 02:50:35 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 7 04:00:46 2014
Subject: No subject

Message-ID: <mailman.30.1415332846.2343.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 7 02:50:35 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 7 04:00:46 2014
Subject: No subject
Message-ID: <mailman.31.1415332846.2343.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 7 02:50:35 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 7 04:00:47 2014
Subject: No subject
Message-ID: <mailman.32.1415332847.2343.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 7 02:50:35 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 7 04:00:47 2014
Subject: No subject
Message-ID: <mailman.33.1415332847.2343.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 7 02:50:35 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 7 04:00:48 2014
Subject: No subject
Message-ID: <mailman.34.1415332848.2343.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 7 02:50:35 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 7 04:00:48 2014
Subject: No subject
Message-ID: <mailman.35.1415332848.2343.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 7 02:50:35 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 7 04:00:48 2014
Subject: No subject
Message-ID: <mailman.36.1415332848.2343.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 7 02:50:35 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 7 04:00:49 2014
Subject: No subject
Message-ID: <mailman.37.1415332849.2343.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 7 02:50:35 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 7 04:00:49 2014
Subject: No subject
Message-ID: <mailman.38.1415332849.2343.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 7 02:50:35 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 7 04:00:50 2014
Subject: No subject
Message-ID: <mailman.39.1415332850.2343.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 7 02:50:35 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 7 04:00:50 2014
Subject: No subject

Message-ID: <mailman.40.1415332850.2343.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 7 02:50:35 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 7 04:00:53 2014
Subject: No subject
Message-ID: <mailman.41.1415332853.2343.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 7 02:50:35 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 7 04:00:54 2014
Subject: No subject
Message-ID: <mailman.42.1415332854.2343.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 7 02:50:35 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 7 04:00:54 2014
Subject: No subject
Message-ID: <mailman.43.1415332854.2343.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 7 02:50:35 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 7 04:00:54 2014
Subject: No subject
Message-ID: <mailman.44.1415332854.2343.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 7 02:50:35 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 7 04:00:55 2014
Subject: No subject
Message-ID: <mailman.45.1415332855.2343.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 7 02:50:35 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 7 04:00:55 2014
Subject: No subject
Message-ID: <mailman.46.1415332855.2343.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 7 02:50:35 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 7 04:00:56 2014
Subject: No subject
Message-ID: <mailman.47.1415332856.2343.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 7 02:50:35 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 7 04:00:56 2014
Subject: No subject
Message-ID: <mailman.48.1415332856.2343.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 7 02:50:35 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 7 04:00:58 2014
Subject: No subject
Message-ID: <mailman.49.1415332858.2343.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 7 02:50:35 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 7 04:00:58 2014
Subject: No subject

Message-ID: <mailman.50.1415332858.2343.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 7 02:50:35 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 7 04:00:59 2014
Subject: No subject
Message-ID: <mailman.51.1415332859.2343.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 7 02:50:35 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 7 04:00:59 2014
Subject: No subject
Message-ID: <mailman.52.1415332859.2343.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 7 02:50:35 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 7 04:01:00 2014
Subject: No subject
Message-ID: <mailman.53.1415332860.2343.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 7 02:50:35 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 7 04:01:00 2014
Subject: No subject
Message-ID: <mailman.54.1415332860.2343.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 7 02:50:35 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 7 04:01:07 2014
Subject: No subject
Message-ID: <mailman.55.1415332867.2343.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 7 02:50:35 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 7 04:01:08 2014
Subject: No subject
Message-ID: <mailman.56.1415332868.2343.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 7 02:50:35 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 7 04:01:13 2014
Subject: No subject
Message-ID: <mailman.57.1415332872.2343.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 7 02:50:35 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 7 04:01:17 2014
Subject: No subject
Message-ID: <mailman.58.1415332877.2343.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 7 02:50:35 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 7 04:01:20 2014
Subject: No subject
Message-ID: <mailman.59.1415332880.2343.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 7 02:50:35 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 7 04:01:23 2014
Subject: No subject

Message-ID: <mailman.60.1415332883.2343.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 7 02:50:35 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 7 04:01:25 2014
Subject: No subject
Message-ID: <mailman.61.1415332885.2343.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 7 02:50:35 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 7 04:01:32 2014
Subject: No subject
Message-ID: <mailman.62.1415332891.2343.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 7 02:50:35 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 7 04:01:36 2014
Subject: No subject
Message-ID: <mailman.63.1415332896.2343.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 7 02:50:35 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 7 04:01:44 2014
Subject: No subject
Message-ID: <mailman.64.1415332904.2343.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 7 02:50:35 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 7 04:01:59 2014
Subject: No subject
Message-ID: <mailman.65.1415332918.2343.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 7 02:50:35 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 7 04:02:05 2014
Subject: No subject
Message-ID: <mailman.66.1415332925.2343.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 7 02:50:35 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 7 04:02:05 2014
Subject: No subject
Message-ID: <mailman.67.1415332925.2343.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 7 02:50:35 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 7 04:02:06 2014
Subject: No subject
Message-ID: <mailman.68.1415332926.2343.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 7 02:50:35 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 7 04:02:06 2014
Subject: No subject
Message-ID: <mailman.69.1415332926.2343.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 7 02:50:35 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 7 04:02:09 2014
Subject: No subject

Message-ID: <mailman.70.1415332929.2343.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 7 02:50:35 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 7 04:02:09 2014
Subject: No subject
Message-ID: <mailman.71.1415332929.2343.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 7 02:50:35 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 7 04:02:10 2014
Subject: No subject
Message-ID: <mailman.72.1415332930.2343.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 7 02:50:35 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 7 04:02:11 2014
Subject: No subject
Message-ID: <mailman.73.1415332931.2343.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 7 02:50:35 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 7 04:02:11 2014
Subject: No subject
Message-ID: <mailman.74.1415332931.2343.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 7 02:50:35 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 7 04:02:13 2014
Subject: No subject
Message-ID: <mailman.75.1415332933.2343.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 7 02:50:35 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 7 04:02:14 2014
Subject: No subject
Message-ID: <mailman.76.1415332934.2343.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 7 02:50:35 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 7 04:02:15 2014
Subject: No subject
Message-ID: <mailman.77.1415332935.2343.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 7 02:50:35 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 7 04:02:15 2014
Subject: No subject
Message-ID: <mailman.78.1415332935.2343.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 7 02:50:35 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 7 04:02:16 2014
Subject: No subject
Message-ID: <mailman.79.1415332936.2343.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 7 02:50:35 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 7 04:02:17 2014
Subject: No subject

Message-ID: <mailman.80.1415332937.2343.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 7 02:50:35 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 7 04:02:17 2014
Subject: No subject
Message-ID: <mailman.81.1415332937.2343.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 7 02:50:35 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 7 04:02:18 2014
Subject: No subject
Message-ID: <mailman.82.1415332938.2343.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 7 02:50:35 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 7 04:02:18 2014
Subject: No subject
Message-ID: <mailman.83.1415332938.2343.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 7 02:50:35 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 7 04:02:22 2014
Subject: No subject
Message-ID: <mailman.84.1415332942.2343.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 7 02:50:35 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 7 04:02:23 2014
Subject: No subject
Message-ID: <mailman.85.1415332943.2343.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 7 02:50:35 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 7 04:02:25 2014
Subject: No subject
Message-ID: <mailman.86.1415332945.2343.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 7 02:50:35 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 7 04:02:27 2014
Subject: No subject
Message-ID: <mailman.87.1415332947.2343.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 7 02:50:35 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 7 04:02:28 2014
Subject: No subject
Message-ID: <mailman.88.1415332948.2343.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 7 02:50:35 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 7 04:02:29 2014
Subject: No subject
Message-ID: <mailman.89.1415332949.2343.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 7 02:50:35 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 7 04:02:30 2014
Subject: No subject

Message-ID: <mailman.91.1415332950.2343.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 7 02:50:35 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 7 04:02:32 2014
Subject: No subject
Message-ID: <mailman.92.1415332952.2343.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 7 02:50:35 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 7 04:02:33 2014
Subject: No subject
Message-ID: <mailman.93.1415332953.2343.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 7 02:50:35 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 7 04:02:47 2014
Subject: No subject
Message-ID: <mailman.94.1415332966.2343.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 7 02:50:35 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 7 04:02:52 2014
Subject: No subject
Message-ID: <mailman.95.1415332971.2343.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 7 02:50:35 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 7 04:02:55 2014
Subject: No subject
Message-ID: <mailman.96.1415332975.2343.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 7 02:50:35 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 7 04:02:57 2014
Subject: No subject
Message-ID: <mailman.97.1415332977.2343.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 7 02:50:35 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 7 04:02:58 2014
Subject: No subject
Message-ID: <mailman.98.1415332978.2343.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 7 02:50:35 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 7 04:03:04 2014
Subject: No subject
Message-ID: <mailman.99.1415332984.2343.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 7 02:50:35 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 7 04:03:09 2014
Subject: No subject
Message-ID: <mailman.100.1415332989.2343.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 7 02:50:35 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 7 04:03:11 2014
Subject: No subject

Message-ID: <mailman.101.1415332991.2343.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 7 02:50:35 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 7 04:03:12 2014
Subject: No subject
Message-ID: <mailman.102.1415332992.2343.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 7 02:50:35 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 7 04:03:13 2014
Subject: No subject
Message-ID: <mailman.103.1415332993.2343.htk-users@eng.cam.ac.uk>
From tonyr at cantabResearch.com Tue Nov 4 20:04:46 2014
From: tonyr at cantabResearch.com (Tony Robinson)
Date: Fri Nov 7 04:29:00 2014
Subject: [HTK-Users] HTK license agreement
In-Reply-To: <545241EC02000049000E3077@pta-emo.csir.co.za>
References: <545241EC02000049000E3077@pta-emo.csir.co.za>
Message-ID: <5459315E.9030409@cantabResearch.com>
I just saw this post - I hope I haven't also missed any replies.
It's been a while since I read the HTK licence, but from memory and past
commercial practices I believe that what you are proposing is entirely
acceptable according to the HTK licence.
In fact I think www.speechmatics.com uses HVite in exactly this way to
do some final tidying up of the large vocabulary speech recognition output.
Tony
On 30/10/14 11:49, Georg Schlunz wrote:
> Good day
>
> Regarding the HTK license, as specified at http://htk.eng.cam.ac.uk/docs/licen
se.shtml , I would like to know whether the following scenario is permitted:
>
> The HTK software (including HVite) sits on a server in-house in our organisati
on, as per license sections 2.1 and 2.3.
> The HTK software (including HVite) is never distributed to a commercial (or no
n-commercial) party, as per license section 2.2.
>
> We have written our own server-client software, where:
> a) the client records speech and sends the audio file to the server, which pas
ses it on to HVite (the server software and HTK sit on the same in-house machine
)
> b) HVite decodes the audio into text
> c) the server replies to the client with the decoded text and the client proce
sses the text somehow
>
> Naturally, the client software contains no HTK code; it only processes data pr
oduced by HTK.
>
> Therefore, may this client software and decoding SERVICE be sold commercially
(as long as we agree to license sections 2.4 and 2.5)?
>
> Thank you

> Georg Schlunz


>
-- ** Cantab is hiring: www.cantabResearch.com/openings ** -Dr A J Robinson, Founder, Cantab Research Ltd
Phone direct: 01223 778240 office: 01223 794497
Company reg no GB 05697423, VAT reg no 925606030
51 Canterbury Street, Cambridge, CB4 3QG, UK
From bogus@does.not.exist.com Wed Nov 19 02:50:31 2014
From: bogus@does.not.exist.com ()
Date: Wed Nov 19 03:41:32 2014
Subject: No subject
Message-ID: <mailman.1.1416368490.1610.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 19 02:50:31 2014
From: bogus@does.not.exist.com ()
Date: Wed Nov 19 03:41:48 2014
Subject: No subject
Message-ID: <mailman.2.1416368508.1610.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 19 02:50:31 2014
From: bogus@does.not.exist.com ()
Date: Wed Nov 19 03:41:48 2014
Subject: No subject
Message-ID: <mailman.3.1416368508.1610.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 19 02:50:31 2014
From: bogus@does.not.exist.com ()
Date: Wed Nov 19 03:41:50 2014
Subject: No subject
Message-ID: <mailman.4.1416368510.1610.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 19 02:50:31 2014
From: bogus@does.not.exist.com ()
Date: Wed Nov 19 03:41:54 2014
Subject: No subject
Message-ID: <mailman.5.1416368513.1610.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 19 02:50:31 2014
From: bogus@does.not.exist.com ()
Date: Wed Nov 19 03:41:58 2014
Subject: No subject
Message-ID: <mailman.6.1416368518.1610.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 19 02:50:31 2014
From: bogus@does.not.exist.com ()
Date: Wed Nov 19 03:42:03 2014
Subject: No subject
Message-ID: <mailman.7.1416368523.1610.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 19 02:50:31 2014
From: bogus@does.not.exist.com ()
Date: Wed Nov 19 03:42:04 2014
Subject: No subject
Message-ID: <mailman.8.1416368524.1610.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 19 02:50:31 2014
From: bogus@does.not.exist.com ()
Date: Wed Nov 19 03:42:05 2014

Subject: No subject
Message-ID: <mailman.9.1416368525.1610.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 19 02:50:31 2014
From: bogus@does.not.exist.com ()
Date: Wed Nov 19 03:42:15 2014
Subject: No subject
Message-ID: <mailman.10.1416368534.1610.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 19 02:50:31 2014
From: bogus@does.not.exist.com ()
Date: Wed Nov 19 03:42:17 2014
Subject: No subject
Message-ID: <mailman.11.1416368537.1610.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 19 02:50:31 2014
From: bogus@does.not.exist.com ()
Date: Wed Nov 19 03:42:20 2014
Subject: No subject
Message-ID: <mailman.12.1416368540.1610.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 19 02:50:31 2014
From: bogus@does.not.exist.com ()
Date: Wed Nov 19 03:42:24 2014
Subject: No subject
Message-ID: <mailman.13.1416368544.1610.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 19 02:50:31 2014
From: bogus@does.not.exist.com ()
Date: Wed Nov 19 03:42:24 2014
Subject: No subject
Message-ID: <mailman.14.1416368544.1610.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 19 02:50:31 2014
From: bogus@does.not.exist.com ()
Date: Wed Nov 19 03:42:25 2014
Subject: No subject
Message-ID: <mailman.15.1416368545.1610.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 19 02:50:31 2014
From: bogus@does.not.exist.com ()
Date: Wed Nov 19 03:42:27 2014
Subject: No subject
Message-ID: <mailman.16.1416368547.1610.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 19 02:50:31 2014
From: bogus@does.not.exist.com ()
Date: Wed Nov 19 03:42:29 2014
Subject: No subject
Message-ID: <mailman.17.1416368549.1610.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 19 02:50:31 2014
From: bogus@does.not.exist.com ()
Date: Wed Nov 19 03:42:32 2014
Subject: No subject
Message-ID: <mailman.18.1416368552.1610.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 19 02:50:31 2014
From: bogus@does.not.exist.com ()
Date: Wed Nov 19 03:42:40 2014

Subject: No subject
Message-ID: <mailman.19.1416368560.1610.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 19 02:50:31 2014
From: bogus@does.not.exist.com ()
Date: Wed Nov 19 03:42:42 2014
Subject: No subject
Message-ID: <mailman.20.1416368562.1610.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 19 02:50:31 2014
From: bogus@does.not.exist.com ()
Date: Wed Nov 19 03:42:48 2014
Subject: No subject
Message-ID: <mailman.21.1416368568.1610.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 19 02:50:31 2014
From: bogus@does.not.exist.com ()
Date: Wed Nov 19 03:42:52 2014
Subject: No subject
Message-ID: <mailman.22.1416368572.1610.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 19 02:50:31 2014
From: bogus@does.not.exist.com ()
Date: Wed Nov 19 03:42:52 2014
Subject: No subject
Message-ID: <mailman.23.1416368572.1610.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 19 02:50:31 2014
From: bogus@does.not.exist.com ()
Date: Wed Nov 19 03:42:54 2014
Subject: No subject
Message-ID: <mailman.24.1416368574.1610.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 19 02:50:31 2014
From: bogus@does.not.exist.com ()
Date: Wed Nov 19 03:42:56 2014
Subject: No subject
Message-ID: <mailman.25.1416368576.1610.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 19 02:50:31 2014
From: bogus@does.not.exist.com ()
Date: Wed Nov 19 03:42:56 2014
Subject: No subject
Message-ID: <mailman.26.1416368576.1610.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 19 02:50:31 2014
From: bogus@does.not.exist.com ()
Date: Wed Nov 19 03:42:57 2014
Subject: No subject
Message-ID: <mailman.27.1416368577.1610.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 19 02:50:31 2014
From: bogus@does.not.exist.com ()
Date: Wed Nov 19 03:42:58 2014
Subject: No subject
Message-ID: <mailman.28.1416368578.1610.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 19 02:50:31 2014
From: bogus@does.not.exist.com ()
Date: Wed Nov 19 03:42:58 2014

Subject: No subject
Message-ID: <mailman.29.1416368578.1610.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 19 02:50:31 2014
From: bogus@does.not.exist.com ()
Date: Wed Nov 19 03:43:01 2014
Subject: No subject
Message-ID: <mailman.30.1416368581.1610.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 19 02:50:31 2014
From: bogus@does.not.exist.com ()
Date: Wed Nov 19 03:43:01 2014
Subject: No subject
Message-ID: <mailman.31.1416368581.1610.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 19 02:50:31 2014
From: bogus@does.not.exist.com ()
Date: Wed Nov 19 03:43:02 2014
Subject: No subject
Message-ID: <mailman.32.1416368582.1610.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 19 02:50:31 2014
From: bogus@does.not.exist.com ()
Date: Wed Nov 19 03:43:02 2014
Subject: No subject
Message-ID: <mailman.33.1416368582.1610.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 19 02:50:31 2014
From: bogus@does.not.exist.com ()
Date: Wed Nov 19 03:43:03 2014
Subject: No subject
Message-ID: <mailman.34.1416368583.1610.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 19 02:50:31 2014
From: bogus@does.not.exist.com ()
Date: Wed Nov 19 03:43:03 2014
Subject: No subject
Message-ID: <mailman.35.1416368583.1610.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 19 02:50:31 2014
From: bogus@does.not.exist.com ()
Date: Wed Nov 19 03:43:04 2014
Subject: No subject
Message-ID: <mailman.36.1416368584.1610.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 19 02:50:31 2014
From: bogus@does.not.exist.com ()
Date: Wed Nov 19 03:43:04 2014
Subject: No subject
Message-ID: <mailman.37.1416368584.1610.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 19 02:50:31 2014
From: bogus@does.not.exist.com ()
Date: Wed Nov 19 03:43:05 2014
Subject: No subject
Message-ID: <mailman.38.1416368585.1610.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 19 02:50:31 2014
From: bogus@does.not.exist.com ()
Date: Wed Nov 19 03:43:06 2014

Subject: No subject
Message-ID: <mailman.39.1416368586.1610.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 19 02:50:31 2014
From: bogus@does.not.exist.com ()
Date: Wed Nov 19 03:43:06 2014
Subject: No subject
Message-ID: <mailman.40.1416368586.1610.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 19 02:50:31 2014
From: bogus@does.not.exist.com ()
Date: Wed Nov 19 03:43:09 2014
Subject: No subject
Message-ID: <mailman.41.1416368589.1610.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 19 02:50:31 2014
From: bogus@does.not.exist.com ()
Date: Wed Nov 19 03:43:09 2014
Subject: No subject
Message-ID: <mailman.42.1416368589.1610.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 19 02:50:31 2014
From: bogus@does.not.exist.com ()
Date: Wed Nov 19 03:43:10 2014
Subject: No subject
Message-ID: <mailman.43.1416368590.1610.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 19 02:50:31 2014
From: bogus@does.not.exist.com ()
Date: Wed Nov 19 03:43:10 2014
Subject: No subject
Message-ID: <mailman.44.1416368590.1610.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 19 02:50:31 2014
From: bogus@does.not.exist.com ()
Date: Wed Nov 19 03:43:11 2014
Subject: No subject
Message-ID: <mailman.45.1416368591.1610.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 19 02:50:31 2014
From: bogus@does.not.exist.com ()
Date: Wed Nov 19 03:43:11 2014
Subject: No subject
Message-ID: <mailman.46.1416368591.1610.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 19 02:50:31 2014
From: bogus@does.not.exist.com ()
Date: Wed Nov 19 03:43:12 2014
Subject: No subject
Message-ID: <mailman.47.1416368592.1610.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 19 02:50:31 2014
From: bogus@does.not.exist.com ()
Date: Wed Nov 19 03:43:13 2014
Subject: No subject
Message-ID: <mailman.48.1416368593.1610.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 19 02:50:31 2014
From: bogus@does.not.exist.com ()
Date: Wed Nov 19 03:43:20 2014

Subject: No subject
Message-ID: <mailman.49.1416368600.1610.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 19 02:50:31 2014
From: bogus@does.not.exist.com ()
Date: Wed Nov 19 03:43:23 2014
Subject: No subject
Message-ID: <mailman.50.1416368603.1610.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 19 02:50:31 2014
From: bogus@does.not.exist.com ()
Date: Wed Nov 19 03:43:27 2014
Subject: No subject
Message-ID: <mailman.51.1416368607.1610.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 19 02:50:31 2014
From: bogus@does.not.exist.com ()
Date: Wed Nov 19 03:43:30 2014
Subject: No subject
Message-ID: <mailman.52.1416368610.1610.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 19 02:50:31 2014
From: bogus@does.not.exist.com ()
Date: Wed Nov 19 03:43:32 2014
Subject: No subject
Message-ID: <mailman.53.1416368612.1610.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 19 02:50:31 2014
From: bogus@does.not.exist.com ()
Date: Wed Nov 19 03:43:32 2014
Subject: No subject
Message-ID: <mailman.54.1416368612.1610.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 19 02:50:31 2014
From: bogus@does.not.exist.com ()
Date: Wed Nov 19 03:43:33 2014
Subject: No subject
Message-ID: <mailman.55.1416368613.1610.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 19 02:50:31 2014
From: bogus@does.not.exist.com ()
Date: Wed Nov 19 03:43:33 2014
Subject: No subject
Message-ID: <mailman.56.1416368613.1610.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 19 02:50:31 2014
From: bogus@does.not.exist.com ()
Date: Wed Nov 19 03:43:34 2014
Subject: No subject
Message-ID: <mailman.57.1416368614.1610.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 19 02:50:31 2014
From: bogus@does.not.exist.com ()
Date: Wed Nov 19 03:43:34 2014
Subject: No subject
Message-ID: <mailman.58.1416368614.1610.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 19 02:50:31 2014
From: bogus@does.not.exist.com ()
Date: Wed Nov 19 03:43:35 2014

Subject: No subject
Message-ID: <mailman.59.1416368615.1610.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 19 02:50:31 2014
From: bogus@does.not.exist.com ()
Date: Wed Nov 19 03:43:35 2014
Subject: No subject
Message-ID: <mailman.60.1416368615.1610.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 19 02:50:31 2014
From: bogus@does.not.exist.com ()
Date: Wed Nov 19 03:43:35 2014
Subject: No subject
Message-ID: <mailman.61.1416368615.1610.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 19 02:50:31 2014
From: bogus@does.not.exist.com ()
Date: Wed Nov 19 03:43:37 2014
Subject: No subject
Message-ID: <mailman.62.1416368617.1610.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 19 02:50:31 2014
From: bogus@does.not.exist.com ()
Date: Wed Nov 19 03:43:41 2014
Subject: No subject
Message-ID: <mailman.63.1416368621.1610.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 19 02:50:31 2014
From: bogus@does.not.exist.com ()
Date: Wed Nov 19 03:43:45 2014
Subject: No subject
Message-ID: <mailman.64.1416368625.1610.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 19 02:50:31 2014
From: bogus@does.not.exist.com ()
Date: Wed Nov 19 03:43:47 2014
Subject: No subject
Message-ID: <mailman.65.1416368627.1610.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 19 02:50:31 2014
From: bogus@does.not.exist.com ()
Date: Wed Nov 19 03:43:47 2014
Subject: No subject
Message-ID: <mailman.66.1416368627.1610.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 19 02:50:31 2014
From: bogus@does.not.exist.com ()
Date: Wed Nov 19 03:43:49 2014
Subject: No subject
Message-ID: <mailman.67.1416368629.1610.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 19 02:50:31 2014
From: bogus@does.not.exist.com ()
Date: Wed Nov 19 03:43:50 2014
Subject: No subject
Message-ID: <mailman.68.1416368630.1610.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 19 02:50:31 2014
From: bogus@does.not.exist.com ()
Date: Wed Nov 19 03:43:52 2014

Subject: No subject
Message-ID: <mailman.69.1416368632.1610.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 19 02:50:31 2014
From: bogus@does.not.exist.com ()
Date: Wed Nov 19 03:43:59 2014
Subject: No subject
Message-ID: <mailman.70.1416368639.1610.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 19 02:50:31 2014
From: bogus@does.not.exist.com ()
Date: Wed Nov 19 03:44:01 2014
Subject: No subject
Message-ID: <mailman.71.1416368641.1610.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 19 02:50:31 2014
From: bogus@does.not.exist.com ()
Date: Wed Nov 19 03:44:04 2014
Subject: No subject
Message-ID: <mailman.72.1416368644.1610.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 19 02:50:31 2014
From: bogus@does.not.exist.com ()
Date: Wed Nov 19 03:44:06 2014
Subject: No subject
Message-ID: <mailman.73.1416368646.1610.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 19 02:50:31 2014
From: bogus@does.not.exist.com ()
Date: Wed Nov 19 03:44:09 2014
Subject: No subject
Message-ID: <mailman.74.1416368649.1610.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 19 02:50:31 2014
From: bogus@does.not.exist.com ()
Date: Wed Nov 19 03:44:11 2014
Subject: No subject
Message-ID: <mailman.75.1416368651.1610.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 19 02:50:31 2014
From: bogus@does.not.exist.com ()
Date: Wed Nov 19 03:44:14 2014
Subject: No subject
Message-ID: <mailman.76.1416368654.1610.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 19 02:50:31 2014
From: bogus@does.not.exist.com ()
Date: Wed Nov 19 03:44:17 2014
Subject: No subject
Message-ID: <mailman.77.1416368657.1610.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 19 02:50:31 2014
From: bogus@does.not.exist.com ()
Date: Wed Nov 19 03:44:19 2014
Subject: No subject
Message-ID: <mailman.78.1416368659.1610.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 19 02:50:31 2014
From: bogus@does.not.exist.com ()
Date: Wed Nov 19 03:44:23 2014

Subject: No subject
Message-ID: <mailman.79.1416368663.1610.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 19 02:50:31 2014
From: bogus@does.not.exist.com ()
Date: Wed Nov 19 03:44:25 2014
Subject: No subject
Message-ID: <mailman.80.1416368665.1610.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 19 02:50:31 2014
From: bogus@does.not.exist.com ()
Date: Wed Nov 19 03:44:27 2014
Subject: No subject
Message-ID: <mailman.81.1416368667.1610.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 19 02:50:31 2014
From: bogus@does.not.exist.com ()
Date: Wed Nov 19 03:44:28 2014
Subject: No subject
Message-ID: <mailman.82.1416368668.1610.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 19 02:50:31 2014
From: bogus@does.not.exist.com ()
Date: Wed Nov 19 03:44:29 2014
Subject: No subject
Message-ID: <mailman.83.1416368669.1610.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 19 02:50:31 2014
From: bogus@does.not.exist.com ()
Date: Wed Nov 19 03:44:30 2014
Subject: No subject
Message-ID: <mailman.84.1416368669.1610.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 19 02:50:31 2014
From: bogus@does.not.exist.com ()
Date: Wed Nov 19 03:44:31 2014
Subject: No subject
Message-ID: <mailman.85.1416368671.1610.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 19 02:50:31 2014
From: bogus@does.not.exist.com ()
Date: Wed Nov 19 03:44:33 2014
Subject: No subject
Message-ID: <mailman.86.1416368673.1610.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 19 02:50:31 2014
From: bogus@does.not.exist.com ()
Date: Wed Nov 19 03:44:34 2014
Subject: No subject
Message-ID: <mailman.87.1416368673.1610.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 19 02:50:31 2014
From: bogus@does.not.exist.com ()
Date: Wed Nov 19 03:44:34 2014
Subject: No subject
Message-ID: <mailman.88.1416368674.1610.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 19 02:50:31 2014
From: bogus@does.not.exist.com ()
Date: Wed Nov 19 03:44:35 2014

Subject: No subject
Message-ID: <mailman.89.1416368675.1610.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 19 02:50:31 2014
From: bogus@does.not.exist.com ()
Date: Wed Nov 19 03:44:36 2014
Subject: No subject
Message-ID: <mailman.91.1416368676.1610.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 19 02:50:31 2014
From: bogus@does.not.exist.com ()
Date: Wed Nov 19 03:44:38 2014
Subject: No subject
Message-ID: <mailman.92.1416368678.1610.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 19 02:50:31 2014
From: bogus@does.not.exist.com ()
Date: Wed Nov 19 03:44:39 2014
Subject: No subject
Message-ID: <mailman.93.1416368679.1610.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 19 02:50:31 2014
From: bogus@does.not.exist.com ()
Date: Wed Nov 19 03:44:41 2014
Subject: No subject
Message-ID: <mailman.94.1416368681.1610.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 19 02:50:31 2014
From: bogus@does.not.exist.com ()
Date: Wed Nov 19 03:44:42 2014
Subject: No subject
Message-ID: <mailman.95.1416368682.1610.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 19 02:50:31 2014
From: bogus@does.not.exist.com ()
Date: Wed Nov 19 03:44:43 2014
Subject: No subject
Message-ID: <mailman.96.1416368683.1610.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 19 02:50:31 2014
From: bogus@does.not.exist.com ()
Date: Wed Nov 19 03:44:45 2014
Subject: No subject
Message-ID: <mailman.97.1416368685.1610.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 19 02:50:31 2014
From: bogus@does.not.exist.com ()
Date: Wed Nov 19 03:44:46 2014
Subject: No subject
Message-ID: <mailman.98.1416368686.1610.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 19 02:50:31 2014
From: bogus@does.not.exist.com ()
Date: Wed Nov 19 03:44:48 2014
Subject: No subject
Message-ID: <mailman.99.1416368688.1610.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 19 02:50:31 2014
From: bogus@does.not.exist.com ()
Date: Wed Nov 19 03:44:49 2014

Subject: No subject
Message-ID: <mailman.100.1416368689.1610.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 19 02:50:31 2014
From: bogus@does.not.exist.com ()
Date: Wed Nov 19 03:44:50 2014
Subject: No subject
Message-ID: <mailman.101.1416368690.1610.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 19 02:50:31 2014
From: bogus@does.not.exist.com ()
Date: Wed Nov 19 03:44:50 2014
Subject: No subject
Message-ID: <mailman.102.1416368690.1610.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 19 02:50:31 2014
From: bogus@does.not.exist.com ()
Date: Wed Nov 19 03:44:51 2014
Subject: No subject
Message-ID: <mailman.103.1416368691.1610.htk-users@eng.cam.ac.uk>
From tonyr at cantabResearch.com Tue Nov 4 20:04:46 2014
From: tonyr at cantabResearch.com (Tony Robinson)
Date: Wed Nov 19 04:00:56 2014
Subject: [HTK-Users] HTK license agreement
In-Reply-To: <545241EC02000049000E3077@pta-emo.csir.co.za>
References: <545241EC02000049000E3077@pta-emo.csir.co.za>
Message-ID: <5459315E.9030409@cantabResearch.com>
I just saw this post - I hope I haven't also missed any replies.
It's been a while since I read the HTK licence, but from memory and past
commercial practices I believe that what you are proposing is entirely
acceptable according to the HTK licence.
In fact I think www.speechmatics.com uses HVite in exactly this way to
do some final tidying up of the large vocabulary speech recognition output.
Tony
On 30/10/14 11:49, Georg Schlunz wrote:
> Good day
>
> Regarding the HTK license, as specified at http://htk.eng.cam.ac.uk/docs/licen
se.shtml , I would like to know whether the following scenario is permitted:
>
> The HTK software (including HVite) sits on a server in-house in our organisati
on, as per license sections 2.1 and 2.3.
> The HTK software (including HVite) is never distributed to a commercial (or no
n-commercial) party, as per license section 2.2.
>
> We have written our own server-client software, where:
> a) the client records speech and sends the audio file to the server, which pas
ses it on to HVite (the server software and HTK sit on the same in-house machine
)
> b) HVite decodes the audio into text
> c) the server replies to the client with the decoded text and the client proce
sses the text somehow
>

> Naturally, the client software contains no HTK code; it only processes data pr
oduced by HTK.
>
> Therefore, may this client software and decoding SERVICE be sold commercially
(as long as we agree to license sections 2.4 and 2.5)?
>
> Thank you
> Georg Schlunz
>
-- ** Cantab is hiring: www.cantabResearch.com/openings ** -Dr A J Robinson, Founder, Cantab Research Ltd
Phone direct: 01223 778240 office: 01223 794497
Company reg no GB 05697423, VAT reg no 925606030
51 Canterbury Street, Cambridge, CB4 3QG, UK
From bogus@does.not.exist.com Thu Nov 20 02:53:16 2014
From: bogus@does.not.exist.com ()
Date: Thu Nov 20 04:00:51 2014
Subject: No subject
Message-ID: <mailman.1.1416456051.17853.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 20 02:53:16 2014
From: bogus@does.not.exist.com ()
Date: Thu Nov 20 04:00:59 2014
Subject: No subject
Message-ID: <mailman.2.1416456059.17853.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 20 02:53:16 2014
From: bogus@does.not.exist.com ()
Date: Thu Nov 20 04:01:02 2014
Subject: No subject
Message-ID: <mailman.3.1416456060.17853.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 20 02:53:16 2014
From: bogus@does.not.exist.com ()
Date: Thu Nov 20 04:01:03 2014
Subject: No subject
Message-ID: <mailman.4.1416456063.17853.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 20 02:53:16 2014
From: bogus@does.not.exist.com ()
Date: Thu Nov 20 04:01:04 2014
Subject: No subject
Message-ID: <mailman.5.1416456064.17853.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 20 02:53:16 2014
From: bogus@does.not.exist.com ()
Date: Thu Nov 20 04:01:04 2014
Subject: No subject
Message-ID: <mailman.6.1416456064.17853.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 20 02:53:16 2014
From: bogus@does.not.exist.com ()
Date: Thu Nov 20 04:01:05 2014
Subject: No subject
Message-ID: <mailman.7.1416456065.17853.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 20 02:53:16 2014
From: bogus@does.not.exist.com ()

Date: Thu Nov 20 04:01:08 2014


Subject: No subject
Message-ID: <mailman.8.1416456068.17853.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 20 02:53:16 2014
From: bogus@does.not.exist.com ()
Date: Thu Nov 20 04:01:08 2014
Subject: No subject
Message-ID: <mailman.9.1416456068.17853.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 20 02:53:16 2014
From: bogus@does.not.exist.com ()
Date: Thu Nov 20 04:01:11 2014
Subject: No subject
Message-ID: <mailman.10.1416456071.17853.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 20 02:53:16 2014
From: bogus@does.not.exist.com ()
Date: Thu Nov 20 04:01:12 2014
Subject: No subject
Message-ID: <mailman.11.1416456072.17853.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 20 02:53:16 2014
From: bogus@does.not.exist.com ()
Date: Thu Nov 20 04:01:15 2014
Subject: No subject
Message-ID: <mailman.12.1416456074.17853.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 20 02:53:16 2014
From: bogus@does.not.exist.com ()
Date: Thu Nov 20 04:01:17 2014
Subject: No subject
Message-ID: <mailman.13.1416456077.17853.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 20 02:53:16 2014
From: bogus@does.not.exist.com ()
Date: Thu Nov 20 04:01:17 2014
Subject: No subject
Message-ID: <mailman.14.1416456077.17853.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 20 02:53:16 2014
From: bogus@does.not.exist.com ()
Date: Thu Nov 20 04:01:18 2014
Subject: No subject
Message-ID: <mailman.15.1416456078.17853.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 20 02:53:16 2014
From: bogus@does.not.exist.com ()
Date: Thu Nov 20 04:01:19 2014
Subject: No subject
Message-ID: <mailman.16.1416456079.17853.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 20 02:53:16 2014
From: bogus@does.not.exist.com ()
Date: Thu Nov 20 04:01:20 2014
Subject: No subject
Message-ID: <mailman.17.1416456080.17853.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 20 02:53:16 2014
From: bogus@does.not.exist.com ()

Date: Thu Nov 20 04:01:20 2014


Subject: No subject
Message-ID: <mailman.18.1416456080.17853.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 20 02:53:16 2014
From: bogus@does.not.exist.com ()
Date: Thu Nov 20 04:01:24 2014
Subject: No subject
Message-ID: <mailman.19.1416456084.17853.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 20 02:53:16 2014
From: bogus@does.not.exist.com ()
Date: Thu Nov 20 04:01:25 2014
Subject: No subject
Message-ID: <mailman.20.1416456085.17853.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 20 02:53:16 2014
From: bogus@does.not.exist.com ()
Date: Thu Nov 20 04:01:34 2014
Subject: No subject
Message-ID: <mailman.21.1416456094.17853.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 20 02:53:16 2014
From: bogus@does.not.exist.com ()
Date: Thu Nov 20 04:01:47 2014
Subject: No subject
Message-ID: <mailman.22.1416456107.17853.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 20 02:53:16 2014
From: bogus@does.not.exist.com ()
Date: Thu Nov 20 04:01:57 2014
Subject: No subject
Message-ID: <mailman.23.1416456117.17853.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 20 02:53:16 2014
From: bogus@does.not.exist.com ()
Date: Thu Nov 20 04:02:00 2014
Subject: No subject
Message-ID: <mailman.24.1416456120.17853.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 20 02:53:16 2014
From: bogus@does.not.exist.com ()
Date: Thu Nov 20 04:02:09 2014
Subject: No subject
Message-ID: <mailman.25.1416456128.17853.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 20 02:53:16 2014
From: bogus@does.not.exist.com ()
Date: Thu Nov 20 04:02:18 2014
Subject: No subject
Message-ID: <mailman.26.1416456138.17853.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 20 02:53:16 2014
From: bogus@does.not.exist.com ()
Date: Thu Nov 20 04:02:24 2014
Subject: No subject
Message-ID: <mailman.27.1416456144.17853.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 20 02:53:16 2014
From: bogus@does.not.exist.com ()

Date: Thu Nov 20 04:02:32 2014


Subject: No subject
Message-ID: <mailman.28.1416456152.17853.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 20 02:53:16 2014
From: bogus@does.not.exist.com ()
Date: Thu Nov 20 04:02:43 2014
Subject: No subject
Message-ID: <mailman.29.1416456163.17853.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 20 02:53:16 2014
From: bogus@does.not.exist.com ()
Date: Thu Nov 20 04:02:53 2014
Subject: No subject
Message-ID: <mailman.30.1416456173.17853.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 20 02:53:16 2014
From: bogus@does.not.exist.com ()
Date: Thu Nov 20 04:02:54 2014
Subject: No subject
Message-ID: <mailman.31.1416456174.17853.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 20 02:53:16 2014
From: bogus@does.not.exist.com ()
Date: Thu Nov 20 04:02:56 2014
Subject: No subject
Message-ID: <mailman.32.1416456176.17853.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 20 02:53:16 2014
From: bogus@does.not.exist.com ()
Date: Thu Nov 20 04:02:58 2014
Subject: No subject
Message-ID: <mailman.33.1416456178.17853.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 20 02:53:16 2014
From: bogus@does.not.exist.com ()
Date: Thu Nov 20 04:03:00 2014
Subject: No subject
Message-ID: <mailman.34.1416456180.17853.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 20 02:53:16 2014
From: bogus@does.not.exist.com ()
Date: Thu Nov 20 04:03:01 2014
Subject: No subject
Message-ID: <mailman.35.1416456181.17853.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 20 02:53:16 2014
From: bogus@does.not.exist.com ()
Date: Thu Nov 20 04:03:03 2014
Subject: No subject
Message-ID: <mailman.36.1416456183.17853.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 20 02:53:16 2014
From: bogus@does.not.exist.com ()
Date: Thu Nov 20 04:03:04 2014
Subject: No subject
Message-ID: <mailman.37.1416456184.17853.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 20 02:53:16 2014
From: bogus@does.not.exist.com ()

Date: Thu Nov 20 04:03:11 2014


Subject: No subject
Message-ID: <mailman.38.1416456191.17853.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 20 02:53:16 2014
From: bogus@does.not.exist.com ()
Date: Thu Nov 20 04:03:19 2014
Subject: No subject
Message-ID: <mailman.39.1416456199.17853.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 20 02:53:16 2014
From: bogus@does.not.exist.com ()
Date: Thu Nov 20 04:03:29 2014
Subject: No subject
Message-ID: <mailman.40.1416456209.17853.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 20 02:53:16 2014
From: bogus@does.not.exist.com ()
Date: Thu Nov 20 04:03:47 2014
Subject: No subject
Message-ID: <mailman.41.1416456227.17853.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 20 02:53:16 2014
From: bogus@does.not.exist.com ()
Date: Thu Nov 20 04:03:54 2014
Subject: No subject
Message-ID: <mailman.42.1416456234.17853.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 20 02:53:16 2014
From: bogus@does.not.exist.com ()
Date: Thu Nov 20 04:04:01 2014
Subject: No subject
Message-ID: <mailman.43.1416456241.17853.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 20 02:53:16 2014
From: bogus@does.not.exist.com ()
Date: Thu Nov 20 04:04:03 2014
Subject: No subject
Message-ID: <mailman.44.1416456243.17853.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 20 02:53:16 2014
From: bogus@does.not.exist.com ()
Date: Thu Nov 20 04:04:13 2014
Subject: No subject
Message-ID: <mailman.45.1416456251.17853.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 20 02:53:16 2014
From: bogus@does.not.exist.com ()
Date: Thu Nov 20 04:04:24 2014
Subject: No subject
Message-ID: <mailman.46.1416456263.17853.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 20 02:53:16 2014
From: bogus@does.not.exist.com ()
Date: Thu Nov 20 04:04:34 2014
Subject: No subject
Message-ID: <mailman.47.1416456273.17853.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 20 02:53:16 2014
From: bogus@does.not.exist.com ()

Date: Thu Nov 20 04:04:46 2014


Subject: No subject
Message-ID: <mailman.48.1416456286.17853.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 20 02:53:16 2014
From: bogus@does.not.exist.com ()
Date: Thu Nov 20 04:05:00 2014
Subject: No subject
Message-ID: <mailman.49.1416456300.17853.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 20 02:53:16 2014
From: bogus@does.not.exist.com ()
Date: Thu Nov 20 04:05:08 2014
Subject: No subject
Message-ID: <mailman.50.1416456307.17853.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 20 02:53:16 2014
From: bogus@does.not.exist.com ()
Date: Thu Nov 20 04:05:10 2014
Subject: No subject
Message-ID: <mailman.51.1416456310.17853.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 20 02:53:16 2014
From: bogus@does.not.exist.com ()
Date: Thu Nov 20 04:05:12 2014
Subject: No subject
Message-ID: <mailman.52.1416456312.17853.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 20 02:53:16 2014
From: bogus@does.not.exist.com ()
Date: Thu Nov 20 04:05:14 2014
Subject: No subject
Message-ID: <mailman.53.1416456314.17853.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 20 02:53:16 2014
From: bogus@does.not.exist.com ()
Date: Thu Nov 20 04:05:17 2014
Subject: No subject
Message-ID: <mailman.54.1416456317.17853.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 20 02:53:16 2014
From: bogus@does.not.exist.com ()
Date: Thu Nov 20 04:05:18 2014
Subject: No subject
Message-ID: <mailman.55.1416456318.17853.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 20 02:53:16 2014
From: bogus@does.not.exist.com ()
Date: Thu Nov 20 04:05:40 2014
Subject: No subject
Message-ID: <mailman.56.1416456339.17853.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 20 02:53:16 2014
From: bogus@does.not.exist.com ()
Date: Thu Nov 20 04:05:41 2014
Subject: No subject
Message-ID: <mailman.57.1416456341.17853.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 20 02:53:16 2014
From: bogus@does.not.exist.com ()

Date: Thu Nov 20 04:05:52 2014


Subject: No subject
Message-ID: <mailman.58.1416456352.17853.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 20 02:53:16 2014
From: bogus@does.not.exist.com ()
Date: Thu Nov 20 04:06:08 2014
Subject: No subject
Message-ID: <mailman.59.1416456367.17853.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 20 02:53:16 2014
From: bogus@does.not.exist.com ()
Date: Thu Nov 20 04:06:17 2014
Subject: No subject
Message-ID: <mailman.60.1416456376.17853.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 20 02:53:16 2014
From: bogus@does.not.exist.com ()
Date: Thu Nov 20 04:06:24 2014
Subject: No subject
Message-ID: <mailman.61.1416456384.17853.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 20 02:53:16 2014
From: bogus@does.not.exist.com ()
Date: Thu Nov 20 04:06:30 2014
Subject: No subject
Message-ID: <mailman.62.1416456390.17853.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 20 02:53:16 2014
From: bogus@does.not.exist.com ()
Date: Thu Nov 20 04:06:37 2014
Subject: No subject
Message-ID: <mailman.63.1416456397.17853.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 20 02:53:16 2014
From: bogus@does.not.exist.com ()
Date: Thu Nov 20 04:06:39 2014
Subject: No subject
Message-ID: <mailman.64.1416456399.17853.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 20 02:53:16 2014
From: bogus@does.not.exist.com ()
Date: Thu Nov 20 04:06:41 2014
Subject: No subject
Message-ID: <mailman.65.1416456401.17853.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 20 02:53:16 2014
From: bogus@does.not.exist.com ()
Date: Thu Nov 20 04:06:42 2014
Subject: No subject
Message-ID: <mailman.66.1416456402.17853.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 20 02:53:16 2014
From: bogus@does.not.exist.com ()
Date: Thu Nov 20 04:06:44 2014
Subject: No subject
Message-ID: <mailman.67.1416456404.17853.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 20 02:53:16 2014
From: bogus@does.not.exist.com ()

Date: Thu Nov 20 04:06:44 2014


Subject: No subject
Message-ID: <mailman.68.1416456404.17853.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 20 02:53:16 2014
From: bogus@does.not.exist.com ()
Date: Thu Nov 20 04:06:46 2014
Subject: No subject
Message-ID: <mailman.69.1416456406.17853.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 20 02:53:16 2014
From: bogus@does.not.exist.com ()
Date: Thu Nov 20 04:06:52 2014
Subject: No subject
Message-ID: <mailman.70.1416456412.17853.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 20 02:53:16 2014
From: bogus@does.not.exist.com ()
Date: Thu Nov 20 04:06:54 2014
Subject: No subject
Message-ID: <mailman.71.1416456414.17853.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 20 02:53:16 2014
From: bogus@does.not.exist.com ()
Date: Thu Nov 20 04:06:56 2014
Subject: No subject
Message-ID: <mailman.72.1416456416.17853.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 20 02:53:16 2014
From: bogus@does.not.exist.com ()
Date: Thu Nov 20 04:06:58 2014
Subject: No subject
Message-ID: <mailman.73.1416456418.17853.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 20 02:53:16 2014
From: bogus@does.not.exist.com ()
Date: Thu Nov 20 04:07:01 2014
Subject: No subject
Message-ID: <mailman.74.1416456421.17853.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 20 02:53:16 2014
From: bogus@does.not.exist.com ()
Date: Thu Nov 20 04:07:02 2014
Subject: No subject
Message-ID: <mailman.75.1416456422.17853.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 20 02:53:16 2014
From: bogus@does.not.exist.com ()
Date: Thu Nov 20 04:07:03 2014
Subject: No subject
Message-ID: <mailman.76.1416456423.17853.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 20 02:53:16 2014
From: bogus@does.not.exist.com ()
Date: Thu Nov 20 04:07:05 2014
Subject: No subject
Message-ID: <mailman.77.1416456425.17853.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 20 02:53:16 2014
From: bogus@does.not.exist.com ()

Date: Thu Nov 20 04:07:12 2014


Subject: No subject
Message-ID: <mailman.78.1416456431.17853.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 20 02:53:16 2014
From: bogus@does.not.exist.com ()
Date: Thu Nov 20 04:07:26 2014
Subject: No subject
Message-ID: <mailman.79.1416456446.17853.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 20 02:53:16 2014
From: bogus@does.not.exist.com ()
Date: Thu Nov 20 04:07:38 2014
Subject: No subject
Message-ID: <mailman.80.1416456457.17853.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 20 02:53:16 2014
From: bogus@does.not.exist.com ()
Date: Thu Nov 20 04:07:55 2014
Subject: No subject
Message-ID: <mailman.81.1416456475.17853.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 20 02:53:16 2014
From: bogus@does.not.exist.com ()
Date: Thu Nov 20 04:07:58 2014
Subject: No subject
Message-ID: <mailman.82.1416456478.17853.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 20 02:53:16 2014
From: bogus@does.not.exist.com ()
Date: Thu Nov 20 04:07:59 2014
Subject: No subject
Message-ID: <mailman.83.1416456479.17853.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 20 02:53:16 2014
From: bogus@does.not.exist.com ()
Date: Thu Nov 20 04:08:02 2014
Subject: No subject
Message-ID: <mailman.84.1416456482.17853.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 20 02:53:16 2014
From: bogus@does.not.exist.com ()
Date: Thu Nov 20 04:08:05 2014
Subject: No subject
Message-ID: <mailman.85.1416456485.17853.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 20 02:53:16 2014
From: bogus@does.not.exist.com ()
Date: Thu Nov 20 04:08:23 2014
Subject: No subject
Message-ID: <mailman.86.1416456503.17853.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 20 02:53:16 2014
From: bogus@does.not.exist.com ()
Date: Thu Nov 20 04:08:31 2014
Subject: No subject
Message-ID: <mailman.87.1416456511.17853.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 20 02:53:16 2014
From: bogus@does.not.exist.com ()

Date: Thu Nov 20 04:08:40 2014


Subject: No subject
Message-ID: <mailman.88.1416456519.17853.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 20 02:53:16 2014
From: bogus@does.not.exist.com ()
Date: Thu Nov 20 04:08:48 2014
Subject: No subject
Message-ID: <mailman.89.1416456528.17853.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 20 02:53:16 2014
From: bogus@does.not.exist.com ()
Date: Thu Nov 20 04:09:02 2014
Subject: No subject
Message-ID: <mailman.91.1416456541.17853.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 20 02:53:16 2014
From: bogus@does.not.exist.com ()
Date: Thu Nov 20 04:09:11 2014
Subject: No subject
Message-ID: <mailman.92.1416456550.17853.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 20 02:53:16 2014
From: bogus@does.not.exist.com ()
Date: Thu Nov 20 04:09:15 2014
Subject: No subject
Message-ID: <mailman.93.1416456555.17853.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 20 02:53:16 2014
From: bogus@does.not.exist.com ()
Date: Thu Nov 20 04:09:23 2014
Subject: No subject
Message-ID: <mailman.94.1416456563.17853.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 20 02:53:16 2014
From: bogus@does.not.exist.com ()
Date: Thu Nov 20 04:09:27 2014
Subject: No subject
Message-ID: <mailman.95.1416456567.17853.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 20 02:53:16 2014
From: bogus@does.not.exist.com ()
Date: Thu Nov 20 04:09:30 2014
Subject: No subject
Message-ID: <mailman.96.1416456570.17853.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 20 02:53:16 2014
From: bogus@does.not.exist.com ()
Date: Thu Nov 20 04:09:36 2014
Subject: No subject
Message-ID: <mailman.97.1416456576.17853.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 20 02:53:16 2014
From: bogus@does.not.exist.com ()
Date: Thu Nov 20 04:09:50 2014
Subject: No subject
Message-ID: <mailman.98.1416456589.17853.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 20 02:53:16 2014
From: bogus@does.not.exist.com ()

Date: Thu Nov 20 04:10:06 2014


Subject: No subject
Message-ID: <mailman.99.1416456606.17853.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 20 02:53:16 2014
From: bogus@does.not.exist.com ()
Date: Thu Nov 20 04:10:09 2014
Subject: No subject
Message-ID: <mailman.100.1416456609.17853.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 20 02:53:16 2014
From: bogus@does.not.exist.com ()
Date: Thu Nov 20 04:10:12 2014
Subject: No subject
Message-ID: <mailman.101.1416456611.17853.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 20 02:53:16 2014
From: bogus@does.not.exist.com ()
Date: Thu Nov 20 04:10:19 2014
Subject: No subject
Message-ID: <mailman.102.1416456619.17853.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 20 02:53:16 2014
From: bogus@does.not.exist.com ()
Date: Thu Nov 20 04:10:31 2014
Subject: No subject
Message-ID: <mailman.103.1416456631.17853.htk-users@eng.cam.ac.uk>
From tonyr at cantabResearch.com Tue Nov 4 20:04:46 2014
From: tonyr at cantabResearch.com (Tony Robinson)
Date: Thu Nov 20 04:33:44 2014
Subject: [HTK-Users] HTK license agreement
In-Reply-To: <545241EC02000049000E3077@pta-emo.csir.co.za>
References: <545241EC02000049000E3077@pta-emo.csir.co.za>
Message-ID: <5459315E.9030409@cantabResearch.com>
I just saw this post - I hope I haven't also missed any replies.
It's been a while since I read the HTK licence, but from memory and past
commercial practices I believe that what you are proposing is entirely
acceptable according to the HTK licence.
In fact I think www.speechmatics.com uses HVite in exactly this way to
do some final tidying up of the large vocabulary speech recognition output.
Tony
On 30/10/14 11:49, Georg Schlunz wrote:
> Good day
>
> Regarding the HTK license, as specified at http://htk.eng.cam.ac.uk/docs/licen
se.shtml , I would like to know whether the following scenario is permitted:
>
> The HTK software (including HVite) sits on a server in-house in our organisati
on, as per license sections 2.1 and 2.3.
> The HTK software (including HVite) is never distributed to a commercial (or no
n-commercial) party, as per license section 2.2.
>
> We have written our own server-client software, where:

> a) the client records speech and sends the audio file to the server, which pas
ses it on to HVite (the server software and HTK sit on the same in-house machine
)
> b) HVite decodes the audio into text
> c) the server replies to the client with the decoded text and the client proce
sses the text somehow
>
> Naturally, the client software contains no HTK code; it only processes data pr
oduced by HTK.
>
> Therefore, may this client software and decoding SERVICE be sold commercially
(as long as we agree to license sections 2.4 and 2.5)?
>
> Thank you
> Georg Schlunz
>
-- ** Cantab is hiring: www.cantabResearch.com/openings ** -Dr A J Robinson, Founder, Cantab Research Ltd
Phone direct: 01223 778240 office: 01223 794497
Company reg no GB 05697423, VAT reg no 925606030
51 Canterbury Street, Cambridge, CB4 3QG, UK
From bogus@does.not.exist.com Fri Nov 21 02:53:25 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 21 04:21:16 2014
Subject: No subject
Message-ID: <mailman.1.1416543676.32149.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 21 02:53:25 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 21 04:21:19 2014
Subject: No subject
Message-ID: <mailman.2.1416543679.32149.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 21 02:53:25 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 21 04:21:20 2014
Subject: No subject
Message-ID: <mailman.3.1416543680.32149.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 21 02:53:25 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 21 04:21:20 2014
Subject: No subject
Message-ID: <mailman.4.1416543680.32149.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 21 02:53:25 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 21 04:21:21 2014
Subject: No subject
Message-ID: <mailman.5.1416543681.32149.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 21 02:53:25 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 21 04:21:22 2014
Subject: No subject
Message-ID: <mailman.6.1416543682.32149.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 21 02:53:25 2014

From: bogus@does.not.exist.com ()
Date: Fri Nov 21 04:21:22 2014
Subject: No subject
Message-ID: <mailman.7.1416543682.32149.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 21 02:53:25 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 21 04:21:23 2014
Subject: No subject
Message-ID: <mailman.8.1416543683.32149.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 21 02:53:25 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 21 04:21:23 2014
Subject: No subject
Message-ID: <mailman.9.1416543683.32149.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 21 02:53:25 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 21 04:21:27 2014
Subject: No subject
Message-ID: <mailman.10.1416543687.32149.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 21 02:53:25 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 21 04:21:27 2014
Subject: No subject
Message-ID: <mailman.11.1416543687.32149.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 21 02:53:25 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 21 04:21:29 2014
Subject: No subject
Message-ID: <mailman.12.1416543689.32149.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 21 02:53:25 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 21 04:21:29 2014
Subject: No subject
Message-ID: <mailman.13.1416543689.32149.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 21 02:53:25 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 21 04:21:30 2014
Subject: No subject
Message-ID: <mailman.14.1416543690.32149.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 21 02:53:25 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 21 04:21:31 2014
Subject: No subject
Message-ID: <mailman.15.1416543691.32149.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 21 02:53:25 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 21 04:21:31 2014
Subject: No subject
Message-ID: <mailman.16.1416543691.32149.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 21 02:53:25 2014

From: bogus@does.not.exist.com ()
Date: Fri Nov 21 04:21:32 2014
Subject: No subject
Message-ID: <mailman.17.1416543692.32149.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 21 02:53:25 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 21 04:21:32 2014
Subject: No subject
Message-ID: <mailman.18.1416543692.32149.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 21 02:53:25 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 21 04:21:34 2014
Subject: No subject
Message-ID: <mailman.19.1416543694.32149.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 21 02:53:25 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 21 04:21:35 2014
Subject: No subject
Message-ID: <mailman.20.1416543695.32149.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 21 02:53:25 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 21 04:21:36 2014
Subject: No subject
Message-ID: <mailman.21.1416543696.32149.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 21 02:53:25 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 21 04:21:39 2014
Subject: No subject
Message-ID: <mailman.22.1416543699.32149.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 21 02:53:25 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 21 04:21:40 2014
Subject: No subject
Message-ID: <mailman.23.1416543700.32149.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 21 02:53:25 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 21 04:21:42 2014
Subject: No subject
Message-ID: <mailman.24.1416543702.32149.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 21 02:53:25 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 21 04:21:44 2014
Subject: No subject
Message-ID: <mailman.25.1416543704.32149.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 21 02:53:25 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 21 04:21:44 2014
Subject: No subject
Message-ID: <mailman.26.1416543704.32149.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 21 02:53:25 2014

From: bogus@does.not.exist.com ()
Date: Fri Nov 21 04:21:45 2014
Subject: No subject
Message-ID: <mailman.27.1416543705.32149.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 21 02:53:25 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 21 04:21:45 2014
Subject: No subject
Message-ID: <mailman.28.1416543705.32149.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 21 02:53:25 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 21 04:21:46 2014
Subject: No subject
Message-ID: <mailman.29.1416543706.32149.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 21 02:53:25 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 21 04:21:49 2014
Subject: No subject
Message-ID: <mailman.30.1416543709.32149.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 21 02:53:25 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 21 04:21:50 2014
Subject: No subject
Message-ID: <mailman.31.1416543710.32149.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 21 02:53:25 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 21 04:21:50 2014
Subject: No subject
Message-ID: <mailman.32.1416543710.32149.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 21 02:53:25 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 21 04:21:51 2014
Subject: No subject
Message-ID: <mailman.33.1416543711.32149.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 21 02:53:25 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 21 04:21:52 2014
Subject: No subject
Message-ID: <mailman.34.1416543712.32149.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 21 02:53:25 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 21 04:21:52 2014
Subject: No subject
Message-ID: <mailman.35.1416543712.32149.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 21 02:53:25 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 21 04:21:53 2014
Subject: No subject
Message-ID: <mailman.36.1416543713.32149.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 21 02:53:25 2014

From: bogus@does.not.exist.com ()
Date: Fri Nov 21 04:21:54 2014
Subject: No subject
Message-ID: <mailman.37.1416543713.32149.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 21 02:53:25 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 21 04:21:54 2014
Subject: No subject
Message-ID: <mailman.38.1416543714.32149.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 21 02:53:25 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 21 04:21:55 2014
Subject: No subject
Message-ID: <mailman.39.1416543715.32149.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 21 02:53:25 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 21 04:21:56 2014
Subject: No subject
Message-ID: <mailman.40.1416543716.32149.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 21 02:53:25 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 21 04:21:59 2014
Subject: No subject
Message-ID: <mailman.41.1416543719.32149.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 21 02:53:25 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 21 04:22:00 2014
Subject: No subject
Message-ID: <mailman.42.1416543720.32149.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 21 02:53:25 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 21 04:22:01 2014
Subject: No subject
Message-ID: <mailman.43.1416543721.32149.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 21 02:53:25 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 21 04:22:01 2014
Subject: No subject
Message-ID: <mailman.44.1416543721.32149.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 21 02:53:25 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 21 04:22:02 2014
Subject: No subject
Message-ID: <mailman.45.1416543722.32149.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 21 02:53:25 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 21 04:22:02 2014
Subject: No subject
Message-ID: <mailman.46.1416543722.32149.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 21 02:53:25 2014

From: bogus@does.not.exist.com ()
Date: Fri Nov 21 04:22:03 2014
Subject: No subject
Message-ID: <mailman.47.1416543723.32149.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 21 02:53:25 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 21 04:22:03 2014
Subject: No subject
Message-ID: <mailman.48.1416543723.32149.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 21 02:53:25 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 21 04:22:06 2014
Subject: No subject
Message-ID: <mailman.49.1416543726.32149.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 21 02:53:25 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 21 04:22:06 2014
Subject: No subject
Message-ID: <mailman.50.1416543726.32149.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 21 02:53:25 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 21 04:22:07 2014
Subject: No subject
Message-ID: <mailman.51.1416543727.32149.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 21 02:53:25 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 21 04:22:07 2014
Subject: No subject
Message-ID: <mailman.52.1416543727.32149.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 21 02:53:25 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 21 04:22:08 2014
Subject: No subject
Message-ID: <mailman.53.1416543728.32149.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 21 02:53:25 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 21 04:22:09 2014
Subject: No subject
Message-ID: <mailman.54.1416543729.32149.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 21 02:53:25 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 21 04:22:09 2014
Subject: No subject
Message-ID: <mailman.55.1416543729.32149.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 21 02:53:25 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 21 04:22:10 2014
Subject: No subject
Message-ID: <mailman.56.1416543730.32149.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 21 02:53:25 2014

From: bogus@does.not.exist.com ()
Date: Fri Nov 21 04:22:10 2014
Subject: No subject
Message-ID: <mailman.57.1416543730.32149.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 21 02:53:25 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 21 04:22:11 2014
Subject: No subject
Message-ID: <mailman.58.1416543731.32149.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 21 02:53:25 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 21 04:22:11 2014
Subject: No subject
Message-ID: <mailman.59.1416543731.32149.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 21 02:53:25 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 21 04:22:13 2014
Subject: No subject
Message-ID: <mailman.60.1416543733.32149.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 21 02:53:25 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 21 04:22:13 2014
Subject: No subject
Message-ID: <mailman.61.1416543733.32149.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 21 02:53:25 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 21 04:22:14 2014
Subject: No subject
Message-ID: <mailman.62.1416543734.32149.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 21 02:53:25 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 21 04:22:14 2014
Subject: No subject
Message-ID: <mailman.63.1416543734.32149.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 21 02:53:25 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 21 04:22:15 2014
Subject: No subject
Message-ID: <mailman.64.1416543735.32149.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 21 02:53:25 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 21 04:22:15 2014
Subject: No subject
Message-ID: <mailman.65.1416543735.32149.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 21 02:53:25 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 21 04:22:16 2014
Subject: No subject
Message-ID: <mailman.66.1416543736.32149.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 21 02:53:25 2014

From: bogus@does.not.exist.com ()
Date: Fri Nov 21 04:22:17 2014
Subject: No subject
Message-ID: <mailman.67.1416543737.32149.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 21 02:53:25 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 21 04:22:17 2014
Subject: No subject
Message-ID: <mailman.68.1416543737.32149.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 21 02:53:25 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 21 04:22:18 2014
Subject: No subject
Message-ID: <mailman.69.1416543738.32149.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 21 02:53:25 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 21 04:22:20 2014
Subject: No subject
Message-ID: <mailman.70.1416543740.32149.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 21 02:53:25 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 21 04:22:21 2014
Subject: No subject
Message-ID: <mailman.71.1416543741.32149.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 21 02:53:25 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 21 04:22:21 2014
Subject: No subject
Message-ID: <mailman.72.1416543741.32149.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 21 02:53:25 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 21 04:22:22 2014
Subject: No subject
Message-ID: <mailman.73.1416543742.32149.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 21 02:53:25 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 21 04:22:22 2014
Subject: No subject
Message-ID: <mailman.74.1416543742.32149.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 21 02:53:25 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 21 04:22:23 2014
Subject: No subject
Message-ID: <mailman.75.1416543743.32149.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 21 02:53:25 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 21 04:22:24 2014
Subject: No subject
Message-ID: <mailman.76.1416543744.32149.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 21 02:53:25 2014

From: bogus@does.not.exist.com ()
Date: Fri Nov 21 04:22:24 2014
Subject: No subject
Message-ID: <mailman.77.1416543744.32149.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 21 02:53:25 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 21 04:22:25 2014
Subject: No subject
Message-ID: <mailman.78.1416543745.32149.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 21 02:53:25 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 21 04:22:25 2014
Subject: No subject
Message-ID: <mailman.79.1416543745.32149.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 21 02:53:25 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 21 04:22:26 2014
Subject: No subject
Message-ID: <mailman.80.1416543746.32149.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 21 02:53:25 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 21 04:22:26 2014
Subject: No subject
Message-ID: <mailman.81.1416543746.32149.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 21 02:53:25 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 21 04:22:27 2014
Subject: No subject
Message-ID: <mailman.82.1416543747.32149.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 21 02:53:25 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 21 04:22:28 2014
Subject: No subject
Message-ID: <mailman.83.1416543748.32149.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 21 02:53:25 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 21 04:22:29 2014
Subject: No subject
Message-ID: <mailman.84.1416543749.32149.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 21 02:53:25 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 21 04:22:30 2014
Subject: No subject
Message-ID: <mailman.85.1416543750.32149.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 21 02:53:25 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 21 04:22:33 2014
Subject: No subject
Message-ID: <mailman.86.1416543753.32149.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 21 02:53:25 2014

From: bogus@does.not.exist.com ()
Date: Fri Nov 21 04:22:34 2014
Subject: No subject
Message-ID: <mailman.87.1416543754.32149.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 21 02:53:25 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 21 04:22:35 2014
Subject: No subject
Message-ID: <mailman.88.1416543755.32149.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 21 02:53:25 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 21 04:22:38 2014
Subject: No subject
Message-ID: <mailman.89.1416543758.32149.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 21 02:53:25 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 21 04:22:39 2014
Subject: No subject
Message-ID: <mailman.91.1416543759.32149.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 21 02:53:25 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 21 04:22:40 2014
Subject: No subject
Message-ID: <mailman.92.1416543760.32149.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 21 02:53:25 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 21 04:22:41 2014
Subject: No subject
Message-ID: <mailman.93.1416543761.32149.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 21 02:53:25 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 21 04:22:43 2014
Subject: No subject
Message-ID: <mailman.94.1416543763.32149.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 21 02:53:25 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 21 04:22:45 2014
Subject: No subject
Message-ID: <mailman.95.1416543765.32149.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 21 02:53:25 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 21 04:22:49 2014
Subject: No subject
Message-ID: <mailman.96.1416543769.32149.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 21 02:53:25 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 21 04:22:54 2014
Subject: No subject
Message-ID: <mailman.97.1416543774.32149.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 21 02:53:25 2014

From: bogus@does.not.exist.com ()
Date: Fri Nov 21 04:22:57 2014
Subject: No subject
Message-ID: <mailman.98.1416543777.32149.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 21 02:53:25 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 21 04:23:01 2014
Subject: No subject
Message-ID: <mailman.99.1416543781.32149.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 21 02:53:25 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 21 04:23:05 2014
Subject: No subject
Message-ID: <mailman.100.1416543785.32149.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 21 02:53:25 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 21 04:23:08 2014
Subject: No subject
Message-ID: <mailman.101.1416543788.32149.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 21 02:53:25 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 21 04:23:12 2014
Subject: No subject
Message-ID: <mailman.102.1416543792.32149.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 21 02:53:25 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 21 04:23:15 2014
Subject: No subject
Message-ID: <mailman.103.1416543795.32149.htk-users@eng.cam.ac.uk>
From tonyr at cantabResearch.com Tue Nov 4 20:04:46 2014
From: tonyr at cantabResearch.com (Tony Robinson)
Date: Fri Nov 21 04:37:50 2014
Subject: [HTK-Users] HTK license agreement
In-Reply-To: <545241EC02000049000E3077@pta-emo.csir.co.za>
References: <545241EC02000049000E3077@pta-emo.csir.co.za>
Message-ID: <5459315E.9030409@cantabResearch.com>
I just saw this post - I hope I haven't also missed any replies.
It's been a while since I read the HTK licence, but from memory and past
commercial practices I believe that what you are proposing is entirely
acceptable according to the HTK licence.
In fact I think www.speechmatics.com uses HVite in exactly this way to
do some final tidying up of the large vocabulary speech recognition output.
Tony
On 30/10/14 11:49, Georg Schlunz wrote:
> Good day
>
> Regarding the HTK license, as specified at http://htk.eng.cam.ac.uk/docs/licen
se.shtml , I would like to know whether the following scenario is permitted:

>
> The HTK software (including HVite) sits on a server in-house in our organisati
on, as per license sections 2.1 and 2.3.
> The HTK software (including HVite) is never distributed to a commercial (or no
n-commercial) party, as per license section 2.2.
>
> We have written our own server-client software, where:
> a) the client records speech and sends the audio file to the server, which pas
ses it on to HVite (the server software and HTK sit on the same in-house machine
)
> b) HVite decodes the audio into text
> c) the server replies to the client with the decoded text and the client proce
sses the text somehow
>
> Naturally, the client software contains no HTK code; it only processes data pr
oduced by HTK.
>
> Therefore, may this client software and decoding SERVICE be sold commercially
(as long as we agree to license sections 2.4 and 2.5)?
>
> Thank you
> Georg Schlunz
>
-- ** Cantab is hiring: www.cantabResearch.com/openings ** -Dr A J Robinson, Founder, Cantab Research Ltd
Phone direct: 01223 778240 office: 01223 794497
Company reg no GB 05697423, VAT reg no 925606030
51 Canterbury Street, Cambridge, CB4 3QG, UK
From bogus@does.not.exist.com Sat Nov 22 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Sat Nov 22 04:21:47 2014
Subject: No subject
Message-ID: <mailman.1.1416630107.14632.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sat Nov 22 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Sat Nov 22 04:21:54 2014
Subject: No subject
Message-ID: <mailman.2.1416630114.14632.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sat Nov 22 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Sat Nov 22 04:21:56 2014
Subject: No subject
Message-ID: <mailman.3.1416630116.14632.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sat Nov 22 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Sat Nov 22 04:22:01 2014
Subject: No subject
Message-ID: <mailman.4.1416630121.14632.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sat Nov 22 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Sat Nov 22 04:22:04 2014
Subject: No subject
Message-ID: <mailman.5.1416630124.14632.htk-users@eng.cam.ac.uk>

From bogus@does.not.exist.com Sat Nov 22 02:50:32 2014


From: bogus@does.not.exist.com ()
Date: Sat Nov 22 04:22:07 2014
Subject: No subject
Message-ID: <mailman.6.1416630127.14632.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sat Nov 22 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Sat Nov 22 04:22:10 2014
Subject: No subject
Message-ID: <mailman.7.1416630130.14632.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sat Nov 22 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Sat Nov 22 04:22:13 2014
Subject: No subject
Message-ID: <mailman.8.1416630133.14632.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sat Nov 22 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Sat Nov 22 04:22:15 2014
Subject: No subject
Message-ID: <mailman.9.1416630135.14632.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sat Nov 22 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Sat Nov 22 04:22:20 2014
Subject: No subject
Message-ID: <mailman.10.1416630140.14632.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sat Nov 22 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Sat Nov 22 04:22:21 2014
Subject: No subject
Message-ID: <mailman.11.1416630141.14632.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sat Nov 22 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Sat Nov 22 04:22:25 2014
Subject: No subject
Message-ID: <mailman.12.1416630145.14632.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sat Nov 22 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Sat Nov 22 04:22:29 2014
Subject: No subject
Message-ID: <mailman.13.1416630149.14632.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sat Nov 22 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Sat Nov 22 04:22:32 2014
Subject: No subject
Message-ID: <mailman.14.1416630152.14632.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sat Nov 22 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Sat Nov 22 04:22:34 2014
Subject: No subject
Message-ID: <mailman.15.1416630154.14632.htk-users@eng.cam.ac.uk>

From bogus@does.not.exist.com Sat Nov 22 02:50:32 2014


From: bogus@does.not.exist.com ()
Date: Sat Nov 22 04:22:34 2014
Subject: No subject
Message-ID: <mailman.16.1416630154.14632.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sat Nov 22 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Sat Nov 22 04:22:37 2014
Subject: No subject
Message-ID: <mailman.17.1416630157.14632.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sat Nov 22 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Sat Nov 22 04:22:40 2014
Subject: No subject
Message-ID: <mailman.18.1416630160.14632.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sat Nov 22 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Sat Nov 22 04:22:46 2014
Subject: No subject
Message-ID: <mailman.19.1416630166.14632.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sat Nov 22 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Sat Nov 22 04:22:48 2014
Subject: No subject
Message-ID: <mailman.20.1416630168.14632.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sat Nov 22 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Sat Nov 22 04:23:00 2014
Subject: No subject
Message-ID: <mailman.21.1416630180.14632.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sat Nov 22 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Sat Nov 22 04:23:13 2014
Subject: No subject
Message-ID: <mailman.22.1416630193.14632.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sat Nov 22 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Sat Nov 22 04:23:21 2014
Subject: No subject
Message-ID: <mailman.23.1416630201.14632.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sat Nov 22 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Sat Nov 22 04:23:25 2014
Subject: No subject
Message-ID: <mailman.24.1416630204.14632.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sat Nov 22 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Sat Nov 22 04:23:28 2014
Subject: No subject
Message-ID: <mailman.25.1416630208.14632.htk-users@eng.cam.ac.uk>

From bogus@does.not.exist.com Sat Nov 22 02:50:32 2014


From: bogus@does.not.exist.com ()
Date: Sat Nov 22 04:23:29 2014
Subject: No subject
Message-ID: <mailman.26.1416630209.14632.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sat Nov 22 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Sat Nov 22 04:23:31 2014
Subject: No subject
Message-ID: <mailman.27.1416630211.14632.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sat Nov 22 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Sat Nov 22 04:23:42 2014
Subject: No subject
Message-ID: <mailman.28.1416630222.14632.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sat Nov 22 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Sat Nov 22 04:23:51 2014
Subject: No subject
Message-ID: <mailman.29.1416630231.14632.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sat Nov 22 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Sat Nov 22 04:24:02 2014
Subject: No subject
Message-ID: <mailman.30.1416630241.14632.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sat Nov 22 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Sat Nov 22 04:24:12 2014
Subject: No subject
Message-ID: <mailman.31.1416630251.14632.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sat Nov 22 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Sat Nov 22 04:24:17 2014
Subject: No subject
Message-ID: <mailman.32.1416630257.14632.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sat Nov 22 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Sat Nov 22 04:24:19 2014
Subject: No subject
Message-ID: <mailman.33.1416630259.14632.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sat Nov 22 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Sat Nov 22 04:24:29 2014
Subject: No subject
Message-ID: <mailman.34.1416630269.14632.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sat Nov 22 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Sat Nov 22 04:24:41 2014
Subject: No subject
Message-ID: <mailman.35.1416630281.14632.htk-users@eng.cam.ac.uk>

From bogus@does.not.exist.com Sat Nov 22 02:50:32 2014


From: bogus@does.not.exist.com ()
Date: Sat Nov 22 04:24:53 2014
Subject: No subject
Message-ID: <mailman.36.1416630293.14632.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sat Nov 22 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Sat Nov 22 04:24:56 2014
Subject: No subject
Message-ID: <mailman.37.1416630296.14632.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sat Nov 22 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Sat Nov 22 04:24:58 2014
Subject: No subject
Message-ID: <mailman.38.1416630298.14632.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sat Nov 22 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Sat Nov 22 04:24:59 2014
Subject: No subject
Message-ID: <mailman.39.1416630299.14632.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sat Nov 22 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Sat Nov 22 04:24:59 2014
Subject: No subject
Message-ID: <mailman.40.1416630299.14632.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sat Nov 22 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Sat Nov 22 04:25:12 2014
Subject: No subject
Message-ID: <mailman.41.1416630312.14632.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sat Nov 22 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Sat Nov 22 04:25:16 2014
Subject: No subject
Message-ID: <mailman.42.1416630316.14632.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sat Nov 22 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Sat Nov 22 04:25:33 2014
Subject: No subject
Message-ID: <mailman.43.1416630333.14632.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sat Nov 22 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Sat Nov 22 04:25:35 2014
Subject: No subject
Message-ID: <mailman.44.1416630335.14632.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sat Nov 22 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Sat Nov 22 04:25:41 2014
Subject: No subject
Message-ID: <mailman.45.1416630341.14632.htk-users@eng.cam.ac.uk>

From bogus@does.not.exist.com Sat Nov 22 02:50:32 2014


From: bogus@does.not.exist.com ()
Date: Sat Nov 22 04:25:55 2014
Subject: No subject
Message-ID: <mailman.46.1416630355.14632.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sat Nov 22 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Sat Nov 22 04:25:58 2014
Subject: No subject
Message-ID: <mailman.47.1416630358.14632.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sat Nov 22 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Sat Nov 22 04:26:04 2014
Subject: No subject
Message-ID: <mailman.48.1416630361.14632.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sat Nov 22 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Sat Nov 22 04:26:11 2014
Subject: No subject
Message-ID: <mailman.49.1416630371.14632.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sat Nov 22 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Sat Nov 22 04:26:14 2014
Subject: No subject
Message-ID: <mailman.50.1416630374.14632.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sat Nov 22 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Sat Nov 22 04:26:20 2014
Subject: No subject
Message-ID: <mailman.51.1416630380.14632.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sat Nov 22 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Sat Nov 22 04:26:25 2014
Subject: No subject
Message-ID: <mailman.52.1416630384.14632.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sat Nov 22 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Sat Nov 22 04:26:25 2014
Subject: No subject
Message-ID: <mailman.53.1416630385.14632.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sat Nov 22 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Sat Nov 22 04:26:26 2014
Subject: No subject
Message-ID: <mailman.54.1416630386.14632.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sat Nov 22 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Sat Nov 22 04:26:26 2014
Subject: No subject
Message-ID: <mailman.55.1416630386.14632.htk-users@eng.cam.ac.uk>

From bogus@does.not.exist.com Sat Nov 22 02:50:32 2014


From: bogus@does.not.exist.com ()
Date: Sat Nov 22 04:26:27 2014
Subject: No subject
Message-ID: <mailman.56.1416630387.14632.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sat Nov 22 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Sat Nov 22 04:26:27 2014
Subject: No subject
Message-ID: <mailman.57.1416630387.14632.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sat Nov 22 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Sat Nov 22 04:26:29 2014
Subject: No subject
Message-ID: <mailman.58.1416630389.14632.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sat Nov 22 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Sat Nov 22 04:26:34 2014
Subject: No subject
Message-ID: <mailman.59.1416630394.14632.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sat Nov 22 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Sat Nov 22 04:26:37 2014
Subject: No subject
Message-ID: <mailman.60.1416630397.14632.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sat Nov 22 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Sat Nov 22 04:26:38 2014
Subject: No subject
Message-ID: <mailman.61.1416630398.14632.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sat Nov 22 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Sat Nov 22 04:26:39 2014
Subject: No subject
Message-ID: <mailman.62.1416630399.14632.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sat Nov 22 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Sat Nov 22 04:26:39 2014
Subject: No subject
Message-ID: <mailman.63.1416630399.14632.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sat Nov 22 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Sat Nov 22 04:26:40 2014
Subject: No subject
Message-ID: <mailman.64.1416630400.14632.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sat Nov 22 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Sat Nov 22 04:26:45 2014
Subject: No subject
Message-ID: <mailman.65.1416630404.14632.htk-users@eng.cam.ac.uk>

From bogus@does.not.exist.com Sat Nov 22 02:50:32 2014


From: bogus@does.not.exist.com ()
Date: Sat Nov 22 04:26:51 2014
Subject: No subject
Message-ID: <mailman.66.1416630410.14632.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sat Nov 22 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Sat Nov 22 04:26:58 2014
Subject: No subject
Message-ID: <mailman.67.1416630418.14632.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sat Nov 22 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Sat Nov 22 04:27:09 2014
Subject: No subject
Message-ID: <mailman.68.1416630428.14632.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sat Nov 22 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Sat Nov 22 04:27:15 2014
Subject: No subject
Message-ID: <mailman.69.1416630435.14632.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sat Nov 22 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Sat Nov 22 04:27:21 2014
Subject: No subject
Message-ID: <mailman.70.1416630441.14632.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sat Nov 22 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Sat Nov 22 04:27:39 2014
Subject: No subject
Message-ID: <mailman.71.1416630459.14632.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sat Nov 22 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Sat Nov 22 04:27:46 2014
Subject: No subject
Message-ID: <mailman.72.1416630466.14632.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sat Nov 22 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Sat Nov 22 04:27:57 2014
Subject: No subject
Message-ID: <mailman.73.1416630476.14632.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sat Nov 22 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Sat Nov 22 04:28:02 2014
Subject: No subject
Message-ID: <mailman.74.1416630482.14632.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sat Nov 22 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Sat Nov 22 04:28:02 2014
Subject: No subject
Message-ID: <mailman.75.1416630482.14632.htk-users@eng.cam.ac.uk>

From bogus@does.not.exist.com Sat Nov 22 02:50:32 2014


From: bogus@does.not.exist.com ()
Date: Sat Nov 22 04:28:03 2014
Subject: No subject
Message-ID: <mailman.76.1416630483.14632.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sat Nov 22 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Sat Nov 22 04:28:03 2014
Subject: No subject
Message-ID: <mailman.77.1416630483.14632.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sat Nov 22 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Sat Nov 22 04:28:04 2014
Subject: No subject
Message-ID: <mailman.78.1416630484.14632.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sat Nov 22 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Sat Nov 22 04:28:05 2014
Subject: No subject
Message-ID: <mailman.79.1416630485.14632.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sat Nov 22 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Sat Nov 22 04:28:05 2014
Subject: No subject
Message-ID: <mailman.80.1416630485.14632.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sat Nov 22 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Sat Nov 22 04:28:06 2014
Subject: No subject
Message-ID: <mailman.81.1416630486.14632.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sat Nov 22 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Sat Nov 22 04:28:06 2014
Subject: No subject
Message-ID: <mailman.82.1416630486.14632.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sat Nov 22 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Sat Nov 22 04:28:07 2014
Subject: No subject
Message-ID: <mailman.83.1416630487.14632.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sat Nov 22 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Sat Nov 22 04:28:08 2014
Subject: No subject
Message-ID: <mailman.84.1416630488.14632.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sat Nov 22 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Sat Nov 22 04:28:09 2014
Subject: No subject
Message-ID: <mailman.85.1416630489.14632.htk-users@eng.cam.ac.uk>

From bogus@does.not.exist.com Sat Nov 22 02:50:32 2014


From: bogus@does.not.exist.com ()
Date: Sat Nov 22 04:28:12 2014
Subject: No subject
Message-ID: <mailman.86.1416630492.14632.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sat Nov 22 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Sat Nov 22 04:28:14 2014
Subject: No subject
Message-ID: <mailman.87.1416630494.14632.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sat Nov 22 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Sat Nov 22 04:28:30 2014
Subject: No subject
Message-ID: <mailman.88.1416630509.14632.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sat Nov 22 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Sat Nov 22 04:28:37 2014
Subject: No subject
Message-ID: <mailman.89.1416630517.14632.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sat Nov 22 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Sat Nov 22 04:28:39 2014
Subject: No subject
Message-ID: <mailman.91.1416630519.14632.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sat Nov 22 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Sat Nov 22 04:28:40 2014
Subject: No subject
Message-ID: <mailman.92.1416630520.14632.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sat Nov 22 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Sat Nov 22 04:28:44 2014
Subject: No subject
Message-ID: <mailman.93.1416630524.14632.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sat Nov 22 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Sat Nov 22 04:28:49 2014
Subject: No subject
Message-ID: <mailman.94.1416630529.14632.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sat Nov 22 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Sat Nov 22 04:28:51 2014
Subject: No subject
Message-ID: <mailman.95.1416630531.14632.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sat Nov 22 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Sat Nov 22 04:28:53 2014
Subject: No subject
Message-ID: <mailman.96.1416630533.14632.htk-users@eng.cam.ac.uk>

From bogus@does.not.exist.com Sat Nov 22 02:50:32 2014


From: bogus@does.not.exist.com ()
Date: Sat Nov 22 04:28:58 2014
Subject: No subject
Message-ID: <mailman.97.1416630538.14632.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sat Nov 22 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Sat Nov 22 04:29:02 2014
Subject: No subject
Message-ID: <mailman.98.1416630542.14632.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sat Nov 22 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Sat Nov 22 04:29:07 2014
Subject: No subject
Message-ID: <mailman.99.1416630547.14632.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sat Nov 22 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Sat Nov 22 04:29:20 2014
Subject: No subject
Message-ID: <mailman.100.1416630560.14632.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sat Nov 22 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Sat Nov 22 04:29:28 2014
Subject: No subject
Message-ID: <mailman.101.1416630568.14632.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sat Nov 22 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Sat Nov 22 04:29:33 2014
Subject: No subject
Message-ID: <mailman.102.1416630573.14632.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sat Nov 22 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Sat Nov 22 04:29:38 2014
Subject: No subject
Message-ID: <mailman.103.1416630578.14632.htk-users@eng.cam.ac.uk>
From tonyr at cantabResearch.com Tue Nov 4 20:04:46 2014
From: tonyr at cantabResearch.com (Tony Robinson)
Date: Sat Nov 22 04:52:34 2014
Subject: [HTK-Users] HTK license agreement
In-Reply-To: <545241EC02000049000E3077@pta-emo.csir.co.za>
References: <545241EC02000049000E3077@pta-emo.csir.co.za>
Message-ID: <5459315E.9030409@cantabResearch.com>
I just saw this post - I hope I haven't also missed any replies.
It's been a while since I read the HTK licence, but from memory and past
commercial practices I believe that what you are proposing is entirely
acceptable according to the HTK licence.
In fact I think www.speechmatics.com uses HVite in exactly this way to
do some final tidying up of the large vocabulary speech recognition output.

Tony
On 30/10/14 11:49, Georg Schlunz wrote:
> Good day
>
> Regarding the HTK license, as specified at http://htk.eng.cam.ac.uk/docs/licen
se.shtml , I would like to know whether the following scenario is permitted:
>
> The HTK software (including HVite) sits on a server in-house in our organisati
on, as per license sections 2.1 and 2.3.
> The HTK software (including HVite) is never distributed to a commercial (or no
n-commercial) party, as per license section 2.2.
>
> We have written our own server-client software, where:
> a) the client records speech and sends the audio file to the server, which pas
ses it on to HVite (the server software and HTK sit on the same in-house machine
)
> b) HVite decodes the audio into text
> c) the server replies to the client with the decoded text and the client proce
sses the text somehow
>
> Naturally, the client software contains no HTK code; it only processes data pr
oduced by HTK.
>
> Therefore, may this client software and decoding SERVICE be sold commercially
(as long as we agree to license sections 2.4 and 2.5)?
>
> Thank you
> Georg Schlunz
>
-- ** Cantab is hiring: www.cantabResearch.com/openings ** -Dr A J Robinson, Founder, Cantab Research Ltd
Phone direct: 01223 778240 office: 01223 794497
Company reg no GB 05697423, VAT reg no 925606030
51 Canterbury Street, Cambridge, CB4 3QG, UK
From bogus@does.not.exist.com Sun Nov 23 02:50:29 2014
From: bogus@does.not.exist.com ()
Date: Sun Nov 23 03:39:38 2014
Subject: No subject
Message-ID: <mailman.1.1416713976.2880.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sun Nov 23 02:50:29 2014
From: bogus@does.not.exist.com ()
Date: Sun Nov 23 03:39:42 2014
Subject: No subject
Message-ID: <mailman.2.1416713982.2880.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sun Nov 23 02:50:29 2014
From: bogus@does.not.exist.com ()
Date: Sun Nov 23 03:39:45 2014
Subject: No subject
Message-ID: <mailman.3.1416713985.2880.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sun Nov 23 02:50:29 2014
From: bogus@does.not.exist.com ()
Date: Sun Nov 23 03:39:48 2014
Subject: No subject
Message-ID: <mailman.4.1416713988.2880.htk-users@eng.cam.ac.uk>

From bogus@does.not.exist.com Sun Nov 23 02:50:29 2014


From: bogus@does.not.exist.com ()
Date: Sun Nov 23 03:39:53 2014
Subject: No subject
Message-ID: <mailman.5.1416713993.2880.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sun Nov 23 02:50:29 2014
From: bogus@does.not.exist.com ()
Date: Sun Nov 23 03:39:57 2014
Subject: No subject
Message-ID: <mailman.6.1416713997.2880.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sun Nov 23 02:50:29 2014
From: bogus@does.not.exist.com ()
Date: Sun Nov 23 03:40:01 2014
Subject: No subject
Message-ID: <mailman.7.1416714001.2880.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sun Nov 23 02:50:29 2014
From: bogus@does.not.exist.com ()
Date: Sun Nov 23 03:40:04 2014
Subject: No subject
Message-ID: <mailman.8.1416714004.2880.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sun Nov 23 02:50:29 2014
From: bogus@does.not.exist.com ()
Date: Sun Nov 23 03:40:06 2014
Subject: No subject
Message-ID: <mailman.9.1416714006.2880.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sun Nov 23 02:50:29 2014
From: bogus@does.not.exist.com ()
Date: Sun Nov 23 03:40:11 2014
Subject: No subject
Message-ID: <mailman.10.1416714011.2880.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sun Nov 23 02:50:29 2014
From: bogus@does.not.exist.com ()
Date: Sun Nov 23 03:40:12 2014
Subject: No subject
Message-ID: <mailman.11.1416714012.2880.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sun Nov 23 02:50:29 2014
From: bogus@does.not.exist.com ()
Date: Sun Nov 23 03:40:13 2014
Subject: No subject
Message-ID: <mailman.12.1416714013.2880.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sun Nov 23 02:50:29 2014
From: bogus@does.not.exist.com ()
Date: Sun Nov 23 03:40:14 2014
Subject: No subject
Message-ID: <mailman.13.1416714014.2880.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sun Nov 23 02:50:29 2014
From: bogus@does.not.exist.com ()
Date: Sun Nov 23 03:40:14 2014
Subject: No subject
Message-ID: <mailman.14.1416714014.2880.htk-users@eng.cam.ac.uk>

From bogus@does.not.exist.com Sun Nov 23 02:50:29 2014


From: bogus@does.not.exist.com ()
Date: Sun Nov 23 03:40:15 2014
Subject: No subject
Message-ID: <mailman.15.1416714015.2880.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sun Nov 23 02:50:29 2014
From: bogus@does.not.exist.com ()
Date: Sun Nov 23 03:40:15 2014
Subject: No subject
Message-ID: <mailman.16.1416714015.2880.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sun Nov 23 02:50:29 2014
From: bogus@does.not.exist.com ()
Date: Sun Nov 23 03:40:15 2014
Subject: No subject
Message-ID: <mailman.17.1416714015.2880.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sun Nov 23 02:50:29 2014
From: bogus@does.not.exist.com ()
Date: Sun Nov 23 03:40:16 2014
Subject: No subject
Message-ID: <mailman.18.1416714016.2880.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sun Nov 23 02:50:29 2014
From: bogus@does.not.exist.com ()
Date: Sun Nov 23 03:40:18 2014
Subject: No subject
Message-ID: <mailman.19.1416714018.2880.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sun Nov 23 02:50:29 2014
From: bogus@does.not.exist.com ()
Date: Sun Nov 23 03:40:19 2014
Subject: No subject
Message-ID: <mailman.20.1416714019.2880.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sun Nov 23 02:50:29 2014
From: bogus@does.not.exist.com ()
Date: Sun Nov 23 03:40:20 2014
Subject: No subject
Message-ID: <mailman.21.1416714020.2880.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sun Nov 23 02:50:29 2014
From: bogus@does.not.exist.com ()
Date: Sun Nov 23 03:40:22 2014
Subject: No subject
Message-ID: <mailman.22.1416714022.2880.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sun Nov 23 02:50:29 2014
From: bogus@does.not.exist.com ()
Date: Sun Nov 23 03:40:23 2014
Subject: No subject
Message-ID: <mailman.23.1416714023.2880.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sun Nov 23 02:50:29 2014
From: bogus@does.not.exist.com ()
Date: Sun Nov 23 03:40:25 2014
Subject: No subject
Message-ID: <mailman.24.1416714025.2880.htk-users@eng.cam.ac.uk>

From bogus@does.not.exist.com Sun Nov 23 02:50:29 2014


From: bogus@does.not.exist.com ()
Date: Sun Nov 23 03:40:27 2014
Subject: No subject
Message-ID: <mailman.25.1416714027.2880.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sun Nov 23 02:50:29 2014
From: bogus@does.not.exist.com ()
Date: Sun Nov 23 03:40:27 2014
Subject: No subject
Message-ID: <mailman.26.1416714027.2880.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sun Nov 23 02:50:29 2014
From: bogus@does.not.exist.com ()
Date: Sun Nov 23 03:40:28 2014
Subject: No subject
Message-ID: <mailman.27.1416714028.2880.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sun Nov 23 02:50:29 2014
From: bogus@does.not.exist.com ()
Date: Sun Nov 23 03:40:28 2014
Subject: No subject
Message-ID: <mailman.28.1416714028.2880.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sun Nov 23 02:50:29 2014
From: bogus@does.not.exist.com ()
Date: Sun Nov 23 03:40:29 2014
Subject: No subject
Message-ID: <mailman.29.1416714029.2880.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sun Nov 23 02:50:29 2014
From: bogus@does.not.exist.com ()
Date: Sun Nov 23 03:40:33 2014
Subject: No subject
Message-ID: <mailman.30.1416714033.2880.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sun Nov 23 02:50:29 2014
From: bogus@does.not.exist.com ()
Date: Sun Nov 23 03:40:36 2014
Subject: No subject
Message-ID: <mailman.31.1416714036.2880.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sun Nov 23 02:50:29 2014
From: bogus@does.not.exist.com ()
Date: Sun Nov 23 03:40:40 2014
Subject: No subject
Message-ID: <mailman.32.1416714040.2880.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sun Nov 23 02:50:29 2014
From: bogus@does.not.exist.com ()
Date: Sun Nov 23 03:40:44 2014
Subject: No subject
Message-ID: <mailman.33.1416714044.2880.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sun Nov 23 02:50:29 2014
From: bogus@does.not.exist.com ()
Date: Sun Nov 23 03:40:47 2014
Subject: No subject
Message-ID: <mailman.34.1416714047.2880.htk-users@eng.cam.ac.uk>

From bogus@does.not.exist.com Sun Nov 23 02:50:29 2014


From: bogus@does.not.exist.com ()
Date: Sun Nov 23 03:40:49 2014
Subject: No subject
Message-ID: <mailman.35.1416714049.2880.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sun Nov 23 02:50:29 2014
From: bogus@does.not.exist.com ()
Date: Sun Nov 23 03:40:50 2014
Subject: No subject
Message-ID: <mailman.36.1416714050.2880.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sun Nov 23 02:50:29 2014
From: bogus@does.not.exist.com ()
Date: Sun Nov 23 03:40:50 2014
Subject: No subject
Message-ID: <mailman.37.1416714050.2880.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sun Nov 23 02:50:29 2014
From: bogus@does.not.exist.com ()
Date: Sun Nov 23 03:40:51 2014
Subject: No subject
Message-ID: <mailman.38.1416714051.2880.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sun Nov 23 02:50:29 2014
From: bogus@does.not.exist.com ()
Date: Sun Nov 23 03:40:51 2014
Subject: No subject
Message-ID: <mailman.39.1416714051.2880.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sun Nov 23 02:50:29 2014
From: bogus@does.not.exist.com ()
Date: Sun Nov 23 03:40:52 2014
Subject: No subject
Message-ID: <mailman.40.1416714052.2880.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sun Nov 23 02:50:29 2014
From: bogus@does.not.exist.com ()
Date: Sun Nov 23 03:40:56 2014
Subject: No subject
Message-ID: <mailman.41.1416714056.2880.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sun Nov 23 02:50:29 2014
From: bogus@does.not.exist.com ()
Date: Sun Nov 23 03:40:57 2014
Subject: No subject
Message-ID: <mailman.42.1416714057.2880.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sun Nov 23 02:50:29 2014
From: bogus@does.not.exist.com ()
Date: Sun Nov 23 03:40:57 2014
Subject: No subject
Message-ID: <mailman.43.1416714057.2880.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sun Nov 23 02:50:29 2014
From: bogus@does.not.exist.com ()
Date: Sun Nov 23 03:40:58 2014
Subject: No subject
Message-ID: <mailman.44.1416714058.2880.htk-users@eng.cam.ac.uk>

From bogus@does.not.exist.com Sun Nov 23 02:50:29 2014


From: bogus@does.not.exist.com ()
Date: Sun Nov 23 03:40:58 2014
Subject: No subject
Message-ID: <mailman.45.1416714058.2880.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sun Nov 23 02:50:29 2014
From: bogus@does.not.exist.com ()
Date: Sun Nov 23 03:40:59 2014
Subject: No subject
Message-ID: <mailman.46.1416714059.2880.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sun Nov 23 02:50:29 2014
From: bogus@does.not.exist.com ()
Date: Sun Nov 23 03:40:59 2014
Subject: No subject
Message-ID: <mailman.47.1416714059.2880.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sun Nov 23 02:50:29 2014
From: bogus@does.not.exist.com ()
Date: Sun Nov 23 03:41:00 2014
Subject: No subject
Message-ID: <mailman.48.1416714060.2880.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sun Nov 23 02:50:29 2014
From: bogus@does.not.exist.com ()
Date: Sun Nov 23 03:41:02 2014
Subject: No subject
Message-ID: <mailman.49.1416714062.2880.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sun Nov 23 02:50:29 2014
From: bogus@does.not.exist.com ()
Date: Sun Nov 23 03:41:02 2014
Subject: No subject
Message-ID: <mailman.50.1416714062.2880.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sun Nov 23 02:50:29 2014
From: bogus@does.not.exist.com ()
Date: Sun Nov 23 03:41:03 2014
Subject: No subject
Message-ID: <mailman.51.1416714063.2880.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sun Nov 23 02:50:29 2014
From: bogus@does.not.exist.com ()
Date: Sun Nov 23 03:41:03 2014
Subject: No subject
Message-ID: <mailman.52.1416714063.2880.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sun Nov 23 02:50:29 2014
From: bogus@does.not.exist.com ()
Date: Sun Nov 23 03:41:04 2014
Subject: No subject
Message-ID: <mailman.53.1416714064.2880.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sun Nov 23 02:50:29 2014
From: bogus@does.not.exist.com ()
Date: Sun Nov 23 03:41:05 2014
Subject: No subject
Message-ID: <mailman.54.1416714065.2880.htk-users@eng.cam.ac.uk>

From bogus@does.not.exist.com Sun Nov 23 02:50:29 2014


From: bogus@does.not.exist.com ()
Date: Sun Nov 23 03:41:08 2014
Subject: No subject
Message-ID: <mailman.55.1416714068.2880.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sun Nov 23 02:50:29 2014
From: bogus@does.not.exist.com ()
Date: Sun Nov 23 03:41:10 2014
Subject: No subject
Message-ID: <mailman.56.1416714070.2880.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sun Nov 23 02:50:29 2014
From: bogus@does.not.exist.com ()
Date: Sun Nov 23 03:41:13 2014
Subject: No subject
Message-ID: <mailman.57.1416714073.2880.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sun Nov 23 02:50:29 2014
From: bogus@does.not.exist.com ()
Date: Sun Nov 23 03:41:16 2014
Subject: No subject
Message-ID: <mailman.58.1416714075.2880.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sun Nov 23 02:50:29 2014
From: bogus@does.not.exist.com ()
Date: Sun Nov 23 03:41:17 2014
Subject: No subject
Message-ID: <mailman.59.1416714077.2880.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sun Nov 23 02:50:29 2014
From: bogus@does.not.exist.com ()
Date: Sun Nov 23 03:41:21 2014
Subject: No subject
Message-ID: <mailman.60.1416714081.2880.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sun Nov 23 02:50:29 2014
From: bogus@does.not.exist.com ()
Date: Sun Nov 23 03:41:24 2014
Subject: No subject
Message-ID: <mailman.61.1416714084.2880.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sun Nov 23 02:50:29 2014
From: bogus@does.not.exist.com ()
Date: Sun Nov 23 03:41:26 2014
Subject: No subject
Message-ID: <mailman.62.1416714086.2880.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sun Nov 23 02:50:29 2014
From: bogus@does.not.exist.com ()
Date: Sun Nov 23 03:41:28 2014
Subject: No subject
Message-ID: <mailman.63.1416714088.2880.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sun Nov 23 02:50:29 2014
From: bogus@does.not.exist.com ()
Date: Sun Nov 23 03:41:31 2014
Subject: No subject
Message-ID: <mailman.64.1416714091.2880.htk-users@eng.cam.ac.uk>

From bogus@does.not.exist.com Sun Nov 23 02:50:29 2014


From: bogus@does.not.exist.com ()
Date: Sun Nov 23 03:41:33 2014
Subject: No subject
Message-ID: <mailman.65.1416714093.2880.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sun Nov 23 02:50:29 2014
From: bogus@does.not.exist.com ()
Date: Sun Nov 23 03:41:36 2014
Subject: No subject
Message-ID: <mailman.66.1416714096.2880.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sun Nov 23 02:50:29 2014
From: bogus@does.not.exist.com ()
Date: Sun Nov 23 03:41:38 2014
Subject: No subject
Message-ID: <mailman.67.1416714098.2880.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sun Nov 23 02:50:29 2014
From: bogus@does.not.exist.com ()
Date: Sun Nov 23 03:41:39 2014
Subject: No subject
Message-ID: <mailman.68.1416714099.2880.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sun Nov 23 02:50:29 2014
From: bogus@does.not.exist.com ()
Date: Sun Nov 23 03:41:39 2014
Subject: No subject
Message-ID: <mailman.69.1416714099.2880.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sun Nov 23 02:50:29 2014
From: bogus@does.not.exist.com ()
Date: Sun Nov 23 03:41:42 2014
Subject: No subject
Message-ID: <mailman.70.1416714102.2880.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sun Nov 23 02:50:29 2014
From: bogus@does.not.exist.com ()
Date: Sun Nov 23 03:41:43 2014
Subject: No subject
Message-ID: <mailman.71.1416714103.2880.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sun Nov 23 02:50:29 2014
From: bogus@does.not.exist.com ()
Date: Sun Nov 23 03:41:43 2014
Subject: No subject
Message-ID: <mailman.72.1416714103.2880.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sun Nov 23 02:50:29 2014
From: bogus@does.not.exist.com ()
Date: Sun Nov 23 03:41:44 2014
Subject: No subject
Message-ID: <mailman.73.1416714104.2880.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sun Nov 23 02:50:29 2014
From: bogus@does.not.exist.com ()
Date: Sun Nov 23 03:41:44 2014
Subject: No subject
Message-ID: <mailman.74.1416714104.2880.htk-users@eng.cam.ac.uk>

From bogus@does.not.exist.com Sun Nov 23 02:50:29 2014


From: bogus@does.not.exist.com ()
Date: Sun Nov 23 03:41:45 2014
Subject: No subject
Message-ID: <mailman.75.1416714104.2880.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sun Nov 23 02:50:29 2014
From: bogus@does.not.exist.com ()
Date: Sun Nov 23 03:41:45 2014
Subject: No subject
Message-ID: <mailman.76.1416714105.2880.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sun Nov 23 02:50:29 2014
From: bogus@does.not.exist.com ()
Date: Sun Nov 23 03:41:46 2014
Subject: No subject
Message-ID: <mailman.77.1416714106.2880.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sun Nov 23 02:50:29 2014
From: bogus@does.not.exist.com ()
Date: Sun Nov 23 03:41:46 2014
Subject: No subject
Message-ID: <mailman.78.1416714106.2880.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sun Nov 23 02:50:29 2014
From: bogus@does.not.exist.com ()
Date: Sun Nov 23 03:41:47 2014
Subject: No subject
Message-ID: <mailman.79.1416714107.2880.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sun Nov 23 02:50:29 2014
From: bogus@does.not.exist.com ()
Date: Sun Nov 23 03:41:47 2014
Subject: No subject
Message-ID: <mailman.80.1416714107.2880.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sun Nov 23 02:50:29 2014
From: bogus@does.not.exist.com ()
Date: Sun Nov 23 03:41:47 2014
Subject: No subject
Message-ID: <mailman.81.1416714107.2880.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sun Nov 23 02:50:29 2014
From: bogus@does.not.exist.com ()
Date: Sun Nov 23 03:41:48 2014
Subject: No subject
Message-ID: <mailman.82.1416714108.2880.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sun Nov 23 02:50:29 2014
From: bogus@does.not.exist.com ()
Date: Sun Nov 23 03:41:49 2014
Subject: No subject
Message-ID: <mailman.83.1416714109.2880.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sun Nov 23 02:50:29 2014
From: bogus@does.not.exist.com ()
Date: Sun Nov 23 03:41:49 2014
Subject: No subject
Message-ID: <mailman.84.1416714109.2880.htk-users@eng.cam.ac.uk>

From bogus@does.not.exist.com Sun Nov 23 02:50:29 2014


From: bogus@does.not.exist.com ()
Date: Sun Nov 23 03:41:50 2014
Subject: No subject
Message-ID: <mailman.85.1416714110.2880.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sun Nov 23 02:50:29 2014
From: bogus@does.not.exist.com ()
Date: Sun Nov 23 03:41:52 2014
Subject: No subject
Message-ID: <mailman.86.1416714112.2880.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sun Nov 23 02:50:29 2014
From: bogus@does.not.exist.com ()
Date: Sun Nov 23 03:41:53 2014
Subject: No subject
Message-ID: <mailman.87.1416714113.2880.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sun Nov 23 02:50:29 2014
From: bogus@does.not.exist.com ()
Date: Sun Nov 23 03:41:54 2014
Subject: No subject
Message-ID: <mailman.88.1416714114.2880.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sun Nov 23 02:50:29 2014
From: bogus@does.not.exist.com ()
Date: Sun Nov 23 03:41:55 2014
Subject: No subject
Message-ID: <mailman.89.1416714115.2880.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sun Nov 23 02:50:29 2014
From: bogus@does.not.exist.com ()
Date: Sun Nov 23 03:41:56 2014
Subject: No subject
Message-ID: <mailman.91.1416714116.2880.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sun Nov 23 02:50:29 2014
From: bogus@does.not.exist.com ()
Date: Sun Nov 23 03:41:57 2014
Subject: No subject
Message-ID: <mailman.92.1416714117.2880.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sun Nov 23 02:50:29 2014
From: bogus@does.not.exist.com ()
Date: Sun Nov 23 03:41:57 2014
Subject: No subject
Message-ID: <mailman.93.1416714117.2880.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sun Nov 23 02:50:29 2014
From: bogus@does.not.exist.com ()
Date: Sun Nov 23 03:41:59 2014
Subject: No subject
Message-ID: <mailman.94.1416714119.2880.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sun Nov 23 02:50:29 2014
From: bogus@does.not.exist.com ()
Date: Sun Nov 23 03:42:00 2014
Subject: No subject
Message-ID: <mailman.95.1416714120.2880.htk-users@eng.cam.ac.uk>

From bogus@does.not.exist.com Sun Nov 23 02:50:29 2014


From: bogus@does.not.exist.com ()
Date: Sun Nov 23 03:42:01 2014
Subject: No subject
Message-ID: <mailman.96.1416714121.2880.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sun Nov 23 02:50:29 2014
From: bogus@does.not.exist.com ()
Date: Sun Nov 23 03:42:03 2014
Subject: No subject
Message-ID: <mailman.97.1416714123.2880.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sun Nov 23 02:50:29 2014
From: bogus@does.not.exist.com ()
Date: Sun Nov 23 03:42:04 2014
Subject: No subject
Message-ID: <mailman.98.1416714124.2880.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sun Nov 23 02:50:29 2014
From: bogus@does.not.exist.com ()
Date: Sun Nov 23 03:42:06 2014
Subject: No subject
Message-ID: <mailman.99.1416714126.2880.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sun Nov 23 02:50:29 2014
From: bogus@does.not.exist.com ()
Date: Sun Nov 23 03:42:07 2014
Subject: No subject
Message-ID: <mailman.100.1416714127.2880.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sun Nov 23 02:50:29 2014
From: bogus@does.not.exist.com ()
Date: Sun Nov 23 03:42:09 2014
Subject: No subject
Message-ID: <mailman.101.1416714128.2880.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sun Nov 23 02:50:29 2014
From: bogus@does.not.exist.com ()
Date: Sun Nov 23 03:42:10 2014
Subject: No subject
Message-ID: <mailman.102.1416714130.2880.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sun Nov 23 02:50:29 2014
From: bogus@does.not.exist.com ()
Date: Sun Nov 23 03:42:10 2014
Subject: No subject
Message-ID: <mailman.103.1416714130.2880.htk-users@eng.cam.ac.uk>
From tonyr at cantabResearch.com Tue Nov 4 20:04:46 2014
From: tonyr at cantabResearch.com (Tony Robinson)
Date: Sun Nov 23 03:58:35 2014
Subject: [HTK-Users] HTK license agreement
In-Reply-To: <545241EC02000049000E3077@pta-emo.csir.co.za>
References: <545241EC02000049000E3077@pta-emo.csir.co.za>
Message-ID: <5459315E.9030409@cantabResearch.com>
I just saw this post - I hope I haven't also missed any replies.
It's been a while since I read the HTK licence, but from memory and past

commercial practices I believe that what you are proposing is entirely


acceptable according to the HTK licence.
In fact I think www.speechmatics.com uses HVite in exactly this way to
do some final tidying up of the large vocabulary speech recognition output.
Tony
On 30/10/14 11:49, Georg Schlunz wrote:
> Good day
>
> Regarding the HTK license, as specified at http://htk.eng.cam.ac.uk/docs/licen
se.shtml , I would like to know whether the following scenario is permitted:
>
> The HTK software (including HVite) sits on a server in-house in our organisati
on, as per license sections 2.1 and 2.3.
> The HTK software (including HVite) is never distributed to a commercial (or no
n-commercial) party, as per license section 2.2.
>
> We have written our own server-client software, where:
> a) the client records speech and sends the audio file to the server, which pas
ses it on to HVite (the server software and HTK sit on the same in-house machine
)
> b) HVite decodes the audio into text
> c) the server replies to the client with the decoded text and the client proce
sses the text somehow
>
> Naturally, the client software contains no HTK code; it only processes data pr
oduced by HTK.
>
> Therefore, may this client software and decoding SERVICE be sold commercially
(as long as we agree to license sections 2.4 and 2.5)?
>
> Thank you
> Georg Schlunz
>
-- ** Cantab is hiring: www.cantabResearch.com/openings ** -Dr A J Robinson, Founder, Cantab Research Ltd
Phone direct: 01223 778240 office: 01223 794497
Company reg no GB 05697423, VAT reg no 925606030
51 Canterbury Street, Cambridge, CB4 3QG, UK
From bogus@does.not.exist.com Mon Nov 24 02:56:06 2014
From: bogus@does.not.exist.com ()
Date: Mon Nov 24 05:49:52 2014
Subject: No subject
Message-ID: <mailman.1.1416808192.17107.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Mon Nov 24 02:56:06 2014
From: bogus@does.not.exist.com ()
Date: Mon Nov 24 05:50:01 2014
Subject: No subject
Message-ID: <mailman.2.1416808201.17107.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Mon Nov 24 02:56:06 2014
From: bogus@does.not.exist.com ()
Date: Mon Nov 24 05:50:04 2014
Subject: No subject

Message-ID: <mailman.3.1416808204.17107.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Mon Nov 24 02:56:06 2014
From: bogus@does.not.exist.com ()
Date: Mon Nov 24 05:50:09 2014
Subject: No subject
Message-ID: <mailman.4.1416808209.17107.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Mon Nov 24 02:56:06 2014
From: bogus@does.not.exist.com ()
Date: Mon Nov 24 05:50:14 2014
Subject: No subject
Message-ID: <mailman.5.1416808214.17107.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Mon Nov 24 02:56:06 2014
From: bogus@does.not.exist.com ()
Date: Mon Nov 24 05:50:18 2014
Subject: No subject
Message-ID: <mailman.6.1416808218.17107.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Mon Nov 24 02:56:06 2014
From: bogus@does.not.exist.com ()
Date: Mon Nov 24 05:50:20 2014
Subject: No subject
Message-ID: <mailman.7.1416808220.17107.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Mon Nov 24 02:56:06 2014
From: bogus@does.not.exist.com ()
Date: Mon Nov 24 05:50:24 2014
Subject: No subject
Message-ID: <mailman.8.1416808224.17107.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Mon Nov 24 02:56:06 2014
From: bogus@does.not.exist.com ()
Date: Mon Nov 24 05:50:28 2014
Subject: No subject
Message-ID: <mailman.9.1416808228.17107.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Mon Nov 24 02:56:06 2014
From: bogus@does.not.exist.com ()
Date: Mon Nov 24 05:50:37 2014
Subject: No subject
Message-ID: <mailman.10.1416808237.17107.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Mon Nov 24 02:56:06 2014
From: bogus@does.not.exist.com ()
Date: Mon Nov 24 05:50:41 2014
Subject: No subject
Message-ID: <mailman.11.1416808241.17107.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Mon Nov 24 02:56:06 2014
From: bogus@does.not.exist.com ()
Date: Mon Nov 24 05:50:48 2014
Subject: No subject
Message-ID: <mailman.12.1416808248.17107.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Mon Nov 24 02:56:06 2014
From: bogus@does.not.exist.com ()
Date: Mon Nov 24 05:50:54 2014
Subject: No subject

Message-ID: <mailman.13.1416808254.17107.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Mon Nov 24 02:56:06 2014
From: bogus@does.not.exist.com ()
Date: Mon Nov 24 05:50:59 2014
Subject: No subject
Message-ID: <mailman.14.1416808259.17107.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Mon Nov 24 02:56:06 2014
From: bogus@does.not.exist.com ()
Date: Mon Nov 24 05:51:03 2014
Subject: No subject
Message-ID: <mailman.15.1416808263.17107.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Mon Nov 24 02:56:06 2014
From: bogus@does.not.exist.com ()
Date: Mon Nov 24 05:51:09 2014
Subject: No subject
Message-ID: <mailman.16.1416808268.17107.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Mon Nov 24 02:56:06 2014
From: bogus@does.not.exist.com ()
Date: Mon Nov 24 05:51:15 2014
Subject: No subject
Message-ID: <mailman.17.1416808275.17107.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Mon Nov 24 02:56:06 2014
From: bogus@does.not.exist.com ()
Date: Mon Nov 24 05:51:22 2014
Subject: No subject
Message-ID: <mailman.18.1416808282.17107.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Mon Nov 24 02:56:06 2014
From: bogus@does.not.exist.com ()
Date: Mon Nov 24 05:51:35 2014
Subject: No subject
Message-ID: <mailman.19.1416808295.17107.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Mon Nov 24 02:56:06 2014
From: bogus@does.not.exist.com ()
Date: Mon Nov 24 05:51:42 2014
Subject: No subject
Message-ID: <mailman.20.1416808302.17107.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Mon Nov 24 02:56:06 2014
From: bogus@does.not.exist.com ()
Date: Mon Nov 24 05:51:54 2014
Subject: No subject
Message-ID: <mailman.21.1416808314.17107.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Mon Nov 24 02:56:06 2014
From: bogus@does.not.exist.com ()
Date: Mon Nov 24 05:52:06 2014
Subject: No subject
Message-ID: <mailman.22.1416808325.17107.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Mon Nov 24 02:56:06 2014
From: bogus@does.not.exist.com ()
Date: Mon Nov 24 05:52:13 2014
Subject: No subject

Message-ID: <mailman.23.1416808333.17107.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Mon Nov 24 02:56:06 2014
From: bogus@does.not.exist.com ()
Date: Mon Nov 24 05:52:19 2014
Subject: No subject
Message-ID: <mailman.24.1416808339.17107.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Mon Nov 24 02:56:06 2014
From: bogus@does.not.exist.com ()
Date: Mon Nov 24 05:52:27 2014
Subject: No subject
Message-ID: <mailman.25.1416808347.17107.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Mon Nov 24 02:56:06 2014
From: bogus@does.not.exist.com ()
Date: Mon Nov 24 05:52:31 2014
Subject: No subject
Message-ID: <mailman.26.1416808351.17107.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Mon Nov 24 02:56:06 2014
From: bogus@does.not.exist.com ()
Date: Mon Nov 24 05:52:34 2014
Subject: No subject
Message-ID: <mailman.27.1416808354.17107.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Mon Nov 24 02:56:06 2014
From: bogus@does.not.exist.com ()
Date: Mon Nov 24 05:52:36 2014
Subject: No subject
Message-ID: <mailman.28.1416808356.17107.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Mon Nov 24 02:56:06 2014
From: bogus@does.not.exist.com ()
Date: Mon Nov 24 05:52:38 2014
Subject: No subject
Message-ID: <mailman.29.1416808358.17107.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Mon Nov 24 02:56:06 2014
From: bogus@does.not.exist.com ()
Date: Mon Nov 24 05:52:47 2014
Subject: No subject
Message-ID: <mailman.30.1416808367.17107.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Mon Nov 24 02:56:06 2014
From: bogus@does.not.exist.com ()
Date: Mon Nov 24 05:52:50 2014
Subject: No subject
Message-ID: <mailman.31.1416808370.17107.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Mon Nov 24 02:56:06 2014
From: bogus@does.not.exist.com ()
Date: Mon Nov 24 05:52:54 2014
Subject: No subject
Message-ID: <mailman.32.1416808374.17107.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Mon Nov 24 02:56:06 2014
From: bogus@does.not.exist.com ()
Date: Mon Nov 24 05:52:57 2014
Subject: No subject

Message-ID: <mailman.33.1416808377.17107.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Mon Nov 24 02:56:06 2014
From: bogus@does.not.exist.com ()
Date: Mon Nov 24 05:52:59 2014
Subject: No subject
Message-ID: <mailman.34.1416808379.17107.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Mon Nov 24 02:56:06 2014
From: bogus@does.not.exist.com ()
Date: Mon Nov 24 05:53:05 2014
Subject: No subject
Message-ID: <mailman.35.1416808385.17107.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Mon Nov 24 02:56:06 2014
From: bogus@does.not.exist.com ()
Date: Mon Nov 24 05:53:10 2014
Subject: No subject
Message-ID: <mailman.36.1416808390.17107.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Mon Nov 24 02:56:06 2014
From: bogus@does.not.exist.com ()
Date: Mon Nov 24 05:53:15 2014
Subject: No subject
Message-ID: <mailman.37.1416808395.17107.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Mon Nov 24 02:56:06 2014
From: bogus@does.not.exist.com ()
Date: Mon Nov 24 05:53:20 2014
Subject: No subject
Message-ID: <mailman.38.1416808400.17107.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Mon Nov 24 02:56:06 2014
From: bogus@does.not.exist.com ()
Date: Mon Nov 24 05:53:23 2014
Subject: No subject
Message-ID: <mailman.39.1416808403.17107.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Mon Nov 24 02:56:06 2014
From: bogus@does.not.exist.com ()
Date: Mon Nov 24 05:53:26 2014
Subject: No subject
Message-ID: <mailman.40.1416808406.17107.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Mon Nov 24 02:56:06 2014
From: bogus@does.not.exist.com ()
Date: Mon Nov 24 05:53:39 2014
Subject: No subject
Message-ID: <mailman.41.1416808419.17107.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Mon Nov 24 02:56:06 2014
From: bogus@does.not.exist.com ()
Date: Mon Nov 24 05:53:46 2014
Subject: No subject
Message-ID: <mailman.42.1416808426.17107.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Mon Nov 24 02:56:06 2014
From: bogus@does.not.exist.com ()
Date: Mon Nov 24 05:53:53 2014
Subject: No subject

Message-ID: <mailman.43.1416808433.17107.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Mon Nov 24 02:56:06 2014
From: bogus@does.not.exist.com ()
Date: Mon Nov 24 05:54:00 2014
Subject: No subject
Message-ID: <mailman.44.1416808440.17107.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Mon Nov 24 02:56:06 2014
From: bogus@does.not.exist.com ()
Date: Mon Nov 24 05:54:05 2014
Subject: No subject
Message-ID: <mailman.45.1416808445.17107.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Mon Nov 24 02:56:06 2014
From: bogus@does.not.exist.com ()
Date: Mon Nov 24 05:54:08 2014
Subject: No subject
Message-ID: <mailman.46.1416808448.17107.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Mon Nov 24 02:56:06 2014
From: bogus@does.not.exist.com ()
Date: Mon Nov 24 05:54:12 2014
Subject: No subject
Message-ID: <mailman.47.1416808452.17107.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Mon Nov 24 02:56:06 2014
From: bogus@does.not.exist.com ()
Date: Mon Nov 24 05:54:16 2014
Subject: No subject
Message-ID: <mailman.48.1416808456.17107.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Mon Nov 24 02:56:06 2014
From: bogus@does.not.exist.com ()
Date: Mon Nov 24 05:54:24 2014
Subject: No subject
Message-ID: <mailman.49.1416808464.17107.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Mon Nov 24 02:56:06 2014
From: bogus@does.not.exist.com ()
Date: Mon Nov 24 05:54:31 2014
Subject: No subject
Message-ID: <mailman.50.1416808471.17107.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Mon Nov 24 02:56:06 2014
From: bogus@does.not.exist.com ()
Date: Mon Nov 24 05:54:39 2014
Subject: No subject
Message-ID: <mailman.51.1416808479.17107.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Mon Nov 24 02:56:06 2014
From: bogus@does.not.exist.com ()
Date: Mon Nov 24 05:54:47 2014
Subject: No subject
Message-ID: <mailman.52.1416808486.17107.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Mon Nov 24 02:56:06 2014
From: bogus@does.not.exist.com ()
Date: Mon Nov 24 05:54:57 2014
Subject: No subject

Message-ID: <mailman.53.1416808497.17107.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Mon Nov 24 02:56:06 2014
From: bogus@does.not.exist.com ()
Date: Mon Nov 24 05:55:07 2014
Subject: No subject
Message-ID: <mailman.54.1416808507.17107.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Mon Nov 24 02:56:06 2014
From: bogus@does.not.exist.com ()
Date: Mon Nov 24 05:55:10 2014
Subject: No subject
Message-ID: <mailman.55.1416808510.17107.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Mon Nov 24 02:56:06 2014
From: bogus@does.not.exist.com ()
Date: Mon Nov 24 05:55:12 2014
Subject: No subject
Message-ID: <mailman.56.1416808512.17107.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Mon Nov 24 02:56:06 2014
From: bogus@does.not.exist.com ()
Date: Mon Nov 24 05:55:14 2014
Subject: No subject
Message-ID: <mailman.57.1416808514.17107.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Mon Nov 24 02:56:06 2014
From: bogus@does.not.exist.com ()
Date: Mon Nov 24 05:55:16 2014
Subject: No subject
Message-ID: <mailman.58.1416808516.17107.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Mon Nov 24 02:56:06 2014
From: bogus@does.not.exist.com ()
Date: Mon Nov 24 05:55:18 2014
Subject: No subject
Message-ID: <mailman.59.1416808518.17107.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Mon Nov 24 02:56:06 2014
From: bogus@does.not.exist.com ()
Date: Mon Nov 24 05:55:21 2014
Subject: No subject
Message-ID: <mailman.60.1416808521.17107.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Mon Nov 24 02:56:06 2014
From: bogus@does.not.exist.com ()
Date: Mon Nov 24 05:55:24 2014
Subject: No subject
Message-ID: <mailman.61.1416808524.17107.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Mon Nov 24 02:56:06 2014
From: bogus@does.not.exist.com ()
Date: Mon Nov 24 05:55:28 2014
Subject: No subject
Message-ID: <mailman.62.1416808528.17107.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Mon Nov 24 02:56:06 2014
From: bogus@does.not.exist.com ()
Date: Mon Nov 24 05:55:30 2014
Subject: No subject

Message-ID: <mailman.63.1416808530.17107.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Mon Nov 24 02:56:06 2014
From: bogus@does.not.exist.com ()
Date: Mon Nov 24 05:55:33 2014
Subject: No subject
Message-ID: <mailman.64.1416808533.17107.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Mon Nov 24 02:56:06 2014
From: bogus@does.not.exist.com ()
Date: Mon Nov 24 05:55:35 2014
Subject: No subject
Message-ID: <mailman.65.1416808535.17107.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Mon Nov 24 02:56:06 2014
From: bogus@does.not.exist.com ()
Date: Mon Nov 24 05:55:39 2014
Subject: No subject
Message-ID: <mailman.66.1416808538.17107.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Mon Nov 24 02:56:06 2014
From: bogus@does.not.exist.com ()
Date: Mon Nov 24 05:55:42 2014
Subject: No subject
Message-ID: <mailman.67.1416808542.17107.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Mon Nov 24 02:56:06 2014
From: bogus@does.not.exist.com ()
Date: Mon Nov 24 05:55:45 2014
Subject: No subject
Message-ID: <mailman.68.1416808545.17107.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Mon Nov 24 02:56:06 2014
From: bogus@does.not.exist.com ()
Date: Mon Nov 24 05:55:47 2014
Subject: No subject
Message-ID: <mailman.69.1416808547.17107.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Mon Nov 24 02:56:06 2014
From: bogus@does.not.exist.com ()
Date: Mon Nov 24 05:55:54 2014
Subject: No subject
Message-ID: <mailman.70.1416808554.17107.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Mon Nov 24 02:56:06 2014
From: bogus@does.not.exist.com ()
Date: Mon Nov 24 05:55:56 2014
Subject: No subject
Message-ID: <mailman.71.1416808556.17107.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Mon Nov 24 02:56:06 2014
From: bogus@does.not.exist.com ()
Date: Mon Nov 24 05:55:58 2014
Subject: No subject
Message-ID: <mailman.72.1416808558.17107.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Mon Nov 24 02:56:06 2014
From: bogus@does.not.exist.com ()
Date: Mon Nov 24 05:56:01 2014
Subject: No subject

Message-ID: <mailman.73.1416808561.17107.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Mon Nov 24 02:56:06 2014
From: bogus@does.not.exist.com ()
Date: Mon Nov 24 05:56:04 2014
Subject: No subject
Message-ID: <mailman.74.1416808564.17107.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Mon Nov 24 02:56:06 2014
From: bogus@does.not.exist.com ()
Date: Mon Nov 24 05:56:06 2014
Subject: No subject
Message-ID: <mailman.75.1416808566.17107.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Mon Nov 24 02:56:06 2014
From: bogus@does.not.exist.com ()
Date: Mon Nov 24 05:56:09 2014
Subject: No subject
Message-ID: <mailman.76.1416808568.17107.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Mon Nov 24 02:56:06 2014
From: bogus@does.not.exist.com ()
Date: Mon Nov 24 05:56:11 2014
Subject: No subject
Message-ID: <mailman.77.1416808571.17107.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Mon Nov 24 02:56:06 2014
From: bogus@does.not.exist.com ()
Date: Mon Nov 24 05:56:14 2014
Subject: No subject
Message-ID: <mailman.78.1416808574.17107.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Mon Nov 24 02:56:06 2014
From: bogus@does.not.exist.com ()
Date: Mon Nov 24 05:56:16 2014
Subject: No subject
Message-ID: <mailman.79.1416808576.17107.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Mon Nov 24 02:56:06 2014
From: bogus@does.not.exist.com ()
Date: Mon Nov 24 05:56:19 2014
Subject: No subject
Message-ID: <mailman.80.1416808579.17107.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Mon Nov 24 02:56:06 2014
From: bogus@does.not.exist.com ()
Date: Mon Nov 24 05:56:22 2014
Subject: No subject
Message-ID: <mailman.81.1416808582.17107.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Mon Nov 24 02:56:06 2014
From: bogus@does.not.exist.com ()
Date: Mon Nov 24 05:56:25 2014
Subject: No subject
Message-ID: <mailman.82.1416808584.17107.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Mon Nov 24 02:56:06 2014
From: bogus@does.not.exist.com ()
Date: Mon Nov 24 05:56:31 2014
Subject: No subject

Message-ID: <mailman.83.1416808591.17107.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Mon Nov 24 02:56:06 2014
From: bogus@does.not.exist.com ()
Date: Mon Nov 24 05:56:33 2014
Subject: No subject
Message-ID: <mailman.84.1416808593.17107.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Mon Nov 24 02:56:06 2014
From: bogus@does.not.exist.com ()
Date: Mon Nov 24 05:56:36 2014
Subject: No subject
Message-ID: <mailman.85.1416808596.17107.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Mon Nov 24 02:56:06 2014
From: bogus@does.not.exist.com ()
Date: Mon Nov 24 05:56:52 2014
Subject: No subject
Message-ID: <mailman.86.1416808612.17107.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Mon Nov 24 02:56:06 2014
From: bogus@does.not.exist.com ()
Date: Mon Nov 24 05:56:55 2014
Subject: No subject
Message-ID: <mailman.87.1416808615.17107.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Mon Nov 24 02:56:06 2014
From: bogus@does.not.exist.com ()
Date: Mon Nov 24 05:56:59 2014
Subject: No subject
Message-ID: <mailman.88.1416808619.17107.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Mon Nov 24 02:56:06 2014
From: bogus@does.not.exist.com ()
Date: Mon Nov 24 05:57:01 2014
Subject: No subject
Message-ID: <mailman.89.1416808621.17107.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Mon Nov 24 02:56:06 2014
From: bogus@does.not.exist.com ()
Date: Mon Nov 24 05:57:03 2014
Subject: No subject
Message-ID: <mailman.91.1416808623.17107.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Mon Nov 24 02:56:06 2014
From: bogus@does.not.exist.com ()
Date: Mon Nov 24 05:57:06 2014
Subject: No subject
Message-ID: <mailman.92.1416808626.17107.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Mon Nov 24 02:56:06 2014
From: bogus@does.not.exist.com ()
Date: Mon Nov 24 05:57:08 2014
Subject: No subject
Message-ID: <mailman.93.1416808628.17107.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Mon Nov 24 02:56:06 2014
From: bogus@does.not.exist.com ()
Date: Mon Nov 24 05:57:15 2014
Subject: No subject

Message-ID: <mailman.94.1416808635.17107.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Mon Nov 24 02:56:06 2014
From: bogus@does.not.exist.com ()
Date: Mon Nov 24 05:57:18 2014
Subject: No subject
Message-ID: <mailman.95.1416808638.17107.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Mon Nov 24 02:56:06 2014
From: bogus@does.not.exist.com ()
Date: Mon Nov 24 05:57:20 2014
Subject: No subject
Message-ID: <mailman.96.1416808640.17107.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Mon Nov 24 02:56:06 2014
From: bogus@does.not.exist.com ()
Date: Mon Nov 24 05:57:27 2014
Subject: No subject
Message-ID: <mailman.97.1416808647.17107.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Mon Nov 24 02:56:06 2014
From: bogus@does.not.exist.com ()
Date: Mon Nov 24 05:57:30 2014
Subject: No subject
Message-ID: <mailman.98.1416808650.17107.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Mon Nov 24 02:56:06 2014
From: bogus@does.not.exist.com ()
Date: Mon Nov 24 05:57:37 2014
Subject: No subject
Message-ID: <mailman.99.1416808657.17107.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Mon Nov 24 02:56:06 2014
From: bogus@does.not.exist.com ()
Date: Mon Nov 24 05:57:41 2014
Subject: No subject
Message-ID: <mailman.100.1416808661.17107.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Mon Nov 24 02:56:06 2014
From: bogus@does.not.exist.com ()
Date: Mon Nov 24 05:57:44 2014
Subject: No subject
Message-ID: <mailman.101.1416808664.17107.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Mon Nov 24 02:56:06 2014
From: bogus@does.not.exist.com ()
Date: Mon Nov 24 05:57:48 2014
Subject: No subject
Message-ID: <mailman.102.1416808668.17107.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Mon Nov 24 02:56:06 2014
From: bogus@does.not.exist.com ()
Date: Mon Nov 24 05:57:52 2014
Subject: No subject
Message-ID: <mailman.103.1416808672.17107.htk-users@eng.cam.ac.uk>
From tonyr at cantabResearch.com Tue Nov 4 20:04:46 2014
From: tonyr at cantabResearch.com (Tony Robinson)
Date: Mon Nov 24 06:29:46 2014
Subject: [HTK-Users] HTK license agreement

In-Reply-To: <545241EC02000049000E3077@pta-emo.csir.co.za>
References: <545241EC02000049000E3077@pta-emo.csir.co.za>
Message-ID: <5459315E.9030409@cantabResearch.com>
I just saw this post - I hope I haven't also missed any replies.
It's been a while since I read the HTK licence, but from memory and past
commercial practices I believe that what you are proposing is entirely
acceptable according to the HTK licence.
In fact I think www.speechmatics.com uses HVite in exactly this way to
do some final tidying up of the large vocabulary speech recognition output.
Tony
On 30/10/14 11:49, Georg Schlunz wrote:
> Good day
>
> Regarding the HTK license, as specified at http://htk.eng.cam.ac.uk/docs/licen
se.shtml , I would like to know whether the following scenario is permitted:
>
> The HTK software (including HVite) sits on a server in-house in our organisati
on, as per license sections 2.1 and 2.3.
> The HTK software (including HVite) is never distributed to a commercial (or no
n-commercial) party, as per license section 2.2.
>
> We have written our own server-client software, where:
> a) the client records speech and sends the audio file to the server, which pas
ses it on to HVite (the server software and HTK sit on the same in-house machine
)
> b) HVite decodes the audio into text
> c) the server replies to the client with the decoded text and the client proce
sses the text somehow
>
> Naturally, the client software contains no HTK code; it only processes data pr
oduced by HTK.
>
> Therefore, may this client software and decoding SERVICE be sold commercially
(as long as we agree to license sections 2.4 and 2.5)?
>
> Thank you
> Georg Schlunz
>
-- ** Cantab is hiring: www.cantabResearch.com/openings ** -Dr A J Robinson, Founder, Cantab Research Ltd
Phone direct: 01223 778240 office: 01223 794497
Company reg no GB 05697423, VAT reg no 925606030
51 Canterbury Street, Cambridge, CB4 3QG, UK
From bogus@does.not.exist.com Tue Nov 25 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Tue Nov 25 03:39:17 2014
Subject: No subject
Message-ID: <mailman.1.1416886757.14847.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Tue Nov 25 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Tue Nov 25 03:39:19 2014

Subject: No subject
Message-ID: <mailman.2.1416886759.14847.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Tue Nov 25 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Tue Nov 25 03:39:20 2014
Subject: No subject
Message-ID: <mailman.3.1416886760.14847.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Tue Nov 25 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Tue Nov 25 03:39:20 2014
Subject: No subject
Message-ID: <mailman.4.1416886760.14847.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Tue Nov 25 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Tue Nov 25 03:39:21 2014
Subject: No subject
Message-ID: <mailman.5.1416886761.14847.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Tue Nov 25 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Tue Nov 25 03:39:21 2014
Subject: No subject
Message-ID: <mailman.6.1416886761.14847.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Tue Nov 25 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Tue Nov 25 03:39:22 2014
Subject: No subject
Message-ID: <mailman.7.1416886762.14847.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Tue Nov 25 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Tue Nov 25 03:39:22 2014
Subject: No subject
Message-ID: <mailman.8.1416886762.14847.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Tue Nov 25 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Tue Nov 25 03:39:23 2014
Subject: No subject
Message-ID: <mailman.9.1416886763.14847.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Tue Nov 25 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Tue Nov 25 03:39:28 2014
Subject: No subject
Message-ID: <mailman.10.1416886768.14847.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Tue Nov 25 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Tue Nov 25 03:39:31 2014
Subject: No subject
Message-ID: <mailman.11.1416886771.14847.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Tue Nov 25 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Tue Nov 25 03:39:36 2014

Subject: No subject
Message-ID: <mailman.12.1416886776.14847.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Tue Nov 25 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Tue Nov 25 03:39:40 2014
Subject: No subject
Message-ID: <mailman.13.1416886780.14847.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Tue Nov 25 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Tue Nov 25 03:39:43 2014
Subject: No subject
Message-ID: <mailman.14.1416886783.14847.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Tue Nov 25 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Tue Nov 25 03:39:47 2014
Subject: No subject
Message-ID: <mailman.15.1416886787.14847.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Tue Nov 25 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Tue Nov 25 03:39:50 2014
Subject: No subject
Message-ID: <mailman.16.1416886790.14847.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Tue Nov 25 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Tue Nov 25 03:39:53 2014
Subject: No subject
Message-ID: <mailman.17.1416886793.14847.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Tue Nov 25 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Tue Nov 25 03:39:54 2014
Subject: No subject
Message-ID: <mailman.18.1416886794.14847.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Tue Nov 25 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Tue Nov 25 03:39:56 2014
Subject: No subject
Message-ID: <mailman.19.1416886796.14847.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Tue Nov 25 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Tue Nov 25 03:39:57 2014
Subject: No subject
Message-ID: <mailman.20.1416886797.14847.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Tue Nov 25 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Tue Nov 25 03:39:59 2014
Subject: No subject
Message-ID: <mailman.21.1416886799.14847.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Tue Nov 25 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Tue Nov 25 03:40:01 2014

Subject: No subject
Message-ID: <mailman.22.1416886801.14847.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Tue Nov 25 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Tue Nov 25 03:40:02 2014
Subject: No subject
Message-ID: <mailman.23.1416886802.14847.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Tue Nov 25 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Tue Nov 25 03:40:04 2014
Subject: No subject
Message-ID: <mailman.24.1416886804.14847.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Tue Nov 25 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Tue Nov 25 03:40:07 2014
Subject: No subject
Message-ID: <mailman.25.1416886807.14847.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Tue Nov 25 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Tue Nov 25 03:40:07 2014
Subject: No subject
Message-ID: <mailman.26.1416886807.14847.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Tue Nov 25 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Tue Nov 25 03:40:08 2014
Subject: No subject
Message-ID: <mailman.27.1416886808.14847.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Tue Nov 25 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Tue Nov 25 03:40:10 2014
Subject: No subject
Message-ID: <mailman.28.1416886810.14847.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Tue Nov 25 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Tue Nov 25 03:40:10 2014
Subject: No subject
Message-ID: <mailman.29.1416886810.14847.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Tue Nov 25 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Tue Nov 25 03:40:17 2014
Subject: No subject
Message-ID: <mailman.30.1416886817.14847.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Tue Nov 25 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Tue Nov 25 03:40:20 2014
Subject: No subject
Message-ID: <mailman.31.1416886820.14847.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Tue Nov 25 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Tue Nov 25 03:40:23 2014

Subject: No subject
Message-ID: <mailman.32.1416886823.14847.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Tue Nov 25 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Tue Nov 25 03:40:27 2014
Subject: No subject
Message-ID: <mailman.33.1416886827.14847.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Tue Nov 25 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Tue Nov 25 03:40:29 2014
Subject: No subject
Message-ID: <mailman.34.1416886829.14847.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Tue Nov 25 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Tue Nov 25 03:40:29 2014
Subject: No subject
Message-ID: <mailman.35.1416886829.14847.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Tue Nov 25 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Tue Nov 25 03:40:30 2014
Subject: No subject
Message-ID: <mailman.36.1416886830.14847.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Tue Nov 25 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Tue Nov 25 03:40:31 2014
Subject: No subject
Message-ID: <mailman.37.1416886831.14847.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Tue Nov 25 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Tue Nov 25 03:40:32 2014
Subject: No subject
Message-ID: <mailman.38.1416886832.14847.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Tue Nov 25 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Tue Nov 25 03:40:32 2014
Subject: No subject
Message-ID: <mailman.39.1416886832.14847.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Tue Nov 25 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Tue Nov 25 03:40:33 2014
Subject: No subject
Message-ID: <mailman.40.1416886833.14847.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Tue Nov 25 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Tue Nov 25 03:40:37 2014
Subject: No subject
Message-ID: <mailman.41.1416886837.14847.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Tue Nov 25 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Tue Nov 25 03:40:37 2014

Subject: No subject
Message-ID: <mailman.42.1416886837.14847.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Tue Nov 25 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Tue Nov 25 03:40:38 2014
Subject: No subject
Message-ID: <mailman.43.1416886838.14847.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Tue Nov 25 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Tue Nov 25 03:40:39 2014
Subject: No subject
Message-ID: <mailman.44.1416886839.14847.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Tue Nov 25 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Tue Nov 25 03:40:39 2014
Subject: No subject
Message-ID: <mailman.45.1416886839.14847.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Tue Nov 25 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Tue Nov 25 03:40:41 2014
Subject: No subject
Message-ID: <mailman.46.1416886841.14847.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Tue Nov 25 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Tue Nov 25 03:40:41 2014
Subject: No subject
Message-ID: <mailman.47.1416886841.14847.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Tue Nov 25 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Tue Nov 25 03:40:49 2014
Subject: No subject
Message-ID: <mailman.48.1416886849.14847.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Tue Nov 25 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Tue Nov 25 03:40:56 2014
Subject: No subject
Message-ID: <mailman.49.1416886856.14847.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Tue Nov 25 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Tue Nov 25 03:40:58 2014
Subject: No subject
Message-ID: <mailman.50.1416886858.14847.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Tue Nov 25 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Tue Nov 25 03:41:01 2014
Subject: No subject
Message-ID: <mailman.51.1416886861.14847.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Tue Nov 25 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Tue Nov 25 03:41:04 2014

Subject: No subject
Message-ID: <mailman.52.1416886864.14847.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Tue Nov 25 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Tue Nov 25 03:41:07 2014
Subject: No subject
Message-ID: <mailman.53.1416886867.14847.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Tue Nov 25 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Tue Nov 25 03:41:09 2014
Subject: No subject
Message-ID: <mailman.54.1416886869.14847.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Tue Nov 25 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Tue Nov 25 03:41:12 2014
Subject: No subject
Message-ID: <mailman.55.1416886872.14847.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Tue Nov 25 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Tue Nov 25 03:41:15 2014
Subject: No subject
Message-ID: <mailman.56.1416886875.14847.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Tue Nov 25 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Tue Nov 25 03:41:17 2014
Subject: No subject
Message-ID: <mailman.57.1416886877.14847.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Tue Nov 25 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Tue Nov 25 03:41:20 2014
Subject: No subject
Message-ID: <mailman.58.1416886880.14847.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Tue Nov 25 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Tue Nov 25 03:41:22 2014
Subject: No subject
Message-ID: <mailman.59.1416886882.14847.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Tue Nov 25 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Tue Nov 25 03:41:23 2014
Subject: No subject
Message-ID: <mailman.60.1416886883.14847.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Tue Nov 25 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Tue Nov 25 03:41:24 2014
Subject: No subject
Message-ID: <mailman.61.1416886884.14847.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Tue Nov 25 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Tue Nov 25 03:41:25 2014

Subject: No subject
Message-ID: <mailman.62.1416886885.14847.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Tue Nov 25 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Tue Nov 25 03:41:25 2014
Subject: No subject
Message-ID: <mailman.63.1416886885.14847.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Tue Nov 25 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Tue Nov 25 03:41:25 2014
Subject: No subject
Message-ID: <mailman.64.1416886885.14847.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Tue Nov 25 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Tue Nov 25 03:41:26 2014
Subject: No subject
Message-ID: <mailman.65.1416886886.14847.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Tue Nov 25 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Tue Nov 25 03:41:27 2014
Subject: No subject
Message-ID: <mailman.66.1416886887.14847.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Tue Nov 25 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Tue Nov 25 03:41:27 2014
Subject: No subject
Message-ID: <mailman.67.1416886887.14847.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Tue Nov 25 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Tue Nov 25 03:41:28 2014
Subject: No subject
Message-ID: <mailman.68.1416886888.14847.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Tue Nov 25 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Tue Nov 25 03:41:28 2014
Subject: No subject
Message-ID: <mailman.69.1416886888.14847.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Tue Nov 25 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Tue Nov 25 03:41:31 2014
Subject: No subject
Message-ID: <mailman.70.1416886891.14847.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Tue Nov 25 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Tue Nov 25 03:41:31 2014
Subject: No subject
Message-ID: <mailman.71.1416886891.14847.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Tue Nov 25 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Tue Nov 25 03:41:32 2014

Subject: No subject
Message-ID: <mailman.72.1416886892.14847.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Tue Nov 25 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Tue Nov 25 03:41:32 2014
Subject: No subject
Message-ID: <mailman.73.1416886892.14847.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Tue Nov 25 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Tue Nov 25 03:41:33 2014
Subject: No subject
Message-ID: <mailman.74.1416886893.14847.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Tue Nov 25 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Tue Nov 25 03:41:33 2014
Subject: No subject
Message-ID: <mailman.75.1416886893.14847.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Tue Nov 25 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Tue Nov 25 03:41:34 2014
Subject: No subject
Message-ID: <mailman.76.1416886894.14847.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Tue Nov 25 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Tue Nov 25 03:41:35 2014
Subject: No subject
Message-ID: <mailman.77.1416886895.14847.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Tue Nov 25 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Tue Nov 25 03:41:35 2014
Subject: No subject
Message-ID: <mailman.78.1416886895.14847.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Tue Nov 25 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Tue Nov 25 03:41:36 2014
Subject: No subject
Message-ID: <mailman.79.1416886896.14847.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Tue Nov 25 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Tue Nov 25 03:41:36 2014
Subject: No subject
Message-ID: <mailman.80.1416886896.14847.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Tue Nov 25 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Tue Nov 25 03:41:37 2014
Subject: No subject
Message-ID: <mailman.81.1416886897.14847.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Tue Nov 25 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Tue Nov 25 03:41:37 2014

Subject: No subject
Message-ID: <mailman.82.1416886897.14847.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Tue Nov 25 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Tue Nov 25 03:41:38 2014
Subject: No subject
Message-ID: <mailman.83.1416886898.14847.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Tue Nov 25 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Tue Nov 25 03:41:39 2014
Subject: No subject
Message-ID: <mailman.84.1416886899.14847.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Tue Nov 25 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Tue Nov 25 03:41:40 2014
Subject: No subject
Message-ID: <mailman.85.1416886900.14847.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Tue Nov 25 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Tue Nov 25 03:41:42 2014
Subject: No subject
Message-ID: <mailman.86.1416886902.14847.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Tue Nov 25 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Tue Nov 25 03:41:42 2014
Subject: No subject
Message-ID: <mailman.87.1416886902.14847.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Tue Nov 25 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Tue Nov 25 03:41:43 2014
Subject: No subject
Message-ID: <mailman.88.1416886903.14847.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Tue Nov 25 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Tue Nov 25 03:41:44 2014
Subject: No subject
Message-ID: <mailman.89.1416886904.14847.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Tue Nov 25 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Tue Nov 25 03:41:45 2014
Subject: No subject
Message-ID: <mailman.91.1416886905.14847.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Tue Nov 25 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Tue Nov 25 03:41:46 2014
Subject: No subject
Message-ID: <mailman.92.1416886906.14847.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Tue Nov 25 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Tue Nov 25 03:41:47 2014

Subject: No subject
Message-ID: <mailman.93.1416886907.14847.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Tue Nov 25 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Tue Nov 25 03:41:49 2014
Subject: No subject
Message-ID: <mailman.94.1416886909.14847.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Tue Nov 25 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Tue Nov 25 03:41:50 2014
Subject: No subject
Message-ID: <mailman.95.1416886910.14847.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Tue Nov 25 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Tue Nov 25 03:41:51 2014
Subject: No subject
Message-ID: <mailman.96.1416886910.14847.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Tue Nov 25 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Tue Nov 25 03:41:52 2014
Subject: No subject
Message-ID: <mailman.97.1416886912.14847.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Tue Nov 25 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Tue Nov 25 03:41:54 2014
Subject: No subject
Message-ID: <mailman.98.1416886914.14847.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Tue Nov 25 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Tue Nov 25 03:41:55 2014
Subject: No subject
Message-ID: <mailman.99.1416886915.14847.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Tue Nov 25 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Tue Nov 25 03:41:56 2014
Subject: No subject
Message-ID: <mailman.100.1416886916.14847.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Tue Nov 25 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Tue Nov 25 03:41:57 2014
Subject: No subject
Message-ID: <mailman.101.1416886917.14847.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Tue Nov 25 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Tue Nov 25 03:41:58 2014
Subject: No subject
Message-ID: <mailman.102.1416886918.14847.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Tue Nov 25 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Tue Nov 25 03:41:59 2014

Subject: No subject
Message-ID: <mailman.103.1416886919.14847.htk-users@eng.cam.ac.uk>
From tonyr at cantabResearch.com Tue Nov 4 20:04:46 2014
From: tonyr at cantabResearch.com (Tony Robinson)
Date: Tue Nov 25 04:05:54 2014
Subject: [HTK-Users] HTK license agreement
In-Reply-To: <545241EC02000049000E3077@pta-emo.csir.co.za>
References: <545241EC02000049000E3077@pta-emo.csir.co.za>
Message-ID: <5459315E.9030409@cantabResearch.com>
I just saw this post - I hope I haven't also missed any replies.
It's been a while since I read the HTK licence, but from memory and past
commercial practices I believe that what you are proposing is entirely
acceptable according to the HTK licence.
In fact I think www.speechmatics.com uses HVite in exactly this way to
do some final tidying up of the large vocabulary speech recognition output.
Tony
On 30/10/14 11:49, Georg Schlunz wrote:
> Good day
>
> Regarding the HTK license, as specified at http://htk.eng.cam.ac.uk/docs/licen
se.shtml , I would like to know whether the following scenario is permitted:
>
> The HTK software (including HVite) sits on a server in-house in our organisati
on, as per license sections 2.1 and 2.3.
> The HTK software (including HVite) is never distributed to a commercial (or no
n-commercial) party, as per license section 2.2.
>
> We have written our own server-client software, where:
> a) the client records speech and sends the audio file to the server, which pas
ses it on to HVite (the server software and HTK sit on the same in-house machine
)
> b) HVite decodes the audio into text
> c) the server replies to the client with the decoded text and the client proce
sses the text somehow
>
> Naturally, the client software contains no HTK code; it only processes data pr
oduced by HTK.
>
> Therefore, may this client software and decoding SERVICE be sold commercially
(as long as we agree to license sections 2.4 and 2.5)?
>
> Thank you
> Georg Schlunz
>
-- ** Cantab is hiring: www.cantabResearch.com/openings ** -Dr A J Robinson, Founder, Cantab Research Ltd
Phone direct: 01223 778240 office: 01223 794497
Company reg no GB 05697423, VAT reg no 925606030
51 Canterbury Street, Cambridge, CB4 3QG, UK
From bogus@does.not.exist.com Wed Nov 26 02:50:34 2014
From: bogus@does.not.exist.com ()

Date: Wed Nov 26 04:04:58 2014


Subject: No subject
Message-ID: <mailman.1.1416974698.11218.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 26 02:50:34 2014
From: bogus@does.not.exist.com ()
Date: Wed Nov 26 04:05:01 2014
Subject: No subject
Message-ID: <mailman.2.1416974701.11218.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 26 02:50:34 2014
From: bogus@does.not.exist.com ()
Date: Wed Nov 26 04:05:02 2014
Subject: No subject
Message-ID: <mailman.3.1416974702.11218.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 26 02:50:34 2014
From: bogus@does.not.exist.com ()
Date: Wed Nov 26 04:05:03 2014
Subject: No subject
Message-ID: <mailman.4.1416974703.11218.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 26 02:50:34 2014
From: bogus@does.not.exist.com ()
Date: Wed Nov 26 04:05:04 2014
Subject: No subject
Message-ID: <mailman.5.1416974704.11218.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 26 02:50:34 2014
From: bogus@does.not.exist.com ()
Date: Wed Nov 26 04:05:04 2014
Subject: No subject
Message-ID: <mailman.6.1416974704.11218.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 26 02:50:34 2014
From: bogus@does.not.exist.com ()
Date: Wed Nov 26 04:05:08 2014
Subject: No subject
Message-ID: <mailman.7.1416974708.11218.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 26 02:50:34 2014
From: bogus@does.not.exist.com ()
Date: Wed Nov 26 04:05:10 2014
Subject: No subject
Message-ID: <mailman.8.1416974710.11218.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 26 02:50:34 2014
From: bogus@does.not.exist.com ()
Date: Wed Nov 26 04:05:14 2014
Subject: No subject
Message-ID: <mailman.9.1416974714.11218.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 26 02:50:34 2014
From: bogus@does.not.exist.com ()
Date: Wed Nov 26 04:05:20 2014
Subject: No subject
Message-ID: <mailman.10.1416974720.11218.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 26 02:50:34 2014
From: bogus@does.not.exist.com ()

Date: Wed Nov 26 04:05:23 2014


Subject: No subject
Message-ID: <mailman.11.1416974723.11218.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 26 02:50:34 2014
From: bogus@does.not.exist.com ()
Date: Wed Nov 26 04:05:30 2014
Subject: No subject
Message-ID: <mailman.12.1416974730.11218.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 26 02:50:34 2014
From: bogus@does.not.exist.com ()
Date: Wed Nov 26 04:05:33 2014
Subject: No subject
Message-ID: <mailman.13.1416974733.11218.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 26 02:50:34 2014
From: bogus@does.not.exist.com ()
Date: Wed Nov 26 04:05:34 2014
Subject: No subject
Message-ID: <mailman.14.1416974734.11218.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 26 02:50:34 2014
From: bogus@does.not.exist.com ()
Date: Wed Nov 26 04:05:35 2014
Subject: No subject
Message-ID: <mailman.15.1416974735.11218.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 26 02:50:34 2014
From: bogus@does.not.exist.com ()
Date: Wed Nov 26 04:05:36 2014
Subject: No subject
Message-ID: <mailman.16.1416974736.11218.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 26 02:50:34 2014
From: bogus@does.not.exist.com ()
Date: Wed Nov 26 04:05:38 2014
Subject: No subject
Message-ID: <mailman.17.1416974738.11218.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 26 02:50:34 2014
From: bogus@does.not.exist.com ()
Date: Wed Nov 26 04:05:39 2014
Subject: No subject
Message-ID: <mailman.18.1416974739.11218.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 26 02:50:34 2014
From: bogus@does.not.exist.com ()
Date: Wed Nov 26 04:05:43 2014
Subject: No subject
Message-ID: <mailman.19.1416974743.11218.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 26 02:50:34 2014
From: bogus@does.not.exist.com ()
Date: Wed Nov 26 04:05:43 2014
Subject: No subject
Message-ID: <mailman.20.1416974743.11218.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 26 02:50:34 2014
From: bogus@does.not.exist.com ()

Date: Wed Nov 26 04:05:46 2014


Subject: No subject
Message-ID: <mailman.21.1416974746.11218.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 26 02:50:34 2014
From: bogus@does.not.exist.com ()
Date: Wed Nov 26 04:05:49 2014
Subject: No subject
Message-ID: <mailman.22.1416974749.11218.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 26 02:50:34 2014
From: bogus@does.not.exist.com ()
Date: Wed Nov 26 04:05:49 2014
Subject: No subject
Message-ID: <mailman.23.1416974749.11218.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 26 02:50:34 2014
From: bogus@does.not.exist.com ()
Date: Wed Nov 26 04:05:51 2014
Subject: No subject
Message-ID: <mailman.24.1416974751.11218.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 26 02:50:34 2014
From: bogus@does.not.exist.com ()
Date: Wed Nov 26 04:06:02 2014
Subject: No subject
Message-ID: <mailman.25.1416974762.11218.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 26 02:50:34 2014
From: bogus@does.not.exist.com ()
Date: Wed Nov 26 04:06:05 2014
Subject: No subject
Message-ID: <mailman.26.1416974765.11218.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 26 02:50:34 2014
From: bogus@does.not.exist.com ()
Date: Wed Nov 26 04:06:07 2014
Subject: No subject
Message-ID: <mailman.27.1416974767.11218.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 26 02:50:34 2014
From: bogus@does.not.exist.com ()
Date: Wed Nov 26 04:06:10 2014
Subject: No subject
Message-ID: <mailman.28.1416974770.11218.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 26 02:50:34 2014
From: bogus@does.not.exist.com ()
Date: Wed Nov 26 04:06:13 2014
Subject: No subject
Message-ID: <mailman.29.1416974773.11218.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 26 02:50:34 2014
From: bogus@does.not.exist.com ()
Date: Wed Nov 26 04:06:20 2014
Subject: No subject
Message-ID: <mailman.30.1416974780.11218.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 26 02:50:34 2014
From: bogus@does.not.exist.com ()

Date: Wed Nov 26 04:06:22 2014


Subject: No subject
Message-ID: <mailman.31.1416974782.11218.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 26 02:50:34 2014
From: bogus@does.not.exist.com ()
Date: Wed Nov 26 04:06:27 2014
Subject: No subject
Message-ID: <mailman.32.1416974787.11218.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 26 02:50:34 2014
From: bogus@does.not.exist.com ()
Date: Wed Nov 26 04:06:30 2014
Subject: No subject
Message-ID: <mailman.33.1416974790.11218.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 26 02:50:34 2014
From: bogus@does.not.exist.com ()
Date: Wed Nov 26 04:06:36 2014
Subject: No subject
Message-ID: <mailman.34.1416974796.11218.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 26 02:50:34 2014
From: bogus@does.not.exist.com ()
Date: Wed Nov 26 04:06:39 2014
Subject: No subject
Message-ID: <mailman.35.1416974799.11218.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 26 02:50:34 2014
From: bogus@does.not.exist.com ()
Date: Wed Nov 26 04:06:42 2014
Subject: No subject
Message-ID: <mailman.36.1416974802.11218.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 26 02:50:34 2014
From: bogus@does.not.exist.com ()
Date: Wed Nov 26 04:06:46 2014
Subject: No subject
Message-ID: <mailman.37.1416974806.11218.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 26 02:50:34 2014
From: bogus@does.not.exist.com ()
Date: Wed Nov 26 04:06:48 2014
Subject: No subject
Message-ID: <mailman.38.1416974808.11218.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 26 02:50:34 2014
From: bogus@does.not.exist.com ()
Date: Wed Nov 26 04:06:52 2014
Subject: No subject
Message-ID: <mailman.39.1416974812.11218.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 26 02:50:34 2014
From: bogus@does.not.exist.com ()
Date: Wed Nov 26 04:06:53 2014
Subject: No subject
Message-ID: <mailman.40.1416974813.11218.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 26 02:50:34 2014
From: bogus@does.not.exist.com ()

Date: Wed Nov 26 04:07:01 2014


Subject: No subject
Message-ID: <mailman.41.1416974821.11218.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 26 02:50:34 2014
From: bogus@does.not.exist.com ()
Date: Wed Nov 26 04:07:02 2014
Subject: No subject
Message-ID: <mailman.42.1416974822.11218.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 26 02:50:34 2014
From: bogus@does.not.exist.com ()
Date: Wed Nov 26 04:07:02 2014
Subject: No subject
Message-ID: <mailman.43.1416974822.11218.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 26 02:50:34 2014
From: bogus@does.not.exist.com ()
Date: Wed Nov 26 04:07:03 2014
Subject: No subject
Message-ID: <mailman.44.1416974823.11218.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 26 02:50:34 2014
From: bogus@does.not.exist.com ()
Date: Wed Nov 26 04:07:04 2014
Subject: No subject
Message-ID: <mailman.45.1416974824.11218.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 26 02:50:34 2014
From: bogus@does.not.exist.com ()
Date: Wed Nov 26 04:07:05 2014
Subject: No subject
Message-ID: <mailman.46.1416974825.11218.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 26 02:50:34 2014
From: bogus@does.not.exist.com ()
Date: Wed Nov 26 04:07:05 2014
Subject: No subject
Message-ID: <mailman.47.1416974825.11218.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 26 02:50:34 2014
From: bogus@does.not.exist.com ()
Date: Wed Nov 26 04:07:06 2014
Subject: No subject
Message-ID: <mailman.48.1416974826.11218.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 26 02:50:34 2014
From: bogus@does.not.exist.com ()
Date: Wed Nov 26 04:07:08 2014
Subject: No subject
Message-ID: <mailman.49.1416974828.11218.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 26 02:50:34 2014
From: bogus@does.not.exist.com ()
Date: Wed Nov 26 04:07:09 2014
Subject: No subject
Message-ID: <mailman.50.1416974829.11218.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 26 02:50:34 2014
From: bogus@does.not.exist.com ()

Date: Wed Nov 26 04:07:10 2014


Subject: No subject
Message-ID: <mailman.51.1416974830.11218.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 26 02:50:34 2014
From: bogus@does.not.exist.com ()
Date: Wed Nov 26 04:07:10 2014
Subject: No subject
Message-ID: <mailman.52.1416974830.11218.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 26 02:50:34 2014
From: bogus@does.not.exist.com ()
Date: Wed Nov 26 04:07:11 2014
Subject: No subject
Message-ID: <mailman.53.1416974831.11218.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 26 02:50:34 2014
From: bogus@does.not.exist.com ()
Date: Wed Nov 26 04:07:11 2014
Subject: No subject
Message-ID: <mailman.54.1416974831.11218.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 26 02:50:34 2014
From: bogus@does.not.exist.com ()
Date: Wed Nov 26 04:07:12 2014
Subject: No subject
Message-ID: <mailman.55.1416974832.11218.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 26 02:50:34 2014
From: bogus@does.not.exist.com ()
Date: Wed Nov 26 04:07:12 2014
Subject: No subject
Message-ID: <mailman.56.1416974832.11218.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 26 02:50:34 2014
From: bogus@does.not.exist.com ()
Date: Wed Nov 26 04:07:13 2014
Subject: No subject
Message-ID: <mailman.57.1416974833.11218.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 26 02:50:34 2014
From: bogus@does.not.exist.com ()
Date: Wed Nov 26 04:07:13 2014
Subject: No subject
Message-ID: <mailman.58.1416974833.11218.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 26 02:50:34 2014
From: bogus@does.not.exist.com ()
Date: Wed Nov 26 04:07:14 2014
Subject: No subject
Message-ID: <mailman.59.1416974834.11218.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 26 02:50:34 2014
From: bogus@does.not.exist.com ()
Date: Wed Nov 26 04:07:15 2014
Subject: No subject
Message-ID: <mailman.60.1416974835.11218.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 26 02:50:34 2014
From: bogus@does.not.exist.com ()

Date: Wed Nov 26 04:07:15 2014


Subject: No subject
Message-ID: <mailman.61.1416974835.11218.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 26 02:50:34 2014
From: bogus@does.not.exist.com ()
Date: Wed Nov 26 04:07:16 2014
Subject: No subject
Message-ID: <mailman.62.1416974836.11218.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 26 02:50:34 2014
From: bogus@does.not.exist.com ()
Date: Wed Nov 26 04:07:17 2014
Subject: No subject
Message-ID: <mailman.63.1416974837.11218.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 26 02:50:34 2014
From: bogus@does.not.exist.com ()
Date: Wed Nov 26 04:07:17 2014
Subject: No subject
Message-ID: <mailman.64.1416974837.11218.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 26 02:50:34 2014
From: bogus@does.not.exist.com ()
Date: Wed Nov 26 04:07:18 2014
Subject: No subject
Message-ID: <mailman.65.1416974838.11218.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 26 02:50:34 2014
From: bogus@does.not.exist.com ()
Date: Wed Nov 26 04:07:18 2014
Subject: No subject
Message-ID: <mailman.66.1416974838.11218.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 26 02:50:34 2014
From: bogus@does.not.exist.com ()
Date: Wed Nov 26 04:07:19 2014
Subject: No subject
Message-ID: <mailman.67.1416974839.11218.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 26 02:50:34 2014
From: bogus@does.not.exist.com ()
Date: Wed Nov 26 04:07:19 2014
Subject: No subject
Message-ID: <mailman.68.1416974839.11218.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 26 02:50:34 2014
From: bogus@does.not.exist.com ()
Date: Wed Nov 26 04:07:20 2014
Subject: No subject
Message-ID: <mailman.69.1416974840.11218.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 26 02:50:34 2014
From: bogus@does.not.exist.com ()
Date: Wed Nov 26 04:07:23 2014
Subject: No subject
Message-ID: <mailman.70.1416974843.11218.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 26 02:50:34 2014
From: bogus@does.not.exist.com ()

Date: Wed Nov 26 04:07:23 2014


Subject: No subject
Message-ID: <mailman.71.1416974843.11218.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 26 02:50:34 2014
From: bogus@does.not.exist.com ()
Date: Wed Nov 26 04:07:24 2014
Subject: No subject
Message-ID: <mailman.72.1416974844.11218.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 26 02:50:34 2014
From: bogus@does.not.exist.com ()
Date: Wed Nov 26 04:07:24 2014
Subject: No subject
Message-ID: <mailman.73.1416974844.11218.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 26 02:50:34 2014
From: bogus@does.not.exist.com ()
Date: Wed Nov 26 04:07:25 2014
Subject: No subject
Message-ID: <mailman.74.1416974845.11218.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 26 02:50:34 2014
From: bogus@does.not.exist.com ()
Date: Wed Nov 26 04:07:25 2014
Subject: No subject
Message-ID: <mailman.75.1416974845.11218.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 26 02:50:34 2014
From: bogus@does.not.exist.com ()
Date: Wed Nov 26 04:07:26 2014
Subject: No subject
Message-ID: <mailman.76.1416974846.11218.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 26 02:50:34 2014
From: bogus@does.not.exist.com ()
Date: Wed Nov 26 04:07:26 2014
Subject: No subject
Message-ID: <mailman.77.1416974846.11218.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 26 02:50:34 2014
From: bogus@does.not.exist.com ()
Date: Wed Nov 26 04:07:27 2014
Subject: No subject
Message-ID: <mailman.78.1416974847.11218.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 26 02:50:34 2014
From: bogus@does.not.exist.com ()
Date: Wed Nov 26 04:07:28 2014
Subject: No subject
Message-ID: <mailman.79.1416974848.11218.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 26 02:50:34 2014
From: bogus@does.not.exist.com ()
Date: Wed Nov 26 04:07:28 2014
Subject: No subject
Message-ID: <mailman.80.1416974848.11218.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 26 02:50:34 2014
From: bogus@does.not.exist.com ()

Date: Wed Nov 26 04:07:29 2014


Subject: No subject
Message-ID: <mailman.81.1416974849.11218.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 26 02:50:34 2014
From: bogus@does.not.exist.com ()
Date: Wed Nov 26 04:07:29 2014
Subject: No subject
Message-ID: <mailman.82.1416974849.11218.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 26 02:50:34 2014
From: bogus@does.not.exist.com ()
Date: Wed Nov 26 04:07:30 2014
Subject: No subject
Message-ID: <mailman.83.1416974850.11218.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 26 02:50:34 2014
From: bogus@does.not.exist.com ()
Date: Wed Nov 26 04:07:33 2014
Subject: No subject
Message-ID: <mailman.84.1416974853.11218.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 26 02:50:34 2014
From: bogus@does.not.exist.com ()
Date: Wed Nov 26 04:07:34 2014
Subject: No subject
Message-ID: <mailman.85.1416974854.11218.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 26 02:50:34 2014
From: bogus@does.not.exist.com ()
Date: Wed Nov 26 04:07:36 2014
Subject: No subject
Message-ID: <mailman.86.1416974856.11218.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 26 02:50:34 2014
From: bogus@does.not.exist.com ()
Date: Wed Nov 26 04:07:37 2014
Subject: No subject
Message-ID: <mailman.87.1416974857.11218.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 26 02:50:34 2014
From: bogus@does.not.exist.com ()
Date: Wed Nov 26 04:07:38 2014
Subject: No subject
Message-ID: <mailman.88.1416974858.11218.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 26 02:50:34 2014
From: bogus@does.not.exist.com ()
Date: Wed Nov 26 04:07:39 2014
Subject: No subject
Message-ID: <mailman.89.1416974859.11218.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 26 02:50:34 2014
From: bogus@does.not.exist.com ()
Date: Wed Nov 26 04:07:41 2014
Subject: No subject
Message-ID: <mailman.91.1416974861.11218.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 26 02:50:34 2014
From: bogus@does.not.exist.com ()

Date: Wed Nov 26 04:07:42 2014


Subject: No subject
Message-ID: <mailman.92.1416974862.11218.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 26 02:50:34 2014
From: bogus@does.not.exist.com ()
Date: Wed Nov 26 04:07:43 2014
Subject: No subject
Message-ID: <mailman.93.1416974863.11218.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 26 02:50:34 2014
From: bogus@does.not.exist.com ()
Date: Wed Nov 26 04:07:45 2014
Subject: No subject
Message-ID: <mailman.94.1416974865.11218.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 26 02:50:34 2014
From: bogus@does.not.exist.com ()
Date: Wed Nov 26 04:07:46 2014
Subject: No subject
Message-ID: <mailman.95.1416974866.11218.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 26 02:50:34 2014
From: bogus@does.not.exist.com ()
Date: Wed Nov 26 04:07:47 2014
Subject: No subject
Message-ID: <mailman.96.1416974867.11218.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 26 02:50:34 2014
From: bogus@does.not.exist.com ()
Date: Wed Nov 26 04:07:49 2014
Subject: No subject
Message-ID: <mailman.97.1416974869.11218.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 26 02:50:34 2014
From: bogus@does.not.exist.com ()
Date: Wed Nov 26 04:07:50 2014
Subject: No subject
Message-ID: <mailman.98.1416974870.11218.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 26 02:50:34 2014
From: bogus@does.not.exist.com ()
Date: Wed Nov 26 04:07:53 2014
Subject: No subject
Message-ID: <mailman.99.1416974873.11218.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 26 02:50:34 2014
From: bogus@does.not.exist.com ()
Date: Wed Nov 26 04:07:54 2014
Subject: No subject
Message-ID: <mailman.100.1416974874.11218.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 26 02:50:34 2014
From: bogus@does.not.exist.com ()
Date: Wed Nov 26 04:07:55 2014
Subject: No subject
Message-ID: <mailman.101.1416974875.11218.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 26 02:50:34 2014
From: bogus@does.not.exist.com ()

Date: Wed Nov 26 04:07:56 2014


Subject: No subject
Message-ID: <mailman.102.1416974876.11218.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 26 02:50:34 2014
From: bogus@does.not.exist.com ()
Date: Wed Nov 26 04:07:57 2014
Subject: No subject
Message-ID: <mailman.103.1416974877.11218.htk-users@eng.cam.ac.uk>
From tonyr at cantabResearch.com Tue Nov 4 20:04:46 2014
From: tonyr at cantabResearch.com (Tony Robinson)
Date: Wed Nov 26 04:25:35 2014
Subject: [HTK-Users] HTK license agreement
In-Reply-To: <545241EC02000049000E3077@pta-emo.csir.co.za>
References: <545241EC02000049000E3077@pta-emo.csir.co.za>
Message-ID: <5459315E.9030409@cantabResearch.com>
I just saw this post - I hope I haven't also missed any replies.
It's been a while since I read the HTK licence, but from memory and past
commercial practices I believe that what you are proposing is entirely
acceptable according to the HTK licence.
In fact I think www.speechmatics.com uses HVite in exactly this way to
do some final tidying up of the large vocabulary speech recognition output.
Tony
On 30/10/14 11:49, Georg Schlunz wrote:
> Good day
>
> Regarding the HTK license, as specified at http://htk.eng.cam.ac.uk/docs/licen
se.shtml , I would like to know whether the following scenario is permitted:
>
> The HTK software (including HVite) sits on a server in-house in our organisati
on, as per license sections 2.1 and 2.3.
> The HTK software (including HVite) is never distributed to a commercial (or no
n-commercial) party, as per license section 2.2.
>
> We have written our own server-client software, where:
> a) the client records speech and sends the audio file to the server, which pas
ses it on to HVite (the server software and HTK sit on the same in-house machine
)
> b) HVite decodes the audio into text
> c) the server replies to the client with the decoded text and the client proce
sses the text somehow
>
> Naturally, the client software contains no HTK code; it only processes data pr
oduced by HTK.
>
> Therefore, may this client software and decoding SERVICE be sold commercially
(as long as we agree to license sections 2.4 and 2.5)?
>
> Thank you
> Georg Schlunz
>
-- ** Cantab is hiring: www.cantabResearch.com/openings ** --

Dr A J Robinson, Founder, Cantab Research Ltd


Phone direct: 01223 778240 office: 01223 794497
Company reg no GB 05697423, VAT reg no 925606030
51 Canterbury Street, Cambridge, CB4 3QG, UK
From bogus@does.not.exist.com Thu Nov 27 02:50:44 2014
From: bogus@does.not.exist.com ()
Date: Thu Nov 27 04:14:30 2014
Subject: No subject
Message-ID: <mailman.1.1417061670.3593.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 27 02:50:44 2014
From: bogus@does.not.exist.com ()
Date: Thu Nov 27 04:14:37 2014
Subject: No subject
Message-ID: <mailman.2.1417061677.3593.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 27 02:50:44 2014
From: bogus@does.not.exist.com ()
Date: Thu Nov 27 04:14:38 2014
Subject: No subject
Message-ID: <mailman.3.1417061678.3593.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 27 02:50:44 2014
From: bogus@does.not.exist.com ()
Date: Thu Nov 27 04:14:39 2014
Subject: No subject
Message-ID: <mailman.4.1417061679.3593.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 27 02:50:44 2014
From: bogus@does.not.exist.com ()
Date: Thu Nov 27 04:14:40 2014
Subject: No subject
Message-ID: <mailman.5.1417061680.3593.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 27 02:50:44 2014
From: bogus@does.not.exist.com ()
Date: Thu Nov 27 04:14:41 2014
Subject: No subject
Message-ID: <mailman.6.1417061681.3593.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 27 02:50:44 2014
From: bogus@does.not.exist.com ()
Date: Thu Nov 27 04:14:42 2014
Subject: No subject
Message-ID: <mailman.7.1417061682.3593.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 27 02:50:44 2014
From: bogus@does.not.exist.com ()
Date: Thu Nov 27 04:14:42 2014
Subject: No subject
Message-ID: <mailman.8.1417061682.3593.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 27 02:50:44 2014
From: bogus@does.not.exist.com ()
Date: Thu Nov 27 04:14:43 2014
Subject: No subject
Message-ID: <mailman.9.1417061683.3593.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 27 02:50:44 2014

From: bogus@does.not.exist.com ()
Date: Thu Nov 27 04:14:45 2014
Subject: No subject
Message-ID: <mailman.10.1417061685.3593.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 27 02:50:44 2014
From: bogus@does.not.exist.com ()
Date: Thu Nov 27 04:14:46 2014
Subject: No subject
Message-ID: <mailman.11.1417061686.3593.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 27 02:50:44 2014
From: bogus@does.not.exist.com ()
Date: Thu Nov 27 04:14:49 2014
Subject: No subject
Message-ID: <mailman.12.1417061689.3593.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 27 02:50:44 2014
From: bogus@does.not.exist.com ()
Date: Thu Nov 27 04:14:49 2014
Subject: No subject
Message-ID: <mailman.13.1417061689.3593.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 27 02:50:44 2014
From: bogus@does.not.exist.com ()
Date: Thu Nov 27 04:14:50 2014
Subject: No subject
Message-ID: <mailman.14.1417061690.3593.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 27 02:50:44 2014
From: bogus@does.not.exist.com ()
Date: Thu Nov 27 04:14:50 2014
Subject: No subject
Message-ID: <mailman.15.1417061690.3593.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 27 02:50:44 2014
From: bogus@does.not.exist.com ()
Date: Thu Nov 27 04:14:51 2014
Subject: No subject
Message-ID: <mailman.16.1417061691.3593.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 27 02:50:44 2014
From: bogus@does.not.exist.com ()
Date: Thu Nov 27 04:14:51 2014
Subject: No subject
Message-ID: <mailman.17.1417061691.3593.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 27 02:50:44 2014
From: bogus@does.not.exist.com ()
Date: Thu Nov 27 04:14:52 2014
Subject: No subject
Message-ID: <mailman.18.1417061692.3593.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 27 02:50:44 2014
From: bogus@does.not.exist.com ()
Date: Thu Nov 27 04:14:56 2014
Subject: No subject
Message-ID: <mailman.19.1417061695.3593.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 27 02:50:44 2014

From: bogus@does.not.exist.com ()
Date: Thu Nov 27 04:14:56 2014
Subject: No subject
Message-ID: <mailman.20.1417061696.3593.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 27 02:50:44 2014
From: bogus@does.not.exist.com ()
Date: Thu Nov 27 04:14:59 2014
Subject: No subject
Message-ID: <mailman.21.1417061699.3593.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 27 02:50:44 2014
From: bogus@does.not.exist.com ()
Date: Thu Nov 27 04:15:01 2014
Subject: No subject
Message-ID: <mailman.22.1417061701.3593.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 27 02:50:44 2014
From: bogus@does.not.exist.com ()
Date: Thu Nov 27 04:15:03 2014
Subject: No subject
Message-ID: <mailman.23.1417061703.3593.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 27 02:50:44 2014
From: bogus@does.not.exist.com ()
Date: Thu Nov 27 04:15:05 2014
Subject: No subject
Message-ID: <mailman.24.1417061705.3593.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 27 02:50:44 2014
From: bogus@does.not.exist.com ()
Date: Thu Nov 27 04:15:07 2014
Subject: No subject
Message-ID: <mailman.25.1417061707.3593.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 27 02:50:44 2014
From: bogus@does.not.exist.com ()
Date: Thu Nov 27 04:15:08 2014
Subject: No subject
Message-ID: <mailman.26.1417061708.3593.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 27 02:50:44 2014
From: bogus@does.not.exist.com ()
Date: Thu Nov 27 04:15:08 2014
Subject: No subject
Message-ID: <mailman.27.1417061708.3593.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 27 02:50:44 2014
From: bogus@does.not.exist.com ()
Date: Thu Nov 27 04:15:09 2014
Subject: No subject
Message-ID: <mailman.28.1417061709.3593.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 27 02:50:44 2014
From: bogus@does.not.exist.com ()
Date: Thu Nov 27 04:15:10 2014
Subject: No subject
Message-ID: <mailman.29.1417061710.3593.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 27 02:50:44 2014

From: bogus@does.not.exist.com ()
Date: Thu Nov 27 04:15:17 2014
Subject: No subject
Message-ID: <mailman.30.1417061717.3593.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 27 02:50:44 2014
From: bogus@does.not.exist.com ()
Date: Thu Nov 27 04:15:21 2014
Subject: No subject
Message-ID: <mailman.31.1417061721.3593.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 27 02:50:44 2014
From: bogus@does.not.exist.com ()
Date: Thu Nov 27 04:15:25 2014
Subject: No subject
Message-ID: <mailman.32.1417061725.3593.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 27 02:50:44 2014
From: bogus@does.not.exist.com ()
Date: Thu Nov 27 04:15:29 2014
Subject: No subject
Message-ID: <mailman.33.1417061729.3593.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 27 02:50:44 2014
From: bogus@does.not.exist.com ()
Date: Thu Nov 27 04:15:30 2014
Subject: No subject
Message-ID: <mailman.34.1417061730.3593.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 27 02:50:44 2014
From: bogus@does.not.exist.com ()
Date: Thu Nov 27 04:15:31 2014
Subject: No subject
Message-ID: <mailman.35.1417061730.3593.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 27 02:50:44 2014
From: bogus@does.not.exist.com ()
Date: Thu Nov 27 04:15:31 2014
Subject: No subject
Message-ID: <mailman.36.1417061731.3593.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 27 02:50:44 2014
From: bogus@does.not.exist.com ()
Date: Thu Nov 27 04:15:32 2014
Subject: No subject
Message-ID: <mailman.37.1417061732.3593.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 27 02:50:44 2014
From: bogus@does.not.exist.com ()
Date: Thu Nov 27 04:15:33 2014
Subject: No subject
Message-ID: <mailman.38.1417061733.3593.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 27 02:50:44 2014
From: bogus@does.not.exist.com ()
Date: Thu Nov 27 04:15:34 2014
Subject: No subject
Message-ID: <mailman.39.1417061734.3593.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 27 02:50:44 2014

From: bogus@does.not.exist.com ()
Date: Thu Nov 27 04:15:34 2014
Subject: No subject
Message-ID: <mailman.40.1417061734.3593.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 27 02:50:44 2014
From: bogus@does.not.exist.com ()
Date: Thu Nov 27 04:15:41 2014
Subject: No subject
Message-ID: <mailman.41.1417061741.3593.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 27 02:50:44 2014
From: bogus@does.not.exist.com ()
Date: Thu Nov 27 04:15:43 2014
Subject: No subject
Message-ID: <mailman.42.1417061743.3593.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 27 02:50:44 2014
From: bogus@does.not.exist.com ()
Date: Thu Nov 27 04:15:43 2014
Subject: No subject
Message-ID: <mailman.43.1417061743.3593.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 27 02:50:44 2014
From: bogus@does.not.exist.com ()
Date: Thu Nov 27 04:15:44 2014
Subject: No subject
Message-ID: <mailman.44.1417061744.3593.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 27 02:50:44 2014
From: bogus@does.not.exist.com ()
Date: Thu Nov 27 04:15:46 2014
Subject: No subject
Message-ID: <mailman.45.1417061746.3593.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 27 02:50:44 2014
From: bogus@does.not.exist.com ()
Date: Thu Nov 27 04:15:50 2014
Subject: No subject
Message-ID: <mailman.46.1417061749.3593.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 27 02:50:44 2014
From: bogus@does.not.exist.com ()
Date: Thu Nov 27 04:15:53 2014
Subject: No subject
Message-ID: <mailman.47.1417061753.3593.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 27 02:50:44 2014
From: bogus@does.not.exist.com ()
Date: Thu Nov 27 04:15:57 2014
Subject: No subject
Message-ID: <mailman.48.1417061757.3593.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 27 02:50:44 2014
From: bogus@does.not.exist.com ()
Date: Thu Nov 27 04:16:03 2014
Subject: No subject
Message-ID: <mailman.49.1417061763.3593.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 27 02:50:44 2014

From: bogus@does.not.exist.com ()
Date: Thu Nov 27 04:16:03 2014
Subject: No subject
Message-ID: <mailman.50.1417061763.3593.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 27 02:50:44 2014
From: bogus@does.not.exist.com ()
Date: Thu Nov 27 04:16:04 2014
Subject: No subject
Message-ID: <mailman.51.1417061764.3593.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 27 02:50:44 2014
From: bogus@does.not.exist.com ()
Date: Thu Nov 27 04:16:05 2014
Subject: No subject
Message-ID: <mailman.52.1417061765.3593.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 27 02:50:44 2014
From: bogus@does.not.exist.com ()
Date: Thu Nov 27 04:16:06 2014
Subject: No subject
Message-ID: <mailman.53.1417061766.3593.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 27 02:50:44 2014
From: bogus@does.not.exist.com ()
Date: Thu Nov 27 04:16:06 2014
Subject: No subject
Message-ID: <mailman.54.1417061766.3593.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 27 02:50:44 2014
From: bogus@does.not.exist.com ()
Date: Thu Nov 27 04:16:07 2014
Subject: No subject
Message-ID: <mailman.55.1417061767.3593.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 27 02:50:44 2014
From: bogus@does.not.exist.com ()
Date: Thu Nov 27 04:16:07 2014
Subject: No subject
Message-ID: <mailman.56.1417061767.3593.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 27 02:50:44 2014
From: bogus@does.not.exist.com ()
Date: Thu Nov 27 04:16:08 2014
Subject: No subject
Message-ID: <mailman.57.1417061768.3593.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 27 02:50:44 2014
From: bogus@does.not.exist.com ()
Date: Thu Nov 27 04:16:08 2014
Subject: No subject
Message-ID: <mailman.58.1417061768.3593.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 27 02:50:44 2014
From: bogus@does.not.exist.com ()
Date: Thu Nov 27 04:16:09 2014
Subject: No subject
Message-ID: <mailman.59.1417061769.3593.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 27 02:50:44 2014

From: bogus@does.not.exist.com ()
Date: Thu Nov 27 04:16:11 2014
Subject: No subject
Message-ID: <mailman.60.1417061771.3593.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 27 02:50:44 2014
From: bogus@does.not.exist.com ()
Date: Thu Nov 27 04:16:14 2014
Subject: No subject
Message-ID: <mailman.61.1417061774.3593.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 27 02:50:44 2014
From: bogus@does.not.exist.com ()
Date: Thu Nov 27 04:16:16 2014
Subject: No subject
Message-ID: <mailman.62.1417061776.3593.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 27 02:50:44 2014
From: bogus@does.not.exist.com ()
Date: Thu Nov 27 04:16:19 2014
Subject: No subject
Message-ID: <mailman.63.1417061779.3593.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 27 02:50:44 2014
From: bogus@does.not.exist.com ()
Date: Thu Nov 27 04:16:24 2014
Subject: No subject
Message-ID: <mailman.64.1417061784.3593.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 27 02:50:44 2014
From: bogus@does.not.exist.com ()
Date: Thu Nov 27 04:16:27 2014
Subject: No subject
Message-ID: <mailman.65.1417061787.3593.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 27 02:50:44 2014
From: bogus@does.not.exist.com ()
Date: Thu Nov 27 04:16:29 2014
Subject: No subject
Message-ID: <mailman.66.1417061789.3593.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 27 02:50:44 2014
From: bogus@does.not.exist.com ()
Date: Thu Nov 27 04:16:33 2014
Subject: No subject
Message-ID: <mailman.67.1417061793.3593.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 27 02:50:44 2014
From: bogus@does.not.exist.com ()
Date: Thu Nov 27 04:16:36 2014
Subject: No subject
Message-ID: <mailman.68.1417061795.3593.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 27 02:50:44 2014
From: bogus@does.not.exist.com ()
Date: Thu Nov 27 04:16:39 2014
Subject: No subject
Message-ID: <mailman.69.1417061799.3593.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 27 02:50:44 2014

From: bogus@does.not.exist.com ()
Date: Thu Nov 27 04:16:42 2014
Subject: No subject
Message-ID: <mailman.70.1417061802.3593.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 27 02:50:44 2014
From: bogus@does.not.exist.com ()
Date: Thu Nov 27 04:16:43 2014
Subject: No subject
Message-ID: <mailman.71.1417061803.3593.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 27 02:50:44 2014
From: bogus@does.not.exist.com ()
Date: Thu Nov 27 04:16:43 2014
Subject: No subject
Message-ID: <mailman.72.1417061803.3593.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 27 02:50:44 2014
From: bogus@does.not.exist.com ()
Date: Thu Nov 27 04:16:44 2014
Subject: No subject
Message-ID: <mailman.73.1417061804.3593.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 27 02:50:44 2014
From: bogus@does.not.exist.com ()
Date: Thu Nov 27 04:16:45 2014
Subject: No subject
Message-ID: <mailman.74.1417061805.3593.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 27 02:50:44 2014
From: bogus@does.not.exist.com ()
Date: Thu Nov 27 04:16:45 2014
Subject: No subject
Message-ID: <mailman.75.1417061805.3593.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 27 02:50:44 2014
From: bogus@does.not.exist.com ()
Date: Thu Nov 27 04:16:46 2014
Subject: No subject
Message-ID: <mailman.76.1417061806.3593.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 27 02:50:44 2014
From: bogus@does.not.exist.com ()
Date: Thu Nov 27 04:16:46 2014
Subject: No subject
Message-ID: <mailman.77.1417061806.3593.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 27 02:50:44 2014
From: bogus@does.not.exist.com ()
Date: Thu Nov 27 04:16:47 2014
Subject: No subject
Message-ID: <mailman.78.1417061807.3593.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 27 02:50:44 2014
From: bogus@does.not.exist.com ()
Date: Thu Nov 27 04:16:48 2014
Subject: No subject
Message-ID: <mailman.79.1417061808.3593.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 27 02:50:44 2014

From: bogus@does.not.exist.com ()
Date: Thu Nov 27 04:16:49 2014
Subject: No subject
Message-ID: <mailman.80.1417061809.3593.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 27 02:50:44 2014
From: bogus@does.not.exist.com ()
Date: Thu Nov 27 04:16:50 2014
Subject: No subject
Message-ID: <mailman.81.1417061810.3593.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 27 02:50:44 2014
From: bogus@does.not.exist.com ()
Date: Thu Nov 27 04:16:50 2014
Subject: No subject
Message-ID: <mailman.82.1417061810.3593.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 27 02:50:44 2014
From: bogus@does.not.exist.com ()
Date: Thu Nov 27 04:16:51 2014
Subject: No subject
Message-ID: <mailman.83.1417061811.3593.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 27 02:50:44 2014
From: bogus@does.not.exist.com ()
Date: Thu Nov 27 04:16:52 2014
Subject: No subject
Message-ID: <mailman.84.1417061812.3593.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 27 02:50:44 2014
From: bogus@does.not.exist.com ()
Date: Thu Nov 27 04:16:53 2014
Subject: No subject
Message-ID: <mailman.85.1417061813.3593.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 27 02:50:44 2014
From: bogus@does.not.exist.com ()
Date: Thu Nov 27 04:16:56 2014
Subject: No subject
Message-ID: <mailman.86.1417061816.3593.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 27 02:50:44 2014
From: bogus@does.not.exist.com ()
Date: Thu Nov 27 04:16:57 2014
Subject: No subject
Message-ID: <mailman.87.1417061817.3593.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 27 02:50:44 2014
From: bogus@does.not.exist.com ()
Date: Thu Nov 27 04:17:00 2014
Subject: No subject
Message-ID: <mailman.88.1417061820.3593.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 27 02:50:44 2014
From: bogus@does.not.exist.com ()
Date: Thu Nov 27 04:17:02 2014
Subject: No subject
Message-ID: <mailman.89.1417061822.3593.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 27 02:50:44 2014

From: bogus@does.not.exist.com ()
Date: Thu Nov 27 04:17:03 2014
Subject: No subject
Message-ID: <mailman.91.1417061823.3593.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 27 02:50:44 2014
From: bogus@does.not.exist.com ()
Date: Thu Nov 27 04:17:04 2014
Subject: No subject
Message-ID: <mailman.92.1417061824.3593.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 27 02:50:44 2014
From: bogus@does.not.exist.com ()
Date: Thu Nov 27 04:17:05 2014
Subject: No subject
Message-ID: <mailman.93.1417061825.3593.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 27 02:50:44 2014
From: bogus@does.not.exist.com ()
Date: Thu Nov 27 04:17:07 2014
Subject: No subject
Message-ID: <mailman.94.1417061827.3593.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 27 02:50:44 2014
From: bogus@does.not.exist.com ()
Date: Thu Nov 27 04:17:08 2014
Subject: No subject
Message-ID: <mailman.95.1417061828.3593.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 27 02:50:44 2014
From: bogus@does.not.exist.com ()
Date: Thu Nov 27 04:17:19 2014
Subject: No subject
Message-ID: <mailman.96.1417061839.3593.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 27 02:50:44 2014
From: bogus@does.not.exist.com ()
Date: Thu Nov 27 04:17:25 2014
Subject: No subject
Message-ID: <mailman.97.1417061845.3593.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 27 02:50:44 2014
From: bogus@does.not.exist.com ()
Date: Thu Nov 27 04:17:30 2014
Subject: No subject
Message-ID: <mailman.98.1417061850.3593.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 27 02:50:44 2014
From: bogus@does.not.exist.com ()
Date: Thu Nov 27 04:17:32 2014
Subject: No subject
Message-ID: <mailman.99.1417061852.3593.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 27 02:50:44 2014
From: bogus@does.not.exist.com ()
Date: Thu Nov 27 04:17:33 2014
Subject: No subject
Message-ID: <mailman.100.1417061853.3593.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 27 02:50:44 2014

From: bogus@does.not.exist.com ()
Date: Thu Nov 27 04:17:34 2014
Subject: No subject
Message-ID: <mailman.101.1417061854.3593.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 27 02:50:44 2014
From: bogus@does.not.exist.com ()
Date: Thu Nov 27 04:17:35 2014
Subject: No subject
Message-ID: <mailman.102.1417061855.3593.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 27 02:50:44 2014
From: bogus@does.not.exist.com ()
Date: Thu Nov 27 04:17:36 2014
Subject: No subject
Message-ID: <mailman.103.1417061856.3593.htk-users@eng.cam.ac.uk>
From tonyr at cantabResearch.com Tue Nov 4 20:04:46 2014
From: tonyr at cantabResearch.com (Tony Robinson)
Date: Thu Nov 27 04:37:36 2014
Subject: [HTK-Users] HTK license agreement
In-Reply-To: <545241EC02000049000E3077@pta-emo.csir.co.za>
References: <545241EC02000049000E3077@pta-emo.csir.co.za>
Message-ID: <5459315E.9030409@cantabResearch.com>
I just saw this post - I hope I haven't also missed any replies.
It's been a while since I read the HTK licence, but from memory and past
commercial practices I believe that what you are proposing is entirely
acceptable according to the HTK licence.
In fact I think www.speechmatics.com uses HVite in exactly this way to
do some final tidying up of the large vocabulary speech recognition output.
Tony
On 30/10/14 11:49, Georg Schlunz wrote:
> Good day
>
> Regarding the HTK license, as specified at http://htk.eng.cam.ac.uk/docs/licen
se.shtml , I would like to know whether the following scenario is permitted:
>
> The HTK software (including HVite) sits on a server in-house in our organisati
on, as per license sections 2.1 and 2.3.
> The HTK software (including HVite) is never distributed to a commercial (or no
n-commercial) party, as per license section 2.2.
>
> We have written our own server-client software, where:
> a) the client records speech and sends the audio file to the server, which pas
ses it on to HVite (the server software and HTK sit on the same in-house machine
)
> b) HVite decodes the audio into text
> c) the server replies to the client with the decoded text and the client proce
sses the text somehow
>
> Naturally, the client software contains no HTK code; it only processes data pr
oduced by HTK.
>
> Therefore, may this client software and decoding SERVICE be sold commercially

(as long as we agree to license sections 2.4 and 2.5)?


>
> Thank you
> Georg Schlunz
>
-- ** Cantab is hiring: www.cantabResearch.com/openings ** -Dr A J Robinson, Founder, Cantab Research Ltd
Phone direct: 01223 778240 office: 01223 794497
Company reg no GB 05697423, VAT reg no 925606030
51 Canterbury Street, Cambridge, CB4 3QG, UK
From bogus@does.not.exist.com Fri Nov 28 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 28 04:14:44 2014
Subject: No subject
Message-ID: <mailman.1.1417148083.23460.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 28 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 28 04:14:49 2014
Subject: No subject
Message-ID: <mailman.2.1417148089.23460.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 28 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 28 04:14:50 2014
Subject: No subject
Message-ID: <mailman.3.1417148089.23460.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 28 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 28 04:14:50 2014
Subject: No subject
Message-ID: <mailman.4.1417148090.23460.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 28 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 28 04:14:51 2014
Subject: No subject
Message-ID: <mailman.5.1417148091.23460.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 28 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 28 04:14:51 2014
Subject: No subject
Message-ID: <mailman.6.1417148091.23460.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 28 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 28 04:14:52 2014
Subject: No subject
Message-ID: <mailman.7.1417148092.23460.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 28 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 28 04:14:53 2014
Subject: No subject
Message-ID: <mailman.8.1417148093.23460.htk-users@eng.cam.ac.uk>

From bogus@does.not.exist.com Fri Nov 28 02:50:32 2014


From: bogus@does.not.exist.com ()
Date: Fri Nov 28 04:14:54 2014
Subject: No subject
Message-ID: <mailman.9.1417148094.23460.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 28 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 28 04:15:01 2014
Subject: No subject
Message-ID: <mailman.10.1417148100.23460.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 28 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 28 04:15:04 2014
Subject: No subject
Message-ID: <mailman.11.1417148104.23460.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 28 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 28 04:15:10 2014
Subject: No subject
Message-ID: <mailman.12.1417148110.23460.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 28 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 28 04:15:11 2014
Subject: No subject
Message-ID: <mailman.13.1417148111.23460.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 28 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 28 04:15:11 2014
Subject: No subject
Message-ID: <mailman.14.1417148111.23460.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 28 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 28 04:15:12 2014
Subject: No subject
Message-ID: <mailman.15.1417148112.23460.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 28 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 28 04:15:12 2014
Subject: No subject
Message-ID: <mailman.16.1417148112.23460.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 28 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 28 04:15:13 2014
Subject: No subject
Message-ID: <mailman.17.1417148113.23460.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 28 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 28 04:15:14 2014
Subject: No subject
Message-ID: <mailman.18.1417148114.23460.htk-users@eng.cam.ac.uk>

From bogus@does.not.exist.com Fri Nov 28 02:50:32 2014


From: bogus@does.not.exist.com ()
Date: Fri Nov 28 04:15:20 2014
Subject: No subject
Message-ID: <mailman.19.1417148119.23460.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 28 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 28 04:15:24 2014
Subject: No subject
Message-ID: <mailman.20.1417148124.23460.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 28 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 28 04:15:30 2014
Subject: No subject
Message-ID: <mailman.21.1417148130.23460.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 28 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 28 04:15:32 2014
Subject: No subject
Message-ID: <mailman.22.1417148132.23460.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 28 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 28 04:15:33 2014
Subject: No subject
Message-ID: <mailman.23.1417148133.23460.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 28 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 28 04:15:38 2014
Subject: No subject
Message-ID: <mailman.24.1417148138.23460.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 28 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 28 04:15:45 2014
Subject: No subject
Message-ID: <mailman.25.1417148145.23460.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 28 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 28 04:15:50 2014
Subject: No subject
Message-ID: <mailman.26.1417148150.23460.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 28 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 28 04:15:57 2014
Subject: No subject
Message-ID: <mailman.27.1417148157.23460.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 28 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 28 04:16:02 2014
Subject: No subject
Message-ID: <mailman.28.1417148161.23460.htk-users@eng.cam.ac.uk>

From bogus@does.not.exist.com Fri Nov 28 02:50:32 2014


From: bogus@does.not.exist.com ()
Date: Fri Nov 28 04:16:06 2014
Subject: No subject
Message-ID: <mailman.29.1417148166.23460.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 28 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 28 04:16:09 2014
Subject: No subject
Message-ID: <mailman.30.1417148169.23460.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 28 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 28 04:16:10 2014
Subject: No subject
Message-ID: <mailman.31.1417148170.23460.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 28 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 28 04:16:11 2014
Subject: No subject
Message-ID: <mailman.32.1417148171.23460.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 28 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 28 04:16:11 2014
Subject: No subject
Message-ID: <mailman.33.1417148171.23460.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 28 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 28 04:16:12 2014
Subject: No subject
Message-ID: <mailman.34.1417148172.23460.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 28 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 28 04:16:12 2014
Subject: No subject
Message-ID: <mailman.35.1417148172.23460.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 28 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 28 04:16:13 2014
Subject: No subject
Message-ID: <mailman.36.1417148173.23460.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 28 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 28 04:16:14 2014
Subject: No subject
Message-ID: <mailman.37.1417148174.23460.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 28 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 28 04:16:15 2014
Subject: No subject
Message-ID: <mailman.38.1417148175.23460.htk-users@eng.cam.ac.uk>

From bogus@does.not.exist.com Fri Nov 28 02:50:32 2014


From: bogus@does.not.exist.com ()
Date: Fri Nov 28 04:16:16 2014
Subject: No subject
Message-ID: <mailman.39.1417148176.23460.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 28 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 28 04:16:16 2014
Subject: No subject
Message-ID: <mailman.40.1417148176.23460.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 28 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 28 04:16:19 2014
Subject: No subject
Message-ID: <mailman.41.1417148179.23460.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 28 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 28 04:16:20 2014
Subject: No subject
Message-ID: <mailman.42.1417148180.23460.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 28 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 28 04:16:20 2014
Subject: No subject
Message-ID: <mailman.43.1417148180.23460.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 28 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 28 04:16:21 2014
Subject: No subject
Message-ID: <mailman.44.1417148181.23460.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 28 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 28 04:16:22 2014
Subject: No subject
Message-ID: <mailman.45.1417148182.23460.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 28 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 28 04:16:22 2014
Subject: No subject
Message-ID: <mailman.46.1417148182.23460.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 28 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 28 04:16:23 2014
Subject: No subject
Message-ID: <mailman.47.1417148183.23460.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 28 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 28 04:16:24 2014
Subject: No subject
Message-ID: <mailman.48.1417148184.23460.htk-users@eng.cam.ac.uk>

From bogus@does.not.exist.com Fri Nov 28 02:50:32 2014


From: bogus@does.not.exist.com ()
Date: Fri Nov 28 04:16:26 2014
Subject: No subject
Message-ID: <mailman.49.1417148186.23460.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 28 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 28 04:16:36 2014
Subject: No subject
Message-ID: <mailman.50.1417148196.23460.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 28 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 28 04:16:37 2014
Subject: No subject
Message-ID: <mailman.51.1417148197.23460.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 28 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 28 04:16:41 2014
Subject: No subject
Message-ID: <mailman.52.1417148200.23460.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 28 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 28 04:16:43 2014
Subject: No subject
Message-ID: <mailman.53.1417148203.23460.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 28 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 28 04:16:46 2014
Subject: No subject
Message-ID: <mailman.54.1417148206.23460.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 28 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 28 04:16:49 2014
Subject: No subject
Message-ID: <mailman.55.1417148209.23460.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 28 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 28 04:16:51 2014
Subject: No subject
Message-ID: <mailman.56.1417148211.23460.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 28 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 28 04:16:54 2014
Subject: No subject
Message-ID: <mailman.57.1417148214.23460.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 28 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 28 04:16:57 2014
Subject: No subject
Message-ID: <mailman.58.1417148217.23460.htk-users@eng.cam.ac.uk>

From bogus@does.not.exist.com Fri Nov 28 02:50:32 2014


From: bogus@does.not.exist.com ()
Date: Fri Nov 28 04:17:01 2014
Subject: No subject
Message-ID: <mailman.59.1417148221.23460.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 28 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 28 04:17:03 2014
Subject: No subject
Message-ID: <mailman.60.1417148223.23460.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 28 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 28 04:17:06 2014
Subject: No subject
Message-ID: <mailman.61.1417148226.23460.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 28 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 28 04:17:10 2014
Subject: No subject
Message-ID: <mailman.62.1417148230.23460.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 28 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 28 04:17:12 2014
Subject: No subject
Message-ID: <mailman.63.1417148232.23460.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 28 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 28 04:17:15 2014
Subject: No subject
Message-ID: <mailman.64.1417148235.23460.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 28 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 28 04:17:18 2014
Subject: No subject
Message-ID: <mailman.65.1417148238.23460.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 28 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 28 04:17:20 2014
Subject: No subject
Message-ID: <mailman.66.1417148240.23460.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 28 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 28 04:17:23 2014
Subject: No subject
Message-ID: <mailman.67.1417148243.23460.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 28 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 28 04:17:25 2014
Subject: No subject
Message-ID: <mailman.68.1417148245.23460.htk-users@eng.cam.ac.uk>

From bogus@does.not.exist.com Fri Nov 28 02:50:32 2014


From: bogus@does.not.exist.com ()
Date: Fri Nov 28 04:17:28 2014
Subject: No subject
Message-ID: <mailman.69.1417148248.23460.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 28 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 28 04:17:33 2014
Subject: No subject
Message-ID: <mailman.70.1417148253.23460.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 28 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 28 04:17:34 2014
Subject: No subject
Message-ID: <mailman.71.1417148254.23460.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 28 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 28 04:17:34 2014
Subject: No subject
Message-ID: <mailman.72.1417148254.23460.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 28 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 28 04:17:35 2014
Subject: No subject
Message-ID: <mailman.73.1417148255.23460.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 28 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 28 04:17:36 2014
Subject: No subject
Message-ID: <mailman.74.1417148256.23460.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 28 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 28 04:17:36 2014
Subject: No subject
Message-ID: <mailman.75.1417148256.23460.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 28 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 28 04:17:37 2014
Subject: No subject
Message-ID: <mailman.76.1417148257.23460.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 28 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 28 04:17:38 2014
Subject: No subject
Message-ID: <mailman.77.1417148258.23460.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 28 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 28 04:17:38 2014
Subject: No subject
Message-ID: <mailman.78.1417148258.23460.htk-users@eng.cam.ac.uk>

From bogus@does.not.exist.com Fri Nov 28 02:50:32 2014


From: bogus@does.not.exist.com ()
Date: Fri Nov 28 04:17:39 2014
Subject: No subject
Message-ID: <mailman.79.1417148259.23460.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 28 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 28 04:17:39 2014
Subject: No subject
Message-ID: <mailman.80.1417148259.23460.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 28 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 28 04:17:40 2014
Subject: No subject
Message-ID: <mailman.81.1417148260.23460.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 28 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 28 04:17:41 2014
Subject: No subject
Message-ID: <mailman.82.1417148261.23460.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 28 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 28 04:17:42 2014
Subject: No subject
Message-ID: <mailman.83.1417148262.23460.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 28 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 28 04:17:43 2014
Subject: No subject
Message-ID: <mailman.84.1417148263.23460.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 28 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 28 04:17:46 2014
Subject: No subject
Message-ID: <mailman.85.1417148266.23460.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 28 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 28 04:17:48 2014
Subject: No subject
Message-ID: <mailman.86.1417148268.23460.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 28 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 28 04:17:50 2014
Subject: No subject
Message-ID: <mailman.87.1417148270.23460.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 28 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 28 04:17:51 2014
Subject: No subject
Message-ID: <mailman.88.1417148271.23460.htk-users@eng.cam.ac.uk>

From bogus@does.not.exist.com Fri Nov 28 02:50:32 2014


From: bogus@does.not.exist.com ()
Date: Fri Nov 28 04:17:52 2014
Subject: No subject
Message-ID: <mailman.89.1417148272.23460.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 28 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 28 04:17:53 2014
Subject: No subject
Message-ID: <mailman.91.1417148273.23460.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 28 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 28 04:17:54 2014
Subject: No subject
Message-ID: <mailman.92.1417148274.23460.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 28 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 28 04:17:55 2014
Subject: No subject
Message-ID: <mailman.93.1417148275.23460.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 28 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 28 04:17:58 2014
Subject: No subject
Message-ID: <mailman.94.1417148278.23460.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 28 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 28 04:18:01 2014
Subject: No subject
Message-ID: <mailman.95.1417148281.23460.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 28 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 28 04:18:02 2014
Subject: No subject
Message-ID: <mailman.96.1417148282.23460.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 28 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 28 04:18:05 2014
Subject: No subject
Message-ID: <mailman.97.1417148285.23460.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 28 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 28 04:18:07 2014
Subject: No subject
Message-ID: <mailman.98.1417148287.23460.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 28 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 28 04:18:09 2014
Subject: No subject
Message-ID: <mailman.99.1417148289.23460.htk-users@eng.cam.ac.uk>

From bogus@does.not.exist.com Fri Nov 28 02:50:32 2014


From: bogus@does.not.exist.com ()
Date: Fri Nov 28 04:18:10 2014
Subject: No subject
Message-ID: <mailman.100.1417148290.23460.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 28 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 28 04:18:11 2014
Subject: No subject
Message-ID: <mailman.101.1417148291.23460.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 28 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 28 04:18:12 2014
Subject: No subject
Message-ID: <mailman.102.1417148292.23460.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 28 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 28 04:18:13 2014
Subject: No subject
Message-ID: <mailman.103.1417148293.23460.htk-users@eng.cam.ac.uk>
From tonyr at cantabResearch.com Tue Nov 4 20:04:46 2014
From: tonyr at cantabResearch.com (Tony Robinson)
Date: Fri Nov 28 04:40:26 2014
Subject: [HTK-Users] HTK license agreement
In-Reply-To: <545241EC02000049000E3077@pta-emo.csir.co.za>
References: <545241EC02000049000E3077@pta-emo.csir.co.za>
Message-ID: <5459315E.9030409@cantabResearch.com>
I just saw this post - I hope I haven't also missed any replies.
It's been a while since I read the HTK licence, but from memory and past
commercial practices I believe that what you are proposing is entirely
acceptable according to the HTK licence.
In fact I think www.speechmatics.com uses HVite in exactly this way to
do some final tidying up of the large vocabulary speech recognition output.
Tony
On 30/10/14 11:49, Georg Schlunz wrote:
> Good day
>
> Regarding the HTK license, as specified at http://htk.eng.cam.ac.uk/docs/licen
se.shtml , I would like to know whether the following scenario is permitted:
>
> The HTK software (including HVite) sits on a server in-house in our organisati
on, as per license sections 2.1 and 2.3.
> The HTK software (including HVite) is never distributed to a commercial (or no
n-commercial) party, as per license section 2.2.
>
> We have written our own server-client software, where:
> a) the client records speech and sends the audio file to the server, which pas
ses it on to HVite (the server software and HTK sit on the same in-house machine
)
> b) HVite decodes the audio into text

> c) the server replies to the client with the decoded text and the client proce
sses the text somehow
>
> Naturally, the client software contains no HTK code; it only processes data pr
oduced by HTK.
>
> Therefore, may this client software and decoding SERVICE be sold commercially
(as long as we agree to license sections 2.4 and 2.5)?
>
> Thank you
> Georg Schlunz
>
-- ** Cantab is hiring: www.cantabResearch.com/openings ** -Dr A J Robinson, Founder, Cantab Research Ltd
Phone direct: 01223 778240 office: 01223 794497
Company reg no GB 05697423, VAT reg no 925606030
51 Canterbury Street, Cambridge, CB4 3QG, UK
From bogus@does.not.exist.com Sat Nov 29 02:50:38 2014
From: bogus@does.not.exist.com ()
Date: Sat Nov 29 04:04:42 2014
Subject: No subject
Message-ID: <mailman.1.1417233882.14239.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sat Nov 29 02:50:38 2014
From: bogus@does.not.exist.com ()
Date: Sat Nov 29 04:06:28 2014
Subject: No subject
Message-ID: <mailman.2.1417233987.14239.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sat Nov 29 02:50:38 2014
From: bogus@does.not.exist.com ()
Date: Sat Nov 29 04:06:58 2014
Subject: No subject
Message-ID: <mailman.3.1417234017.14239.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sat Nov 29 02:50:38 2014
From: bogus@does.not.exist.com ()
Date: Sat Nov 29 04:07:25 2014
Subject: No subject
Message-ID: <mailman.4.1417234044.14239.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sat Nov 29 02:50:38 2014
From: bogus@does.not.exist.com ()
Date: Sat Nov 29 04:07:56 2014
Subject: No subject
Message-ID: <mailman.5.1417234076.14239.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sat Nov 29 02:50:38 2014
From: bogus@does.not.exist.com ()
Date: Sat Nov 29 04:08:23 2014
Subject: No subject
Message-ID: <mailman.6.1417234102.14239.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sat Nov 29 02:50:38 2014
From: bogus@does.not.exist.com ()
Date: Sat Nov 29 04:08:49 2014
Subject: No subject
Message-ID: <mailman.7.1417234128.14239.htk-users@eng.cam.ac.uk>

From bogus@does.not.exist.com Sat Nov 29 02:50:38 2014


From: bogus@does.not.exist.com ()
Date: Sat Nov 29 04:09:07 2014
Subject: No subject
Message-ID: <mailman.8.1417234147.14239.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sat Nov 29 02:50:38 2014
From: bogus@does.not.exist.com ()
Date: Sat Nov 29 04:09:48 2014
Subject: No subject
Message-ID: <mailman.9.1417234187.14239.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sat Nov 29 02:50:38 2014
From: bogus@does.not.exist.com ()
Date: Sat Nov 29 04:10:25 2014
Subject: No subject
Message-ID: <mailman.10.1417234224.14239.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sat Nov 29 02:50:38 2014
From: bogus@does.not.exist.com ()
Date: Sat Nov 29 04:10:52 2014
Subject: No subject
Message-ID: <mailman.11.1417234251.14239.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sat Nov 29 02:50:38 2014
From: bogus@does.not.exist.com ()
Date: Sat Nov 29 04:11:30 2014
Subject: No subject
Message-ID: <mailman.12.1417234290.14239.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sat Nov 29 02:50:38 2014
From: bogus@does.not.exist.com ()
Date: Sat Nov 29 04:12:00 2014
Subject: No subject
Message-ID: <mailman.13.1417234320.14239.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sat Nov 29 02:50:38 2014
From: bogus@does.not.exist.com ()
Date: Sat Nov 29 04:12:27 2014
Subject: No subject
Message-ID: <mailman.14.1417234347.14239.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sat Nov 29 02:50:38 2014
From: bogus@does.not.exist.com ()
Date: Sat Nov 29 04:12:59 2014
Subject: No subject
Message-ID: <mailman.15.1417234378.14239.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sat Nov 29 02:50:38 2014
From: bogus@does.not.exist.com ()
Date: Sat Nov 29 04:13:31 2014
Subject: No subject
Message-ID: <mailman.16.1417234411.14239.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sat Nov 29 02:50:38 2014
From: bogus@does.not.exist.com ()
Date: Sat Nov 29 04:13:53 2014
Subject: No subject
Message-ID: <mailman.17.1417234432.14239.htk-users@eng.cam.ac.uk>

From bogus@does.not.exist.com Sat Nov 29 02:50:38 2014


From: bogus@does.not.exist.com ()
Date: Sat Nov 29 04:14:28 2014
Subject: No subject
Message-ID: <mailman.18.1417234467.14239.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sat Nov 29 02:50:38 2014
From: bogus@does.not.exist.com ()
Date: Sat Nov 29 04:15:00 2014
Subject: No subject
Message-ID: <mailman.19.1417234499.14239.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sat Nov 29 02:50:38 2014
From: bogus@does.not.exist.com ()
Date: Sat Nov 29 04:15:23 2014
Subject: No subject
Message-ID: <mailman.20.1417234523.14239.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sat Nov 29 02:50:38 2014
From: bogus@does.not.exist.com ()
Date: Sat Nov 29 04:15:58 2014
Subject: No subject
Message-ID: <mailman.21.1417234558.14239.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sat Nov 29 02:50:38 2014
From: bogus@does.not.exist.com ()
Date: Sat Nov 29 04:16:27 2014
Subject: No subject
Message-ID: <mailman.22.1417234586.14239.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sat Nov 29 02:50:38 2014
From: bogus@does.not.exist.com ()
Date: Sat Nov 29 04:16:37 2014
Subject: No subject
Message-ID: <mailman.23.1417234597.14239.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sat Nov 29 02:50:38 2014
From: bogus@does.not.exist.com ()
Date: Sat Nov 29 04:16:40 2014
Subject: No subject
Message-ID: <mailman.24.1417234600.14239.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sat Nov 29 02:50:38 2014
From: bogus@does.not.exist.com ()
Date: Sat Nov 29 04:17:02 2014
Subject: No subject
Message-ID: <mailman.25.1417234621.14239.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sat Nov 29 02:50:38 2014
From: bogus@does.not.exist.com ()
Date: Sat Nov 29 04:17:20 2014
Subject: No subject
Message-ID: <mailman.26.1417234640.14239.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sat Nov 29 02:50:38 2014
From: bogus@does.not.exist.com ()
Date: Sat Nov 29 04:17:35 2014
Subject: No subject
Message-ID: <mailman.27.1417234655.14239.htk-users@eng.cam.ac.uk>

From bogus@does.not.exist.com Sat Nov 29 02:50:38 2014


From: bogus@does.not.exist.com ()
Date: Sat Nov 29 04:17:56 2014
Subject: No subject
Message-ID: <mailman.28.1417234676.14239.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sat Nov 29 02:50:38 2014
From: bogus@does.not.exist.com ()
Date: Sat Nov 29 04:18:05 2014
Subject: No subject
Message-ID: <mailman.29.1417234684.14239.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sat Nov 29 02:50:38 2014
From: bogus@does.not.exist.com ()
Date: Sat Nov 29 04:18:22 2014
Subject: No subject
Message-ID: <mailman.30.1417234702.14239.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sat Nov 29 02:50:38 2014
From: bogus@does.not.exist.com ()
Date: Sat Nov 29 04:18:32 2014
Subject: No subject
Message-ID: <mailman.31.1417234712.14239.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sat Nov 29 02:50:38 2014
From: bogus@does.not.exist.com ()
Date: Sat Nov 29 04:18:41 2014
Subject: No subject
Message-ID: <mailman.32.1417234720.14239.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sat Nov 29 02:50:38 2014
From: bogus@does.not.exist.com ()
Date: Sat Nov 29 04:18:49 2014
Subject: No subject
Message-ID: <mailman.33.1417234728.14239.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sat Nov 29 02:50:38 2014
From: bogus@does.not.exist.com ()
Date: Sat Nov 29 04:18:58 2014
Subject: No subject
Message-ID: <mailman.34.1417234738.14239.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sat Nov 29 02:50:38 2014
From: bogus@does.not.exist.com ()
Date: Sat Nov 29 04:19:03 2014
Subject: No subject
Message-ID: <mailman.35.1417234743.14239.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sat Nov 29 02:50:38 2014
From: bogus@does.not.exist.com ()
Date: Sat Nov 29 04:19:05 2014
Subject: No subject
Message-ID: <mailman.36.1417234745.14239.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sat Nov 29 02:50:38 2014
From: bogus@does.not.exist.com ()
Date: Sat Nov 29 04:19:07 2014
Subject: No subject
Message-ID: <mailman.37.1417234747.14239.htk-users@eng.cam.ac.uk>

From bogus@does.not.exist.com Sat Nov 29 02:50:38 2014


From: bogus@does.not.exist.com ()
Date: Sat Nov 29 04:19:10 2014
Subject: No subject
Message-ID: <mailman.38.1417234749.14239.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sat Nov 29 02:50:38 2014
From: bogus@does.not.exist.com ()
Date: Sat Nov 29 04:19:12 2014
Subject: No subject
Message-ID: <mailman.39.1417234752.14239.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sat Nov 29 02:50:38 2014
From: bogus@does.not.exist.com ()
Date: Sat Nov 29 04:19:13 2014
Subject: No subject
Message-ID: <mailman.40.1417234753.14239.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sat Nov 29 02:50:38 2014
From: bogus@does.not.exist.com ()
Date: Sat Nov 29 04:19:18 2014
Subject: No subject
Message-ID: <mailman.41.1417234758.14239.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sat Nov 29 02:50:38 2014
From: bogus@does.not.exist.com ()
Date: Sat Nov 29 04:19:19 2014
Subject: No subject
Message-ID: <mailman.42.1417234759.14239.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sat Nov 29 02:50:38 2014
From: bogus@does.not.exist.com ()
Date: Sat Nov 29 04:19:20 2014
Subject: No subject
Message-ID: <mailman.43.1417234760.14239.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sat Nov 29 02:50:38 2014
From: bogus@does.not.exist.com ()
Date: Sat Nov 29 04:19:21 2014
Subject: No subject
Message-ID: <mailman.44.1417234761.14239.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sat Nov 29 02:50:38 2014
From: bogus@does.not.exist.com ()
Date: Sat Nov 29 04:19:22 2014
Subject: No subject
Message-ID: <mailman.45.1417234762.14239.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sat Nov 29 02:50:38 2014
From: bogus@does.not.exist.com ()
Date: Sat Nov 29 04:19:22 2014
Subject: No subject
Message-ID: <mailman.46.1417234762.14239.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sat Nov 29 02:50:38 2014
From: bogus@does.not.exist.com ()
Date: Sat Nov 29 04:19:23 2014
Subject: No subject
Message-ID: <mailman.47.1417234763.14239.htk-users@eng.cam.ac.uk>

From bogus@does.not.exist.com Sat Nov 29 02:50:38 2014


From: bogus@does.not.exist.com ()
Date: Sat Nov 29 04:19:25 2014
Subject: No subject
Message-ID: <mailman.48.1417234765.14239.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sat Nov 29 02:50:38 2014
From: bogus@does.not.exist.com ()
Date: Sat Nov 29 04:19:28 2014
Subject: No subject
Message-ID: <mailman.49.1417234768.14239.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sat Nov 29 02:50:38 2014
From: bogus@does.not.exist.com ()
Date: Sat Nov 29 04:19:29 2014
Subject: No subject
Message-ID: <mailman.50.1417234769.14239.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sat Nov 29 02:50:38 2014
From: bogus@does.not.exist.com ()
Date: Sat Nov 29 04:19:29 2014
Subject: No subject
Message-ID: <mailman.51.1417234769.14239.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sat Nov 29 02:50:38 2014
From: bogus@does.not.exist.com ()
Date: Sat Nov 29 04:19:30 2014
Subject: No subject
Message-ID: <mailman.52.1417234770.14239.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sat Nov 29 02:50:38 2014
From: bogus@does.not.exist.com ()
Date: Sat Nov 29 04:19:30 2014
Subject: No subject
Message-ID: <mailman.53.1417234770.14239.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sat Nov 29 02:50:38 2014
From: bogus@does.not.exist.com ()
Date: Sat Nov 29 04:19:31 2014
Subject: No subject
Message-ID: <mailman.54.1417234771.14239.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sat Nov 29 02:50:38 2014
From: bogus@does.not.exist.com ()
Date: Sat Nov 29 04:19:32 2014
Subject: No subject
Message-ID: <mailman.55.1417234772.14239.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sat Nov 29 02:50:38 2014
From: bogus@does.not.exist.com ()
Date: Sat Nov 29 04:19:32 2014
Subject: No subject
Message-ID: <mailman.56.1417234772.14239.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sat Nov 29 02:50:38 2014
From: bogus@does.not.exist.com ()
Date: Sat Nov 29 04:19:33 2014
Subject: No subject
Message-ID: <mailman.57.1417234773.14239.htk-users@eng.cam.ac.uk>

From bogus@does.not.exist.com Sat Nov 29 02:50:38 2014


From: bogus@does.not.exist.com ()
Date: Sat Nov 29 04:19:33 2014
Subject: No subject
Message-ID: <mailman.58.1417234773.14239.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sat Nov 29 02:50:38 2014
From: bogus@does.not.exist.com ()
Date: Sat Nov 29 04:19:34 2014
Subject: No subject
Message-ID: <mailman.59.1417234774.14239.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sat Nov 29 02:50:38 2014
From: bogus@does.not.exist.com ()
Date: Sat Nov 29 04:19:35 2014
Subject: No subject
Message-ID: <mailman.60.1417234775.14239.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sat Nov 29 02:50:38 2014
From: bogus@does.not.exist.com ()
Date: Sat Nov 29 04:19:35 2014
Subject: No subject
Message-ID: <mailman.61.1417234775.14239.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sat Nov 29 02:50:38 2014
From: bogus@does.not.exist.com ()
Date: Sat Nov 29 04:19:36 2014
Subject: No subject
Message-ID: <mailman.62.1417234776.14239.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sat Nov 29 02:50:38 2014
From: bogus@does.not.exist.com ()
Date: Sat Nov 29 04:19:36 2014
Subject: No subject
Message-ID: <mailman.63.1417234776.14239.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sat Nov 29 02:50:38 2014
From: bogus@does.not.exist.com ()
Date: Sat Nov 29 04:19:38 2014
Subject: No subject
Message-ID: <mailman.64.1417234778.14239.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sat Nov 29 02:50:38 2014
From: bogus@does.not.exist.com ()
Date: Sat Nov 29 04:19:38 2014
Subject: No subject
Message-ID: <mailman.65.1417234778.14239.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sat Nov 29 02:50:38 2014
From: bogus@does.not.exist.com ()
Date: Sat Nov 29 04:19:39 2014
Subject: No subject
Message-ID: <mailman.66.1417234779.14239.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sat Nov 29 02:50:38 2014
From: bogus@does.not.exist.com ()
Date: Sat Nov 29 04:19:40 2014
Subject: No subject
Message-ID: <mailman.67.1417234780.14239.htk-users@eng.cam.ac.uk>

From bogus@does.not.exist.com Sat Nov 29 02:50:38 2014


From: bogus@does.not.exist.com ()
Date: Sat Nov 29 04:19:40 2014
Subject: No subject
Message-ID: <mailman.68.1417234780.14239.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sat Nov 29 02:50:38 2014
From: bogus@does.not.exist.com ()
Date: Sat Nov 29 04:19:41 2014
Subject: No subject
Message-ID: <mailman.69.1417234781.14239.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sat Nov 29 02:50:38 2014
From: bogus@does.not.exist.com ()
Date: Sat Nov 29 04:19:44 2014
Subject: No subject
Message-ID: <mailman.70.1417234784.14239.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sat Nov 29 02:50:38 2014
From: bogus@does.not.exist.com ()
Date: Sat Nov 29 04:19:45 2014
Subject: No subject
Message-ID: <mailman.71.1417234785.14239.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sat Nov 29 02:50:38 2014
From: bogus@does.not.exist.com ()
Date: Sat Nov 29 04:19:46 2014
Subject: No subject
Message-ID: <mailman.72.1417234786.14239.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sat Nov 29 02:50:38 2014
From: bogus@does.not.exist.com ()
Date: Sat Nov 29 04:19:47 2014
Subject: No subject
Message-ID: <mailman.73.1417234787.14239.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sat Nov 29 02:50:38 2014
From: bogus@does.not.exist.com ()
Date: Sat Nov 29 04:19:47 2014
Subject: No subject
Message-ID: <mailman.74.1417234787.14239.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sat Nov 29 02:50:38 2014
From: bogus@does.not.exist.com ()
Date: Sat Nov 29 04:19:48 2014
Subject: No subject
Message-ID: <mailman.75.1417234788.14239.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sat Nov 29 02:50:38 2014
From: bogus@does.not.exist.com ()
Date: Sat Nov 29 04:19:49 2014
Subject: No subject
Message-ID: <mailman.76.1417234789.14239.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sat Nov 29 02:50:38 2014
From: bogus@does.not.exist.com ()
Date: Sat Nov 29 04:19:49 2014
Subject: No subject
Message-ID: <mailman.77.1417234789.14239.htk-users@eng.cam.ac.uk>

From bogus@does.not.exist.com Sat Nov 29 02:50:38 2014


From: bogus@does.not.exist.com ()
Date: Sat Nov 29 04:19:50 2014
Subject: No subject
Message-ID: <mailman.78.1417234790.14239.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sat Nov 29 02:50:38 2014
From: bogus@does.not.exist.com ()
Date: Sat Nov 29 04:19:50 2014
Subject: No subject
Message-ID: <mailman.79.1417234790.14239.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sat Nov 29 02:50:38 2014
From: bogus@does.not.exist.com ()
Date: Sat Nov 29 04:19:51 2014
Subject: No subject
Message-ID: <mailman.80.1417234791.14239.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sat Nov 29 02:50:38 2014
From: bogus@does.not.exist.com ()
Date: Sat Nov 29 04:19:52 2014
Subject: No subject
Message-ID: <mailman.81.1417234792.14239.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sat Nov 29 02:50:38 2014
From: bogus@does.not.exist.com ()
Date: Sat Nov 29 04:19:52 2014
Subject: No subject
Message-ID: <mailman.82.1417234792.14239.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sat Nov 29 02:50:38 2014
From: bogus@does.not.exist.com ()
Date: Sat Nov 29 04:19:53 2014
Subject: No subject
Message-ID: <mailman.83.1417234793.14239.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sat Nov 29 02:50:38 2014
From: bogus@does.not.exist.com ()
Date: Sat Nov 29 04:19:55 2014
Subject: No subject
Message-ID: <mailman.84.1417234795.14239.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sat Nov 29 02:50:38 2014
From: bogus@does.not.exist.com ()
Date: Sat Nov 29 04:19:56 2014
Subject: No subject
Message-ID: <mailman.85.1417234796.14239.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sat Nov 29 02:50:38 2014
From: bogus@does.not.exist.com ()
Date: Sat Nov 29 04:20:07 2014
Subject: No subject
Message-ID: <mailman.86.1417234807.14239.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sat Nov 29 02:50:38 2014
From: bogus@does.not.exist.com ()
Date: Sat Nov 29 04:20:09 2014
Subject: No subject
Message-ID: <mailman.87.1417234809.14239.htk-users@eng.cam.ac.uk>

From bogus@does.not.exist.com Sat Nov 29 02:50:38 2014


From: bogus@does.not.exist.com ()
Date: Sat Nov 29 04:20:10 2014
Subject: No subject
Message-ID: <mailman.88.1417234810.14239.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sat Nov 29 02:50:38 2014
From: bogus@does.not.exist.com ()
Date: Sat Nov 29 04:20:12 2014
Subject: No subject
Message-ID: <mailman.89.1417234812.14239.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sat Nov 29 02:50:38 2014
From: bogus@does.not.exist.com ()
Date: Sat Nov 29 04:20:13 2014
Subject: No subject
Message-ID: <mailman.91.1417234813.14239.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sat Nov 29 02:50:38 2014
From: bogus@does.not.exist.com ()
Date: Sat Nov 29 04:20:14 2014
Subject: No subject
Message-ID: <mailman.92.1417234814.14239.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sat Nov 29 02:50:38 2014
From: bogus@does.not.exist.com ()
Date: Sat Nov 29 04:20:15 2014
Subject: No subject
Message-ID: <mailman.93.1417234815.14239.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sat Nov 29 02:50:38 2014
From: bogus@does.not.exist.com ()
Date: Sat Nov 29 04:20:19 2014
Subject: No subject
Message-ID: <mailman.94.1417234819.14239.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sat Nov 29 02:50:38 2014
From: bogus@does.not.exist.com ()
Date: Sat Nov 29 04:20:21 2014
Subject: No subject
Message-ID: <mailman.95.1417234821.14239.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sat Nov 29 02:50:38 2014
From: bogus@does.not.exist.com ()
Date: Sat Nov 29 04:20:23 2014
Subject: No subject
Message-ID: <mailman.96.1417234823.14239.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sat Nov 29 02:50:38 2014
From: bogus@does.not.exist.com ()
Date: Sat Nov 29 04:20:27 2014
Subject: No subject
Message-ID: <mailman.97.1417234827.14239.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sat Nov 29 02:50:38 2014
From: bogus@does.not.exist.com ()
Date: Sat Nov 29 04:20:29 2014
Subject: No subject
Message-ID: <mailman.98.1417234829.14239.htk-users@eng.cam.ac.uk>

From bogus@does.not.exist.com Sat Nov 29 02:50:38 2014


From: bogus@does.not.exist.com ()
Date: Sat Nov 29 04:20:34 2014
Subject: No subject
Message-ID: <mailman.99.1417234834.14239.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sat Nov 29 02:50:38 2014
From: bogus@does.not.exist.com ()
Date: Sat Nov 29 04:20:36 2014
Subject: No subject
Message-ID: <mailman.100.1417234836.14239.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sat Nov 29 02:50:38 2014
From: bogus@does.not.exist.com ()
Date: Sat Nov 29 04:20:39 2014
Subject: No subject
Message-ID: <mailman.101.1417234839.14239.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sat Nov 29 02:50:38 2014
From: bogus@does.not.exist.com ()
Date: Sat Nov 29 04:20:41 2014
Subject: No subject
Message-ID: <mailman.102.1417234841.14239.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sat Nov 29 02:50:38 2014
From: bogus@does.not.exist.com ()
Date: Sat Nov 29 04:20:45 2014
Subject: No subject
Message-ID: <mailman.103.1417234845.14239.htk-users@eng.cam.ac.uk>
From tonyr at cantabResearch.com Tue Nov 4 20:04:46 2014
From: tonyr at cantabResearch.com (Tony Robinson)
Date: Sat Nov 29 04:42:16 2014
Subject: [HTK-Users] HTK license agreement
In-Reply-To: <545241EC02000049000E3077@pta-emo.csir.co.za>
References: <545241EC02000049000E3077@pta-emo.csir.co.za>
Message-ID: <5459315E.9030409@cantabResearch.com>
I just saw this post - I hope I haven't also missed any replies.
It's been a while since I read the HTK licence, but from memory and past
commercial practices I believe that what you are proposing is entirely
acceptable according to the HTK licence.
In fact I think www.speechmatics.com uses HVite in exactly this way to
do some final tidying up of the large vocabulary speech recognition output.
Tony
On 30/10/14 11:49, Georg Schlunz wrote:
> Good day
>
> Regarding the HTK license, as specified at http://htk.eng.cam.ac.uk/docs/licen
se.shtml , I would like to know whether the following scenario is permitted:
>
> The HTK software (including HVite) sits on a server in-house in our organisati
on, as per license sections 2.1 and 2.3.
> The HTK software (including HVite) is never distributed to a commercial (or no

n-commercial) party, as per license section 2.2.


>
> We have written our own server-client software, where:
> a) the client records speech and sends the audio file to the server, which pas
ses it on to HVite (the server software and HTK sit on the same in-house machine
)
> b) HVite decodes the audio into text
> c) the server replies to the client with the decoded text and the client proce
sses the text somehow
>
> Naturally, the client software contains no HTK code; it only processes data pr
oduced by HTK.
>
> Therefore, may this client software and decoding SERVICE be sold commercially
(as long as we agree to license sections 2.4 and 2.5)?
>
> Thank you
> Georg Schlunz
>
-- ** Cantab is hiring: www.cantabResearch.com/openings ** -Dr A J Robinson, Founder, Cantab Research Ltd
Phone direct: 01223 778240 office: 01223 794497
Company reg no GB 05697423, VAT reg no 925606030
51 Canterbury Street, Cambridge, CB4 3QG, UK
From bogus@does.not.exist.com Sun Nov 30 02:51:37 2014
From: bogus@does.not.exist.com ()
Date: Sun Nov 30 03:56:17 2014
Subject: No subject
Message-ID: <mailman.1.1417319775.28676.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sun Nov 30 02:51:37 2014
From: bogus@does.not.exist.com ()
Date: Sun Nov 30 03:56:20 2014
Subject: No subject
Message-ID: <mailman.2.1417319780.28676.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sun Nov 30 02:51:37 2014
From: bogus@does.not.exist.com ()
Date: Sun Nov 30 03:56:21 2014
Subject: No subject
Message-ID: <mailman.3.1417319781.28676.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sun Nov 30 02:51:37 2014
From: bogus@does.not.exist.com ()
Date: Sun Nov 30 03:56:22 2014
Subject: No subject
Message-ID: <mailman.4.1417319782.28676.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sun Nov 30 02:51:37 2014
From: bogus@does.not.exist.com ()
Date: Sun Nov 30 03:56:22 2014
Subject: No subject
Message-ID: <mailman.5.1417319782.28676.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sun Nov 30 02:51:37 2014
From: bogus@does.not.exist.com ()
Date: Sun Nov 30 03:56:23 2014
Subject: No subject

Message-ID: <mailman.6.1417319783.28676.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sun Nov 30 02:51:37 2014
From: bogus@does.not.exist.com ()
Date: Sun Nov 30 03:56:23 2014
Subject: No subject
Message-ID: <mailman.7.1417319783.28676.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sun Nov 30 02:51:37 2014
From: bogus@does.not.exist.com ()
Date: Sun Nov 30 03:56:24 2014
Subject: No subject
Message-ID: <mailman.8.1417319784.28676.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sun Nov 30 02:51:37 2014
From: bogus@does.not.exist.com ()
Date: Sun Nov 30 03:56:25 2014
Subject: No subject
Message-ID: <mailman.9.1417319785.28676.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sun Nov 30 02:51:37 2014
From: bogus@does.not.exist.com ()
Date: Sun Nov 30 03:56:31 2014
Subject: No subject
Message-ID: <mailman.10.1417319791.28676.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sun Nov 30 02:51:37 2014
From: bogus@does.not.exist.com ()
Date: Sun Nov 30 03:56:32 2014
Subject: No subject
Message-ID: <mailman.11.1417319792.28676.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sun Nov 30 02:51:37 2014
From: bogus@does.not.exist.com ()
Date: Sun Nov 30 03:56:35 2014
Subject: No subject
Message-ID: <mailman.12.1417319795.28676.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sun Nov 30 02:51:37 2014
From: bogus@does.not.exist.com ()
Date: Sun Nov 30 03:56:37 2014
Subject: No subject
Message-ID: <mailman.13.1417319797.28676.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sun Nov 30 02:51:37 2014
From: bogus@does.not.exist.com ()
Date: Sun Nov 30 03:56:41 2014
Subject: No subject
Message-ID: <mailman.14.1417319800.28676.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sun Nov 30 02:51:37 2014
From: bogus@does.not.exist.com ()
Date: Sun Nov 30 03:56:43 2014
Subject: No subject
Message-ID: <mailman.15.1417319803.28676.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sun Nov 30 02:51:37 2014
From: bogus@does.not.exist.com ()
Date: Sun Nov 30 03:56:46 2014
Subject: No subject

Message-ID: <mailman.16.1417319806.28676.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sun Nov 30 02:51:37 2014
From: bogus@does.not.exist.com ()
Date: Sun Nov 30 03:56:49 2014
Subject: No subject
Message-ID: <mailman.17.1417319809.28676.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sun Nov 30 02:51:37 2014
From: bogus@does.not.exist.com ()
Date: Sun Nov 30 03:56:52 2014
Subject: No subject
Message-ID: <mailman.18.1417319811.28676.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sun Nov 30 02:51:37 2014
From: bogus@does.not.exist.com ()
Date: Sun Nov 30 03:56:59 2014
Subject: No subject
Message-ID: <mailman.19.1417319819.28676.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sun Nov 30 02:51:37 2014
From: bogus@does.not.exist.com ()
Date: Sun Nov 30 03:57:02 2014
Subject: No subject
Message-ID: <mailman.20.1417319822.28676.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sun Nov 30 02:51:37 2014
From: bogus@does.not.exist.com ()
Date: Sun Nov 30 03:57:05 2014
Subject: No subject
Message-ID: <mailman.21.1417319825.28676.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sun Nov 30 02:51:37 2014
From: bogus@does.not.exist.com ()
Date: Sun Nov 30 03:57:07 2014
Subject: No subject
Message-ID: <mailman.22.1417319827.28676.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sun Nov 30 02:51:37 2014
From: bogus@does.not.exist.com ()
Date: Sun Nov 30 03:57:08 2014
Subject: No subject
Message-ID: <mailman.23.1417319828.28676.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sun Nov 30 02:51:37 2014
From: bogus@does.not.exist.com ()
Date: Sun Nov 30 03:57:10 2014
Subject: No subject
Message-ID: <mailman.24.1417319830.28676.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sun Nov 30 02:51:37 2014
From: bogus@does.not.exist.com ()
Date: Sun Nov 30 03:57:12 2014
Subject: No subject
Message-ID: <mailman.25.1417319832.28676.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sun Nov 30 02:51:37 2014
From: bogus@does.not.exist.com ()
Date: Sun Nov 30 03:57:13 2014
Subject: No subject

Message-ID: <mailman.26.1417319833.28676.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sun Nov 30 02:51:37 2014
From: bogus@does.not.exist.com ()
Date: Sun Nov 30 03:57:14 2014
Subject: No subject
Message-ID: <mailman.27.1417319834.28676.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sun Nov 30 02:51:37 2014
From: bogus@does.not.exist.com ()
Date: Sun Nov 30 03:57:14 2014
Subject: No subject
Message-ID: <mailman.28.1417319834.28676.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sun Nov 30 02:51:37 2014
From: bogus@does.not.exist.com ()
Date: Sun Nov 30 03:57:15 2014
Subject: No subject
Message-ID: <mailman.29.1417319835.28676.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sun Nov 30 02:51:37 2014
From: bogus@does.not.exist.com ()
Date: Sun Nov 30 03:57:18 2014
Subject: No subject
Message-ID: <mailman.30.1417319838.28676.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sun Nov 30 02:51:37 2014
From: bogus@does.not.exist.com ()
Date: Sun Nov 30 03:57:18 2014
Subject: No subject
Message-ID: <mailman.31.1417319838.28676.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sun Nov 30 02:51:37 2014
From: bogus@does.not.exist.com ()
Date: Sun Nov 30 03:57:19 2014
Subject: No subject
Message-ID: <mailman.32.1417319839.28676.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sun Nov 30 02:51:37 2014
From: bogus@does.not.exist.com ()
Date: Sun Nov 30 03:57:20 2014
Subject: No subject
Message-ID: <mailman.33.1417319840.28676.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sun Nov 30 02:51:37 2014
From: bogus@does.not.exist.com ()
Date: Sun Nov 30 03:57:20 2014
Subject: No subject
Message-ID: <mailman.34.1417319840.28676.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sun Nov 30 02:51:37 2014
From: bogus@does.not.exist.com ()
Date: Sun Nov 30 03:57:21 2014
Subject: No subject
Message-ID: <mailman.35.1417319841.28676.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sun Nov 30 02:51:37 2014
From: bogus@does.not.exist.com ()
Date: Sun Nov 30 03:57:21 2014
Subject: No subject

Message-ID: <mailman.36.1417319841.28676.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sun Nov 30 02:51:37 2014
From: bogus@does.not.exist.com ()
Date: Sun Nov 30 03:57:22 2014
Subject: No subject
Message-ID: <mailman.37.1417319842.28676.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sun Nov 30 02:51:37 2014
From: bogus@does.not.exist.com ()
Date: Sun Nov 30 03:57:23 2014
Subject: No subject
Message-ID: <mailman.38.1417319843.28676.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sun Nov 30 02:51:37 2014
From: bogus@does.not.exist.com ()
Date: Sun Nov 30 03:57:24 2014
Subject: No subject
Message-ID: <mailman.39.1417319844.28676.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sun Nov 30 02:51:37 2014
From: bogus@does.not.exist.com ()
Date: Sun Nov 30 03:57:24 2014
Subject: No subject
Message-ID: <mailman.40.1417319844.28676.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sun Nov 30 02:51:37 2014
From: bogus@does.not.exist.com ()
Date: Sun Nov 30 03:57:27 2014
Subject: No subject
Message-ID: <mailman.41.1417319847.28676.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sun Nov 30 02:51:37 2014
From: bogus@does.not.exist.com ()
Date: Sun Nov 30 03:57:28 2014
Subject: No subject
Message-ID: <mailman.42.1417319848.28676.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sun Nov 30 02:51:37 2014
From: bogus@does.not.exist.com ()
Date: Sun Nov 30 03:57:28 2014
Subject: No subject
Message-ID: <mailman.43.1417319848.28676.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sun Nov 30 02:51:37 2014
From: bogus@does.not.exist.com ()
Date: Sun Nov 30 03:57:29 2014
Subject: No subject
Message-ID: <mailman.44.1417319849.28676.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sun Nov 30 02:51:37 2014
From: bogus@does.not.exist.com ()
Date: Sun Nov 30 03:57:30 2014
Subject: No subject
Message-ID: <mailman.45.1417319850.28676.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sun Nov 30 02:51:37 2014
From: bogus@does.not.exist.com ()
Date: Sun Nov 30 03:57:30 2014
Subject: No subject

Message-ID: <mailman.46.1417319850.28676.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sun Nov 30 02:51:37 2014
From: bogus@does.not.exist.com ()
Date: Sun Nov 30 03:57:31 2014
Subject: No subject
Message-ID: <mailman.47.1417319851.28676.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sun Nov 30 02:51:37 2014
From: bogus@does.not.exist.com ()
Date: Sun Nov 30 03:57:31 2014
Subject: No subject
Message-ID: <mailman.48.1417319851.28676.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sun Nov 30 02:51:37 2014
From: bogus@does.not.exist.com ()
Date: Sun Nov 30 03:57:33 2014
Subject: No subject
Message-ID: <mailman.49.1417319853.28676.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sun Nov 30 02:51:37 2014
From: bogus@does.not.exist.com ()
Date: Sun Nov 30 03:57:34 2014
Subject: No subject
Message-ID: <mailman.50.1417319854.28676.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sun Nov 30 02:51:37 2014
From: bogus@does.not.exist.com ()
Date: Sun Nov 30 03:57:34 2014
Subject: No subject
Message-ID: <mailman.51.1417319854.28676.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sun Nov 30 02:51:37 2014
From: bogus@does.not.exist.com ()
Date: Sun Nov 30 03:57:35 2014
Subject: No subject
Message-ID: <mailman.52.1417319855.28676.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sun Nov 30 02:51:37 2014
From: bogus@does.not.exist.com ()
Date: Sun Nov 30 03:57:35 2014
Subject: No subject
Message-ID: <mailman.53.1417319855.28676.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sun Nov 30 02:51:37 2014
From: bogus@does.not.exist.com ()
Date: Sun Nov 30 03:57:36 2014
Subject: No subject
Message-ID: <mailman.54.1417319856.28676.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sun Nov 30 02:51:37 2014
From: bogus@does.not.exist.com ()
Date: Sun Nov 30 03:57:36 2014
Subject: No subject
Message-ID: <mailman.55.1417319856.28676.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sun Nov 30 02:51:37 2014
From: bogus@does.not.exist.com ()
Date: Sun Nov 30 03:57:37 2014
Subject: No subject

Message-ID: <mailman.56.1417319857.28676.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sun Nov 30 02:51:37 2014
From: bogus@does.not.exist.com ()
Date: Sun Nov 30 03:57:41 2014
Subject: No subject
Message-ID: <mailman.57.1417319861.28676.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sun Nov 30 02:51:37 2014
From: bogus@does.not.exist.com ()
Date: Sun Nov 30 03:57:43 2014
Subject: No subject
Message-ID: <mailman.58.1417319863.28676.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sun Nov 30 02:51:37 2014
From: bogus@does.not.exist.com ()
Date: Sun Nov 30 03:57:45 2014
Subject: No subject
Message-ID: <mailman.59.1417319865.28676.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sun Nov 30 02:51:37 2014
From: bogus@does.not.exist.com ()
Date: Sun Nov 30 03:57:48 2014
Subject: No subject
Message-ID: <mailman.60.1417319868.28676.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sun Nov 30 02:51:37 2014
From: bogus@does.not.exist.com ()
Date: Sun Nov 30 03:57:52 2014
Subject: No subject
Message-ID: <mailman.61.1417319871.28676.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sun Nov 30 02:51:37 2014
From: bogus@does.not.exist.com ()
Date: Sun Nov 30 03:57:54 2014
Subject: No subject
Message-ID: <mailman.62.1417319874.28676.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sun Nov 30 02:51:37 2014
From: bogus@does.not.exist.com ()
Date: Sun Nov 30 03:57:58 2014
Subject: No subject
Message-ID: <mailman.63.1417319878.28676.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sun Nov 30 02:51:37 2014
From: bogus@does.not.exist.com ()
Date: Sun Nov 30 03:58:01 2014
Subject: No subject
Message-ID: <mailman.64.1417319881.28676.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sun Nov 30 02:51:37 2014
From: bogus@does.not.exist.com ()
Date: Sun Nov 30 03:58:03 2014
Subject: No subject
Message-ID: <mailman.65.1417319883.28676.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sun Nov 30 02:51:37 2014
From: bogus@does.not.exist.com ()
Date: Sun Nov 30 03:58:06 2014
Subject: No subject

Message-ID: <mailman.66.1417319886.28676.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sun Nov 30 02:51:37 2014
From: bogus@does.not.exist.com ()
Date: Sun Nov 30 03:58:08 2014
Subject: No subject
Message-ID: <mailman.67.1417319888.28676.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sun Nov 30 02:51:37 2014
From: bogus@does.not.exist.com ()
Date: Sun Nov 30 03:58:11 2014
Subject: No subject
Message-ID: <mailman.68.1417319891.28676.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sun Nov 30 02:51:37 2014
From: bogus@does.not.exist.com ()
Date: Sun Nov 30 03:58:14 2014
Subject: No subject
Message-ID: <mailman.69.1417319894.28676.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sun Nov 30 02:51:37 2014
From: bogus@does.not.exist.com ()
Date: Sun Nov 30 03:58:21 2014
Subject: No subject
Message-ID: <mailman.70.1417319901.28676.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sun Nov 30 02:51:37 2014
From: bogus@does.not.exist.com ()
Date: Sun Nov 30 03:58:22 2014
Subject: No subject
Message-ID: <mailman.71.1417319902.28676.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sun Nov 30 02:51:37 2014
From: bogus@does.not.exist.com ()
Date: Sun Nov 30 03:58:25 2014
Subject: No subject
Message-ID: <mailman.72.1417319905.28676.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sun Nov 30 02:51:37 2014
From: bogus@does.not.exist.com ()
Date: Sun Nov 30 03:58:26 2014
Subject: No subject
Message-ID: <mailman.73.1417319906.28676.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sun Nov 30 02:51:37 2014
From: bogus@does.not.exist.com ()
Date: Sun Nov 30 03:58:27 2014
Subject: No subject
Message-ID: <mailman.74.1417319907.28676.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sun Nov 30 02:51:37 2014
From: bogus@does.not.exist.com ()
Date: Sun Nov 30 03:58:27 2014
Subject: No subject
Message-ID: <mailman.75.1417319907.28676.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sun Nov 30 02:51:37 2014
From: bogus@does.not.exist.com ()
Date: Sun Nov 30 03:58:28 2014
Subject: No subject

Message-ID: <mailman.76.1417319908.28676.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sun Nov 30 02:51:37 2014
From: bogus@does.not.exist.com ()
Date: Sun Nov 30 03:58:29 2014
Subject: No subject
Message-ID: <mailman.77.1417319909.28676.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sun Nov 30 02:51:37 2014
From: bogus@does.not.exist.com ()
Date: Sun Nov 30 03:58:29 2014
Subject: No subject
Message-ID: <mailman.78.1417319909.28676.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sun Nov 30 02:51:37 2014
From: bogus@does.not.exist.com ()
Date: Sun Nov 30 03:58:30 2014
Subject: No subject
Message-ID: <mailman.79.1417319910.28676.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sun Nov 30 02:51:37 2014
From: bogus@does.not.exist.com ()
Date: Sun Nov 30 03:58:31 2014
Subject: No subject
Message-ID: <mailman.80.1417319911.28676.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sun Nov 30 02:51:37 2014
From: bogus@does.not.exist.com ()
Date: Sun Nov 30 03:58:31 2014
Subject: No subject
Message-ID: <mailman.81.1417319911.28676.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sun Nov 30 02:51:37 2014
From: bogus@does.not.exist.com ()
Date: Sun Nov 30 03:58:32 2014
Subject: No subject
Message-ID: <mailman.82.1417319912.28676.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sun Nov 30 02:51:37 2014
From: bogus@does.not.exist.com ()
Date: Sun Nov 30 03:58:32 2014
Subject: No subject
Message-ID: <mailman.83.1417319912.28676.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sun Nov 30 02:51:37 2014
From: bogus@does.not.exist.com ()
Date: Sun Nov 30 03:58:34 2014
Subject: No subject
Message-ID: <mailman.84.1417319914.28676.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sun Nov 30 02:51:37 2014
From: bogus@does.not.exist.com ()
Date: Sun Nov 30 03:58:35 2014
Subject: No subject
Message-ID: <mailman.85.1417319915.28676.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sun Nov 30 02:51:37 2014
From: bogus@does.not.exist.com ()
Date: Sun Nov 30 03:58:37 2014
Subject: No subject

Message-ID: <mailman.86.1417319917.28676.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sun Nov 30 02:51:37 2014
From: bogus@does.not.exist.com ()
Date: Sun Nov 30 03:58:38 2014
Subject: No subject
Message-ID: <mailman.87.1417319918.28676.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sun Nov 30 02:51:37 2014
From: bogus@does.not.exist.com ()
Date: Sun Nov 30 03:58:39 2014
Subject: No subject
Message-ID: <mailman.88.1417319919.28676.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sun Nov 30 02:51:37 2014
From: bogus@does.not.exist.com ()
Date: Sun Nov 30 03:58:40 2014
Subject: No subject
Message-ID: <mailman.89.1417319920.28676.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sun Nov 30 02:51:37 2014
From: bogus@does.not.exist.com ()
Date: Sun Nov 30 03:58:41 2014
Subject: No subject
Message-ID: <mailman.91.1417319921.28676.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sun Nov 30 02:51:37 2014
From: bogus@does.not.exist.com ()
Date: Sun Nov 30 03:58:43 2014
Subject: No subject
Message-ID: <mailman.92.1417319923.28676.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sun Nov 30 02:51:37 2014
From: bogus@does.not.exist.com ()
Date: Sun Nov 30 03:58:44 2014
Subject: No subject
Message-ID: <mailman.93.1417319924.28676.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sun Nov 30 02:51:37 2014
From: bogus@does.not.exist.com ()
Date: Sun Nov 30 03:58:46 2014
Subject: No subject
Message-ID: <mailman.94.1417319926.28676.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sun Nov 30 02:51:37 2014
From: bogus@does.not.exist.com ()
Date: Sun Nov 30 03:58:47 2014
Subject: No subject
Message-ID: <mailman.95.1417319927.28676.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sun Nov 30 02:51:37 2014
From: bogus@does.not.exist.com ()
Date: Sun Nov 30 03:58:48 2014
Subject: No subject
Message-ID: <mailman.96.1417319928.28676.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sun Nov 30 02:51:37 2014
From: bogus@does.not.exist.com ()
Date: Sun Nov 30 03:58:50 2014
Subject: No subject

Message-ID: <mailman.97.1417319930.28676.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sun Nov 30 02:51:37 2014
From: bogus@does.not.exist.com ()
Date: Sun Nov 30 03:58:51 2014
Subject: No subject
Message-ID: <mailman.98.1417319931.28676.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sun Nov 30 02:51:37 2014
From: bogus@does.not.exist.com ()
Date: Sun Nov 30 03:58:53 2014
Subject: No subject
Message-ID: <mailman.99.1417319933.28676.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sun Nov 30 02:51:37 2014
From: bogus@does.not.exist.com ()
Date: Sun Nov 30 03:58:54 2014
Subject: No subject
Message-ID: <mailman.100.1417319934.28676.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sun Nov 30 02:51:37 2014
From: bogus@does.not.exist.com ()
Date: Sun Nov 30 03:58:55 2014
Subject: No subject
Message-ID: <mailman.101.1417319935.28676.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sun Nov 30 02:51:37 2014
From: bogus@does.not.exist.com ()
Date: Sun Nov 30 03:58:56 2014
Subject: No subject
Message-ID: <mailman.102.1417319936.28676.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sun Nov 30 02:51:37 2014
From: bogus@does.not.exist.com ()
Date: Sun Nov 30 03:58:57 2014
Subject: No subject
Message-ID: <mailman.103.1417319937.28676.htk-users@eng.cam.ac.uk>
From tonyr at cantabResearch.com Tue Nov 4 20:04:46 2014
From: tonyr at cantabResearch.com (Tony Robinson)
Date: Sun Nov 30 04:17:23 2014
Subject: [HTK-Users] HTK license agreement
In-Reply-To: <545241EC02000049000E3077@pta-emo.csir.co.za>
References: <545241EC02000049000E3077@pta-emo.csir.co.za>
Message-ID: <5459315E.9030409@cantabResearch.com>
I just saw this post - I hope I haven't also missed any replies.
It's been a while since I read the HTK licence, but from memory and past
commercial practices I believe that what you are proposing is entirely
acceptable according to the HTK licence.
In fact I think www.speechmatics.com uses HVite in exactly this way to
do some final tidying up of the large vocabulary speech recognition output.
Tony
On 30/10/14 11:49, Georg Schlunz wrote:
> Good day

>
> Regarding the HTK license, as specified at http://htk.eng.cam.ac.uk/docs/licen
se.shtml , I would like to know whether the following scenario is permitted:
>
> The HTK software (including HVite) sits on a server in-house in our organisati
on, as per license sections 2.1 and 2.3.
> The HTK software (including HVite) is never distributed to a commercial (or no
n-commercial) party, as per license section 2.2.
>
> We have written our own server-client software, where:
> a) the client records speech and sends the audio file to the server, which pas
ses it on to HVite (the server software and HTK sit on the same in-house machine
)
> b) HVite decodes the audio into text
> c) the server replies to the client with the decoded text and the client proce
sses the text somehow
>
> Naturally, the client software contains no HTK code; it only processes data pr
oduced by HTK.
>
> Therefore, may this client software and decoding SERVICE be sold commercially
(as long as we agree to license sections 2.4 and 2.5)?
>
> Thank you
> Georg Schlunz
>
-- ** Cantab is hiring: www.cantabResearch.com/openings ** -Dr A J Robinson, Founder, Cantab Research Ltd
Phone direct: 01223 778240 office: 01223 794497
Company reg no GB 05697423, VAT reg no 925606030
51 Canterbury Street, Cambridge, CB4 3QG, UK
From tonyr at cantabResearch.com Tue Nov 4 20:04:46 2014
From: tonyr at cantabResearch.com (Tony Robinson)
Date: Mon Dec 1 04:39:01 2014
Subject: [HTK-Users] HTK license agreement
In-Reply-To: <545241EC02000049000E3077@pta-emo.csir.co.za>
References: <545241EC02000049000E3077@pta-emo.csir.co.za>
Message-ID: <5459315E.9030409@cantabResearch.com>
I just saw this post - I hope I haven't also missed any replies.
It's been a while since I read the HTK licence, but from memory and past
commercial practices I believe that what you are proposing is entirely
acceptable according to the HTK licence.
In fact I think www.speechmatics.com uses HVite in exactly this way to
do some final tidying up of the large vocabulary speech recognition output.
Tony
On 30/10/14 11:49, Georg Schlunz wrote:
> Good day
>
> Regarding the HTK license, as specified at http://htk.eng.cam.ac.uk/docs/licen
se.shtml , I would like to know whether the following scenario is permitted:
>
> The HTK software (including HVite) sits on a server in-house in our organisati

on, as per license sections 2.1 and 2.3.


> The HTK software (including HVite) is never distributed to a commercial (or no
n-commercial) party, as per license section 2.2.
>
> We have written our own server-client software, where:
> a) the client records speech and sends the audio file to the server, which pas
ses it on to HVite (the server software and HTK sit on the same in-house machine
)
> b) HVite decodes the audio into text
> c) the server replies to the client with the decoded text and the client proce
sses the text somehow
>
> Naturally, the client software contains no HTK code; it only processes data pr
oduced by HTK.
>
> Therefore, may this client software and decoding SERVICE be sold commercially
(as long as we agree to license sections 2.4 and 2.5)?
>
> Thank you
> Georg Schlunz
>
-- ** Cantab is hiring: www.cantabResearch.com/openings ** -Dr A J Robinson, Founder, Cantab Research Ltd
Phone direct: 01223 778240 office: 01223 794497
Company reg no GB 05697423, VAT reg no 925606030
51 Canterbury Street, Cambridge, CB4 3QG, UK
From tonyr at cantabResearch.com Tue Nov 4 20:04:46 2014
From: tonyr at cantabResearch.com (Tony Robinson)
Date: Tue Dec 2 04:52:23 2014
Subject: [HTK-Users] HTK license agreement
In-Reply-To: <545241EC02000049000E3077@pta-emo.csir.co.za>
References: <545241EC02000049000E3077@pta-emo.csir.co.za>
Message-ID: <5459315E.9030409@cantabResearch.com>
I just saw this post - I hope I haven't also missed any replies.
It's been a while since I read the HTK licence, but from memory and past
commercial practices I believe that what you are proposing is entirely
acceptable according to the HTK licence.
In fact I think www.speechmatics.com uses HVite in exactly this way to
do some final tidying up of the large vocabulary speech recognition output.
Tony
On 30/10/14 11:49, Georg Schlunz wrote:
> Good day
>
> Regarding the HTK license, as specified at http://htk.eng.cam.ac.uk/docs/licen
se.shtml , I would like to know whether the following scenario is permitted:
>
> The HTK software (including HVite) sits on a server in-house in our organisati
on, as per license sections 2.1 and 2.3.
> The HTK software (including HVite) is never distributed to a commercial (or no
n-commercial) party, as per license section 2.2.
>
> We have written our own server-client software, where:

> a) the client records speech and sends the audio file to the server, which pas
ses it on to HVite (the server software and HTK sit on the same in-house machine
)
> b) HVite decodes the audio into text
> c) the server replies to the client with the decoded text and the client proce
sses the text somehow
>
> Naturally, the client software contains no HTK code; it only processes data pr
oduced by HTK.
>
> Therefore, may this client software and decoding SERVICE be sold commercially
(as long as we agree to license sections 2.4 and 2.5)?
>
> Thank you
> Georg Schlunz
>
-- ** Cantab is hiring: www.cantabResearch.com/openings ** -Dr A J Robinson, Founder, Cantab Research Ltd
Phone direct: 01223 778240 office: 01223 794497
Company reg no GB 05697423, VAT reg no 925606030
51 Canterbury Street, Cambridge, CB4 3QG, UK
From tonyr at cantabResearch.com Tue Nov 4 20:04:46 2014
From: tonyr at cantabResearch.com (Tony Robinson)
Date: Wed Dec 3 04:49:55 2014
Subject: [HTK-Users] HTK license agreement
In-Reply-To: <545241EC02000049000E3077@pta-emo.csir.co.za>
References: <545241EC02000049000E3077@pta-emo.csir.co.za>
Message-ID: <5459315E.9030409@cantabResearch.com>
I just saw this post - I hope I haven't also missed any replies.
It's been a while since I read the HTK licence, but from memory and past
commercial practices I believe that what you are proposing is entirely
acceptable according to the HTK licence.
In fact I think www.speechmatics.com uses HVite in exactly this way to
do some final tidying up of the large vocabulary speech recognition output.
Tony
On 30/10/14 11:49, Georg Schlunz wrote:
> Good day
>
> Regarding the HTK license, as specified at http://htk.eng.cam.ac.uk/docs/licen
se.shtml , I would like to know whether the following scenario is permitted:
>
> The HTK software (including HVite) sits on a server in-house in our organisati
on, as per license sections 2.1 and 2.3.
> The HTK software (including HVite) is never distributed to a commercial (or no
n-commercial) party, as per license section 2.2.
>
> We have written our own server-client software, where:
> a) the client records speech and sends the audio file to the server, which pas
ses it on to HVite (the server software and HTK sit on the same in-house machine
)
> b) HVite decodes the audio into text
> c) the server replies to the client with the decoded text and the client proce

sses the text somehow


>
> Naturally, the client software contains no HTK code; it only processes data pr
oduced by HTK.
>
> Therefore, may this client software and decoding SERVICE be sold commercially
(as long as we agree to license sections 2.4 and 2.5)?
>
> Thank you
> Georg Schlunz
>
-- ** Cantab is hiring: www.cantabResearch.com/openings ** -Dr A J Robinson, Founder, Cantab Research Ltd
Phone direct: 01223 778240 office: 01223 794497
Company reg no GB 05697423, VAT reg no 925606030
51 Canterbury Street, Cambridge, CB4 3QG, UK
From tonyr at cantabResearch.com Tue Nov 4 20:04:46 2014
From: tonyr at cantabResearch.com (Tony Robinson)
Date: Thu Dec 4 04:41:50 2014
Subject: [HTK-Users] HTK license agreement
In-Reply-To: <545241EC02000049000E3077@pta-emo.csir.co.za>
References: <545241EC02000049000E3077@pta-emo.csir.co.za>
Message-ID: <5459315E.9030409@cantabResearch.com>
I just saw this post - I hope I haven't also missed any replies.
It's been a while since I read the HTK licence, but from memory and past
commercial practices I believe that what you are proposing is entirely
acceptable according to the HTK licence.
In fact I think www.speechmatics.com uses HVite in exactly this way to
do some final tidying up of the large vocabulary speech recognition output.
Tony
On 30/10/14 11:49, Georg Schlunz wrote:
> Good day
>
> Regarding the HTK license, as specified at http://htk.eng.cam.ac.uk/docs/licen
se.shtml , I would like to know whether the following scenario is permitted:
>
> The HTK software (including HVite) sits on a server in-house in our organisati
on, as per license sections 2.1 and 2.3.
> The HTK software (including HVite) is never distributed to a commercial (or no
n-commercial) party, as per license section 2.2.
>
> We have written our own server-client software, where:
> a) the client records speech and sends the audio file to the server, which pas
ses it on to HVite (the server software and HTK sit on the same in-house machine
)
> b) HVite decodes the audio into text
> c) the server replies to the client with the decoded text and the client proce
sses the text somehow
>
> Naturally, the client software contains no HTK code; it only processes data pr
oduced by HTK.
>

> Therefore, may this client software and decoding SERVICE be sold commercially
(as long as we agree to license sections 2.4 and 2.5)?
>
> Thank you
> Georg Schlunz
>
-- ** Cantab is hiring: www.cantabResearch.com/openings ** -Dr A J Robinson, Founder, Cantab Research Ltd
Phone direct: 01223 778240 office: 01223 794497
Company reg no GB 05697423, VAT reg no 925606030
51 Canterbury Street, Cambridge, CB4 3QG, UK
From tonyr at cantabResearch.com Tue Nov 4 20:04:46 2014
From: tonyr at cantabResearch.com (Tony Robinson)
Date: Fri Dec 5 04:56:42 2014
Subject: [HTK-Users] HTK license agreement
In-Reply-To: <545241EC02000049000E3077@pta-emo.csir.co.za>
References: <545241EC02000049000E3077@pta-emo.csir.co.za>
Message-ID: <5459315E.9030409@cantabResearch.com>
I just saw this post - I hope I haven't also missed any replies.
It's been a while since I read the HTK licence, but from memory and past
commercial practices I believe that what you are proposing is entirely
acceptable according to the HTK licence.
In fact I think www.speechmatics.com uses HVite in exactly this way to
do some final tidying up of the large vocabulary speech recognition output.
Tony
On 30/10/14 11:49, Georg Schlunz wrote:
> Good day
>
> Regarding the HTK license, as specified at http://htk.eng.cam.ac.uk/docs/licen
se.shtml , I would like to know whether the following scenario is permitted:
>
> The HTK software (including HVite) sits on a server in-house in our organisati
on, as per license sections 2.1 and 2.3.
> The HTK software (including HVite) is never distributed to a commercial (or no
n-commercial) party, as per license section 2.2.
>
> We have written our own server-client software, where:
> a) the client records speech and sends the audio file to the server, which pas
ses it on to HVite (the server software and HTK sit on the same in-house machine
)
> b) HVite decodes the audio into text
> c) the server replies to the client with the decoded text and the client proce
sses the text somehow
>
> Naturally, the client software contains no HTK code; it only processes data pr
oduced by HTK.
>
> Therefore, may this client software and decoding SERVICE be sold commercially
(as long as we agree to license sections 2.4 and 2.5)?
>
> Thank you
> Georg Schlunz

>
-- ** Cantab is hiring: www.cantabResearch.com/openings ** -Dr A J Robinson, Founder, Cantab Research Ltd
Phone direct: 01223 778240 office: 01223 794497
Company reg no GB 05697423, VAT reg no 925606030
51 Canterbury Street, Cambridge, CB4 3QG, UK
From tonyr at cantabResearch.com Tue Nov 4 20:04:46 2014
From: tonyr at cantabResearch.com (Tony Robinson)
Date: Sat Dec 6 04:47:34 2014
Subject: [HTK-Users] HTK license agreement
In-Reply-To: <545241EC02000049000E3077@pta-emo.csir.co.za>
References: <545241EC02000049000E3077@pta-emo.csir.co.za>
Message-ID: <5459315E.9030409@cantabResearch.com>
I just saw this post - I hope I haven't also missed any replies.
It's been a while since I read the HTK licence, but from memory and past
commercial practices I believe that what you are proposing is entirely
acceptable according to the HTK licence.
In fact I think www.speechmatics.com uses HVite in exactly this way to
do some final tidying up of the large vocabulary speech recognition output.
Tony
On 30/10/14 11:49, Georg Schlunz wrote:
> Good day
>
> Regarding the HTK license, as specified at http://htk.eng.cam.ac.uk/docs/licen
se.shtml , I would like to know whether the following scenario is permitted:
>
> The HTK software (including HVite) sits on a server in-house in our organisati
on, as per license sections 2.1 and 2.3.
> The HTK software (including HVite) is never distributed to a commercial (or no
n-commercial) party, as per license section 2.2.
>
> We have written our own server-client software, where:
> a) the client records speech and sends the audio file to the server, which pas
ses it on to HVite (the server software and HTK sit on the same in-house machine
)
> b) HVite decodes the audio into text
> c) the server replies to the client with the decoded text and the client proce
sses the text somehow
>
> Naturally, the client software contains no HTK code; it only processes data pr
oduced by HTK.
>
> Therefore, may this client software and decoding SERVICE be sold commercially
(as long as we agree to license sections 2.4 and 2.5)?
>
> Thank you
> Georg Schlunz
>
-- ** Cantab is hiring: www.cantabResearch.com/openings ** -Dr A J Robinson, Founder, Cantab Research Ltd
Phone direct: 01223 778240 office: 01223 794497

Company reg no GB 05697423, VAT reg no 925606030


51 Canterbury Street, Cambridge, CB4 3QG, UK
From tonyr at cantabResearch.com Tue Nov 4 20:04:46 2014
From: tonyr at cantabResearch.com (Tony Robinson)
Date: Sun Dec 7 04:31:48 2014
Subject: [HTK-Users] HTK license agreement
In-Reply-To: <545241EC02000049000E3077@pta-emo.csir.co.za>
References: <545241EC02000049000E3077@pta-emo.csir.co.za>
Message-ID: <5459315E.9030409@cantabResearch.com>
I just saw this post - I hope I haven't also missed any replies.
It's been a while since I read the HTK licence, but from memory and past
commercial practices I believe that what you are proposing is entirely
acceptable according to the HTK licence.
In fact I think www.speechmatics.com uses HVite in exactly this way to
do some final tidying up of the large vocabulary speech recognition output.
Tony
On 30/10/14 11:49, Georg Schlunz wrote:
> Good day
>
> Regarding the HTK license, as specified at http://htk.eng.cam.ac.uk/docs/licen
se.shtml , I would like to know whether the following scenario is permitted:
>
> The HTK software (including HVite) sits on a server in-house in our organisati
on, as per license sections 2.1 and 2.3.
> The HTK software (including HVite) is never distributed to a commercial (or no
n-commercial) party, as per license section 2.2.
>
> We have written our own server-client software, where:
> a) the client records speech and sends the audio file to the server, which pas
ses it on to HVite (the server software and HTK sit on the same in-house machine
)
> b) HVite decodes the audio into text
> c) the server replies to the client with the decoded text and the client proce
sses the text somehow
>
> Naturally, the client software contains no HTK code; it only processes data pr
oduced by HTK.
>
> Therefore, may this client software and decoding SERVICE be sold commercially
(as long as we agree to license sections 2.4 and 2.5)?
>
> Thank you
> Georg Schlunz
>
-- ** Cantab is hiring: www.cantabResearch.com/openings ** -Dr A J Robinson, Founder, Cantab Research Ltd
Phone direct: 01223 778240 office: 01223 794497
Company reg no GB 05697423, VAT reg no 925606030
51 Canterbury Street, Cambridge, CB4 3QG, UK
From tonyr at cantabResearch.com Tue Nov 4 20:04:46 2014
From: tonyr at cantabResearch.com (Tony Robinson)

Date: Mon Dec 8 04:40:59 2014


Subject: [HTK-Users] HTK license agreement
In-Reply-To: <545241EC02000049000E3077@pta-emo.csir.co.za>
References: <545241EC02000049000E3077@pta-emo.csir.co.za>
Message-ID: <5459315E.9030409@cantabResearch.com>
I just saw this post - I hope I haven't also missed any replies.
It's been a while since I read the HTK licence, but from memory and past
commercial practices I believe that what you are proposing is entirely
acceptable according to the HTK licence.
In fact I think www.speechmatics.com uses HVite in exactly this way to
do some final tidying up of the large vocabulary speech recognition output.
Tony
On 30/10/14 11:49, Georg Schlunz wrote:
> Good day
>
> Regarding the HTK license, as specified at http://htk.eng.cam.ac.uk/docs/licen
se.shtml , I would like to know whether the following scenario is permitted:
>
> The HTK software (including HVite) sits on a server in-house in our organisati
on, as per license sections 2.1 and 2.3.
> The HTK software (including HVite) is never distributed to a commercial (or no
n-commercial) party, as per license section 2.2.
>
> We have written our own server-client software, where:
> a) the client records speech and sends the audio file to the server, which pas
ses it on to HVite (the server software and HTK sit on the same in-house machine
)
> b) HVite decodes the audio into text
> c) the server replies to the client with the decoded text and the client proce
sses the text somehow
>
> Naturally, the client software contains no HTK code; it only processes data pr
oduced by HTK.
>
> Therefore, may this client software and decoding SERVICE be sold commercially
(as long as we agree to license sections 2.4 and 2.5)?
>
> Thank you
> Georg Schlunz
>
-- ** Cantab is hiring: www.cantabResearch.com/openings ** -Dr A J Robinson, Founder, Cantab Research Ltd
Phone direct: 01223 778240 office: 01223 794497
Company reg no GB 05697423, VAT reg no 925606030
51 Canterbury Street, Cambridge, CB4 3QG, UK
From tonyr at cantabResearch.com Tue Nov 4 20:04:46 2014
From: tonyr at cantabResearch.com (Tony Robinson)
Date: Tue Dec 9 04:59:29 2014
Subject: [HTK-Users] HTK license agreement
In-Reply-To: <545241EC02000049000E3077@pta-emo.csir.co.za>
References: <545241EC02000049000E3077@pta-emo.csir.co.za>
Message-ID: <5459315E.9030409@cantabResearch.com>

I just saw this post - I hope I haven't also missed any replies.
It's been a while since I read the HTK licence, but from memory and past
commercial practices I believe that what you are proposing is entirely
acceptable according to the HTK licence.
In fact I think www.speechmatics.com uses HVite in exactly this way to
do some final tidying up of the large vocabulary speech recognition output.
Tony
On 30/10/14 11:49, Georg Schlunz wrote:
> Good day
>
> Regarding the HTK license, as specified at http://htk.eng.cam.ac.uk/docs/licen
se.shtml , I would like to know whether the following scenario is permitted:
>
> The HTK software (including HVite) sits on a server in-house in our organisati
on, as per license sections 2.1 and 2.3.
> The HTK software (including HVite) is never distributed to a commercial (or no
n-commercial) party, as per license section 2.2.
>
> We have written our own server-client software, where:
> a) the client records speech and sends the audio file to the server, which pas
ses it on to HVite (the server software and HTK sit on the same in-house machine
)
> b) HVite decodes the audio into text
> c) the server replies to the client with the decoded text and the client proce
sses the text somehow
>
> Naturally, the client software contains no HTK code; it only processes data pr
oduced by HTK.
>
> Therefore, may this client software and decoding SERVICE be sold commercially
(as long as we agree to license sections 2.4 and 2.5)?
>
> Thank you
> Georg Schlunz
>
-- ** Cantab is hiring: www.cantabResearch.com/openings ** -Dr A J Robinson, Founder, Cantab Research Ltd
Phone direct: 01223 778240 office: 01223 794497
Company reg no GB 05697423, VAT reg no 925606030
51 Canterbury Street, Cambridge, CB4 3QG, UK
From tonyr at cantabResearch.com Tue Nov 4 20:04:46 2014
From: tonyr at cantabResearch.com (Tony Robinson)
Date: Wed Dec 10 04:42:13 2014
Subject: [HTK-Users] HTK license agreement
In-Reply-To: <545241EC02000049000E3077@pta-emo.csir.co.za>
References: <545241EC02000049000E3077@pta-emo.csir.co.za>
Message-ID: <5459315E.9030409@cantabResearch.com>
I just saw this post - I hope I haven't also missed any replies.
It's been a while since I read the HTK licence, but from memory and past
commercial practices I believe that what you are proposing is entirely

acceptable according to the HTK licence.


In fact I think www.speechmatics.com uses HVite in exactly this way to
do some final tidying up of the large vocabulary speech recognition output.
Tony
On 30/10/14 11:49, Georg Schlunz wrote:
> Good day
>
> Regarding the HTK license, as specified at http://htk.eng.cam.ac.uk/docs/licen
se.shtml , I would like to know whether the following scenario is permitted:
>
> The HTK software (including HVite) sits on a server in-house in our organisati
on, as per license sections 2.1 and 2.3.
> The HTK software (including HVite) is never distributed to a commercial (or no
n-commercial) party, as per license section 2.2.
>
> We have written our own server-client software, where:
> a) the client records speech and sends the audio file to the server, which pas
ses it on to HVite (the server software and HTK sit on the same in-house machine
)
> b) HVite decodes the audio into text
> c) the server replies to the client with the decoded text and the client proce
sses the text somehow
>
> Naturally, the client software contains no HTK code; it only processes data pr
oduced by HTK.
>
> Therefore, may this client software and decoding SERVICE be sold commercially
(as long as we agree to license sections 2.4 and 2.5)?
>
> Thank you
> Georg Schlunz
>
-- ** Cantab is hiring: www.cantabResearch.com/openings ** -Dr A J Robinson, Founder, Cantab Research Ltd
Phone direct: 01223 778240 office: 01223 794497
Company reg no GB 05697423, VAT reg no 925606030
51 Canterbury Street, Cambridge, CB4 3QG, UK
From tonyr at cantabResearch.com Tue Nov 4 20:04:46 2014
From: tonyr at cantabResearch.com (Tony Robinson)
Date: Thu Dec 11 04:56:12 2014
Subject: [HTK-Users] HTK license agreement
In-Reply-To: <545241EC02000049000E3077@pta-emo.csir.co.za>
References: <545241EC02000049000E3077@pta-emo.csir.co.za>
Message-ID: <5459315E.9030409@cantabResearch.com>
I just saw this post - I hope I haven't also missed any replies.
It's been a while since I read the HTK licence, but from memory and past
commercial practices I believe that what you are proposing is entirely
acceptable according to the HTK licence.
In fact I think www.speechmatics.com uses HVite in exactly this way to
do some final tidying up of the large vocabulary speech recognition output.

Tony
On 30/10/14 11:49, Georg Schlunz wrote:
> Good day
>
> Regarding the HTK license, as specified at http://htk.eng.cam.ac.uk/docs/licen
se.shtml , I would like to know whether the following scenario is permitted:
>
> The HTK software (including HVite) sits on a server in-house in our organisati
on, as per license sections 2.1 and 2.3.
> The HTK software (including HVite) is never distributed to a commercial (or no
n-commercial) party, as per license section 2.2.
>
> We have written our own server-client software, where:
> a) the client records speech and sends the audio file to the server, which pas
ses it on to HVite (the server software and HTK sit on the same in-house machine
)
> b) HVite decodes the audio into text
> c) the server replies to the client with the decoded text and the client proce
sses the text somehow
>
> Naturally, the client software contains no HTK code; it only processes data pr
oduced by HTK.
>
> Therefore, may this client software and decoding SERVICE be sold commercially
(as long as we agree to license sections 2.4 and 2.5)?
>
> Thank you
> Georg Schlunz
>
-- ** Cantab is hiring: www.cantabResearch.com/openings ** -Dr A J Robinson, Founder, Cantab Research Ltd
Phone direct: 01223 778240 office: 01223 794497
Company reg no GB 05697423, VAT reg no 925606030
51 Canterbury Street, Cambridge, CB4 3QG, UK
From tonyr at cantabResearch.com Tue Nov 4 20:04:46 2014
From: tonyr at cantabResearch.com (Tony Robinson)
Date: Fri Dec 12 04:58:45 2014
Subject: [HTK-Users] HTK license agreement
In-Reply-To: <545241EC02000049000E3077@pta-emo.csir.co.za>
References: <545241EC02000049000E3077@pta-emo.csir.co.za>
Message-ID: <5459315E.9030409@cantabResearch.com>
I just saw this post - I hope I haven't also missed any replies.
It's been a while since I read the HTK licence, but from memory and past
commercial practices I believe that what you are proposing is entirely
acceptable according to the HTK licence.
In fact I think www.speechmatics.com uses HVite in exactly this way to
do some final tidying up of the large vocabulary speech recognition output.
Tony
On 30/10/14 11:49, Georg Schlunz wrote:
> Good day

>
> Regarding the HTK license, as specified at http://htk.eng.cam.ac.uk/docs/licen
se.shtml , I would like to know whether the following scenario is permitted:
>
> The HTK software (including HVite) sits on a server in-house in our organisati
on, as per license sections 2.1 and 2.3.
> The HTK software (including HVite) is never distributed to a commercial (or no
n-commercial) party, as per license section 2.2.
>
> We have written our own server-client software, where:
> a) the client records speech and sends the audio file to the server, which pas
ses it on to HVite (the server software and HTK sit on the same in-house machine
)
> b) HVite decodes the audio into text
> c) the server replies to the client with the decoded text and the client proce
sses the text somehow
>
> Naturally, the client software contains no HTK code; it only processes data pr
oduced by HTK.
>
> Therefore, may this client software and decoding SERVICE be sold commercially
(as long as we agree to license sections 2.4 and 2.5)?
>
> Thank you
> Georg Schlunz
>
-- ** Cantab is hiring: www.cantabResearch.com/openings ** -Dr A J Robinson, Founder, Cantab Research Ltd
Phone direct: 01223 778240 office: 01223 794497
Company reg no GB 05697423, VAT reg no 925606030
51 Canterbury Street, Cambridge, CB4 3QG, UK
From tonyr at cantabResearch.com Tue Nov 4 20:04:46 2014
From: tonyr at cantabResearch.com (Tony Robinson)
Date: Sat Dec 13 05:02:45 2014
Subject: [HTK-Users] HTK license agreement
In-Reply-To: <545241EC02000049000E3077@pta-emo.csir.co.za>
References: <545241EC02000049000E3077@pta-emo.csir.co.za>
Message-ID: <5459315E.9030409@cantabResearch.com>
I just saw this post - I hope I haven't also missed any replies.
It's been a while since I read the HTK licence, but from memory and past
commercial practices I believe that what you are proposing is entirely
acceptable according to the HTK licence.
In fact I think www.speechmatics.com uses HVite in exactly this way to
do some final tidying up of the large vocabulary speech recognition output.
Tony
On 30/10/14 11:49, Georg Schlunz wrote:
> Good day
>
> Regarding the HTK license, as specified at http://htk.eng.cam.ac.uk/docs/licen
se.shtml , I would like to know whether the following scenario is permitted:
>
> The HTK software (including HVite) sits on a server in-house in our organisati

on, as per license sections 2.1 and 2.3.


> The HTK software (including HVite) is never distributed to a commercial (or no
n-commercial) party, as per license section 2.2.
>
> We have written our own server-client software, where:
> a) the client records speech and sends the audio file to the server, which pas
ses it on to HVite (the server software and HTK sit on the same in-house machine
)
> b) HVite decodes the audio into text
> c) the server replies to the client with the decoded text and the client proce
sses the text somehow
>
> Naturally, the client software contains no HTK code; it only processes data pr
oduced by HTK.
>
> Therefore, may this client software and decoding SERVICE be sold commercially
(as long as we agree to license sections 2.4 and 2.5)?
>
> Thank you
> Georg Schlunz
>
-- ** Cantab is hiring: www.cantabResearch.com/openings ** -Dr A J Robinson, Founder, Cantab Research Ltd
Phone direct: 01223 778240 office: 01223 794497
Company reg no GB 05697423, VAT reg no 925606030
51 Canterbury Street, Cambridge, CB4 3QG, UK
From tonyr at cantabResearch.com Tue Nov 4 20:04:46 2014
From: tonyr at cantabResearch.com (Tony Robinson)
Date: Tue Dec 16 04:06:55 2014
Subject: [HTK-Users] HTK license agreement
In-Reply-To: <545241EC02000049000E3077@pta-emo.csir.co.za>
References: <545241EC02000049000E3077@pta-emo.csir.co.za>
Message-ID: <5459315E.9030409@cantabResearch.com>
I just saw this post - I hope I haven't also missed any replies.
It's been a while since I read the HTK licence, but from memory and past
commercial practices I believe that what you are proposing is entirely
acceptable according to the HTK licence.
In fact I think www.speechmatics.com uses HVite in exactly this way to
do some final tidying up of the large vocabulary speech recognition output.
Tony
On 30/10/14 11:49, Georg Schlunz wrote:
> Good day
>
> Regarding the HTK license, as specified at http://htk.eng.cam.ac.uk/docs/licen
se.shtml , I would like to know whether the following scenario is permitted:
>
> The HTK software (including HVite) sits on a server in-house in our organisati
on, as per license sections 2.1 and 2.3.
> The HTK software (including HVite) is never distributed to a commercial (or no
n-commercial) party, as per license section 2.2.
>
> We have written our own server-client software, where:

> a) the client records speech and sends the audio file to the server, which pas
ses it on to HVite (the server software and HTK sit on the same in-house machine
)
> b) HVite decodes the audio into text
> c) the server replies to the client with the decoded text and the client proce
sses the text somehow
>
> Naturally, the client software contains no HTK code; it only processes data pr
oduced by HTK.
>
> Therefore, may this client software and decoding SERVICE be sold commercially
(as long as we agree to license sections 2.4 and 2.5)?
>
> Thank you
> Georg Schlunz
>
-- ** Cantab is hiring: www.cantabResearch.com/openings ** -Dr A J Robinson, Founder, Cantab Research Ltd
Phone direct: 01223 778240 office: 01223 794497
Company reg no GB 05697423, VAT reg no 925606030
51 Canterbury Street, Cambridge, CB4 3QG, UK
From tonyr at cantabResearch.com Tue Nov 4 20:04:46 2014
From: tonyr at cantabResearch.com (Tony Robinson)
Date: Wed Dec 17 04:41:44 2014
Subject: [HTK-Users] HTK license agreement
In-Reply-To: <545241EC02000049000E3077@pta-emo.csir.co.za>
References: <545241EC02000049000E3077@pta-emo.csir.co.za>
Message-ID: <5459315E.9030409@cantabResearch.com>
I just saw this post - I hope I haven't also missed any replies.
It's been a while since I read the HTK licence, but from memory and past
commercial practices I believe that what you are proposing is entirely
acceptable according to the HTK licence.
In fact I think www.speechmatics.com uses HVite in exactly this way to
do some final tidying up of the large vocabulary speech recognition output.
Tony
On 30/10/14 11:49, Georg Schlunz wrote:
> Good day
>
> Regarding the HTK license, as specified at http://htk.eng.cam.ac.uk/docs/licen
se.shtml , I would like to know whether the following scenario is permitted:
>
> The HTK software (including HVite) sits on a server in-house in our organisati
on, as per license sections 2.1 and 2.3.
> The HTK software (including HVite) is never distributed to a commercial (or no
n-commercial) party, as per license section 2.2.
>
> We have written our own server-client software, where:
> a) the client records speech and sends the audio file to the server, which pas
ses it on to HVite (the server software and HTK sit on the same in-house machine
)
> b) HVite decodes the audio into text
> c) the server replies to the client with the decoded text and the client proce

sses the text somehow


>
> Naturally, the client software contains no HTK code; it only processes data pr
oduced by HTK.
>
> Therefore, may this client software and decoding SERVICE be sold commercially
(as long as we agree to license sections 2.4 and 2.5)?
>
> Thank you
> Georg Schlunz
>
-- ** Cantab is hiring: www.cantabResearch.com/openings ** -Dr A J Robinson, Founder, Cantab Research Ltd
Phone direct: 01223 778240 office: 01223 794497
Company reg no GB 05697423, VAT reg no 925606030
51 Canterbury Street, Cambridge, CB4 3QG, UK
From tonyr at cantabResearch.com Tue Nov 4 20:04:46 2014
From: tonyr at cantabResearch.com (Tony Robinson)
Date: Thu Dec 18 04:39:00 2014
Subject: [HTK-Users] HTK license agreement
In-Reply-To: <545241EC02000049000E3077@pta-emo.csir.co.za>
References: <545241EC02000049000E3077@pta-emo.csir.co.za>
Message-ID: <5459315E.9030409@cantabResearch.com>
I just saw this post - I hope I haven't also missed any replies.
It's been a while since I read the HTK licence, but from memory and past
commercial practices I believe that what you are proposing is entirely
acceptable according to the HTK licence.
In fact I think www.speechmatics.com uses HVite in exactly this way to
do some final tidying up of the large vocabulary speech recognition output.
Tony
On 30/10/14 11:49, Georg Schlunz wrote:
> Good day
>
> Regarding the HTK license, as specified at http://htk.eng.cam.ac.uk/docs/licen
se.shtml , I would like to know whether the following scenario is permitted:
>
> The HTK software (including HVite) sits on a server in-house in our organisati
on, as per license sections 2.1 and 2.3.
> The HTK software (including HVite) is never distributed to a commercial (or no
n-commercial) party, as per license section 2.2.
>
> We have written our own server-client software, where:
> a) the client records speech and sends the audio file to the server, which pas
ses it on to HVite (the server software and HTK sit on the same in-house machine
)
> b) HVite decodes the audio into text
> c) the server replies to the client with the decoded text and the client proce
sses the text somehow
>
> Naturally, the client software contains no HTK code; it only processes data pr
oduced by HTK.
>

> Therefore, may this client software and decoding SERVICE be sold commercially
(as long as we agree to license sections 2.4 and 2.5)?
>
> Thank you
> Georg Schlunz
>
-- ** Cantab is hiring: www.cantabResearch.com/openings ** -Dr A J Robinson, Founder, Cantab Research Ltd
Phone direct: 01223 778240 office: 01223 794497
Company reg no GB 05697423, VAT reg no 925606030
51 Canterbury Street, Cambridge, CB4 3QG, UK
From tonyr at cantabResearch.com Tue Nov 4 20:04:46 2014
From: tonyr at cantabResearch.com (Tony Robinson)
Date: Fri Dec 19 04:43:00 2014
Subject: [HTK-Users] HTK license agreement
In-Reply-To: <545241EC02000049000E3077@pta-emo.csir.co.za>
References: <545241EC02000049000E3077@pta-emo.csir.co.za>
Message-ID: <5459315E.9030409@cantabResearch.com>
I just saw this post - I hope I haven't also missed any replies.
It's been a while since I read the HTK licence, but from memory and past
commercial practices I believe that what you are proposing is entirely
acceptable according to the HTK licence.
In fact I think www.speechmatics.com uses HVite in exactly this way to
do some final tidying up of the large vocabulary speech recognition output.
Tony
On 30/10/14 11:49, Georg Schlunz wrote:
> Good day
>
> Regarding the HTK license, as specified at http://htk.eng.cam.ac.uk/docs/licen
se.shtml , I would like to know whether the following scenario is permitted:
>
> The HTK software (including HVite) sits on a server in-house in our organisati
on, as per license sections 2.1 and 2.3.
> The HTK software (including HVite) is never distributed to a commercial (or no
n-commercial) party, as per license section 2.2.
>
> We have written our own server-client software, where:
> a) the client records speech and sends the audio file to the server, which pas
ses it on to HVite (the server software and HTK sit on the same in-house machine
)
> b) HVite decodes the audio into text
> c) the server replies to the client with the decoded text and the client proce
sses the text somehow
>
> Naturally, the client software contains no HTK code; it only processes data pr
oduced by HTK.
>
> Therefore, may this client software and decoding SERVICE be sold commercially
(as long as we agree to license sections 2.4 and 2.5)?
>
> Thank you
> Georg Schlunz

>
-- ** Cantab is hiring: www.cantabResearch.com/openings ** -Dr A J Robinson, Founder, Cantab Research Ltd
Phone direct: 01223 778240 office: 01223 794497
Company reg no GB 05697423, VAT reg no 925606030
51 Canterbury Street, Cambridge, CB4 3QG, UK
From tonyr at cantabResearch.com Tue Nov 4 20:04:46 2014
From: tonyr at cantabResearch.com (Tony Robinson)
Date: Sat Dec 20 04:42:30 2014
Subject: [HTK-Users] HTK license agreement
In-Reply-To: <545241EC02000049000E3077@pta-emo.csir.co.za>
References: <545241EC02000049000E3077@pta-emo.csir.co.za>
Message-ID: <5459315E.9030409@cantabResearch.com>
I just saw this post - I hope I haven't also missed any replies.
It's been a while since I read the HTK licence, but from memory and past
commercial practices I believe that what you are proposing is entirely
acceptable according to the HTK licence.
In fact I think www.speechmatics.com uses HVite in exactly this way to
do some final tidying up of the large vocabulary speech recognition output.
Tony
On 30/10/14 11:49, Georg Schlunz wrote:
> Good day
>
> Regarding the HTK license, as specified at http://htk.eng.cam.ac.uk/docs/licen
se.shtml , I would like to know whether the following scenario is permitted:
>
> The HTK software (including HVite) sits on a server in-house in our organisati
on, as per license sections 2.1 and 2.3.
> The HTK software (including HVite) is never distributed to a commercial (or no
n-commercial) party, as per license section 2.2.
>
> We have written our own server-client software, where:
> a) the client records speech and sends the audio file to the server, which pas
ses it on to HVite (the server software and HTK sit on the same in-house machine
)
> b) HVite decodes the audio into text
> c) the server replies to the client with the decoded text and the client proce
sses the text somehow
>
> Naturally, the client software contains no HTK code; it only processes data pr
oduced by HTK.
>
> Therefore, may this client software and decoding SERVICE be sold commercially
(as long as we agree to license sections 2.4 and 2.5)?
>
> Thank you
> Georg Schlunz
>
-- ** Cantab is hiring: www.cantabResearch.com/openings ** -Dr A J Robinson, Founder, Cantab Research Ltd
Phone direct: 01223 778240 office: 01223 794497

Company reg no GB 05697423, VAT reg no 925606030


51 Canterbury Street, Cambridge, CB4 3QG, UK
From tonyr at cantabResearch.com Tue Nov 4 20:04:46 2014
From: tonyr at cantabResearch.com (Tony Robinson)
Date: Sun Dec 21 04:19:08 2014
Subject: [HTK-Users] HTK license agreement
In-Reply-To: <545241EC02000049000E3077@pta-emo.csir.co.za>
References: <545241EC02000049000E3077@pta-emo.csir.co.za>
Message-ID: <5459315E.9030409@cantabResearch.com>
I just saw this post - I hope I haven't also missed any replies.
It's been a while since I read the HTK licence, but from memory and past
commercial practices I believe that what you are proposing is entirely
acceptable according to the HTK licence.
In fact I think www.speechmatics.com uses HVite in exactly this way to
do some final tidying up of the large vocabulary speech recognition output.
Tony
On 30/10/14 11:49, Georg Schlunz wrote:
> Good day
>
> Regarding the HTK license, as specified at http://htk.eng.cam.ac.uk/docs/licen
se.shtml , I would like to know whether the following scenario is permitted:
>
> The HTK software (including HVite) sits on a server in-house in our organisati
on, as per license sections 2.1 and 2.3.
> The HTK software (including HVite) is never distributed to a commercial (or no
n-commercial) party, as per license section 2.2.
>
> We have written our own server-client software, where:
> a) the client records speech and sends the audio file to the server, which pas
ses it on to HVite (the server software and HTK sit on the same in-house machine
)
> b) HVite decodes the audio into text
> c) the server replies to the client with the decoded text and the client proce
sses the text somehow
>
> Naturally, the client software contains no HTK code; it only processes data pr
oduced by HTK.
>
> Therefore, may this client software and decoding SERVICE be sold commercially
(as long as we agree to license sections 2.4 and 2.5)?
>
> Thank you
> Georg Schlunz
>
-- ** Cantab is hiring: www.cantabResearch.com/openings ** -Dr A J Robinson, Founder, Cantab Research Ltd
Phone direct: 01223 778240 office: 01223 794497
Company reg no GB 05697423, VAT reg no 925606030
51 Canterbury Street, Cambridge, CB4 3QG, UK
From tonyr at cantabResearch.com Tue Nov 4 20:04:46 2014
From: tonyr at cantabResearch.com (Tony Robinson)

Date: Mon Dec 22 04:21:02 2014


Subject: [HTK-Users] HTK license agreement
In-Reply-To: <545241EC02000049000E3077@pta-emo.csir.co.za>
References: <545241EC02000049000E3077@pta-emo.csir.co.za>
Message-ID: <5459315E.9030409@cantabResearch.com>
I just saw this post - I hope I haven't also missed any replies.
It's been a while since I read the HTK licence, but from memory and past
commercial practices I believe that what you are proposing is entirely
acceptable according to the HTK licence.
In fact I think www.speechmatics.com uses HVite in exactly this way to
do some final tidying up of the large vocabulary speech recognition output.
Tony
On 30/10/14 11:49, Georg Schlunz wrote:
> Good day
>
> Regarding the HTK license, as specified at http://htk.eng.cam.ac.uk/docs/licen
se.shtml , I would like to know whether the following scenario is permitted:
>
> The HTK software (including HVite) sits on a server in-house in our organisati
on, as per license sections 2.1 and 2.3.
> The HTK software (including HVite) is never distributed to a commercial (or no
n-commercial) party, as per license section 2.2.
>
> We have written our own server-client software, where:
> a) the client records speech and sends the audio file to the server, which pas
ses it on to HVite (the server software and HTK sit on the same in-house machine
)
> b) HVite decodes the audio into text
> c) the server replies to the client with the decoded text and the client proce
sses the text somehow
>
> Naturally, the client software contains no HTK code; it only processes data pr
oduced by HTK.
>
> Therefore, may this client software and decoding SERVICE be sold commercially
(as long as we agree to license sections 2.4 and 2.5)?
>
> Thank you
> Georg Schlunz
>
-- ** Cantab is hiring: www.cantabResearch.com/openings ** -Dr A J Robinson, Founder, Cantab Research Ltd
Phone direct: 01223 778240 office: 01223 794497
Company reg no GB 05697423, VAT reg no 925606030
51 Canterbury Street, Cambridge, CB4 3QG, UK
From tonyr at cantabResearch.com Tue Nov 4 20:04:46 2014
From: tonyr at cantabResearch.com (Tony Robinson)
Date: Tue Dec 23 04:43:46 2014
Subject: [HTK-Users] HTK license agreement
In-Reply-To: <545241EC02000049000E3077@pta-emo.csir.co.za>
References: <545241EC02000049000E3077@pta-emo.csir.co.za>
Message-ID: <5459315E.9030409@cantabResearch.com>

I just saw this post - I hope I haven't also missed any replies.
It's been a while since I read the HTK licence, but from memory and past
commercial practices I believe that what you are proposing is entirely
acceptable according to the HTK licence.
In fact I think www.speechmatics.com uses HVite in exactly this way to
do some final tidying up of the large vocabulary speech recognition output.
Tony
On 30/10/14 11:49, Georg Schlunz wrote:
> Good day
>
> Regarding the HTK license, as specified at http://htk.eng.cam.ac.uk/docs/licen
se.shtml , I would like to know whether the following scenario is permitted:
>
> The HTK software (including HVite) sits on a server in-house in our organisati
on, as per license sections 2.1 and 2.3.
> The HTK software (including HVite) is never distributed to a commercial (or no
n-commercial) party, as per license section 2.2.
>
> We have written our own server-client software, where:
> a) the client records speech and sends the audio file to the server, which pas
ses it on to HVite (the server software and HTK sit on the same in-house machine
)
> b) HVite decodes the audio into text
> c) the server replies to the client with the decoded text and the client proce
sses the text somehow
>
> Naturally, the client software contains no HTK code; it only processes data pr
oduced by HTK.
>
> Therefore, may this client software and decoding SERVICE be sold commercially
(as long as we agree to license sections 2.4 and 2.5)?
>
> Thank you
> Georg Schlunz
>
-- ** Cantab is hiring: www.cantabResearch.com/openings ** -Dr A J Robinson, Founder, Cantab Research Ltd
Phone direct: 01223 778240 office: 01223 794497
Company reg no GB 05697423, VAT reg no 925606030
51 Canterbury Street, Cambridge, CB4 3QG, UK
From tonyr at cantabResearch.com Tue Nov 4 20:04:46 2014
From: tonyr at cantabResearch.com (Tony Robinson)
Date: Wed Dec 24 04:50:56 2014
Subject: [HTK-Users] HTK license agreement
In-Reply-To: <545241EC02000049000E3077@pta-emo.csir.co.za>
References: <545241EC02000049000E3077@pta-emo.csir.co.za>
Message-ID: <5459315E.9030409@cantabResearch.com>
I just saw this post - I hope I haven't also missed any replies.
It's been a while since I read the HTK licence, but from memory and past
commercial practices I believe that what you are proposing is entirely

acceptable according to the HTK licence.


In fact I think www.speechmatics.com uses HVite in exactly this way to
do some final tidying up of the large vocabulary speech recognition output.
Tony
On 30/10/14 11:49, Georg Schlunz wrote:
> Good day
>
> Regarding the HTK license, as specified at http://htk.eng.cam.ac.uk/docs/licen
se.shtml , I would like to know whether the following scenario is permitted:
>
> The HTK software (including HVite) sits on a server in-house in our organisati
on, as per license sections 2.1 and 2.3.
> The HTK software (including HVite) is never distributed to a commercial (or no
n-commercial) party, as per license section 2.2.
>
> We have written our own server-client software, where:
> a) the client records speech and sends the audio file to the server, which pas
ses it on to HVite (the server software and HTK sit on the same in-house machine
)
> b) HVite decodes the audio into text
> c) the server replies to the client with the decoded text and the client proce
sses the text somehow
>
> Naturally, the client software contains no HTK code; it only processes data pr
oduced by HTK.
>
> Therefore, may this client software and decoding SERVICE be sold commercially
(as long as we agree to license sections 2.4 and 2.5)?
>
> Thank you
> Georg Schlunz
>
-- ** Cantab is hiring: www.cantabResearch.com/openings ** -Dr A J Robinson, Founder, Cantab Research Ltd
Phone direct: 01223 778240 office: 01223 794497
Company reg no GB 05697423, VAT reg no 925606030
51 Canterbury Street, Cambridge, CB4 3QG, UK
From tonyr at cantabResearch.com Tue Nov 4 20:04:46 2014
From: tonyr at cantabResearch.com (Tony Robinson)
Date: Thu Dec 25 04:29:40 2014
Subject: [HTK-Users] HTK license agreement
In-Reply-To: <545241EC02000049000E3077@pta-emo.csir.co.za>
References: <545241EC02000049000E3077@pta-emo.csir.co.za>
Message-ID: <5459315E.9030409@cantabResearch.com>
I just saw this post - I hope I haven't also missed any replies.
It's been a while since I read the HTK licence, but from memory and past
commercial practices I believe that what you are proposing is entirely
acceptable according to the HTK licence.
In fact I think www.speechmatics.com uses HVite in exactly this way to
do some final tidying up of the large vocabulary speech recognition output.

Tony
On 30/10/14 11:49, Georg Schlunz wrote:
> Good day
>
> Regarding the HTK license, as specified at http://htk.eng.cam.ac.uk/docs/licen
se.shtml , I would like to know whether the following scenario is permitted:
>
> The HTK software (including HVite) sits on a server in-house in our organisati
on, as per license sections 2.1 and 2.3.
> The HTK software (including HVite) is never distributed to a commercial (or no
n-commercial) party, as per license section 2.2.
>
> We have written our own server-client software, where:
> a) the client records speech and sends the audio file to the server, which pas
ses it on to HVite (the server software and HTK sit on the same in-house machine
)
> b) HVite decodes the audio into text
> c) the server replies to the client with the decoded text and the client proce
sses the text somehow
>
> Naturally, the client software contains no HTK code; it only processes data pr
oduced by HTK.
>
> Therefore, may this client software and decoding SERVICE be sold commercially
(as long as we agree to license sections 2.4 and 2.5)?
>
> Thank you
> Georg Schlunz
>
-- ** Cantab is hiring: www.cantabResearch.com/openings ** -Dr A J Robinson, Founder, Cantab Research Ltd
Phone direct: 01223 778240 office: 01223 794497
Company reg no GB 05697423, VAT reg no 925606030
51 Canterbury Street, Cambridge, CB4 3QG, UK
From tonyr at cantabResearch.com Tue Nov 4 20:04:46 2014
From: tonyr at cantabResearch.com (Tony Robinson)
Date: Fri Dec 26 04:18:56 2014
Subject: [HTK-Users] HTK license agreement
In-Reply-To: <545241EC02000049000E3077@pta-emo.csir.co.za>
References: <545241EC02000049000E3077@pta-emo.csir.co.za>
Message-ID: <5459315E.9030409@cantabResearch.com>
I just saw this post - I hope I haven't also missed any replies.
It's been a while since I read the HTK licence, but from memory and past
commercial practices I believe that what you are proposing is entirely
acceptable according to the HTK licence.
In fact I think www.speechmatics.com uses HVite in exactly this way to
do some final tidying up of the large vocabulary speech recognition output.
Tony
On 30/10/14 11:49, Georg Schlunz wrote:
> Good day

>
> Regarding the HTK license, as specified at http://htk.eng.cam.ac.uk/docs/licen
se.shtml , I would like to know whether the following scenario is permitted:
>
> The HTK software (including HVite) sits on a server in-house in our organisati
on, as per license sections 2.1 and 2.3.
> The HTK software (including HVite) is never distributed to a commercial (or no
n-commercial) party, as per license section 2.2.
>
> We have written our own server-client software, where:
> a) the client records speech and sends the audio file to the server, which pas
ses it on to HVite (the server software and HTK sit on the same in-house machine
)
> b) HVite decodes the audio into text
> c) the server replies to the client with the decoded text and the client proce
sses the text somehow
>
> Naturally, the client software contains no HTK code; it only processes data pr
oduced by HTK.
>
> Therefore, may this client software and decoding SERVICE be sold commercially
(as long as we agree to license sections 2.4 and 2.5)?
>
> Thank you
> Georg Schlunz
>
-- ** Cantab is hiring: www.cantabResearch.com/openings ** -Dr A J Robinson, Founder, Cantab Research Ltd
Phone direct: 01223 778240 office: 01223 794497
Company reg no GB 05697423, VAT reg no 925606030
51 Canterbury Street, Cambridge, CB4 3QG, UK
From tonyr at cantabResearch.com Tue Nov 4 20:04:46 2014
From: tonyr at cantabResearch.com (Tony Robinson)
Date: Sat Dec 27 04:18:41 2014
Subject: [HTK-Users] HTK license agreement
In-Reply-To: <545241EC02000049000E3077@pta-emo.csir.co.za>
References: <545241EC02000049000E3077@pta-emo.csir.co.za>
Message-ID: <5459315E.9030409@cantabResearch.com>
I just saw this post - I hope I haven't also missed any replies.
It's been a while since I read the HTK licence, but from memory and past
commercial practices I believe that what you are proposing is entirely
acceptable according to the HTK licence.
In fact I think www.speechmatics.com uses HVite in exactly this way to
do some final tidying up of the large vocabulary speech recognition output.
Tony
On 30/10/14 11:49, Georg Schlunz wrote:
> Good day
>
> Regarding the HTK license, as specified at http://htk.eng.cam.ac.uk/docs/licen
se.shtml , I would like to know whether the following scenario is permitted:
>
> The HTK software (including HVite) sits on a server in-house in our organisati

on, as per license sections 2.1 and 2.3.


> The HTK software (including HVite) is never distributed to a commercial (or no
n-commercial) party, as per license section 2.2.
>
> We have written our own server-client software, where:
> a) the client records speech and sends the audio file to the server, which pas
ses it on to HVite (the server software and HTK sit on the same in-house machine
)
> b) HVite decodes the audio into text
> c) the server replies to the client with the decoded text and the client proce
sses the text somehow
>
> Naturally, the client software contains no HTK code; it only processes data pr
oduced by HTK.
>
> Therefore, may this client software and decoding SERVICE be sold commercially
(as long as we agree to license sections 2.4 and 2.5)?
>
> Thank you
> Georg Schlunz
>
-- ** Cantab is hiring: www.cantabResearch.com/openings ** -Dr A J Robinson, Founder, Cantab Research Ltd
Phone direct: 01223 778240 office: 01223 794497
Company reg no GB 05697423, VAT reg no 925606030
51 Canterbury Street, Cambridge, CB4 3QG, UK
From tonyr at cantabResearch.com Tue Nov 4 20:04:46 2014
From: tonyr at cantabResearch.com (Tony Robinson)
Date: Sun Dec 28 04:37:35 2014
Subject: [HTK-Users] HTK license agreement
In-Reply-To: <545241EC02000049000E3077@pta-emo.csir.co.za>
References: <545241EC02000049000E3077@pta-emo.csir.co.za>
Message-ID: <5459315E.9030409@cantabResearch.com>
I just saw this post - I hope I haven't also missed any replies.
It's been a while since I read the HTK licence, but from memory and past
commercial practices I believe that what you are proposing is entirely
acceptable according to the HTK licence.
In fact I think www.speechmatics.com uses HVite in exactly this way to
do some final tidying up of the large vocabulary speech recognition output.
Tony
On 30/10/14 11:49, Georg Schlunz wrote:
> Good day
>
> Regarding the HTK license, as specified at http://htk.eng.cam.ac.uk/docs/licen
se.shtml , I would like to know whether the following scenario is permitted:
>
> The HTK software (including HVite) sits on a server in-house in our organisati
on, as per license sections 2.1 and 2.3.
> The HTK software (including HVite) is never distributed to a commercial (or no
n-commercial) party, as per license section 2.2.
>
> We have written our own server-client software, where:

> a) the client records speech and sends the audio file to the server, which pas
ses it on to HVite (the server software and HTK sit on the same in-house machine
)
> b) HVite decodes the audio into text
> c) the server replies to the client with the decoded text and the client proce
sses the text somehow
>
> Naturally, the client software contains no HTK code; it only processes data pr
oduced by HTK.
>
> Therefore, may this client software and decoding SERVICE be sold commercially
(as long as we agree to license sections 2.4 and 2.5)?
>
> Thank you
> Georg Schlunz
>
-- ** Cantab is hiring: www.cantabResearch.com/openings ** -Dr A J Robinson, Founder, Cantab Research Ltd
Phone direct: 01223 778240 office: 01223 794497
Company reg no GB 05697423, VAT reg no 925606030
51 Canterbury Street, Cambridge, CB4 3QG, UK
From tonyr at cantabResearch.com Tue Nov 4 20:04:46 2014
From: tonyr at cantabResearch.com (Tony Robinson)
Date: Mon Dec 29 04:38:18 2014
Subject: [HTK-Users] HTK license agreement
In-Reply-To: <545241EC02000049000E3077@pta-emo.csir.co.za>
References: <545241EC02000049000E3077@pta-emo.csir.co.za>
Message-ID: <5459315E.9030409@cantabResearch.com>
I just saw this post - I hope I haven't also missed any replies.
It's been a while since I read the HTK licence, but from memory and past
commercial practices I believe that what you are proposing is entirely
acceptable according to the HTK licence.
In fact I think www.speechmatics.com uses HVite in exactly this way to
do some final tidying up of the large vocabulary speech recognition output.
Tony
On 30/10/14 11:49, Georg Schlunz wrote:
> Good day
>
> Regarding the HTK license, as specified at http://htk.eng.cam.ac.uk/docs/licen
se.shtml , I would like to know whether the following scenario is permitted:
>
> The HTK software (including HVite) sits on a server in-house in our organisati
on, as per license sections 2.1 and 2.3.
> The HTK software (including HVite) is never distributed to a commercial (or no
n-commercial) party, as per license section 2.2.
>
> We have written our own server-client software, where:
> a) the client records speech and sends the audio file to the server, which pas
ses it on to HVite (the server software and HTK sit on the same in-house machine
)
> b) HVite decodes the audio into text
> c) the server replies to the client with the decoded text and the client proce

sses the text somehow


>
> Naturally, the client software contains no HTK code; it only processes data pr
oduced by HTK.
>
> Therefore, may this client software and decoding SERVICE be sold commercially
(as long as we agree to license sections 2.4 and 2.5)?
>
> Thank you
> Georg Schlunz
>
-- ** Cantab is hiring: www.cantabResearch.com/openings ** -Dr A J Robinson, Founder, Cantab Research Ltd
Phone direct: 01223 778240 office: 01223 794497
Company reg no GB 05697423, VAT reg no 925606030
51 Canterbury Street, Cambridge, CB4 3QG, UK
From tonyr at cantabResearch.com Tue Nov 4 20:04:46 2014
From: tonyr at cantabResearch.com (Tony Robinson)
Date: Tue Dec 30 04:54:18 2014
Subject: [HTK-Users] HTK license agreement
In-Reply-To: <545241EC02000049000E3077@pta-emo.csir.co.za>
References: <545241EC02000049000E3077@pta-emo.csir.co.za>
Message-ID: <5459315E.9030409@cantabResearch.com>
I just saw this post - I hope I haven't also missed any replies.
It's been a while since I read the HTK licence, but from memory and past
commercial practices I believe that what you are proposing is entirely
acceptable according to the HTK licence.
In fact I think www.speechmatics.com uses HVite in exactly this way to
do some final tidying up of the large vocabulary speech recognition output.
Tony
On 30/10/14 11:49, Georg Schlunz wrote:
> Good day
>
> Regarding the HTK license, as specified at http://htk.eng.cam.ac.uk/docs/licen
se.shtml , I would like to know whether the following scenario is permitted:
>
> The HTK software (including HVite) sits on a server in-house in our organisati
on, as per license sections 2.1 and 2.3.
> The HTK software (including HVite) is never distributed to a commercial (or no
n-commercial) party, as per license section 2.2.
>
> We have written our own server-client software, where:
> a) the client records speech and sends the audio file to the server, which pas
ses it on to HVite (the server software and HTK sit on the same in-house machine
)
> b) HVite decodes the audio into text
> c) the server replies to the client with the decoded text and the client proce
sses the text somehow
>
> Naturally, the client software contains no HTK code; it only processes data pr
oduced by HTK.
>

> Therefore, may this client software and decoding SERVICE be sold commercially
(as long as we agree to license sections 2.4 and 2.5)?
>
> Thank you
> Georg Schlunz
>
-- ** Cantab is hiring: www.cantabResearch.com/openings ** -Dr A J Robinson, Founder, Cantab Research Ltd
Phone direct: 01223 778240 office: 01223 794497
Company reg no GB 05697423, VAT reg no 925606030
51 Canterbury Street, Cambridge, CB4 3QG, UK
From tonyr at cantabResearch.com Tue Nov 4 20:04:46 2014
From: tonyr at cantabResearch.com (Tony Robinson)
Date: Wed Dec 31 04:46:25 2014
Subject: [HTK-Users] HTK license agreement
In-Reply-To: <545241EC02000049000E3077@pta-emo.csir.co.za>
References: <545241EC02000049000E3077@pta-emo.csir.co.za>
Message-ID: <5459315E.9030409@cantabResearch.com>
I just saw this post - I hope I haven't also missed any replies.
It's been a while since I read the HTK licence, but from memory and past
commercial practices I believe that what you are proposing is entirely
acceptable according to the HTK licence.
In fact I think www.speechmatics.com uses HVite in exactly this way to
do some final tidying up of the large vocabulary speech recognition output.
Tony
On 30/10/14 11:49, Georg Schlunz wrote:
> Good day
>
> Regarding the HTK license, as specified at http://htk.eng.cam.ac.uk/docs/licen
se.shtml , I would like to know whether the following scenario is permitted:
>
> The HTK software (including HVite) sits on a server in-house in our organisati
on, as per license sections 2.1 and 2.3.
> The HTK software (including HVite) is never distributed to a commercial (or no
n-commercial) party, as per license section 2.2.
>
> We have written our own server-client software, where:
> a) the client records speech and sends the audio file to the server, which pas
ses it on to HVite (the server software and HTK sit on the same in-house machine
)
> b) HVite decodes the audio into text
> c) the server replies to the client with the decoded text and the client proce
sses the text somehow
>
> Naturally, the client software contains no HTK code; it only processes data pr
oduced by HTK.
>
> Therefore, may this client software and decoding SERVICE be sold commercially
(as long as we agree to license sections 2.4 and 2.5)?
>
> Thank you
> Georg Schlunz

>
-- ** Cantab is hiring: www.cantabResearch.com/openings ** -Dr A J Robinson, Founder, Cantab Research Ltd
Phone direct: 01223 778240 office: 01223 794497
Company reg no GB 05697423, VAT reg no 925606030
51 Canterbury Street, Cambridge, CB4 3QG, UK
From tonyr at cantabResearch.com Tue Nov 4 20:04:46 2014
From: tonyr at cantabResearch.com (Tony Robinson)
Date: Thu Jan 1 04:47:04 2015
Subject: [HTK-Users] HTK license agreement
In-Reply-To: <545241EC02000049000E3077@pta-emo.csir.co.za>
References: <545241EC02000049000E3077@pta-emo.csir.co.za>
Message-ID: <5459315E.9030409@cantabResearch.com>
I just saw this post - I hope I haven't also missed any replies.
It's been a while since I read the HTK licence, but from memory and past
commercial practices I believe that what you are proposing is entirely
acceptable according to the HTK licence.
In fact I think www.speechmatics.com uses HVite in exactly this way to
do some final tidying up of the large vocabulary speech recognition output.
Tony
On 30/10/14 11:49, Georg Schlunz wrote:
> Good day
>
> Regarding the HTK license, as specified at http://htk.eng.cam.ac.uk/docs/licen
se.shtml , I would like to know whether the following scenario is permitted:
>
> The HTK software (including HVite) sits on a server in-house in our organisati
on, as per license sections 2.1 and 2.3.
> The HTK software (including HVite) is never distributed to a commercial (or no
n-commercial) party, as per license section 2.2.
>
> We have written our own server-client software, where:
> a) the client records speech and sends the audio file to the server, which pas
ses it on to HVite (the server software and HTK sit on the same in-house machine
)
> b) HVite decodes the audio into text
> c) the server replies to the client with the decoded text and the client proce
sses the text somehow
>
> Naturally, the client software contains no HTK code; it only processes data pr
oduced by HTK.
>
> Therefore, may this client software and decoding SERVICE be sold commercially
(as long as we agree to license sections 2.4 and 2.5)?
>
> Thank you
> Georg Schlunz
>
-- ** Cantab is hiring: www.cantabResearch.com/openings ** -Dr A J Robinson, Founder, Cantab Research Ltd
Phone direct: 01223 778240 office: 01223 794497

Company reg no GB 05697423, VAT reg no 925606030


51 Canterbury Street, Cambridge, CB4 3QG, UK
From tonyr at cantabResearch.com Tue Nov 4 20:04:46 2014
From: tonyr at cantabResearch.com (Tony Robinson)
Date: Fri Jan 2 04:48:11 2015
Subject: [HTK-Users] HTK license agreement
In-Reply-To: <545241EC02000049000E3077@pta-emo.csir.co.za>
References: <545241EC02000049000E3077@pta-emo.csir.co.za>
Message-ID: <5459315E.9030409@cantabResearch.com>
I just saw this post - I hope I haven't also missed any replies.
It's been a while since I read the HTK licence, but from memory and past
commercial practices I believe that what you are proposing is entirely
acceptable according to the HTK licence.
In fact I think www.speechmatics.com uses HVite in exactly this way to
do some final tidying up of the large vocabulary speech recognition output.
Tony
On 30/10/14 11:49, Georg Schlunz wrote:
> Good day
>
> Regarding the HTK license, as specified at http://htk.eng.cam.ac.uk/docs/licen
se.shtml , I would like to know whether the following scenario is permitted:
>
> The HTK software (including HVite) sits on a server in-house in our organisati
on, as per license sections 2.1 and 2.3.
> The HTK software (including HVite) is never distributed to a commercial (or no
n-commercial) party, as per license section 2.2.
>
> We have written our own server-client software, where:
> a) the client records speech and sends the audio file to the server, which pas
ses it on to HVite (the server software and HTK sit on the same in-house machine
)
> b) HVite decodes the audio into text
> c) the server replies to the client with the decoded text and the client proce
sses the text somehow
>
> Naturally, the client software contains no HTK code; it only processes data pr
oduced by HTK.
>
> Therefore, may this client software and decoding SERVICE be sold commercially
(as long as we agree to license sections 2.4 and 2.5)?
>
> Thank you
> Georg Schlunz
>
-- ** Cantab is hiring: www.cantabResearch.com/openings ** -Dr A J Robinson, Founder, Cantab Research Ltd
Phone direct: 01223 778240 office: 01223 794497
Company reg no GB 05697423, VAT reg no 925606030
51 Canterbury Street, Cambridge, CB4 3QG, UK
From tonyr at cantabResearch.com Tue Nov 4 20:04:46 2014
From: tonyr at cantabResearch.com (Tony Robinson)

Date: Sat Jan 3 04:39:17 2015


Subject: [HTK-Users] HTK license agreement
In-Reply-To: <545241EC02000049000E3077@pta-emo.csir.co.za>
References: <545241EC02000049000E3077@pta-emo.csir.co.za>
Message-ID: <5459315E.9030409@cantabResearch.com>
I just saw this post - I hope I haven't also missed any replies.
It's been a while since I read the HTK licence, but from memory and past
commercial practices I believe that what you are proposing is entirely
acceptable according to the HTK licence.
In fact I think www.speechmatics.com uses HVite in exactly this way to
do some final tidying up of the large vocabulary speech recognition output.
Tony
On 30/10/14 11:49, Georg Schlunz wrote:
> Good day
>
> Regarding the HTK license, as specified at http://htk.eng.cam.ac.uk/docs/licen
se.shtml , I would like to know whether the following scenario is permitted:
>
> The HTK software (including HVite) sits on a server in-house in our organisati
on, as per license sections 2.1 and 2.3.
> The HTK software (including HVite) is never distributed to a commercial (or no
n-commercial) party, as per license section 2.2.
>
> We have written our own server-client software, where:
> a) the client records speech and sends the audio file to the server, which pas
ses it on to HVite (the server software and HTK sit on the same in-house machine
)
> b) HVite decodes the audio into text
> c) the server replies to the client with the decoded text and the client proce
sses the text somehow
>
> Naturally, the client software contains no HTK code; it only processes data pr
oduced by HTK.
>
> Therefore, may this client software and decoding SERVICE be sold commercially
(as long as we agree to license sections 2.4 and 2.5)?
>
> Thank you
> Georg Schlunz
>
-- ** Cantab is hiring: www.cantabResearch.com/openings ** -Dr A J Robinson, Founder, Cantab Research Ltd
Phone direct: 01223 778240 office: 01223 794497
Company reg no GB 05697423, VAT reg no 925606030
51 Canterbury Street, Cambridge, CB4 3QG, UK
From tonyr at cantabResearch.com Tue Nov 4 20:04:46 2014
From: tonyr at cantabResearch.com (Tony Robinson)
Date: Sun Jan 4 04:37:01 2015
Subject: [HTK-Users] HTK license agreement
In-Reply-To: <545241EC02000049000E3077@pta-emo.csir.co.za>
References: <545241EC02000049000E3077@pta-emo.csir.co.za>
Message-ID: <5459315E.9030409@cantabResearch.com>

I just saw this post - I hope I haven't also missed any replies.
It's been a while since I read the HTK licence, but from memory and past
commercial practices I believe that what you are proposing is entirely
acceptable according to the HTK licence.
In fact I think www.speechmatics.com uses HVite in exactly this way to
do some final tidying up of the large vocabulary speech recognition output.
Tony
On 30/10/14 11:49, Georg Schlunz wrote:
> Good day
>
> Regarding the HTK license, as specified at http://htk.eng.cam.ac.uk/docs/licen
se.shtml , I would like to know whether the following scenario is permitted:
>
> The HTK software (including HVite) sits on a server in-house in our organisati
on, as per license sections 2.1 and 2.3.
> The HTK software (including HVite) is never distributed to a commercial (or no
n-commercial) party, as per license section 2.2.
>
> We have written our own server-client software, where:
> a) the client records speech and sends the audio file to the server, which pas
ses it on to HVite (the server software and HTK sit on the same in-house machine
)
> b) HVite decodes the audio into text
> c) the server replies to the client with the decoded text and the client proce
sses the text somehow
>
> Naturally, the client software contains no HTK code; it only processes data pr
oduced by HTK.
>
> Therefore, may this client software and decoding SERVICE be sold commercially
(as long as we agree to license sections 2.4 and 2.5)?
>
> Thank you
> Georg Schlunz
>
-- ** Cantab is hiring: www.cantabResearch.com/openings ** -Dr A J Robinson, Founder, Cantab Research Ltd
Phone direct: 01223 778240 office: 01223 794497
Company reg no GB 05697423, VAT reg no 925606030
51 Canterbury Street, Cambridge, CB4 3QG, UK
From tonyr at cantabResearch.com Tue Nov 4 20:04:46 2014
From: tonyr at cantabResearch.com (Tony Robinson)
Date: Mon Jan 5 04:31:11 2015
Subject: [HTK-Users] HTK license agreement
In-Reply-To: <545241EC02000049000E3077@pta-emo.csir.co.za>
References: <545241EC02000049000E3077@pta-emo.csir.co.za>
Message-ID: <5459315E.9030409@cantabResearch.com>
I just saw this post - I hope I haven't also missed any replies.
It's been a while since I read the HTK licence, but from memory and past
commercial practices I believe that what you are proposing is entirely

acceptable according to the HTK licence.


In fact I think www.speechmatics.com uses HVite in exactly this way to
do some final tidying up of the large vocabulary speech recognition output.
Tony
On 30/10/14 11:49, Georg Schlunz wrote:
> Good day
>
> Regarding the HTK license, as specified at http://htk.eng.cam.ac.uk/docs/licen
se.shtml , I would like to know whether the following scenario is permitted:
>
> The HTK software (including HVite) sits on a server in-house in our organisati
on, as per license sections 2.1 and 2.3.
> The HTK software (including HVite) is never distributed to a commercial (or no
n-commercial) party, as per license section 2.2.
>
> We have written our own server-client software, where:
> a) the client records speech and sends the audio file to the server, which pas
ses it on to HVite (the server software and HTK sit on the same in-house machine
)
> b) HVite decodes the audio into text
> c) the server replies to the client with the decoded text and the client proce
sses the text somehow
>
> Naturally, the client software contains no HTK code; it only processes data pr
oduced by HTK.
>
> Therefore, may this client software and decoding SERVICE be sold commercially
(as long as we agree to license sections 2.4 and 2.5)?
>
> Thank you
> Georg Schlunz
>
-- ** Cantab is hiring: www.cantabResearch.com/openings ** -Dr A J Robinson, Founder, Cantab Research Ltd
Phone direct: 01223 778240 office: 01223 794497
Company reg no GB 05697423, VAT reg no 925606030
51 Canterbury Street, Cambridge, CB4 3QG, UK
From tonyr at cantabResearch.com Tue Nov 4 20:04:46 2014
From: tonyr at cantabResearch.com (Tony Robinson)
Date: Tue Jan 6 04:36:07 2015
Subject: [HTK-Users] HTK license agreement
In-Reply-To: <545241EC02000049000E3077@pta-emo.csir.co.za>
References: <545241EC02000049000E3077@pta-emo.csir.co.za>
Message-ID: <5459315E.9030409@cantabResearch.com>
I just saw this post - I hope I haven't also missed any replies.
It's been a while since I read the HTK licence, but from memory and past
commercial practices I believe that what you are proposing is entirely
acceptable according to the HTK licence.
In fact I think www.speechmatics.com uses HVite in exactly this way to
do some final tidying up of the large vocabulary speech recognition output.

Tony
On 30/10/14 11:49, Georg Schlunz wrote:
> Good day
>
> Regarding the HTK license, as specified at http://htk.eng.cam.ac.uk/docs/licen
se.shtml , I would like to know whether the following scenario is permitted:
>
> The HTK software (including HVite) sits on a server in-house in our organisati
on, as per license sections 2.1 and 2.3.
> The HTK software (including HVite) is never distributed to a commercial (or no
n-commercial) party, as per license section 2.2.
>
> We have written our own server-client software, where:
> a) the client records speech and sends the audio file to the server, which pas
ses it on to HVite (the server software and HTK sit on the same in-house machine
)
> b) HVite decodes the audio into text
> c) the server replies to the client with the decoded text and the client proce
sses the text somehow
>
> Naturally, the client software contains no HTK code; it only processes data pr
oduced by HTK.
>
> Therefore, may this client software and decoding SERVICE be sold commercially
(as long as we agree to license sections 2.4 and 2.5)?
>
> Thank you
> Georg Schlunz
>
-- ** Cantab is hiring: www.cantabResearch.com/openings ** -Dr A J Robinson, Founder, Cantab Research Ltd
Phone direct: 01223 778240 office: 01223 794497
Company reg no GB 05697423, VAT reg no 925606030
51 Canterbury Street, Cambridge, CB4 3QG, UK
From tonyr at cantabResearch.com Tue Nov 4 20:04:46 2014
From: tonyr at cantabResearch.com (Tony Robinson)
Date: Wed Jan 7 04:55:44 2015
Subject: [HTK-Users] HTK license agreement
In-Reply-To: <545241EC02000049000E3077@pta-emo.csir.co.za>
References: <545241EC02000049000E3077@pta-emo.csir.co.za>
Message-ID: <5459315E.9030409@cantabResearch.com>
I just saw this post - I hope I haven't also missed any replies.
It's been a while since I read the HTK licence, but from memory and past
commercial practices I believe that what you are proposing is entirely
acceptable according to the HTK licence.
In fact I think www.speechmatics.com uses HVite in exactly this way to
do some final tidying up of the large vocabulary speech recognition output.
Tony
On 30/10/14 11:49, Georg Schlunz wrote:
> Good day

>
> Regarding the HTK license, as specified at http://htk.eng.cam.ac.uk/docs/licen
se.shtml , I would like to know whether the following scenario is permitted:
>
> The HTK software (including HVite) sits on a server in-house in our organisati
on, as per license sections 2.1 and 2.3.
> The HTK software (including HVite) is never distributed to a commercial (or no
n-commercial) party, as per license section 2.2.
>
> We have written our own server-client software, where:
> a) the client records speech and sends the audio file to the server, which pas
ses it on to HVite (the server software and HTK sit on the same in-house machine
)
> b) HVite decodes the audio into text
> c) the server replies to the client with the decoded text and the client proce
sses the text somehow
>
> Naturally, the client software contains no HTK code; it only processes data pr
oduced by HTK.
>
> Therefore, may this client software and decoding SERVICE be sold commercially
(as long as we agree to license sections 2.4 and 2.5)?
>
> Thank you
> Georg Schlunz
>
-- ** Cantab is hiring: www.cantabResearch.com/openings ** -Dr A J Robinson, Founder, Cantab Research Ltd
Phone direct: 01223 778240 office: 01223 794497
Company reg no GB 05697423, VAT reg no 925606030
51 Canterbury Street, Cambridge, CB4 3QG, UK
From tonyr at cantabResearch.com Tue Nov 4 20:04:46 2014
From: tonyr at cantabResearch.com (Tony Robinson)
Date: Thu Jan 8 05:00:34 2015
Subject: [HTK-Users] HTK license agreement
In-Reply-To: <545241EC02000049000E3077@pta-emo.csir.co.za>
References: <545241EC02000049000E3077@pta-emo.csir.co.za>
Message-ID: <5459315E.9030409@cantabResearch.com>
I just saw this post - I hope I haven't also missed any replies.
It's been a while since I read the HTK licence, but from memory and past
commercial practices I believe that what you are proposing is entirely
acceptable according to the HTK licence.
In fact I think www.speechmatics.com uses HVite in exactly this way to
do some final tidying up of the large vocabulary speech recognition output.
Tony
On 30/10/14 11:49, Georg Schlunz wrote:
> Good day
>
> Regarding the HTK license, as specified at http://htk.eng.cam.ac.uk/docs/licen
se.shtml , I would like to know whether the following scenario is permitted:
>
> The HTK software (including HVite) sits on a server in-house in our organisati

on, as per license sections 2.1 and 2.3.


> The HTK software (including HVite) is never distributed to a commercial (or no
n-commercial) party, as per license section 2.2.
>
> We have written our own server-client software, where:
> a) the client records speech and sends the audio file to the server, which pas
ses it on to HVite (the server software and HTK sit on the same in-house machine
)
> b) HVite decodes the audio into text
> c) the server replies to the client with the decoded text and the client proce
sses the text somehow
>
> Naturally, the client software contains no HTK code; it only processes data pr
oduced by HTK.
>
> Therefore, may this client software and decoding SERVICE be sold commercially
(as long as we agree to license sections 2.4 and 2.5)?
>
> Thank you
> Georg Schlunz
>
-- ** Cantab is hiring: www.cantabResearch.com/openings ** -Dr A J Robinson, Founder, Cantab Research Ltd
Phone direct: 01223 778240 office: 01223 794497
Company reg no GB 05697423, VAT reg no 925606030
51 Canterbury Street, Cambridge, CB4 3QG, UK
From tonyr at cantabResearch.com Tue Nov 4 20:04:46 2014
From: tonyr at cantabResearch.com (Tony Robinson)
Date: Fri Jan 9 04:51:11 2015
Subject: [HTK-Users] HTK license agreement
In-Reply-To: <545241EC02000049000E3077@pta-emo.csir.co.za>
References: <545241EC02000049000E3077@pta-emo.csir.co.za>
Message-ID: <5459315E.9030409@cantabResearch.com>
I just saw this post - I hope I haven't also missed any replies.
It's been a while since I read the HTK licence, but from memory and past
commercial practices I believe that what you are proposing is entirely
acceptable according to the HTK licence.
In fact I think www.speechmatics.com uses HVite in exactly this way to
do some final tidying up of the large vocabulary speech recognition output.
Tony
On 30/10/14 11:49, Georg Schlunz wrote:
> Good day
>
> Regarding the HTK license, as specified at http://htk.eng.cam.ac.uk/docs/licen
se.shtml , I would like to know whether the following scenario is permitted:
>
> The HTK software (including HVite) sits on a server in-house in our organisati
on, as per license sections 2.1 and 2.3.
> The HTK software (including HVite) is never distributed to a commercial (or no
n-commercial) party, as per license section 2.2.
>
> We have written our own server-client software, where:

> a) the client records speech and sends the audio file to the server, which pas
ses it on to HVite (the server software and HTK sit on the same in-house machine
)
> b) HVite decodes the audio into text
> c) the server replies to the client with the decoded text and the client proce
sses the text somehow
>
> Naturally, the client software contains no HTK code; it only processes data pr
oduced by HTK.
>
> Therefore, may this client software and decoding SERVICE be sold commercially
(as long as we agree to license sections 2.4 and 2.5)?
>
> Thank you
> Georg Schlunz
>
-- ** Cantab is hiring: www.cantabResearch.com/openings ** -Dr A J Robinson, Founder, Cantab Research Ltd
Phone direct: 01223 778240 office: 01223 794497
Company reg no GB 05697423, VAT reg no 925606030
51 Canterbury Street, Cambridge, CB4 3QG, UK
From tonyr at cantabResearch.com Tue Nov 4 20:04:46 2014
From: tonyr at cantabResearch.com (Tony Robinson)
Date: Sat Jan 10 04:35:18 2015
Subject: [HTK-Users] HTK license agreement
In-Reply-To: <545241EC02000049000E3077@pta-emo.csir.co.za>
References: <545241EC02000049000E3077@pta-emo.csir.co.za>
Message-ID: <5459315E.9030409@cantabResearch.com>
I just saw this post - I hope I haven't also missed any replies.
It's been a while since I read the HTK licence, but from memory and past
commercial practices I believe that what you are proposing is entirely
acceptable according to the HTK licence.
In fact I think www.speechmatics.com uses HVite in exactly this way to
do some final tidying up of the large vocabulary speech recognition output.
Tony
On 30/10/14 11:49, Georg Schlunz wrote:
> Good day
>
> Regarding the HTK license, as specified at http://htk.eng.cam.ac.uk/docs/licen
se.shtml , I would like to know whether the following scenario is permitted:
>
> The HTK software (including HVite) sits on a server in-house in our organisati
on, as per license sections 2.1 and 2.3.
> The HTK software (including HVite) is never distributed to a commercial (or no
n-commercial) party, as per license section 2.2.
>
> We have written our own server-client software, where:
> a) the client records speech and sends the audio file to the server, which pas
ses it on to HVite (the server software and HTK sit on the same in-house machine
)
> b) HVite decodes the audio into text
> c) the server replies to the client with the decoded text and the client proce

sses the text somehow


>
> Naturally, the client software contains no HTK code; it only processes data pr
oduced by HTK.
>
> Therefore, may this client software and decoding SERVICE be sold commercially
(as long as we agree to license sections 2.4 and 2.5)?
>
> Thank you
> Georg Schlunz
>
-- ** Cantab is hiring: www.cantabResearch.com/openings ** -Dr A J Robinson, Founder, Cantab Research Ltd
Phone direct: 01223 778240 office: 01223 794497
Company reg no GB 05697423, VAT reg no 925606030
51 Canterbury Street, Cambridge, CB4 3QG, UK
From tonyr at cantabResearch.com Tue Nov 4 20:04:46 2014
From: tonyr at cantabResearch.com (Tony Robinson)
Date: Sun Jan 11 04:47:34 2015
Subject: [HTK-Users] HTK license agreement
In-Reply-To: <545241EC02000049000E3077@pta-emo.csir.co.za>
References: <545241EC02000049000E3077@pta-emo.csir.co.za>
Message-ID: <5459315E.9030409@cantabResearch.com>
I just saw this post - I hope I haven't also missed any replies.
It's been a while since I read the HTK licence, but from memory and past
commercial practices I believe that what you are proposing is entirely
acceptable according to the HTK licence.
In fact I think www.speechmatics.com uses HVite in exactly this way to
do some final tidying up of the large vocabulary speech recognition output.
Tony
On 30/10/14 11:49, Georg Schlunz wrote:
> Good day
>
> Regarding the HTK license, as specified at http://htk.eng.cam.ac.uk/docs/licen
se.shtml , I would like to know whether the following scenario is permitted:
>
> The HTK software (including HVite) sits on a server in-house in our organisati
on, as per license sections 2.1 and 2.3.
> The HTK software (including HVite) is never distributed to a commercial (or no
n-commercial) party, as per license section 2.2.
>
> We have written our own server-client software, where:
> a) the client records speech and sends the audio file to the server, which pas
ses it on to HVite (the server software and HTK sit on the same in-house machine
)
> b) HVite decodes the audio into text
> c) the server replies to the client with the decoded text and the client proce
sses the text somehow
>
> Naturally, the client software contains no HTK code; it only processes data pr
oduced by HTK.
>

> Therefore, may this client software and decoding SERVICE be sold commercially
(as long as we agree to license sections 2.4 and 2.5)?
>
> Thank you
> Georg Schlunz
>
-- ** Cantab is hiring: www.cantabResearch.com/openings ** -Dr A J Robinson, Founder, Cantab Research Ltd
Phone direct: 01223 778240 office: 01223 794497
Company reg no GB 05697423, VAT reg no 925606030
51 Canterbury Street, Cambridge, CB4 3QG, UK
From tonyr at cantabResearch.com Tue Nov 4 20:04:46 2014
From: tonyr at cantabResearch.com (Tony Robinson)
Date: Mon Jan 12 04:56:14 2015
Subject: [HTK-Users] HTK license agreement
In-Reply-To: <545241EC02000049000E3077@pta-emo.csir.co.za>
References: <545241EC02000049000E3077@pta-emo.csir.co.za>
Message-ID: <5459315E.9030409@cantabResearch.com>
I just saw this post - I hope I haven't also missed any replies.
It's been a while since I read the HTK licence, but from memory and past
commercial practices I believe that what you are proposing is entirely
acceptable according to the HTK licence.
In fact I think www.speechmatics.com uses HVite in exactly this way to
do some final tidying up of the large vocabulary speech recognition output.
Tony
On 30/10/14 11:49, Georg Schlunz wrote:
> Good day
>
> Regarding the HTK license, as specified at http://htk.eng.cam.ac.uk/docs/licen
se.shtml , I would like to know whether the following scenario is permitted:
>
> The HTK software (including HVite) sits on a server in-house in our organisati
on, as per license sections 2.1 and 2.3.
> The HTK software (including HVite) is never distributed to a commercial (or no
n-commercial) party, as per license section 2.2.
>
> We have written our own server-client software, where:
> a) the client records speech and sends the audio file to the server, which pas
ses it on to HVite (the server software and HTK sit on the same in-house machine
)
> b) HVite decodes the audio into text
> c) the server replies to the client with the decoded text and the client proce
sses the text somehow
>
> Naturally, the client software contains no HTK code; it only processes data pr
oduced by HTK.
>
> Therefore, may this client software and decoding SERVICE be sold commercially
(as long as we agree to license sections 2.4 and 2.5)?
>
> Thank you
> Georg Schlunz

>
-- ** Cantab is hiring: www.cantabResearch.com/openings ** -Dr A J Robinson, Founder, Cantab Research Ltd
Phone direct: 01223 778240 office: 01223 794497
Company reg no GB 05697423, VAT reg no 925606030
51 Canterbury Street, Cambridge, CB4 3QG, UK
From tonyr at cantabResearch.com Tue Nov 4 20:04:46 2014
From: tonyr at cantabResearch.com (Tony Robinson)
Date: Tue Jan 13 04:20:12 2015
Subject: [HTK-Users] HTK license agreement
In-Reply-To: <545241EC02000049000E3077@pta-emo.csir.co.za>
References: <545241EC02000049000E3077@pta-emo.csir.co.za>
Message-ID: <5459315E.9030409@cantabResearch.com>
I just saw this post - I hope I haven't also missed any replies.
It's been a while since I read the HTK licence, but from memory and past
commercial practices I believe that what you are proposing is entirely
acceptable according to the HTK licence.
In fact I think www.speechmatics.com uses HVite in exactly this way to
do some final tidying up of the large vocabulary speech recognition output.
Tony
On 30/10/14 11:49, Georg Schlunz wrote:
> Good day
>
> Regarding the HTK license, as specified at http://htk.eng.cam.ac.uk/docs/licen
se.shtml , I would like to know whether the following scenario is permitted:
>
> The HTK software (including HVite) sits on a server in-house in our organisati
on, as per license sections 2.1 and 2.3.
> The HTK software (including HVite) is never distributed to a commercial (or no
n-commercial) party, as per license section 2.2.
>
> We have written our own server-client software, where:
> a) the client records speech and sends the audio file to the server, which pas
ses it on to HVite (the server software and HTK sit on the same in-house machine
)
> b) HVite decodes the audio into text
> c) the server replies to the client with the decoded text and the client proce
sses the text somehow
>
> Naturally, the client software contains no HTK code; it only processes data pr
oduced by HTK.
>
> Therefore, may this client software and decoding SERVICE be sold commercially
(as long as we agree to license sections 2.4 and 2.5)?
>
> Thank you
> Georg Schlunz
>
-- ** Cantab is hiring: www.cantabResearch.com/openings ** -Dr A J Robinson, Founder, Cantab Research Ltd
Phone direct: 01223 778240 office: 01223 794497

Company reg no GB 05697423, VAT reg no 925606030


51 Canterbury Street, Cambridge, CB4 3QG, UK
From tonyr at cantabResearch.com Tue Nov 4 20:04:46 2014
From: tonyr at cantabResearch.com (Tony Robinson)
Date: Wed Jan 14 05:02:04 2015
Subject: [HTK-Users] HTK license agreement
In-Reply-To: <545241EC02000049000E3077@pta-emo.csir.co.za>
References: <545241EC02000049000E3077@pta-emo.csir.co.za>
Message-ID: <5459315E.9030409@cantabResearch.com>
I just saw this post - I hope I haven't also missed any replies.
It's been a while since I read the HTK licence, but from memory and past
commercial practices I believe that what you are proposing is entirely
acceptable according to the HTK licence.
In fact I think www.speechmatics.com uses HVite in exactly this way to
do some final tidying up of the large vocabulary speech recognition output.
Tony
On 30/10/14 11:49, Georg Schlunz wrote:
> Good day
>
> Regarding the HTK license, as specified at http://htk.eng.cam.ac.uk/docs/licen
se.shtml , I would like to know whether the following scenario is permitted:
>
> The HTK software (including HVite) sits on a server in-house in our organisati
on, as per license sections 2.1 and 2.3.
> The HTK software (including HVite) is never distributed to a commercial (or no
n-commercial) party, as per license section 2.2.
>
> We have written our own server-client software, where:
> a) the client records speech and sends the audio file to the server, which pas
ses it on to HVite (the server software and HTK sit on the same in-house machine
)
> b) HVite decodes the audio into text
> c) the server replies to the client with the decoded text and the client proce
sses the text somehow
>
> Naturally, the client software contains no HTK code; it only processes data pr
oduced by HTK.
>
> Therefore, may this client software and decoding SERVICE be sold commercially
(as long as we agree to license sections 2.4 and 2.5)?
>
> Thank you
> Georg Schlunz
>
-- ** Cantab is hiring: www.cantabResearch.com/openings ** -Dr A J Robinson, Founder, Cantab Research Ltd
Phone direct: 01223 778240 office: 01223 794497
Company reg no GB 05697423, VAT reg no 925606030
51 Canterbury Street, Cambridge, CB4 3QG, UK
From tonyr at cantabResearch.com Tue Nov 4 20:04:46 2014
From: tonyr at cantabResearch.com (Tony Robinson)

Date: Thu Jan 15 04:57:30 2015


Subject: [HTK-Users] HTK license agreement
In-Reply-To: <545241EC02000049000E3077@pta-emo.csir.co.za>
References: <545241EC02000049000E3077@pta-emo.csir.co.za>
Message-ID: <5459315E.9030409@cantabResearch.com>
I just saw this post - I hope I haven't also missed any replies.
It's been a while since I read the HTK licence, but from memory and past
commercial practices I believe that what you are proposing is entirely
acceptable according to the HTK licence.
In fact I think www.speechmatics.com uses HVite in exactly this way to
do some final tidying up of the large vocabulary speech recognition output.
Tony
On 30/10/14 11:49, Georg Schlunz wrote:
> Good day
>
> Regarding the HTK license, as specified at http://htk.eng.cam.ac.uk/docs/licen
se.shtml , I would like to know whether the following scenario is permitted:
>
> The HTK software (including HVite) sits on a server in-house in our organisati
on, as per license sections 2.1 and 2.3.
> The HTK software (including HVite) is never distributed to a commercial (or no
n-commercial) party, as per license section 2.2.
>
> We have written our own server-client software, where:
> a) the client records speech and sends the audio file to the server, which pas
ses it on to HVite (the server software and HTK sit on the same in-house machine
)
> b) HVite decodes the audio into text
> c) the server replies to the client with the decoded text and the client proce
sses the text somehow
>
> Naturally, the client software contains no HTK code; it only processes data pr
oduced by HTK.
>
> Therefore, may this client software and decoding SERVICE be sold commercially
(as long as we agree to license sections 2.4 and 2.5)?
>
> Thank you
> Georg Schlunz
>
-- ** Cantab is hiring: www.cantabResearch.com/openings ** -Dr A J Robinson, Founder, Cantab Research Ltd
Phone direct: 01223 778240 office: 01223 794497
Company reg no GB 05697423, VAT reg no 925606030
51 Canterbury Street, Cambridge, CB4 3QG, UK
From tonyr at cantabResearch.com Tue Nov 4 20:04:46 2014
From: tonyr at cantabResearch.com (Tony Robinson)
Date: Fri Jan 16 05:02:02 2015
Subject: [HTK-Users] HTK license agreement
In-Reply-To: <545241EC02000049000E3077@pta-emo.csir.co.za>
References: <545241EC02000049000E3077@pta-emo.csir.co.za>
Message-ID: <5459315E.9030409@cantabResearch.com>

I just saw this post - I hope I haven't also missed any replies.
It's been a while since I read the HTK licence, but from memory and past
commercial practices I believe that what you are proposing is entirely
acceptable according to the HTK licence.
In fact I think www.speechmatics.com uses HVite in exactly this way to
do some final tidying up of the large vocabulary speech recognition output.
Tony
On 30/10/14 11:49, Georg Schlunz wrote:
> Good day
>
> Regarding the HTK license, as specified at http://htk.eng.cam.ac.uk/docs/licen
se.shtml , I would like to know whether the following scenario is permitted:
>
> The HTK software (including HVite) sits on a server in-house in our organisati
on, as per license sections 2.1 and 2.3.
> The HTK software (including HVite) is never distributed to a commercial (or no
n-commercial) party, as per license section 2.2.
>
> We have written our own server-client software, where:
> a) the client records speech and sends the audio file to the server, which pas
ses it on to HVite (the server software and HTK sit on the same in-house machine
)
> b) HVite decodes the audio into text
> c) the server replies to the client with the decoded text and the client proce
sses the text somehow
>
> Naturally, the client software contains no HTK code; it only processes data pr
oduced by HTK.
>
> Therefore, may this client software and decoding SERVICE be sold commercially
(as long as we agree to license sections 2.4 and 2.5)?
>
> Thank you
> Georg Schlunz
>
-- ** Cantab is hiring: www.cantabResearch.com/openings ** -Dr A J Robinson, Founder, Cantab Research Ltd
Phone direct: 01223 778240 office: 01223 794497
Company reg no GB 05697423, VAT reg no 925606030
51 Canterbury Street, Cambridge, CB4 3QG, UK
From tonyr at cantabResearch.com Tue Nov 4 20:04:46 2014
From: tonyr at cantabResearch.com (Tony Robinson)
Date: Sat Jan 17 04:58:06 2015
Subject: [HTK-Users] HTK license agreement
In-Reply-To: <545241EC02000049000E3077@pta-emo.csir.co.za>
References: <545241EC02000049000E3077@pta-emo.csir.co.za>
Message-ID: <5459315E.9030409@cantabResearch.com>
I just saw this post - I hope I haven't also missed any replies.
It's been a while since I read the HTK licence, but from memory and past
commercial practices I believe that what you are proposing is entirely

acceptable according to the HTK licence.


In fact I think www.speechmatics.com uses HVite in exactly this way to
do some final tidying up of the large vocabulary speech recognition output.
Tony
On 30/10/14 11:49, Georg Schlunz wrote:
> Good day
>
> Regarding the HTK license, as specified at http://htk.eng.cam.ac.uk/docs/licen
se.shtml , I would like to know whether the following scenario is permitted:
>
> The HTK software (including HVite) sits on a server in-house in our organisati
on, as per license sections 2.1 and 2.3.
> The HTK software (including HVite) is never distributed to a commercial (or no
n-commercial) party, as per license section 2.2.
>
> We have written our own server-client software, where:
> a) the client records speech and sends the audio file to the server, which pas
ses it on to HVite (the server software and HTK sit on the same in-house machine
)
> b) HVite decodes the audio into text
> c) the server replies to the client with the decoded text and the client proce
sses the text somehow
>
> Naturally, the client software contains no HTK code; it only processes data pr
oduced by HTK.
>
> Therefore, may this client software and decoding SERVICE be sold commercially
(as long as we agree to license sections 2.4 and 2.5)?
>
> Thank you
> Georg Schlunz
>
-- ** Cantab is hiring: www.cantabResearch.com/openings ** -Dr A J Robinson, Founder, Cantab Research Ltd
Phone direct: 01223 778240 office: 01223 794497
Company reg no GB 05697423, VAT reg no 925606030
51 Canterbury Street, Cambridge, CB4 3QG, UK
From tonyr at cantabResearch.com Tue Nov 4 20:04:46 2014
From: tonyr at cantabResearch.com (Tony Robinson)
Date: Sun Jan 18 04:54:26 2015
Subject: [HTK-Users] HTK license agreement
In-Reply-To: <545241EC02000049000E3077@pta-emo.csir.co.za>
References: <545241EC02000049000E3077@pta-emo.csir.co.za>
Message-ID: <5459315E.9030409@cantabResearch.com>
I just saw this post - I hope I haven't also missed any replies.
It's been a while since I read the HTK licence, but from memory and past
commercial practices I believe that what you are proposing is entirely
acceptable according to the HTK licence.
In fact I think www.speechmatics.com uses HVite in exactly this way to
do some final tidying up of the large vocabulary speech recognition output.

Tony
On 30/10/14 11:49, Georg Schlunz wrote:
> Good day
>
> Regarding the HTK license, as specified at http://htk.eng.cam.ac.uk/docs/licen
se.shtml , I would like to know whether the following scenario is permitted:
>
> The HTK software (including HVite) sits on a server in-house in our organisati
on, as per license sections 2.1 and 2.3.
> The HTK software (including HVite) is never distributed to a commercial (or no
n-commercial) party, as per license section 2.2.
>
> We have written our own server-client software, where:
> a) the client records speech and sends the audio file to the server, which pas
ses it on to HVite (the server software and HTK sit on the same in-house machine
)
> b) HVite decodes the audio into text
> c) the server replies to the client with the decoded text and the client proce
sses the text somehow
>
> Naturally, the client software contains no HTK code; it only processes data pr
oduced by HTK.
>
> Therefore, may this client software and decoding SERVICE be sold commercially
(as long as we agree to license sections 2.4 and 2.5)?
>
> Thank you
> Georg Schlunz
>
-- ** Cantab is hiring: www.cantabResearch.com/openings ** -Dr A J Robinson, Founder, Cantab Research Ltd
Phone direct: 01223 778240 office: 01223 794497
Company reg no GB 05697423, VAT reg no 925606030
51 Canterbury Street, Cambridge, CB4 3QG, UK
From tonyr at cantabResearch.com Tue Nov 4 20:04:46 2014
From: tonyr at cantabResearch.com (Tony Robinson)
Date: Mon Jan 19 04:50:50 2015
Subject: [HTK-Users] HTK license agreement
In-Reply-To: <545241EC02000049000E3077@pta-emo.csir.co.za>
References: <545241EC02000049000E3077@pta-emo.csir.co.za>
Message-ID: <5459315E.9030409@cantabResearch.com>
I just saw this post - I hope I haven't also missed any replies.
It's been a while since I read the HTK licence, but from memory and past
commercial practices I believe that what you are proposing is entirely
acceptable according to the HTK licence.
In fact I think www.speechmatics.com uses HVite in exactly this way to
do some final tidying up of the large vocabulary speech recognition output.
Tony
On 30/10/14 11:49, Georg Schlunz wrote:
> Good day

>
> Regarding the HTK license, as specified at http://htk.eng.cam.ac.uk/docs/licen
se.shtml , I would like to know whether the following scenario is permitted:
>
> The HTK software (including HVite) sits on a server in-house in our organisati
on, as per license sections 2.1 and 2.3.
> The HTK software (including HVite) is never distributed to a commercial (or no
n-commercial) party, as per license section 2.2.
>
> We have written our own server-client software, where:
> a) the client records speech and sends the audio file to the server, which pas
ses it on to HVite (the server software and HTK sit on the same in-house machine
)
> b) HVite decodes the audio into text
> c) the server replies to the client with the decoded text and the client proce
sses the text somehow
>
> Naturally, the client software contains no HTK code; it only processes data pr
oduced by HTK.
>
> Therefore, may this client software and decoding SERVICE be sold commercially
(as long as we agree to license sections 2.4 and 2.5)?
>
> Thank you
> Georg Schlunz
>
-- ** Cantab is hiring: www.cantabResearch.com/openings ** -Dr A J Robinson, Founder, Cantab Research Ltd
Phone direct: 01223 778240 office: 01223 794497
Company reg no GB 05697423, VAT reg no 925606030
51 Canterbury Street, Cambridge, CB4 3QG, UK
From tonyr at cantabResearch.com Tue Nov 4 20:04:46 2014
From: tonyr at cantabResearch.com (Tony Robinson)
Date: Tue Jan 20 05:04:51 2015
Subject: [HTK-Users] HTK license agreement
In-Reply-To: <545241EC02000049000E3077@pta-emo.csir.co.za>
References: <545241EC02000049000E3077@pta-emo.csir.co.za>
Message-ID: <5459315E.9030409@cantabResearch.com>
I just saw this post - I hope I haven't also missed any replies.
It's been a while since I read the HTK licence, but from memory and past
commercial practices I believe that what you are proposing is entirely
acceptable according to the HTK licence.
In fact I think www.speechmatics.com uses HVite in exactly this way to
do some final tidying up of the large vocabulary speech recognition output.
Tony
On 30/10/14 11:49, Georg Schlunz wrote:
> Good day
>
> Regarding the HTK license, as specified at http://htk.eng.cam.ac.uk/docs/licen
se.shtml , I would like to know whether the following scenario is permitted:
>
> The HTK software (including HVite) sits on a server in-house in our organisati

on, as per license sections 2.1 and 2.3.


> The HTK software (including HVite) is never distributed to a commercial (or no
n-commercial) party, as per license section 2.2.
>
> We have written our own server-client software, where:
> a) the client records speech and sends the audio file to the server, which pas
ses it on to HVite (the server software and HTK sit on the same in-house machine
)
> b) HVite decodes the audio into text
> c) the server replies to the client with the decoded text and the client proce
sses the text somehow
>
> Naturally, the client software contains no HTK code; it only processes data pr
oduced by HTK.
>
> Therefore, may this client software and decoding SERVICE be sold commercially
(as long as we agree to license sections 2.4 and 2.5)?
>
> Thank you
> Georg Schlunz
>
-- ** Cantab is hiring: www.cantabResearch.com/openings ** -Dr A J Robinson, Founder, Cantab Research Ltd
Phone direct: 01223 778240 office: 01223 794497
Company reg no GB 05697423, VAT reg no 925606030
51 Canterbury Street, Cambridge, CB4 3QG, UK
From tonyr at cantabResearch.com Tue Nov 4 20:04:46 2014
From: tonyr at cantabResearch.com (Tony Robinson)
Date: Wed Jan 21 04:56:05 2015
Subject: [HTK-Users] HTK license agreement
In-Reply-To: <545241EC02000049000E3077@pta-emo.csir.co.za>
References: <545241EC02000049000E3077@pta-emo.csir.co.za>
Message-ID: <5459315E.9030409@cantabResearch.com>
I just saw this post - I hope I haven't also missed any replies.
It's been a while since I read the HTK licence, but from memory and past
commercial practices I believe that what you are proposing is entirely
acceptable according to the HTK licence.
In fact I think www.speechmatics.com uses HVite in exactly this way to
do some final tidying up of the large vocabulary speech recognition output.
Tony
On 30/10/14 11:49, Georg Schlunz wrote:
> Good day
>
> Regarding the HTK license, as specified at http://htk.eng.cam.ac.uk/docs/licen
se.shtml , I would like to know whether the following scenario is permitted:
>
> The HTK software (including HVite) sits on a server in-house in our organisati
on, as per license sections 2.1 and 2.3.
> The HTK software (including HVite) is never distributed to a commercial (or no
n-commercial) party, as per license section 2.2.
>
> We have written our own server-client software, where:

> a) the client records speech and sends the audio file to the server, which pas
ses it on to HVite (the server software and HTK sit on the same in-house machine
)
> b) HVite decodes the audio into text
> c) the server replies to the client with the decoded text and the client proce
sses the text somehow
>
> Naturally, the client software contains no HTK code; it only processes data pr
oduced by HTK.
>
> Therefore, may this client software and decoding SERVICE be sold commercially
(as long as we agree to license sections 2.4 and 2.5)?
>
> Thank you
> Georg Schlunz
>
-- ** Cantab is hiring: www.cantabResearch.com/openings ** -Dr A J Robinson, Founder, Cantab Research Ltd
Phone direct: 01223 778240 office: 01223 794497
Company reg no GB 05697423, VAT reg no 925606030
51 Canterbury Street, Cambridge, CB4 3QG, UK
From tonyr at cantabResearch.com Tue Nov 4 20:04:46 2014
From: tonyr at cantabResearch.com (Tony Robinson)
Date: Thu Jan 22 04:53:37 2015
Subject: [HTK-Users] HTK license agreement
In-Reply-To: <545241EC02000049000E3077@pta-emo.csir.co.za>
References: <545241EC02000049000E3077@pta-emo.csir.co.za>
Message-ID: <5459315E.9030409@cantabResearch.com>
I just saw this post - I hope I haven't also missed any replies.
It's been a while since I read the HTK licence, but from memory and past
commercial practices I believe that what you are proposing is entirely
acceptable according to the HTK licence.
In fact I think www.speechmatics.com uses HVite in exactly this way to
do some final tidying up of the large vocabulary speech recognition output.
Tony
On 30/10/14 11:49, Georg Schlunz wrote:
> Good day
>
> Regarding the HTK license, as specified at http://htk.eng.cam.ac.uk/docs/licen
se.shtml , I would like to know whether the following scenario is permitted:
>
> The HTK software (including HVite) sits on a server in-house in our organisati
on, as per license sections 2.1 and 2.3.
> The HTK software (including HVite) is never distributed to a commercial (or no
n-commercial) party, as per license section 2.2.
>
> We have written our own server-client software, where:
> a) the client records speech and sends the audio file to the server, which pas
ses it on to HVite (the server software and HTK sit on the same in-house machine
)
> b) HVite decodes the audio into text
> c) the server replies to the client with the decoded text and the client proce

sses the text somehow


>
> Naturally, the client software contains no HTK code; it only processes data pr
oduced by HTK.
>
> Therefore, may this client software and decoding SERVICE be sold commercially
(as long as we agree to license sections 2.4 and 2.5)?
>
> Thank you
> Georg Schlunz
>
-- ** Cantab is hiring: www.cantabResearch.com/openings ** -Dr A J Robinson, Founder, Cantab Research Ltd
Phone direct: 01223 778240 office: 01223 794497
Company reg no GB 05697423, VAT reg no 925606030
51 Canterbury Street, Cambridge, CB4 3QG, UK
From tonyr at cantabResearch.com Tue Nov 4 20:04:46 2014
From: tonyr at cantabResearch.com (Tony Robinson)
Date: Fri Jan 23 04:51:19 2015
Subject: [HTK-Users] HTK license agreement
In-Reply-To: <545241EC02000049000E3077@pta-emo.csir.co.za>
References: <545241EC02000049000E3077@pta-emo.csir.co.za>
Message-ID: <5459315E.9030409@cantabResearch.com>
I just saw this post - I hope I haven't also missed any replies.
It's been a while since I read the HTK licence, but from memory and past
commercial practices I believe that what you are proposing is entirely
acceptable according to the HTK licence.
In fact I think www.speechmatics.com uses HVite in exactly this way to
do some final tidying up of the large vocabulary speech recognition output.
Tony
On 30/10/14 11:49, Georg Schlunz wrote:
> Good day
>
> Regarding the HTK license, as specified at http://htk.eng.cam.ac.uk/docs/licen
se.shtml , I would like to know whether the following scenario is permitted:
>
> The HTK software (including HVite) sits on a server in-house in our organisati
on, as per license sections 2.1 and 2.3.
> The HTK software (including HVite) is never distributed to a commercial (or no
n-commercial) party, as per license section 2.2.
>
> We have written our own server-client software, where:
> a) the client records speech and sends the audio file to the server, which pas
ses it on to HVite (the server software and HTK sit on the same in-house machine
)
> b) HVite decodes the audio into text
> c) the server replies to the client with the decoded text and the client proce
sses the text somehow
>
> Naturally, the client software contains no HTK code; it only processes data pr
oduced by HTK.
>

> Therefore, may this client software and decoding SERVICE be sold commercially
(as long as we agree to license sections 2.4 and 2.5)?
>
> Thank you
> Georg Schlunz
>
-- ** Cantab is hiring: www.cantabResearch.com/openings ** -Dr A J Robinson, Founder, Cantab Research Ltd
Phone direct: 01223 778240 office: 01223 794497
Company reg no GB 05697423, VAT reg no 925606030
51 Canterbury Street, Cambridge, CB4 3QG, UK
From tonyr at cantabResearch.com Tue Nov 4 20:04:46 2014
From: tonyr at cantabResearch.com (Tony Robinson)
Date: Sat Jan 24 04:20:10 2015
Subject: [HTK-Users] HTK license agreement
In-Reply-To: <545241EC02000049000E3077@pta-emo.csir.co.za>
References: <545241EC02000049000E3077@pta-emo.csir.co.za>
Message-ID: <5459315E.9030409@cantabResearch.com>
I just saw this post - I hope I haven't also missed any replies.
It's been a while since I read the HTK licence, but from memory and past
commercial practices I believe that what you are proposing is entirely
acceptable according to the HTK licence.
In fact I think www.speechmatics.com uses HVite in exactly this way to
do some final tidying up of the large vocabulary speech recognition output.
Tony
On 30/10/14 11:49, Georg Schlunz wrote:
> Good day
>
> Regarding the HTK license, as specified at http://htk.eng.cam.ac.uk/docs/licen
se.shtml , I would like to know whether the following scenario is permitted:
>
> The HTK software (including HVite) sits on a server in-house in our organisati
on, as per license sections 2.1 and 2.3.
> The HTK software (including HVite) is never distributed to a commercial (or no
n-commercial) party, as per license section 2.2.
>
> We have written our own server-client software, where:
> a) the client records speech and sends the audio file to the server, which pas
ses it on to HVite (the server software and HTK sit on the same in-house machine
)
> b) HVite decodes the audio into text
> c) the server replies to the client with the decoded text and the client proce
sses the text somehow
>
> Naturally, the client software contains no HTK code; it only processes data pr
oduced by HTK.
>
> Therefore, may this client software and decoding SERVICE be sold commercially
(as long as we agree to license sections 2.4 and 2.5)?
>
> Thank you
> Georg Schlunz

>
-- ** Cantab is hiring: www.cantabResearch.com/openings ** -Dr A J Robinson, Founder, Cantab Research Ltd
Phone direct: 01223 778240 office: 01223 794497
Company reg no GB 05697423, VAT reg no 925606030
51 Canterbury Street, Cambridge, CB4 3QG, UK
From tonyr at cantabResearch.com Tue Nov 4 20:04:46 2014
From: tonyr at cantabResearch.com (Tony Robinson)
Date: Sun Jan 25 05:03:57 2015
Subject: [HTK-Users] HTK license agreement
In-Reply-To: <545241EC02000049000E3077@pta-emo.csir.co.za>
References: <545241EC02000049000E3077@pta-emo.csir.co.za>
Message-ID: <5459315E.9030409@cantabResearch.com>
I just saw this post - I hope I haven't also missed any replies.
It's been a while since I read the HTK licence, but from memory and past
commercial practices I believe that what you are proposing is entirely
acceptable according to the HTK licence.
In fact I think www.speechmatics.com uses HVite in exactly this way to
do some final tidying up of the large vocabulary speech recognition output.
Tony
On 30/10/14 11:49, Georg Schlunz wrote:
> Good day
>
> Regarding the HTK license, as specified at http://htk.eng.cam.ac.uk/docs/licen
se.shtml , I would like to know whether the following scenario is permitted:
>
> The HTK software (including HVite) sits on a server in-house in our organisati
on, as per license sections 2.1 and 2.3.
> The HTK software (including HVite) is never distributed to a commercial (or no
n-commercial) party, as per license section 2.2.
>
> We have written our own server-client software, where:
> a) the client records speech and sends the audio file to the server, which pas
ses it on to HVite (the server software and HTK sit on the same in-house machine
)
> b) HVite decodes the audio into text
> c) the server replies to the client with the decoded text and the client proce
sses the text somehow
>
> Naturally, the client software contains no HTK code; it only processes data pr
oduced by HTK.
>
> Therefore, may this client software and decoding SERVICE be sold commercially
(as long as we agree to license sections 2.4 and 2.5)?
>
> Thank you
> Georg Schlunz
>
-- ** Cantab is hiring: www.cantabResearch.com/openings ** -Dr A J Robinson, Founder, Cantab Research Ltd
Phone direct: 01223 778240 office: 01223 794497

Company reg no GB 05697423, VAT reg no 925606030


51 Canterbury Street, Cambridge, CB4 3QG, UK
From tonyr at cantabResearch.com Tue Nov 4 20:04:46 2014
From: tonyr at cantabResearch.com (Tony Robinson)
Date: Mon Jan 26 05:03:08 2015
Subject: [HTK-Users] HTK license agreement
In-Reply-To: <545241EC02000049000E3077@pta-emo.csir.co.za>
References: <545241EC02000049000E3077@pta-emo.csir.co.za>
Message-ID: <5459315E.9030409@cantabResearch.com>
I just saw this post - I hope I haven't also missed any replies.
It's been a while since I read the HTK licence, but from memory and past
commercial practices I believe that what you are proposing is entirely
acceptable according to the HTK licence.
In fact I think www.speechmatics.com uses HVite in exactly this way to
do some final tidying up of the large vocabulary speech recognition output.
Tony
On 30/10/14 11:49, Georg Schlunz wrote:
> Good day
>
> Regarding the HTK license, as specified at http://htk.eng.cam.ac.uk/docs/licen
se.shtml , I would like to know whether the following scenario is permitted:
>
> The HTK software (including HVite) sits on a server in-house in our organisati
on, as per license sections 2.1 and 2.3.
> The HTK software (including HVite) is never distributed to a commercial (or no
n-commercial) party, as per license section 2.2.
>
> We have written our own server-client software, where:
> a) the client records speech and sends the audio file to the server, which pas
ses it on to HVite (the server software and HTK sit on the same in-house machine
)
> b) HVite decodes the audio into text
> c) the server replies to the client with the decoded text and the client proce
sses the text somehow
>
> Naturally, the client software contains no HTK code; it only processes data pr
oduced by HTK.
>
> Therefore, may this client software and decoding SERVICE be sold commercially
(as long as we agree to license sections 2.4 and 2.5)?
>
> Thank you
> Georg Schlunz
>
-- ** Cantab is hiring: www.cantabResearch.com/openings ** -Dr A J Robinson, Founder, Cantab Research Ltd
Phone direct: 01223 778240 office: 01223 794497
Company reg no GB 05697423, VAT reg no 925606030
51 Canterbury Street, Cambridge, CB4 3QG, UK
From tonyr at cantabResearch.com Tue Nov 4 20:04:46 2014
From: tonyr at cantabResearch.com (Tony Robinson)

Date: Tue Jan 27 04:58:24 2015


Subject: [HTK-Users] HTK license agreement
In-Reply-To: <545241EC02000049000E3077@pta-emo.csir.co.za>
References: <545241EC02000049000E3077@pta-emo.csir.co.za>
Message-ID: <5459315E.9030409@cantabResearch.com>
I just saw this post - I hope I haven't also missed any replies.
It's been a while since I read the HTK licence, but from memory and past
commercial practices I believe that what you are proposing is entirely
acceptable according to the HTK licence.
In fact I think www.speechmatics.com uses HVite in exactly this way to
do some final tidying up of the large vocabulary speech recognition output.
Tony
On 30/10/14 11:49, Georg Schlunz wrote:
> Good day
>
> Regarding the HTK license, as specified at http://htk.eng.cam.ac.uk/docs/licen
se.shtml , I would like to know whether the following scenario is permitted:
>
> The HTK software (including HVite) sits on a server in-house in our organisati
on, as per license sections 2.1 and 2.3.
> The HTK software (including HVite) is never distributed to a commercial (or no
n-commercial) party, as per license section 2.2.
>
> We have written our own server-client software, where:
> a) the client records speech and sends the audio file to the server, which pas
ses it on to HVite (the server software and HTK sit on the same in-house machine
)
> b) HVite decodes the audio into text
> c) the server replies to the client with the decoded text and the client proce
sses the text somehow
>
> Naturally, the client software contains no HTK code; it only processes data pr
oduced by HTK.
>
> Therefore, may this client software and decoding SERVICE be sold commercially
(as long as we agree to license sections 2.4 and 2.5)?
>
> Thank you
> Georg Schlunz
>
-- ** Cantab is hiring: www.cantabResearch.com/openings ** -Dr A J Robinson, Founder, Cantab Research Ltd
Phone direct: 01223 778240 office: 01223 794497
Company reg no GB 05697423, VAT reg no 925606030
51 Canterbury Street, Cambridge, CB4 3QG, UK
From tonyr at cantabResearch.com Tue Nov 4 20:04:46 2014
From: tonyr at cantabResearch.com (Tony Robinson)
Date: Wed Jan 28 04:20:15 2015
Subject: [HTK-Users] HTK license agreement
In-Reply-To: <545241EC02000049000E3077@pta-emo.csir.co.za>
References: <545241EC02000049000E3077@pta-emo.csir.co.za>
Message-ID: <5459315E.9030409@cantabResearch.com>

I just saw this post - I hope I haven't also missed any replies.
It's been a while since I read the HTK licence, but from memory and past
commercial practices I believe that what you are proposing is entirely
acceptable according to the HTK licence.
In fact I think www.speechmatics.com uses HVite in exactly this way to
do some final tidying up of the large vocabulary speech recognition output.
Tony
On 30/10/14 11:49, Georg Schlunz wrote:
> Good day
>
> Regarding the HTK license, as specified at http://htk.eng.cam.ac.uk/docs/licen
se.shtml , I would like to know whether the following scenario is permitted:
>
> The HTK software (including HVite) sits on a server in-house in our organisati
on, as per license sections 2.1 and 2.3.
> The HTK software (including HVite) is never distributed to a commercial (or no
n-commercial) party, as per license section 2.2.
>
> We have written our own server-client software, where:
> a) the client records speech and sends the audio file to the server, which pas
ses it on to HVite (the server software and HTK sit on the same in-house machine
)
> b) HVite decodes the audio into text
> c) the server replies to the client with the decoded text and the client proce
sses the text somehow
>
> Naturally, the client software contains no HTK code; it only processes data pr
oduced by HTK.
>
> Therefore, may this client software and decoding SERVICE be sold commercially
(as long as we agree to license sections 2.4 and 2.5)?
>
> Thank you
> Georg Schlunz
>
-- ** Cantab is hiring: www.cantabResearch.com/openings ** -Dr A J Robinson, Founder, Cantab Research Ltd
Phone direct: 01223 778240 office: 01223 794497
Company reg no GB 05697423, VAT reg no 925606030
51 Canterbury Street, Cambridge, CB4 3QG, UK
From tonyr at cantabResearch.com Tue Nov 4 20:04:46 2014
From: tonyr at cantabResearch.com (Tony Robinson)
Date: Thu Jan 29 05:06:27 2015
Subject: [HTK-Users] HTK license agreement
In-Reply-To: <545241EC02000049000E3077@pta-emo.csir.co.za>
References: <545241EC02000049000E3077@pta-emo.csir.co.za>
Message-ID: <5459315E.9030409@cantabResearch.com>
I just saw this post - I hope I haven't also missed any replies.
It's been a while since I read the HTK licence, but from memory and past
commercial practices I believe that what you are proposing is entirely

acceptable according to the HTK licence.


In fact I think www.speechmatics.com uses HVite in exactly this way to
do some final tidying up of the large vocabulary speech recognition output.
Tony
On 30/10/14 11:49, Georg Schlunz wrote:
> Good day
>
> Regarding the HTK license, as specified at http://htk.eng.cam.ac.uk/docs/licen
se.shtml , I would like to know whether the following scenario is permitted:
>
> The HTK software (including HVite) sits on a server in-house in our organisati
on, as per license sections 2.1 and 2.3.
> The HTK software (including HVite) is never distributed to a commercial (or no
n-commercial) party, as per license section 2.2.
>
> We have written our own server-client software, where:
> a) the client records speech and sends the audio file to the server, which pas
ses it on to HVite (the server software and HTK sit on the same in-house machine
)
> b) HVite decodes the audio into text
> c) the server replies to the client with the decoded text and the client proce
sses the text somehow
>
> Naturally, the client software contains no HTK code; it only processes data pr
oduced by HTK.
>
> Therefore, may this client software and decoding SERVICE be sold commercially
(as long as we agree to license sections 2.4 and 2.5)?
>
> Thank you
> Georg Schlunz
>
-- ** Cantab is hiring: www.cantabResearch.com/openings ** -Dr A J Robinson, Founder, Cantab Research Ltd
Phone direct: 01223 778240 office: 01223 794497
Company reg no GB 05697423, VAT reg no 925606030
51 Canterbury Street, Cambridge, CB4 3QG, UK
From tonyr at cantabResearch.com Tue Nov 4 20:04:46 2014
From: tonyr at cantabResearch.com (Tony Robinson)
Date: Fri Jan 30 04:23:33 2015
Subject: [HTK-Users] HTK license agreement
In-Reply-To: <545241EC02000049000E3077@pta-emo.csir.co.za>
References: <545241EC02000049000E3077@pta-emo.csir.co.za>
Message-ID: <5459315E.9030409@cantabResearch.com>
I just saw this post - I hope I haven't also missed any replies.
It's been a while since I read the HTK licence, but from memory and past
commercial practices I believe that what you are proposing is entirely
acceptable according to the HTK licence.
In fact I think www.speechmatics.com uses HVite in exactly this way to
do some final tidying up of the large vocabulary speech recognition output.

Tony
On 30/10/14 11:49, Georg Schlunz wrote:
> Good day
>
> Regarding the HTK license, as specified at http://htk.eng.cam.ac.uk/docs/licen
se.shtml , I would like to know whether the following scenario is permitted:
>
> The HTK software (including HVite) sits on a server in-house in our organisati
on, as per license sections 2.1 and 2.3.
> The HTK software (including HVite) is never distributed to a commercial (or no
n-commercial) party, as per license section 2.2.
>
> We have written our own server-client software, where:
> a) the client records speech and sends the audio file to the server, which pas
ses it on to HVite (the server software and HTK sit on the same in-house machine
)
> b) HVite decodes the audio into text
> c) the server replies to the client with the decoded text and the client proce
sses the text somehow
>
> Naturally, the client software contains no HTK code; it only processes data pr
oduced by HTK.
>
> Therefore, may this client software and decoding SERVICE be sold commercially
(as long as we agree to license sections 2.4 and 2.5)?
>
> Thank you
> Georg Schlunz
>
-- ** Cantab is hiring: www.cantabResearch.com/openings ** -Dr A J Robinson, Founder, Cantab Research Ltd
Phone direct: 01223 778240 office: 01223 794497
Company reg no GB 05697423, VAT reg no 925606030
51 Canterbury Street, Cambridge, CB4 3QG, UK
From tonyr at cantabResearch.com Tue Nov 4 20:04:46 2014
From: tonyr at cantabResearch.com (Tony Robinson)
Date: Sat Jan 31 05:12:50 2015
Subject: [HTK-Users] HTK license agreement
In-Reply-To: <545241EC02000049000E3077@pta-emo.csir.co.za>
References: <545241EC02000049000E3077@pta-emo.csir.co.za>
Message-ID: <5459315E.9030409@cantabResearch.com>
I just saw this post - I hope I haven't also missed any replies.
It's been a while since I read the HTK licence, but from memory and past
commercial practices I believe that what you are proposing is entirely
acceptable according to the HTK licence.
In fact I think www.speechmatics.com uses HVite in exactly this way to
do some final tidying up of the large vocabulary speech recognition output.
Tony
On 30/10/14 11:49, Georg Schlunz wrote:
> Good day

>
> Regarding the HTK license, as specified at http://htk.eng.cam.ac.uk/docs/licen
se.shtml , I would like to know whether the following scenario is permitted:
>
> The HTK software (including HVite) sits on a server in-house in our organisati
on, as per license sections 2.1 and 2.3.
> The HTK software (including HVite) is never distributed to a commercial (or no
n-commercial) party, as per license section 2.2.
>
> We have written our own server-client software, where:
> a) the client records speech and sends the audio file to the server, which pas
ses it on to HVite (the server software and HTK sit on the same in-house machine
)
> b) HVite decodes the audio into text
> c) the server replies to the client with the decoded text and the client proce
sses the text somehow
>
> Naturally, the client software contains no HTK code; it only processes data pr
oduced by HTK.
>
> Therefore, may this client software and decoding SERVICE be sold commercially
(as long as we agree to license sections 2.4 and 2.5)?
>
> Thank you
> Georg Schlunz
>
-- ** Cantab is hiring: www.cantabResearch.com/openings ** -Dr A J Robinson, Founder, Cantab Research Ltd
Phone direct: 01223 778240 office: 01223 794497
Company reg no GB 05697423, VAT reg no 925606030
51 Canterbury Street, Cambridge, CB4 3QG, UK
From tonyr at cantabResearch.com Tue Nov 4 20:04:46 2014
From: tonyr at cantabResearch.com (Tony Robinson)
Date: Sun Feb 1 05:05:41 2015
Subject: [HTK-Users] HTK license agreement
In-Reply-To: <545241EC02000049000E3077@pta-emo.csir.co.za>
References: <545241EC02000049000E3077@pta-emo.csir.co.za>
Message-ID: <5459315E.9030409@cantabResearch.com>
I just saw this post - I hope I haven't also missed any replies.
It's been a while since I read the HTK licence, but from memory and past
commercial practices I believe that what you are proposing is entirely
acceptable according to the HTK licence.
In fact I think www.speechmatics.com uses HVite in exactly this way to
do some final tidying up of the large vocabulary speech recognition output.
Tony
On 30/10/14 11:49, Georg Schlunz wrote:
> Good day
>
> Regarding the HTK license, as specified at http://htk.eng.cam.ac.uk/docs/licen
se.shtml , I would like to know whether the following scenario is permitted:
>
> The HTK software (including HVite) sits on a server in-house in our organisati

on, as per license sections 2.1 and 2.3.


> The HTK software (including HVite) is never distributed to a commercial (or no
n-commercial) party, as per license section 2.2.
>
> We have written our own server-client software, where:
> a) the client records speech and sends the audio file to the server, which pas
ses it on to HVite (the server software and HTK sit on the same in-house machine
)
> b) HVite decodes the audio into text
> c) the server replies to the client with the decoded text and the client proce
sses the text somehow
>
> Naturally, the client software contains no HTK code; it only processes data pr
oduced by HTK.
>
> Therefore, may this client software and decoding SERVICE be sold commercially
(as long as we agree to license sections 2.4 and 2.5)?
>
> Thank you
> Georg Schlunz
>
-- ** Cantab is hiring: www.cantabResearch.com/openings ** -Dr A J Robinson, Founder, Cantab Research Ltd
Phone direct: 01223 778240 office: 01223 794497
Company reg no GB 05697423, VAT reg no 925606030
51 Canterbury Street, Cambridge, CB4 3QG, UK
From tonyr at cantabResearch.com Tue Nov 4 20:04:46 2014
From: tonyr at cantabResearch.com (Tony Robinson)
Date: Mon Feb 2 04:59:20 2015
Subject: [HTK-Users] HTK license agreement
In-Reply-To: <545241EC02000049000E3077@pta-emo.csir.co.za>
References: <545241EC02000049000E3077@pta-emo.csir.co.za>
Message-ID: <5459315E.9030409@cantabResearch.com>
I just saw this post - I hope I haven't also missed any replies.
It's been a while since I read the HTK licence, but from memory and past
commercial practices I believe that what you are proposing is entirely
acceptable according to the HTK licence.
In fact I think www.speechmatics.com uses HVite in exactly this way to
do some final tidying up of the large vocabulary speech recognition output.
Tony
On 30/10/14 11:49, Georg Schlunz wrote:
> Good day
>
> Regarding the HTK license, as specified at http://htk.eng.cam.ac.uk/docs/licen
se.shtml , I would like to know whether the following scenario is permitted:
>
> The HTK software (including HVite) sits on a server in-house in our organisati
on, as per license sections 2.1 and 2.3.
> The HTK software (including HVite) is never distributed to a commercial (or no
n-commercial) party, as per license section 2.2.
>
> We have written our own server-client software, where:

> a) the client records speech and sends the audio file to the server, which pas
ses it on to HVite (the server software and HTK sit on the same in-house machine
)
> b) HVite decodes the audio into text
> c) the server replies to the client with the decoded text and the client proce
sses the text somehow
>
> Naturally, the client software contains no HTK code; it only processes data pr
oduced by HTK.
>
> Therefore, may this client software and decoding SERVICE be sold commercially
(as long as we agree to license sections 2.4 and 2.5)?
>
> Thank you
> Georg Schlunz
>
-- ** Cantab is hiring: www.cantabResearch.com/openings ** -Dr A J Robinson, Founder, Cantab Research Ltd
Phone direct: 01223 778240 office: 01223 794497
Company reg no GB 05697423, VAT reg no 925606030
51 Canterbury Street, Cambridge, CB4 3QG, UK
From tonyr at cantabResearch.com Tue Nov 4 20:04:46 2014
From: tonyr at cantabResearch.com (Tony Robinson)
Date: Tue Feb 3 04:36:23 2015
Subject: [HTK-Users] HTK license agreement
In-Reply-To: <545241EC02000049000E3077@pta-emo.csir.co.za>
References: <545241EC02000049000E3077@pta-emo.csir.co.za>
Message-ID: <5459315E.9030409@cantabResearch.com>
I just saw this post - I hope I haven't also missed any replies.
It's been a while since I read the HTK licence, but from memory and past
commercial practices I believe that what you are proposing is entirely
acceptable according to the HTK licence.
In fact I think www.speechmatics.com uses HVite in exactly this way to
do some final tidying up of the large vocabulary speech recognition output.
Tony
On 30/10/14 11:49, Georg Schlunz wrote:
> Good day
>
> Regarding the HTK license, as specified at http://htk.eng.cam.ac.uk/docs/licen
se.shtml , I would like to know whether the following scenario is permitted:
>
> The HTK software (including HVite) sits on a server in-house in our organisati
on, as per license sections 2.1 and 2.3.
> The HTK software (including HVite) is never distributed to a commercial (or no
n-commercial) party, as per license section 2.2.
>
> We have written our own server-client software, where:
> a) the client records speech and sends the audio file to the server, which pas
ses it on to HVite (the server software and HTK sit on the same in-house machine
)
> b) HVite decodes the audio into text
> c) the server replies to the client with the decoded text and the client proce

sses the text somehow


>
> Naturally, the client software contains no HTK code; it only processes data pr
oduced by HTK.
>
> Therefore, may this client software and decoding SERVICE be sold commercially
(as long as we agree to license sections 2.4 and 2.5)?
>
> Thank you
> Georg Schlunz
>
-- ** Cantab is hiring: www.cantabResearch.com/openings ** -Dr A J Robinson, Founder, Cantab Research Ltd
Phone direct: 01223 778240 office: 01223 794497
Company reg no GB 05697423, VAT reg no 925606030
51 Canterbury Street, Cambridge, CB4 3QG, UK
From tonyr at cantabResearch.com Tue Nov 4 20:04:46 2014
From: tonyr at cantabResearch.com (Tony Robinson)
Date: Wed Feb 4 04:24:40 2015
Subject: [HTK-Users] HTK license agreement
In-Reply-To: <545241EC02000049000E3077@pta-emo.csir.co.za>
References: <545241EC02000049000E3077@pta-emo.csir.co.za>
Message-ID: <5459315E.9030409@cantabResearch.com>
I just saw this post - I hope I haven't also missed any replies.
It's been a while since I read the HTK licence, but from memory and past
commercial practices I believe that what you are proposing is entirely
acceptable according to the HTK licence.
In fact I think www.speechmatics.com uses HVite in exactly this way to
do some final tidying up of the large vocabulary speech recognition output.
Tony
On 30/10/14 11:49, Georg Schlunz wrote:
> Good day
>
> Regarding the HTK license, as specified at http://htk.eng.cam.ac.uk/docs/licen
se.shtml , I would like to know whether the following scenario is permitted:
>
> The HTK software (including HVite) sits on a server in-house in our organisati
on, as per license sections 2.1 and 2.3.
> The HTK software (including HVite) is never distributed to a commercial (or no
n-commercial) party, as per license section 2.2.
>
> We have written our own server-client software, where:
> a) the client records speech and sends the audio file to the server, which pas
ses it on to HVite (the server software and HTK sit on the same in-house machine
)
> b) HVite decodes the audio into text
> c) the server replies to the client with the decoded text and the client proce
sses the text somehow
>
> Naturally, the client software contains no HTK code; it only processes data pr
oduced by HTK.
>

> Therefore, may this client software and decoding SERVICE be sold commercially
(as long as we agree to license sections 2.4 and 2.5)?
>
> Thank you
> Georg Schlunz
>
-- ** Cantab is hiring: www.cantabResearch.com/openings ** -Dr A J Robinson, Founder, Cantab Research Ltd
Phone direct: 01223 778240 office: 01223 794497
Company reg no GB 05697423, VAT reg no 925606030
51 Canterbury Street, Cambridge, CB4 3QG, UK
From tonyr at cantabResearch.com Tue Nov 4 20:04:46 2014
From: tonyr at cantabResearch.com (Tony Robinson)
Date: Thu Feb 5 04:29:41 2015
Subject: [HTK-Users] HTK license agreement
In-Reply-To: <545241EC02000049000E3077@pta-emo.csir.co.za>
References: <545241EC02000049000E3077@pta-emo.csir.co.za>
Message-ID: <5459315E.9030409@cantabResearch.com>
I just saw this post - I hope I haven't also missed any replies.
It's been a while since I read the HTK licence, but from memory and past
commercial practices I believe that what you are proposing is entirely
acceptable according to the HTK licence.
In fact I think www.speechmatics.com uses HVite in exactly this way to
do some final tidying up of the large vocabulary speech recognition output.
Tony
On 30/10/14 11:49, Georg Schlunz wrote:
> Good day
>
> Regarding the HTK license, as specified at http://htk.eng.cam.ac.uk/docs/licen
se.shtml , I would like to know whether the following scenario is permitted:
>
> The HTK software (including HVite) sits on a server in-house in our organisati
on, as per license sections 2.1 and 2.3.
> The HTK software (including HVite) is never distributed to a commercial (or no
n-commercial) party, as per license section 2.2.
>
> We have written our own server-client software, where:
> a) the client records speech and sends the audio file to the server, which pas
ses it on to HVite (the server software and HTK sit on the same in-house machine
)
> b) HVite decodes the audio into text
> c) the server replies to the client with the decoded text and the client proce
sses the text somehow
>
> Naturally, the client software contains no HTK code; it only processes data pr
oduced by HTK.
>
> Therefore, may this client software and decoding SERVICE be sold commercially
(as long as we agree to license sections 2.4 and 2.5)?
>
> Thank you
> Georg Schlunz

>
-- ** Cantab is hiring: www.cantabResearch.com/openings ** -Dr A J Robinson, Founder, Cantab Research Ltd
Phone direct: 01223 778240 office: 01223 794497
Company reg no GB 05697423, VAT reg no 925606030
51 Canterbury Street, Cambridge, CB4 3QG, UK
From tonyr at cantabResearch.com Tue Nov 4 20:04:46 2014
From: tonyr at cantabResearch.com (Tony Robinson)
Date: Fri Feb 6 04:27:21 2015
Subject: [HTK-Users] HTK license agreement
In-Reply-To: <545241EC02000049000E3077@pta-emo.csir.co.za>
References: <545241EC02000049000E3077@pta-emo.csir.co.za>
Message-ID: <5459315E.9030409@cantabResearch.com>
I just saw this post - I hope I haven't also missed any replies.
It's been a while since I read the HTK licence, but from memory and past
commercial practices I believe that what you are proposing is entirely
acceptable according to the HTK licence.
In fact I think www.speechmatics.com uses HVite in exactly this way to
do some final tidying up of the large vocabulary speech recognition output.
Tony
On 30/10/14 11:49, Georg Schlunz wrote:
> Good day
>
> Regarding the HTK license, as specified at http://htk.eng.cam.ac.uk/docs/licen
se.shtml , I would like to know whether the following scenario is permitted:
>
> The HTK software (including HVite) sits on a server in-house in our organisati
on, as per license sections 2.1 and 2.3.
> The HTK software (including HVite) is never distributed to a commercial (or no
n-commercial) party, as per license section 2.2.
>
> We have written our own server-client software, where:
> a) the client records speech and sends the audio file to the server, which pas
ses it on to HVite (the server software and HTK sit on the same in-house machine
)
> b) HVite decodes the audio into text
> c) the server replies to the client with the decoded text and the client proce
sses the text somehow
>
> Naturally, the client software contains no HTK code; it only processes data pr
oduced by HTK.
>
> Therefore, may this client software and decoding SERVICE be sold commercially
(as long as we agree to license sections 2.4 and 2.5)?
>
> Thank you
> Georg Schlunz
>
-- ** Cantab is hiring: www.cantabResearch.com/openings ** -Dr A J Robinson, Founder, Cantab Research Ltd
Phone direct: 01223 778240 office: 01223 794497

Company reg no GB 05697423, VAT reg no 925606030


51 Canterbury Street, Cambridge, CB4 3QG, UK
From tonyr at cantabResearch.com Tue Nov 4 20:04:46 2014
From: tonyr at cantabResearch.com (Tony Robinson)
Date: Sat Feb 7 04:20:20 2015
Subject: [HTK-Users] HTK license agreement
In-Reply-To: <545241EC02000049000E3077@pta-emo.csir.co.za>
References: <545241EC02000049000E3077@pta-emo.csir.co.za>
Message-ID: <5459315E.9030409@cantabResearch.com>
I just saw this post - I hope I haven't also missed any replies.
It's been a while since I read the HTK licence, but from memory and past
commercial practices I believe that what you are proposing is entirely
acceptable according to the HTK licence.
In fact I think www.speechmatics.com uses HVite in exactly this way to
do some final tidying up of the large vocabulary speech recognition output.
Tony
On 30/10/14 11:49, Georg Schlunz wrote:
> Good day
>
> Regarding the HTK license, as specified at http://htk.eng.cam.ac.uk/docs/licen
se.shtml , I would like to know whether the following scenario is permitted:
>
> The HTK software (including HVite) sits on a server in-house in our organisati
on, as per license sections 2.1 and 2.3.
> The HTK software (including HVite) is never distributed to a commercial (or no
n-commercial) party, as per license section 2.2.
>
> We have written our own server-client software, where:
> a) the client records speech and sends the audio file to the server, which pas
ses it on to HVite (the server software and HTK sit on the same in-house machine
)
> b) HVite decodes the audio into text
> c) the server replies to the client with the decoded text and the client proce
sses the text somehow
>
> Naturally, the client software contains no HTK code; it only processes data pr
oduced by HTK.
>
> Therefore, may this client software and decoding SERVICE be sold commercially
(as long as we agree to license sections 2.4 and 2.5)?
>
> Thank you
> Georg Schlunz
>
-- ** Cantab is hiring: www.cantabResearch.com/openings ** -Dr A J Robinson, Founder, Cantab Research Ltd
Phone direct: 01223 778240 office: 01223 794497
Company reg no GB 05697423, VAT reg no 925606030
51 Canterbury Street, Cambridge, CB4 3QG, UK
From tonyr at cantabResearch.com Tue Nov 4 20:04:46 2014
From: tonyr at cantabResearch.com (Tony Robinson)

Date: Sun Feb 8 04:51:07 2015


Subject: [HTK-Users] HTK license agreement
In-Reply-To: <545241EC02000049000E3077@pta-emo.csir.co.za>
References: <545241EC02000049000E3077@pta-emo.csir.co.za>
Message-ID: <5459315E.9030409@cantabResearch.com>
I just saw this post - I hope I haven't also missed any replies.
It's been a while since I read the HTK licence, but from memory and past
commercial practices I believe that what you are proposing is entirely
acceptable according to the HTK licence.
In fact I think www.speechmatics.com uses HVite in exactly this way to
do some final tidying up of the large vocabulary speech recognition output.
Tony
On 30/10/14 11:49, Georg Schlunz wrote:
> Good day
>
> Regarding the HTK license, as specified at http://htk.eng.cam.ac.uk/docs/licen
se.shtml , I would like to know whether the following scenario is permitted:
>
> The HTK software (including HVite) sits on a server in-house in our organisati
on, as per license sections 2.1 and 2.3.
> The HTK software (including HVite) is never distributed to a commercial (or no
n-commercial) party, as per license section 2.2.
>
> We have written our own server-client software, where:
> a) the client records speech and sends the audio file to the server, which pas
ses it on to HVite (the server software and HTK sit on the same in-house machine
)
> b) HVite decodes the audio into text
> c) the server replies to the client with the decoded text and the client proce
sses the text somehow
>
> Naturally, the client software contains no HTK code; it only processes data pr
oduced by HTK.
>
> Therefore, may this client software and decoding SERVICE be sold commercially
(as long as we agree to license sections 2.4 and 2.5)?
>
> Thank you
> Georg Schlunz
>
-- ** Cantab is hiring: www.cantabResearch.com/openings ** -Dr A J Robinson, Founder, Cantab Research Ltd
Phone direct: 01223 778240 office: 01223 794497
Company reg no GB 05697423, VAT reg no 925606030
51 Canterbury Street, Cambridge, CB4 3QG, UK
From tonyr at cantabResearch.com Tue Nov 4 20:04:46 2014
From: tonyr at cantabResearch.com (Tony Robinson)
Date: Mon Feb 9 04:21:35 2015
Subject: [HTK-Users] HTK license agreement
In-Reply-To: <545241EC02000049000E3077@pta-emo.csir.co.za>
References: <545241EC02000049000E3077@pta-emo.csir.co.za>
Message-ID: <5459315E.9030409@cantabResearch.com>

I just saw this post - I hope I haven't also missed any replies.
It's been a while since I read the HTK licence, but from memory and past
commercial practices I believe that what you are proposing is entirely
acceptable according to the HTK licence.
In fact I think www.speechmatics.com uses HVite in exactly this way to
do some final tidying up of the large vocabulary speech recognition output.
Tony
On 30/10/14 11:49, Georg Schlunz wrote:
> Good day
>
> Regarding the HTK license, as specified at http://htk.eng.cam.ac.uk/docs/licen
se.shtml , I would like to know whether the following scenario is permitted:
>
> The HTK software (including HVite) sits on a server in-house in our organisati
on, as per license sections 2.1 and 2.3.
> The HTK software (including HVite) is never distributed to a commercial (or no
n-commercial) party, as per license section 2.2.
>
> We have written our own server-client software, where:
> a) the client records speech and sends the audio file to the server, which pas
ses it on to HVite (the server software and HTK sit on the same in-house machine
)
> b) HVite decodes the audio into text
> c) the server replies to the client with the decoded text and the client proce
sses the text somehow
>
> Naturally, the client software contains no HTK code; it only processes data pr
oduced by HTK.
>
> Therefore, may this client software and decoding SERVICE be sold commercially
(as long as we agree to license sections 2.4 and 2.5)?
>
> Thank you
> Georg Schlunz
>
-- ** Cantab is hiring: www.cantabResearch.com/openings ** -Dr A J Robinson, Founder, Cantab Research Ltd
Phone direct: 01223 778240 office: 01223 794497
Company reg no GB 05697423, VAT reg no 925606030
51 Canterbury Street, Cambridge, CB4 3QG, UK
From tonyr at cantabResearch.com Tue Nov 4 20:04:46 2014
From: tonyr at cantabResearch.com (Tony Robinson)
Date: Tue Feb 10 04:25:05 2015
Subject: [HTK-Users] HTK license agreement
In-Reply-To: <545241EC02000049000E3077@pta-emo.csir.co.za>
References: <545241EC02000049000E3077@pta-emo.csir.co.za>
Message-ID: <5459315E.9030409@cantabResearch.com>
I just saw this post - I hope I haven't also missed any replies.
It's been a while since I read the HTK licence, but from memory and past
commercial practices I believe that what you are proposing is entirely

acceptable according to the HTK licence.


In fact I think www.speechmatics.com uses HVite in exactly this way to
do some final tidying up of the large vocabulary speech recognition output.
Tony
On 30/10/14 11:49, Georg Schlunz wrote:
> Good day
>
> Regarding the HTK license, as specified at http://htk.eng.cam.ac.uk/docs/licen
se.shtml , I would like to know whether the following scenario is permitted:
>
> The HTK software (including HVite) sits on a server in-house in our organisati
on, as per license sections 2.1 and 2.3.
> The HTK software (including HVite) is never distributed to a commercial (or no
n-commercial) party, as per license section 2.2.
>
> We have written our own server-client software, where:
> a) the client records speech and sends the audio file to the server, which pas
ses it on to HVite (the server software and HTK sit on the same in-house machine
)
> b) HVite decodes the audio into text
> c) the server replies to the client with the decoded text and the client proce
sses the text somehow
>
> Naturally, the client software contains no HTK code; it only processes data pr
oduced by HTK.
>
> Therefore, may this client software and decoding SERVICE be sold commercially
(as long as we agree to license sections 2.4 and 2.5)?
>
> Thank you
> Georg Schlunz
>
-- ** Cantab is hiring: www.cantabResearch.com/openings ** -Dr A J Robinson, Founder, Cantab Research Ltd
Phone direct: 01223 778240 office: 01223 794497
Company reg no GB 05697423, VAT reg no 925606030
51 Canterbury Street, Cambridge, CB4 3QG, UK
From tonyr at cantabResearch.com Tue Nov 4 20:04:46 2014
From: tonyr at cantabResearch.com (Tony Robinson)
Date: Wed Feb 11 04:29:37 2015
Subject: [HTK-Users] HTK license agreement
In-Reply-To: <545241EC02000049000E3077@pta-emo.csir.co.za>
References: <545241EC02000049000E3077@pta-emo.csir.co.za>
Message-ID: <5459315E.9030409@cantabResearch.com>
I just saw this post - I hope I haven't also missed any replies.
It's been a while since I read the HTK licence, but from memory and past
commercial practices I believe that what you are proposing is entirely
acceptable according to the HTK licence.
In fact I think www.speechmatics.com uses HVite in exactly this way to
do some final tidying up of the large vocabulary speech recognition output.

Tony
On 30/10/14 11:49, Georg Schlunz wrote:
> Good day
>
> Regarding the HTK license, as specified at http://htk.eng.cam.ac.uk/docs/licen
se.shtml , I would like to know whether the following scenario is permitted:
>
> The HTK software (including HVite) sits on a server in-house in our organisati
on, as per license sections 2.1 and 2.3.
> The HTK software (including HVite) is never distributed to a commercial (or no
n-commercial) party, as per license section 2.2.
>
> We have written our own server-client software, where:
> a) the client records speech and sends the audio file to the server, which pas
ses it on to HVite (the server software and HTK sit on the same in-house machine
)
> b) HVite decodes the audio into text
> c) the server replies to the client with the decoded text and the client proce
sses the text somehow
>
> Naturally, the client software contains no HTK code; it only processes data pr
oduced by HTK.
>
> Therefore, may this client software and decoding SERVICE be sold commercially
(as long as we agree to license sections 2.4 and 2.5)?
>
> Thank you
> Georg Schlunz
>
-- ** Cantab is hiring: www.cantabResearch.com/openings ** -Dr A J Robinson, Founder, Cantab Research Ltd
Phone direct: 01223 778240 office: 01223 794497
Company reg no GB 05697423, VAT reg no 925606030
51 Canterbury Street, Cambridge, CB4 3QG, UK
From tonyr at cantabResearch.com Tue Nov 4 20:04:46 2014
From: tonyr at cantabResearch.com (Tony Robinson)
Date: Thu Feb 12 04:47:37 2015
Subject: [HTK-Users] HTK license agreement
In-Reply-To: <545241EC02000049000E3077@pta-emo.csir.co.za>
References: <545241EC02000049000E3077@pta-emo.csir.co.za>
Message-ID: <5459315E.9030409@cantabResearch.com>
I just saw this post - I hope I haven't also missed any replies.
It's been a while since I read the HTK licence, but from memory and past
commercial practices I believe that what you are proposing is entirely
acceptable according to the HTK licence.
In fact I think www.speechmatics.com uses HVite in exactly this way to
do some final tidying up of the large vocabulary speech recognition output.
Tony
On 30/10/14 11:49, Georg Schlunz wrote:
> Good day

>
> Regarding the HTK license, as specified at http://htk.eng.cam.ac.uk/docs/licen
se.shtml , I would like to know whether the following scenario is permitted:
>
> The HTK software (including HVite) sits on a server in-house in our organisati
on, as per license sections 2.1 and 2.3.
> The HTK software (including HVite) is never distributed to a commercial (or no
n-commercial) party, as per license section 2.2.
>
> We have written our own server-client software, where:
> a) the client records speech and sends the audio file to the server, which pas
ses it on to HVite (the server software and HTK sit on the same in-house machine
)
> b) HVite decodes the audio into text
> c) the server replies to the client with the decoded text and the client proce
sses the text somehow
>
> Naturally, the client software contains no HTK code; it only processes data pr
oduced by HTK.
>
> Therefore, may this client software and decoding SERVICE be sold commercially
(as long as we agree to license sections 2.4 and 2.5)?
>
> Thank you
> Georg Schlunz
>
-- ** Cantab is hiring: www.cantabResearch.com/openings ** -Dr A J Robinson, Founder, Cantab Research Ltd
Phone direct: 01223 778240 office: 01223 794497
Company reg no GB 05697423, VAT reg no 925606030
51 Canterbury Street, Cambridge, CB4 3QG, UK
From tonyr at cantabResearch.com Tue Nov 4 20:04:46 2014
From: tonyr at cantabResearch.com (Tony Robinson)
Date: Fri Feb 13 04:59:33 2015
Subject: [HTK-Users] HTK license agreement
In-Reply-To: <545241EC02000049000E3077@pta-emo.csir.co.za>
References: <545241EC02000049000E3077@pta-emo.csir.co.za>
Message-ID: <5459315E.9030409@cantabResearch.com>
I just saw this post - I hope I haven't also missed any replies.
It's been a while since I read the HTK licence, but from memory and past
commercial practices I believe that what you are proposing is entirely
acceptable according to the HTK licence.
In fact I think www.speechmatics.com uses HVite in exactly this way to
do some final tidying up of the large vocabulary speech recognition output.
Tony
On 30/10/14 11:49, Georg Schlunz wrote:
> Good day
>
> Regarding the HTK license, as specified at http://htk.eng.cam.ac.uk/docs/licen
se.shtml , I would like to know whether the following scenario is permitted:
>
> The HTK software (including HVite) sits on a server in-house in our organisati

on, as per license sections 2.1 and 2.3.


> The HTK software (including HVite) is never distributed to a commercial (or no
n-commercial) party, as per license section 2.2.
>
> We have written our own server-client software, where:
> a) the client records speech and sends the audio file to the server, which pas
ses it on to HVite (the server software and HTK sit on the same in-house machine
)
> b) HVite decodes the audio into text
> c) the server replies to the client with the decoded text and the client proce
sses the text somehow
>
> Naturally, the client software contains no HTK code; it only processes data pr
oduced by HTK.
>
> Therefore, may this client software and decoding SERVICE be sold commercially
(as long as we agree to license sections 2.4 and 2.5)?
>
> Thank you
> Georg Schlunz
>
-- ** Cantab is hiring: www.cantabResearch.com/openings ** -Dr A J Robinson, Founder, Cantab Research Ltd
Phone direct: 01223 778240 office: 01223 794497
Company reg no GB 05697423, VAT reg no 925606030
51 Canterbury Street, Cambridge, CB4 3QG, UK
From tonyr at cantabResearch.com Tue Nov 4 20:04:46 2014
From: tonyr at cantabResearch.com (Tony Robinson)
Date: Sat Feb 14 05:14:51 2015
Subject: [HTK-Users] HTK license agreement
In-Reply-To: <545241EC02000049000E3077@pta-emo.csir.co.za>
References: <545241EC02000049000E3077@pta-emo.csir.co.za>
Message-ID: <5459315E.9030409@cantabResearch.com>
I just saw this post - I hope I haven't also missed any replies.
It's been a while since I read the HTK licence, but from memory and past
commercial practices I believe that what you are proposing is entirely
acceptable according to the HTK licence.
In fact I think www.speechmatics.com uses HVite in exactly this way to
do some final tidying up of the large vocabulary speech recognition output.
Tony
On 30/10/14 11:49, Georg Schlunz wrote:
> Good day
>
> Regarding the HTK license, as specified at http://htk.eng.cam.ac.uk/docs/licen
se.shtml , I would like to know whether the following scenario is permitted:
>
> The HTK software (including HVite) sits on a server in-house in our organisati
on, as per license sections 2.1 and 2.3.
> The HTK software (including HVite) is never distributed to a commercial (or no
n-commercial) party, as per license section 2.2.
>
> We have written our own server-client software, where:

> a) the client records speech and sends the audio file to the server, which pas
ses it on to HVite (the server software and HTK sit on the same in-house machine
)
> b) HVite decodes the audio into text
> c) the server replies to the client with the decoded text and the client proce
sses the text somehow
>
> Naturally, the client software contains no HTK code; it only processes data pr
oduced by HTK.
>
> Therefore, may this client software and decoding SERVICE be sold commercially
(as long as we agree to license sections 2.4 and 2.5)?
>
> Thank you
> Georg Schlunz
>
-- ** Cantab is hiring: www.cantabResearch.com/openings ** -Dr A J Robinson, Founder, Cantab Research Ltd
Phone direct: 01223 778240 office: 01223 794497
Company reg no GB 05697423, VAT reg no 925606030
51 Canterbury Street, Cambridge, CB4 3QG, UK
From tonyr at cantabResearch.com Tue Nov 4 20:04:46 2014
From: tonyr at cantabResearch.com (Tony Robinson)
Date: Sun Feb 15 04:31:03 2015
Subject: [HTK-Users] HTK license agreement
In-Reply-To: <545241EC02000049000E3077@pta-emo.csir.co.za>
References: <545241EC02000049000E3077@pta-emo.csir.co.za>
Message-ID: <5459315E.9030409@cantabResearch.com>
I just saw this post - I hope I haven't also missed any replies.
It's been a while since I read the HTK licence, but from memory and past
commercial practices I believe that what you are proposing is entirely
acceptable according to the HTK licence.
In fact I think www.speechmatics.com uses HVite in exactly this way to
do some final tidying up of the large vocabulary speech recognition output.
Tony
On 30/10/14 11:49, Georg Schlunz wrote:
> Good day
>
> Regarding the HTK license, as specified at http://htk.eng.cam.ac.uk/docs/licen
se.shtml , I would like to know whether the following scenario is permitted:
>
> The HTK software (including HVite) sits on a server in-house in our organisati
on, as per license sections 2.1 and 2.3.
> The HTK software (including HVite) is never distributed to a commercial (or no
n-commercial) party, as per license section 2.2.
>
> We have written our own server-client software, where:
> a) the client records speech and sends the audio file to the server, which pas
ses it on to HVite (the server software and HTK sit on the same in-house machine
)
> b) HVite decodes the audio into text
> c) the server replies to the client with the decoded text and the client proce

sses the text somehow


>
> Naturally, the client software contains no HTK code; it only processes data pr
oduced by HTK.
>
> Therefore, may this client software and decoding SERVICE be sold commercially
(as long as we agree to license sections 2.4 and 2.5)?
>
> Thank you
> Georg Schlunz
>
-- ** Cantab is hiring: www.cantabResearch.com/openings ** -Dr A J Robinson, Founder, Cantab Research Ltd
Phone direct: 01223 778240 office: 01223 794497
Company reg no GB 05697423, VAT reg no 925606030
51 Canterbury Street, Cambridge, CB4 3QG, UK
From tonyr at cantabResearch.com Tue Nov 4 20:04:46 2014
From: tonyr at cantabResearch.com (Tony Robinson)
Date: Mon Feb 16 04:27:52 2015
Subject: [HTK-Users] HTK license agreement
In-Reply-To: <545241EC02000049000E3077@pta-emo.csir.co.za>
References: <545241EC02000049000E3077@pta-emo.csir.co.za>
Message-ID: <5459315E.9030409@cantabResearch.com>
I just saw this post - I hope I haven't also missed any replies.
It's been a while since I read the HTK licence, but from memory and past
commercial practices I believe that what you are proposing is entirely
acceptable according to the HTK licence.
In fact I think www.speechmatics.com uses HVite in exactly this way to
do some final tidying up of the large vocabulary speech recognition output.
Tony
On 30/10/14 11:49, Georg Schlunz wrote:
> Good day
>
> Regarding the HTK license, as specified at http://htk.eng.cam.ac.uk/docs/licen
se.shtml , I would like to know whether the following scenario is permitted:
>
> The HTK software (including HVite) sits on a server in-house in our organisati
on, as per license sections 2.1 and 2.3.
> The HTK software (including HVite) is never distributed to a commercial (or no
n-commercial) party, as per license section 2.2.
>
> We have written our own server-client software, where:
> a) the client records speech and sends the audio file to the server, which pas
ses it on to HVite (the server software and HTK sit on the same in-house machine
)
> b) HVite decodes the audio into text
> c) the server replies to the client with the decoded text and the client proce
sses the text somehow
>
> Naturally, the client software contains no HTK code; it only processes data pr
oduced by HTK.
>

> Therefore, may this client software and decoding SERVICE be sold commercially
(as long as we agree to license sections 2.4 and 2.5)?
>
> Thank you
> Georg Schlunz
>
-- ** Cantab is hiring: www.cantabResearch.com/openings ** -Dr A J Robinson, Founder, Cantab Research Ltd
Phone direct: 01223 778240 office: 01223 794497
Company reg no GB 05697423, VAT reg no 925606030
51 Canterbury Street, Cambridge, CB4 3QG, UK
From tonyr at cantabResearch.com Tue Nov 4 20:04:46 2014
From: tonyr at cantabResearch.com (Tony Robinson)
Date: Tue Feb 17 04:27:45 2015
Subject: [HTK-Users] HTK license agreement
In-Reply-To: <545241EC02000049000E3077@pta-emo.csir.co.za>
References: <545241EC02000049000E3077@pta-emo.csir.co.za>
Message-ID: <5459315E.9030409@cantabResearch.com>
I just saw this post - I hope I haven't also missed any replies.
It's been a while since I read the HTK licence, but from memory and past
commercial practices I believe that what you are proposing is entirely
acceptable according to the HTK licence.
In fact I think www.speechmatics.com uses HVite in exactly this way to
do some final tidying up of the large vocabulary speech recognition output.
Tony
On 30/10/14 11:49, Georg Schlunz wrote:
> Good day
>
> Regarding the HTK license, as specified at http://htk.eng.cam.ac.uk/docs/licen
se.shtml , I would like to know whether the following scenario is permitted:
>
> The HTK software (including HVite) sits on a server in-house in our organisati
on, as per license sections 2.1 and 2.3.
> The HTK software (including HVite) is never distributed to a commercial (or no
n-commercial) party, as per license section 2.2.
>
> We have written our own server-client software, where:
> a) the client records speech and sends the audio file to the server, which pas
ses it on to HVite (the server software and HTK sit on the same in-house machine
)
> b) HVite decodes the audio into text
> c) the server replies to the client with the decoded text and the client proce
sses the text somehow
>
> Naturally, the client software contains no HTK code; it only processes data pr
oduced by HTK.
>
> Therefore, may this client software and decoding SERVICE be sold commercially
(as long as we agree to license sections 2.4 and 2.5)?
>
> Thank you
> Georg Schlunz

>
-- ** Cantab is hiring: www.cantabResearch.com/openings ** -Dr A J Robinson, Founder, Cantab Research Ltd
Phone direct: 01223 778240 office: 01223 794497
Company reg no GB 05697423, VAT reg no 925606030
51 Canterbury Street, Cambridge, CB4 3QG, UK
From tonyr at cantabResearch.com Tue Nov 4 20:04:46 2014
From: tonyr at cantabResearch.com (Tony Robinson)
Date: Wed Feb 18 04:25:48 2015
Subject: [HTK-Users] HTK license agreement
In-Reply-To: <545241EC02000049000E3077@pta-emo.csir.co.za>
References: <545241EC02000049000E3077@pta-emo.csir.co.za>
Message-ID: <5459315E.9030409@cantabResearch.com>
I just saw this post - I hope I haven't also missed any replies.
It's been a while since I read the HTK licence, but from memory and past
commercial practices I believe that what you are proposing is entirely
acceptable according to the HTK licence.
In fact I think www.speechmatics.com uses HVite in exactly this way to
do some final tidying up of the large vocabulary speech recognition output.
Tony
On 30/10/14 11:49, Georg Schlunz wrote:
> Good day
>
> Regarding the HTK license, as specified at http://htk.eng.cam.ac.uk/docs/licen
se.shtml , I would like to know whether the following scenario is permitted:
>
> The HTK software (including HVite) sits on a server in-house in our organisati
on, as per license sections 2.1 and 2.3.
> The HTK software (including HVite) is never distributed to a commercial (or no
n-commercial) party, as per license section 2.2.
>
> We have written our own server-client software, where:
> a) the client records speech and sends the audio file to the server, which pas
ses it on to HVite (the server software and HTK sit on the same in-house machine
)
> b) HVite decodes the audio into text
> c) the server replies to the client with the decoded text and the client proce
sses the text somehow
>
> Naturally, the client software contains no HTK code; it only processes data pr
oduced by HTK.
>
> Therefore, may this client software and decoding SERVICE be sold commercially
(as long as we agree to license sections 2.4 and 2.5)?
>
> Thank you
> Georg Schlunz
>
-- ** Cantab is hiring: www.cantabResearch.com/openings ** -Dr A J Robinson, Founder, Cantab Research Ltd
Phone direct: 01223 778240 office: 01223 794497

Company reg no GB 05697423, VAT reg no 925606030


51 Canterbury Street, Cambridge, CB4 3QG, UK
From tonyr at cantabResearch.com Tue Nov 4 20:04:46 2014
From: tonyr at cantabResearch.com (Tony Robinson)
Date: Thu Feb 19 04:35:31 2015
Subject: [HTK-Users] HTK license agreement
In-Reply-To: <545241EC02000049000E3077@pta-emo.csir.co.za>
References: <545241EC02000049000E3077@pta-emo.csir.co.za>
Message-ID: <5459315E.9030409@cantabResearch.com>
I just saw this post - I hope I haven't also missed any replies.
It's been a while since I read the HTK licence, but from memory and past
commercial practices I believe that what you are proposing is entirely
acceptable according to the HTK licence.
In fact I think www.speechmatics.com uses HVite in exactly this way to
do some final tidying up of the large vocabulary speech recognition output.
Tony
On 30/10/14 11:49, Georg Schlunz wrote:
> Good day
>
> Regarding the HTK license, as specified at http://htk.eng.cam.ac.uk/docs/licen
se.shtml , I would like to know whether the following scenario is permitted:
>
> The HTK software (including HVite) sits on a server in-house in our organisati
on, as per license sections 2.1 and 2.3.
> The HTK software (including HVite) is never distributed to a commercial (or no
n-commercial) party, as per license section 2.2.
>
> We have written our own server-client software, where:
> a) the client records speech and sends the audio file to the server, which pas
ses it on to HVite (the server software and HTK sit on the same in-house machine
)
> b) HVite decodes the audio into text
> c) the server replies to the client with the decoded text and the client proce
sses the text somehow
>
> Naturally, the client software contains no HTK code; it only processes data pr
oduced by HTK.
>
> Therefore, may this client software and decoding SERVICE be sold commercially
(as long as we agree to license sections 2.4 and 2.5)?
>
> Thank you
> Georg Schlunz
>
-- ** Cantab is hiring: www.cantabResearch.com/openings ** -Dr A J Robinson, Founder, Cantab Research Ltd
Phone direct: 01223 778240 office: 01223 794497
Company reg no GB 05697423, VAT reg no 925606030
51 Canterbury Street, Cambridge, CB4 3QG, UK
From tonyr at cantabResearch.com Tue Nov 4 20:04:46 2014
From: tonyr at cantabResearch.com (Tony Robinson)

Date: Fri Feb 20 04:27:14 2015


Subject: [HTK-Users] HTK license agreement
In-Reply-To: <545241EC02000049000E3077@pta-emo.csir.co.za>
References: <545241EC02000049000E3077@pta-emo.csir.co.za>
Message-ID: <5459315E.9030409@cantabResearch.com>
I just saw this post - I hope I haven't also missed any replies.
It's been a while since I read the HTK licence, but from memory and past
commercial practices I believe that what you are proposing is entirely
acceptable according to the HTK licence.
In fact I think www.speechmatics.com uses HVite in exactly this way to
do some final tidying up of the large vocabulary speech recognition output.
Tony
On 30/10/14 11:49, Georg Schlunz wrote:
> Good day
>
> Regarding the HTK license, as specified at http://htk.eng.cam.ac.uk/docs/licen
se.shtml , I would like to know whether the following scenario is permitted:
>
> The HTK software (including HVite) sits on a server in-house in our organisati
on, as per license sections 2.1 and 2.3.
> The HTK software (including HVite) is never distributed to a commercial (or no
n-commercial) party, as per license section 2.2.
>
> We have written our own server-client software, where:
> a) the client records speech and sends the audio file to the server, which pas
ses it on to HVite (the server software and HTK sit on the same in-house machine
)
> b) HVite decodes the audio into text
> c) the server replies to the client with the decoded text and the client proce
sses the text somehow
>
> Naturally, the client software contains no HTK code; it only processes data pr
oduced by HTK.
>
> Therefore, may this client software and decoding SERVICE be sold commercially
(as long as we agree to license sections 2.4 and 2.5)?
>
> Thank you
> Georg Schlunz
>
-- ** Cantab is hiring: www.cantabResearch.com/openings ** -Dr A J Robinson, Founder, Cantab Research Ltd
Phone direct: 01223 778240 office: 01223 794497
Company reg no GB 05697423, VAT reg no 925606030
51 Canterbury Street, Cambridge, CB4 3QG, UK
From tonyr at cantabResearch.com Tue Nov 4 20:04:46 2014
From: tonyr at cantabResearch.com (Tony Robinson)
Date: Sat Feb 21 04:26:59 2015
Subject: [HTK-Users] HTK license agreement
In-Reply-To: <545241EC02000049000E3077@pta-emo.csir.co.za>
References: <545241EC02000049000E3077@pta-emo.csir.co.za>
Message-ID: <5459315E.9030409@cantabResearch.com>

I just saw this post - I hope I haven't also missed any replies.
It's been a while since I read the HTK licence, but from memory and past
commercial practices I believe that what you are proposing is entirely
acceptable according to the HTK licence.
In fact I think www.speechmatics.com uses HVite in exactly this way to
do some final tidying up of the large vocabulary speech recognition output.
Tony
On 30/10/14 11:49, Georg Schlunz wrote:
> Good day
>
> Regarding the HTK license, as specified at http://htk.eng.cam.ac.uk/docs/licen
se.shtml , I would like to know whether the following scenario is permitted:
>
> The HTK software (including HVite) sits on a server in-house in our organisati
on, as per license sections 2.1 and 2.3.
> The HTK software (including HVite) is never distributed to a commercial (or no
n-commercial) party, as per license section 2.2.
>
> We have written our own server-client software, where:
> a) the client records speech and sends the audio file to the server, which pas
ses it on to HVite (the server software and HTK sit on the same in-house machine
)
> b) HVite decodes the audio into text
> c) the server replies to the client with the decoded text and the client proce
sses the text somehow
>
> Naturally, the client software contains no HTK code; it only processes data pr
oduced by HTK.
>
> Therefore, may this client software and decoding SERVICE be sold commercially
(as long as we agree to license sections 2.4 and 2.5)?
>
> Thank you
> Georg Schlunz
>
-- ** Cantab is hiring: www.cantabResearch.com/openings ** -Dr A J Robinson, Founder, Cantab Research Ltd
Phone direct: 01223 778240 office: 01223 794497
Company reg no GB 05697423, VAT reg no 925606030
51 Canterbury Street, Cambridge, CB4 3QG, UK
From tonyr at cantabResearch.com Tue Nov 4 20:04:46 2014
From: tonyr at cantabResearch.com (Tony Robinson)
Date: Sun Feb 22 04:24:56 2015
Subject: [HTK-Users] HTK license agreement
In-Reply-To: <545241EC02000049000E3077@pta-emo.csir.co.za>
References: <545241EC02000049000E3077@pta-emo.csir.co.za>
Message-ID: <5459315E.9030409@cantabResearch.com>
I just saw this post - I hope I haven't also missed any replies.
It's been a while since I read the HTK licence, but from memory and past
commercial practices I believe that what you are proposing is entirely

acceptable according to the HTK licence.


In fact I think www.speechmatics.com uses HVite in exactly this way to
do some final tidying up of the large vocabulary speech recognition output.
Tony
On 30/10/14 11:49, Georg Schlunz wrote:
> Good day
>
> Regarding the HTK license, as specified at http://htk.eng.cam.ac.uk/docs/licen
se.shtml , I would like to know whether the following scenario is permitted:
>
> The HTK software (including HVite) sits on a server in-house in our organisati
on, as per license sections 2.1 and 2.3.
> The HTK software (including HVite) is never distributed to a commercial (or no
n-commercial) party, as per license section 2.2.
>
> We have written our own server-client software, where:
> a) the client records speech and sends the audio file to the server, which pas
ses it on to HVite (the server software and HTK sit on the same in-house machine
)
> b) HVite decodes the audio into text
> c) the server replies to the client with the decoded text and the client proce
sses the text somehow
>
> Naturally, the client software contains no HTK code; it only processes data pr
oduced by HTK.
>
> Therefore, may this client software and decoding SERVICE be sold commercially
(as long as we agree to license sections 2.4 and 2.5)?
>
> Thank you
> Georg Schlunz
>
-- ** Cantab is hiring: www.cantabResearch.com/openings ** -Dr A J Robinson, Founder, Cantab Research Ltd
Phone direct: 01223 778240 office: 01223 794497
Company reg no GB 05697423, VAT reg no 925606030
51 Canterbury Street, Cambridge, CB4 3QG, UK
From tonyr at cantabResearch.com Tue Nov 4 20:04:46 2014
From: tonyr at cantabResearch.com (Tony Robinson)
Date: Mon Feb 23 04:57:28 2015
Subject: [HTK-Users] HTK license agreement
In-Reply-To: <545241EC02000049000E3077@pta-emo.csir.co.za>
References: <545241EC02000049000E3077@pta-emo.csir.co.za>
Message-ID: <5459315E.9030409@cantabResearch.com>
I just saw this post - I hope I haven't also missed any replies.
It's been a while since I read the HTK licence, but from memory and past
commercial practices I believe that what you are proposing is entirely
acceptable according to the HTK licence.
In fact I think www.speechmatics.com uses HVite in exactly this way to
do some final tidying up of the large vocabulary speech recognition output.

Tony
On 30/10/14 11:49, Georg Schlunz wrote:
> Good day
>
> Regarding the HTK license, as specified at http://htk.eng.cam.ac.uk/docs/licen
se.shtml , I would like to know whether the following scenario is permitted:
>
> The HTK software (including HVite) sits on a server in-house in our organisati
on, as per license sections 2.1 and 2.3.
> The HTK software (including HVite) is never distributed to a commercial (or no
n-commercial) party, as per license section 2.2.
>
> We have written our own server-client software, where:
> a) the client records speech and sends the audio file to the server, which pas
ses it on to HVite (the server software and HTK sit on the same in-house machine
)
> b) HVite decodes the audio into text
> c) the server replies to the client with the decoded text and the client proce
sses the text somehow
>
> Naturally, the client software contains no HTK code; it only processes data pr
oduced by HTK.
>
> Therefore, may this client software and decoding SERVICE be sold commercially
(as long as we agree to license sections 2.4 and 2.5)?
>
> Thank you
> Georg Schlunz
>
-- ** Cantab is hiring: www.cantabResearch.com/openings ** -Dr A J Robinson, Founder, Cantab Research Ltd
Phone direct: 01223 778240 office: 01223 794497
Company reg no GB 05697423, VAT reg no 925606030
51 Canterbury Street, Cambridge, CB4 3QG, UK
From tonyr at cantabResearch.com Tue Nov 4 20:04:46 2014
From: tonyr at cantabResearch.com (Tony Robinson)
Date: Tue Feb 24 04:37:39 2015
Subject: [HTK-Users] HTK license agreement
In-Reply-To: <545241EC02000049000E3077@pta-emo.csir.co.za>
References: <545241EC02000049000E3077@pta-emo.csir.co.za>
Message-ID: <5459315E.9030409@cantabResearch.com>
I just saw this post - I hope I haven't also missed any replies.
It's been a while since I read the HTK licence, but from memory and past
commercial practices I believe that what you are proposing is entirely
acceptable according to the HTK licence.
In fact I think www.speechmatics.com uses HVite in exactly this way to
do some final tidying up of the large vocabulary speech recognition output.
Tony
On 30/10/14 11:49, Georg Schlunz wrote:
> Good day

>
> Regarding the HTK license, as specified at http://htk.eng.cam.ac.uk/docs/licen
se.shtml , I would like to know whether the following scenario is permitted:
>
> The HTK software (including HVite) sits on a server in-house in our organisati
on, as per license sections 2.1 and 2.3.
> The HTK software (including HVite) is never distributed to a commercial (or no
n-commercial) party, as per license section 2.2.
>
> We have written our own server-client software, where:
> a) the client records speech and sends the audio file to the server, which pas
ses it on to HVite (the server software and HTK sit on the same in-house machine
)
> b) HVite decodes the audio into text
> c) the server replies to the client with the decoded text and the client proce
sses the text somehow
>
> Naturally, the client software contains no HTK code; it only processes data pr
oduced by HTK.
>
> Therefore, may this client software and decoding SERVICE be sold commercially
(as long as we agree to license sections 2.4 and 2.5)?
>
> Thank you
> Georg Schlunz
>
-- ** Cantab is hiring: www.cantabResearch.com/openings ** -Dr A J Robinson, Founder, Cantab Research Ltd
Phone direct: 01223 778240 office: 01223 794497
Company reg no GB 05697423, VAT reg no 925606030
51 Canterbury Street, Cambridge, CB4 3QG, UK
From tonyr at cantabResearch.com Tue Nov 4 20:04:46 2014
From: tonyr at cantabResearch.com (Tony Robinson)
Date: Wed Feb 25 06:04:20 2015
Subject: [HTK-Users] HTK license agreement
In-Reply-To: <545241EC02000049000E3077@pta-emo.csir.co.za>
References: <545241EC02000049000E3077@pta-emo.csir.co.za>
Message-ID: <5459315E.9030409@cantabResearch.com>
I just saw this post - I hope I haven't also missed any replies.
It's been a while since I read the HTK licence, but from memory and past
commercial practices I believe that what you are proposing is entirely
acceptable according to the HTK licence.
In fact I think www.speechmatics.com uses HVite in exactly this way to
do some final tidying up of the large vocabulary speech recognition output.
Tony
On 30/10/14 11:49, Georg Schlunz wrote:
> Good day
>
> Regarding the HTK license, as specified at http://htk.eng.cam.ac.uk/docs/licen
se.shtml , I would like to know whether the following scenario is permitted:
>
> The HTK software (including HVite) sits on a server in-house in our organisati

on, as per license sections 2.1 and 2.3.


> The HTK software (including HVite) is never distributed to a commercial (or no
n-commercial) party, as per license section 2.2.
>
> We have written our own server-client software, where:
> a) the client records speech and sends the audio file to the server, which pas
ses it on to HVite (the server software and HTK sit on the same in-house machine
)
> b) HVite decodes the audio into text
> c) the server replies to the client with the decoded text and the client proce
sses the text somehow
>
> Naturally, the client software contains no HTK code; it only processes data pr
oduced by HTK.
>
> Therefore, may this client software and decoding SERVICE be sold commercially
(as long as we agree to license sections 2.4 and 2.5)?
>
> Thank you
> Georg Schlunz
>
-- ** Cantab is hiring: www.cantabResearch.com/openings ** -Dr A J Robinson, Founder, Cantab Research Ltd
Phone direct: 01223 778240 office: 01223 794497
Company reg no GB 05697423, VAT reg no 925606030
51 Canterbury Street, Cambridge, CB4 3QG, UK
From tonyr at cantabResearch.com Tue Nov 4 20:04:46 2014
From: tonyr at cantabResearch.com (Tony Robinson)
Date: Thu Feb 26 04:49:09 2015
Subject: [HTK-Users] HTK license agreement
In-Reply-To: <545241EC02000049000E3077@pta-emo.csir.co.za>
References: <545241EC02000049000E3077@pta-emo.csir.co.za>
Message-ID: <5459315E.9030409@cantabResearch.com>
I just saw this post - I hope I haven't also missed any replies.
It's been a while since I read the HTK licence, but from memory and past
commercial practices I believe that what you are proposing is entirely
acceptable according to the HTK licence.
In fact I think www.speechmatics.com uses HVite in exactly this way to
do some final tidying up of the large vocabulary speech recognition output.
Tony
On 30/10/14 11:49, Georg Schlunz wrote:
> Good day
>
> Regarding the HTK license, as specified at http://htk.eng.cam.ac.uk/docs/licen
se.shtml , I would like to know whether the following scenario is permitted:
>
> The HTK software (including HVite) sits on a server in-house in our organisati
on, as per license sections 2.1 and 2.3.
> The HTK software (including HVite) is never distributed to a commercial (or no
n-commercial) party, as per license section 2.2.
>
> We have written our own server-client software, where:

> a) the client records speech and sends the audio file to the server, which pas
ses it on to HVite (the server software and HTK sit on the same in-house machine
)
> b) HVite decodes the audio into text
> c) the server replies to the client with the decoded text and the client proce
sses the text somehow
>
> Naturally, the client software contains no HTK code; it only processes data pr
oduced by HTK.
>
> Therefore, may this client software and decoding SERVICE be sold commercially
(as long as we agree to license sections 2.4 and 2.5)?
>
> Thank you
> Georg Schlunz
>
-- ** Cantab is hiring: www.cantabResearch.com/openings ** -Dr A J Robinson, Founder, Cantab Research Ltd
Phone direct: 01223 778240 office: 01223 794497
Company reg no GB 05697423, VAT reg no 925606030
51 Canterbury Street, Cambridge, CB4 3QG, UK
From tonyr at cantabResearch.com Tue Nov 4 20:04:46 2014
From: tonyr at cantabResearch.com (Tony Robinson)
Date: Fri Feb 27 05:03:56 2015
Subject: [HTK-Users] HTK license agreement
In-Reply-To: <545241EC02000049000E3077@pta-emo.csir.co.za>
References: <545241EC02000049000E3077@pta-emo.csir.co.za>
Message-ID: <5459315E.9030409@cantabResearch.com>
I just saw this post - I hope I haven't also missed any replies.
It's been a while since I read the HTK licence, but from memory and past
commercial practices I believe that what you are proposing is entirely
acceptable according to the HTK licence.
In fact I think www.speechmatics.com uses HVite in exactly this way to
do some final tidying up of the large vocabulary speech recognition output.
Tony
On 30/10/14 11:49, Georg Schlunz wrote:
> Good day
>
> Regarding the HTK license, as specified at http://htk.eng.cam.ac.uk/docs/licen
se.shtml , I would like to know whether the following scenario is permitted:
>
> The HTK software (including HVite) sits on a server in-house in our organisati
on, as per license sections 2.1 and 2.3.
> The HTK software (including HVite) is never distributed to a commercial (or no
n-commercial) party, as per license section 2.2.
>
> We have written our own server-client software, where:
> a) the client records speech and sends the audio file to the server, which pas
ses it on to HVite (the server software and HTK sit on the same in-house machine
)
> b) HVite decodes the audio into text
> c) the server replies to the client with the decoded text and the client proce

sses the text somehow


>
> Naturally, the client software contains no HTK code; it only processes data pr
oduced by HTK.
>
> Therefore, may this client software and decoding SERVICE be sold commercially
(as long as we agree to license sections 2.4 and 2.5)?
>
> Thank you
> Georg Schlunz
>
-- ** Cantab is hiring: www.cantabResearch.com/openings ** -Dr A J Robinson, Founder, Cantab Research Ltd
Phone direct: 01223 778240 office: 01223 794497
Company reg no GB 05697423, VAT reg no 925606030
51 Canterbury Street, Cambridge, CB4 3QG, UK
From tonyr at cantabResearch.com Tue Nov 4 20:04:46 2014
From: tonyr at cantabResearch.com (Tony Robinson)
Date: Sat Feb 28 04:43:35 2015
Subject: [HTK-Users] HTK license agreement
In-Reply-To: <545241EC02000049000E3077@pta-emo.csir.co.za>
References: <545241EC02000049000E3077@pta-emo.csir.co.za>
Message-ID: <5459315E.9030409@cantabResearch.com>
I just saw this post - I hope I haven't also missed any replies.
It's been a while since I read the HTK licence, but from memory and past
commercial practices I believe that what you are proposing is entirely
acceptable according to the HTK licence.
In fact I think www.speechmatics.com uses HVite in exactly this way to
do some final tidying up of the large vocabulary speech recognition output.
Tony
On 30/10/14 11:49, Georg Schlunz wrote:
> Good day
>
> Regarding the HTK license, as specified at http://htk.eng.cam.ac.uk/docs/licen
se.shtml , I would like to know whether the following scenario is permitted:
>
> The HTK software (including HVite) sits on a server in-house in our organisati
on, as per license sections 2.1 and 2.3.
> The HTK software (including HVite) is never distributed to a commercial (or no
n-commercial) party, as per license section 2.2.
>
> We have written our own server-client software, where:
> a) the client records speech and sends the audio file to the server, which pas
ses it on to HVite (the server software and HTK sit on the same in-house machine
)
> b) HVite decodes the audio into text
> c) the server replies to the client with the decoded text and the client proce
sses the text somehow
>
> Naturally, the client software contains no HTK code; it only processes data pr
oduced by HTK.
>

> Therefore, may this client software and decoding SERVICE be sold commercially
(as long as we agree to license sections 2.4 and 2.5)?
>
> Thank you
> Georg Schlunz
>
-- ** Cantab is hiring: www.cantabResearch.com/openings ** -Dr A J Robinson, Founder, Cantab Research Ltd
Phone direct: 01223 778240 office: 01223 794497
Company reg no GB 05697423, VAT reg no 925606030
51 Canterbury Street, Cambridge, CB4 3QG, UK
From tonyr at cantabResearch.com Tue Nov 4 20:04:46 2014
From: tonyr at cantabResearch.com (Tony Robinson)
Date: Sun Mar 1 04:50:11 2015
Subject: [HTK-Users] HTK license agreement
In-Reply-To: <545241EC02000049000E3077@pta-emo.csir.co.za>
References: <545241EC02000049000E3077@pta-emo.csir.co.za>
Message-ID: <5459315E.9030409@cantabResearch.com>
I just saw this post - I hope I haven't also missed any replies.
It's been a while since I read the HTK licence, but from memory and past
commercial practices I believe that what you are proposing is entirely
acceptable according to the HTK licence.
In fact I think www.speechmatics.com uses HVite in exactly this way to
do some final tidying up of the large vocabulary speech recognition output.
Tony
On 30/10/14 11:49, Georg Schlunz wrote:
> Good day
>
> Regarding the HTK license, as specified at http://htk.eng.cam.ac.uk/docs/licen
se.shtml , I would like to know whether the following scenario is permitted:
>
> The HTK software (including HVite) sits on a server in-house in our organisati
on, as per license sections 2.1 and 2.3.
> The HTK software (including HVite) is never distributed to a commercial (or no
n-commercial) party, as per license section 2.2.
>
> We have written our own server-client software, where:
> a) the client records speech and sends the audio file to the server, which pas
ses it on to HVite (the server software and HTK sit on the same in-house machine
)
> b) HVite decodes the audio into text
> c) the server replies to the client with the decoded text and the client proce
sses the text somehow
>
> Naturally, the client software contains no HTK code; it only processes data pr
oduced by HTK.
>
> Therefore, may this client software and decoding SERVICE be sold commercially
(as long as we agree to license sections 2.4 and 2.5)?
>
> Thank you
> Georg Schlunz

>
-- ** Cantab is hiring: www.cantabResearch.com/openings ** -Dr A J Robinson, Founder, Cantab Research Ltd
Phone direct: 01223 778240 office: 01223 794497
Company reg no GB 05697423, VAT reg no 925606030
51 Canterbury Street, Cambridge, CB4 3QG, UK
From tonyr at cantabResearch.com Tue Nov 4 20:04:46 2014
From: tonyr at cantabResearch.com (Tony Robinson)
Date: Mon Mar 2 04:29:15 2015
Subject: [HTK-Users] HTK license agreement
In-Reply-To: <545241EC02000049000E3077@pta-emo.csir.co.za>
References: <545241EC02000049000E3077@pta-emo.csir.co.za>
Message-ID: <5459315E.9030409@cantabResearch.com>
I just saw this post - I hope I haven't also missed any replies.
It's been a while since I read the HTK licence, but from memory and past
commercial practices I believe that what you are proposing is entirely
acceptable according to the HTK licence.
In fact I think www.speechmatics.com uses HVite in exactly this way to
do some final tidying up of the large vocabulary speech recognition output.
Tony
On 30/10/14 11:49, Georg Schlunz wrote:
> Good day
>
> Regarding the HTK license, as specified at http://htk.eng.cam.ac.uk/docs/licen
se.shtml , I would like to know whether the following scenario is permitted:
>
> The HTK software (including HVite) sits on a server in-house in our organisati
on, as per license sections 2.1 and 2.3.
> The HTK software (including HVite) is never distributed to a commercial (or no
n-commercial) party, as per license section 2.2.
>
> We have written our own server-client software, where:
> a) the client records speech and sends the audio file to the server, which pas
ses it on to HVite (the server software and HTK sit on the same in-house machine
)
> b) HVite decodes the audio into text
> c) the server replies to the client with the decoded text and the client proce
sses the text somehow
>
> Naturally, the client software contains no HTK code; it only processes data pr
oduced by HTK.
>
> Therefore, may this client software and decoding SERVICE be sold commercially
(as long as we agree to license sections 2.4 and 2.5)?
>
> Thank you
> Georg Schlunz
>
-- ** Cantab is hiring: www.cantabResearch.com/openings ** -Dr A J Robinson, Founder, Cantab Research Ltd
Phone direct: 01223 778240 office: 01223 794497

Company reg no GB 05697423, VAT reg no 925606030


51 Canterbury Street, Cambridge, CB4 3QG, UK
From tonyr at cantabResearch.com Tue Nov 4 20:04:46 2014
From: tonyr at cantabResearch.com (Tony Robinson)
Date: Tue Mar 3 04:50:57 2015
Subject: [HTK-Users] HTK license agreement
In-Reply-To: <545241EC02000049000E3077@pta-emo.csir.co.za>
References: <545241EC02000049000E3077@pta-emo.csir.co.za>
Message-ID: <5459315E.9030409@cantabResearch.com>
I just saw this post - I hope I haven't also missed any replies.
It's been a while since I read the HTK licence, but from memory and past
commercial practices I believe that what you are proposing is entirely
acceptable according to the HTK licence.
In fact I think www.speechmatics.com uses HVite in exactly this way to
do some final tidying up of the large vocabulary speech recognition output.
Tony
On 30/10/14 11:49, Georg Schlunz wrote:
> Good day
>
> Regarding the HTK license, as specified at http://htk.eng.cam.ac.uk/docs/licen
se.shtml , I would like to know whether the following scenario is permitted:
>
> The HTK software (including HVite) sits on a server in-house in our organisati
on, as per license sections 2.1 and 2.3.
> The HTK software (including HVite) is never distributed to a commercial (or no
n-commercial) party, as per license section 2.2.
>
> We have written our own server-client software, where:
> a) the client records speech and sends the audio file to the server, which pas
ses it on to HVite (the server software and HTK sit on the same in-house machine
)
> b) HVite decodes the audio into text
> c) the server replies to the client with the decoded text and the client proce
sses the text somehow
>
> Naturally, the client software contains no HTK code; it only processes data pr
oduced by HTK.
>
> Therefore, may this client software and decoding SERVICE be sold commercially
(as long as we agree to license sections 2.4 and 2.5)?
>
> Thank you
> Georg Schlunz
>
-- ** Cantab is hiring: www.cantabResearch.com/openings ** -Dr A J Robinson, Founder, Cantab Research Ltd
Phone direct: 01223 778240 office: 01223 794497
Company reg no GB 05697423, VAT reg no 925606030
51 Canterbury Street, Cambridge, CB4 3QG, UK
From tonyr at cantabResearch.com Tue Nov 4 20:04:46 2014
From: tonyr at cantabResearch.com (Tony Robinson)

Date: Wed Mar 4 04:32:12 2015


Subject: [HTK-Users] HTK license agreement
In-Reply-To: <545241EC02000049000E3077@pta-emo.csir.co.za>
References: <545241EC02000049000E3077@pta-emo.csir.co.za>
Message-ID: <5459315E.9030409@cantabResearch.com>
I just saw this post - I hope I haven't also missed any replies.
It's been a while since I read the HTK licence, but from memory and past
commercial practices I believe that what you are proposing is entirely
acceptable according to the HTK licence.
In fact I think www.speechmatics.com uses HVite in exactly this way to
do some final tidying up of the large vocabulary speech recognition output.
Tony
On 30/10/14 11:49, Georg Schlunz wrote:
> Good day
>
> Regarding the HTK license, as specified at http://htk.eng.cam.ac.uk/docs/licen
se.shtml , I would like to know whether the following scenario is permitted:
>
> The HTK software (including HVite) sits on a server in-house in our organisati
on, as per license sections 2.1 and 2.3.
> The HTK software (including HVite) is never distributed to a commercial (or no
n-commercial) party, as per license section 2.2.
>
> We have written our own server-client software, where:
> a) the client records speech and sends the audio file to the server, which pas
ses it on to HVite (the server software and HTK sit on the same in-house machine
)
> b) HVite decodes the audio into text
> c) the server replies to the client with the decoded text and the client proce
sses the text somehow
>
> Naturally, the client software contains no HTK code; it only processes data pr
oduced by HTK.
>
> Therefore, may this client software and decoding SERVICE be sold commercially
(as long as we agree to license sections 2.4 and 2.5)?
>
> Thank you
> Georg Schlunz
>
-- ** Cantab is hiring: www.cantabResearch.com/openings ** -Dr A J Robinson, Founder, Cantab Research Ltd
Phone direct: 01223 778240 office: 01223 794497
Company reg no GB 05697423, VAT reg no 925606030
51 Canterbury Street, Cambridge, CB4 3QG, UK
From tonyr at cantabResearch.com Tue Nov 4 20:04:46 2014
From: tonyr at cantabResearch.com (Tony Robinson)
Date: Thu Mar 5 05:37:54 2015
Subject: [HTK-Users] HTK license agreement
In-Reply-To: <545241EC02000049000E3077@pta-emo.csir.co.za>
References: <545241EC02000049000E3077@pta-emo.csir.co.za>
Message-ID: <5459315E.9030409@cantabResearch.com>

I just saw this post - I hope I haven't also missed any replies.
It's been a while since I read the HTK licence, but from memory and past
commercial practices I believe that what you are proposing is entirely
acceptable according to the HTK licence.
In fact I think www.speechmatics.com uses HVite in exactly this way to
do some final tidying up of the large vocabulary speech recognition output.
Tony
On 30/10/14 11:49, Georg Schlunz wrote:
> Good day
>
> Regarding the HTK license, as specified at http://htk.eng.cam.ac.uk/docs/licen
se.shtml , I would like to know whether the following scenario is permitted:
>
> The HTK software (including HVite) sits on a server in-house in our organisati
on, as per license sections 2.1 and 2.3.
> The HTK software (including HVite) is never distributed to a commercial (or no
n-commercial) party, as per license section 2.2.
>
> We have written our own server-client software, where:
> a) the client records speech and sends the audio file to the server, which pas
ses it on to HVite (the server software and HTK sit on the same in-house machine
)
> b) HVite decodes the audio into text
> c) the server replies to the client with the decoded text and the client proce
sses the text somehow
>
> Naturally, the client software contains no HTK code; it only processes data pr
oduced by HTK.
>
> Therefore, may this client software and decoding SERVICE be sold commercially
(as long as we agree to license sections 2.4 and 2.5)?
>
> Thank you
> Georg Schlunz
>
-- ** Cantab is hiring: www.cantabResearch.com/openings ** -Dr A J Robinson, Founder, Cantab Research Ltd
Phone direct: 01223 778240 office: 01223 794497
Company reg no GB 05697423, VAT reg no 925606030
51 Canterbury Street, Cambridge, CB4 3QG, UK
From tonyr at cantabResearch.com Tue Nov 4 20:04:46 2014
From: tonyr at cantabResearch.com (Tony Robinson)
Date: Fri Mar 6 05:27:18 2015
Subject: [HTK-Users] HTK license agreement
In-Reply-To: <545241EC02000049000E3077@pta-emo.csir.co.za>
References: <545241EC02000049000E3077@pta-emo.csir.co.za>
Message-ID: <5459315E.9030409@cantabResearch.com>
I just saw this post - I hope I haven't also missed any replies.
It's been a while since I read the HTK licence, but from memory and past
commercial practices I believe that what you are proposing is entirely

acceptable according to the HTK licence.


In fact I think www.speechmatics.com uses HVite in exactly this way to
do some final tidying up of the large vocabulary speech recognition output.
Tony
On 30/10/14 11:49, Georg Schlunz wrote:
> Good day
>
> Regarding the HTK license, as specified at http://htk.eng.cam.ac.uk/docs/licen
se.shtml , I would like to know whether the following scenario is permitted:
>
> The HTK software (including HVite) sits on a server in-house in our organisati
on, as per license sections 2.1 and 2.3.
> The HTK software (including HVite) is never distributed to a commercial (or no
n-commercial) party, as per license section 2.2.
>
> We have written our own server-client software, where:
> a) the client records speech and sends the audio file to the server, which pas
ses it on to HVite (the server software and HTK sit on the same in-house machine
)
> b) HVite decodes the audio into text
> c) the server replies to the client with the decoded text and the client proce
sses the text somehow
>
> Naturally, the client software contains no HTK code; it only processes data pr
oduced by HTK.
>
> Therefore, may this client software and decoding SERVICE be sold commercially
(as long as we agree to license sections 2.4 and 2.5)?
>
> Thank you
> Georg Schlunz
>
-- ** Cantab is hiring: www.cantabResearch.com/openings ** -Dr A J Robinson, Founder, Cantab Research Ltd
Phone direct: 01223 778240 office: 01223 794497
Company reg no GB 05697423, VAT reg no 925606030
51 Canterbury Street, Cambridge, CB4 3QG, UK
From tonyr at cantabResearch.com Tue Nov 4 20:04:46 2014
From: tonyr at cantabResearch.com (Tony Robinson)
Date: Sat Mar 7 04:55:42 2015
Subject: [HTK-Users] HTK license agreement
In-Reply-To: <545241EC02000049000E3077@pta-emo.csir.co.za>
References: <545241EC02000049000E3077@pta-emo.csir.co.za>
Message-ID: <5459315E.9030409@cantabResearch.com>
I just saw this post - I hope I haven't also missed any replies.
It's been a while since I read the HTK licence, but from memory and past
commercial practices I believe that what you are proposing is entirely
acceptable according to the HTK licence.
In fact I think www.speechmatics.com uses HVite in exactly this way to
do some final tidying up of the large vocabulary speech recognition output.

Tony
On 30/10/14 11:49, Georg Schlunz wrote:
> Good day
>
> Regarding the HTK license, as specified at http://htk.eng.cam.ac.uk/docs/licen
se.shtml , I would like to know whether the following scenario is permitted:
>
> The HTK software (including HVite) sits on a server in-house in our organisati
on, as per license sections 2.1 and 2.3.
> The HTK software (including HVite) is never distributed to a commercial (or no
n-commercial) party, as per license section 2.2.
>
> We have written our own server-client software, where:
> a) the client records speech and sends the audio file to the server, which pas
ses it on to HVite (the server software and HTK sit on the same in-house machine
)
> b) HVite decodes the audio into text
> c) the server replies to the client with the decoded text and the client proce
sses the text somehow
>
> Naturally, the client software contains no HTK code; it only processes data pr
oduced by HTK.
>
> Therefore, may this client software and decoding SERVICE be sold commercially
(as long as we agree to license sections 2.4 and 2.5)?
>
> Thank you
> Georg Schlunz
>
-- ** Cantab is hiring: www.cantabResearch.com/openings ** -Dr A J Robinson, Founder, Cantab Research Ltd
Phone direct: 01223 778240 office: 01223 794497
Company reg no GB 05697423, VAT reg no 925606030
51 Canterbury Street, Cambridge, CB4 3QG, UK
From tonyr at cantabResearch.com Tue Nov 4 20:04:46 2014
From: tonyr at cantabResearch.com (Tony Robinson)
Date: Sun Mar 8 04:40:52 2015
Subject: [HTK-Users] HTK license agreement
In-Reply-To: <545241EC02000049000E3077@pta-emo.csir.co.za>
References: <545241EC02000049000E3077@pta-emo.csir.co.za>
Message-ID: <5459315E.9030409@cantabResearch.com>
I just saw this post - I hope I haven't also missed any replies.
It's been a while since I read the HTK licence, but from memory and past
commercial practices I believe that what you are proposing is entirely
acceptable according to the HTK licence.
In fact I think www.speechmatics.com uses HVite in exactly this way to
do some final tidying up of the large vocabulary speech recognition output.
Tony
On 30/10/14 11:49, Georg Schlunz wrote:
> Good day

>
> Regarding the HTK license, as specified at http://htk.eng.cam.ac.uk/docs/licen
se.shtml , I would like to know whether the following scenario is permitted:
>
> The HTK software (including HVite) sits on a server in-house in our organisati
on, as per license sections 2.1 and 2.3.
> The HTK software (including HVite) is never distributed to a commercial (or no
n-commercial) party, as per license section 2.2.
>
> We have written our own server-client software, where:
> a) the client records speech and sends the audio file to the server, which pas
ses it on to HVite (the server software and HTK sit on the same in-house machine
)
> b) HVite decodes the audio into text
> c) the server replies to the client with the decoded text and the client proce
sses the text somehow
>
> Naturally, the client software contains no HTK code; it only processes data pr
oduced by HTK.
>
> Therefore, may this client software and decoding SERVICE be sold commercially
(as long as we agree to license sections 2.4 and 2.5)?
>
> Thank you
> Georg Schlunz
>
-- ** Cantab is hiring: www.cantabResearch.com/openings ** -Dr A J Robinson, Founder, Cantab Research Ltd
Phone direct: 01223 778240 office: 01223 794497
Company reg no GB 05697423, VAT reg no 925606030
51 Canterbury Street, Cambridge, CB4 3QG, UK
From tonyr at cantabResearch.com Tue Nov 4 20:04:46 2014
From: tonyr at cantabResearch.com (Tony Robinson)
Date: Mon Mar 9 05:14:30 2015
Subject: [HTK-Users] HTK license agreement
In-Reply-To: <545241EC02000049000E3077@pta-emo.csir.co.za>
References: <545241EC02000049000E3077@pta-emo.csir.co.za>
Message-ID: <5459315E.9030409@cantabResearch.com>
I just saw this post - I hope I haven't also missed any replies.
It's been a while since I read the HTK licence, but from memory and past
commercial practices I believe that what you are proposing is entirely
acceptable according to the HTK licence.
In fact I think www.speechmatics.com uses HVite in exactly this way to
do some final tidying up of the large vocabulary speech recognition output.
Tony
On 30/10/14 11:49, Georg Schlunz wrote:
> Good day
>
> Regarding the HTK license, as specified at http://htk.eng.cam.ac.uk/docs/licen
se.shtml , I would like to know whether the following scenario is permitted:
>
> The HTK software (including HVite) sits on a server in-house in our organisati

on, as per license sections 2.1 and 2.3.


> The HTK software (including HVite) is never distributed to a commercial (or no
n-commercial) party, as per license section 2.2.
>
> We have written our own server-client software, where:
> a) the client records speech and sends the audio file to the server, which pas
ses it on to HVite (the server software and HTK sit on the same in-house machine
)
> b) HVite decodes the audio into text
> c) the server replies to the client with the decoded text and the client proce
sses the text somehow
>
> Naturally, the client software contains no HTK code; it only processes data pr
oduced by HTK.
>
> Therefore, may this client software and decoding SERVICE be sold commercially
(as long as we agree to license sections 2.4 and 2.5)?
>
> Thank you
> Georg Schlunz
>
-- ** Cantab is hiring: www.cantabResearch.com/openings ** -Dr A J Robinson, Founder, Cantab Research Ltd
Phone direct: 01223 778240 office: 01223 794497
Company reg no GB 05697423, VAT reg no 925606030
51 Canterbury Street, Cambridge, CB4 3QG, UK
From tonyr at cantabResearch.com Tue Nov 4 20:04:46 2014
From: tonyr at cantabResearch.com (Tony Robinson)
Date: Tue Mar 10 04:52:02 2015
Subject: [HTK-Users] HTK license agreement
In-Reply-To: <545241EC02000049000E3077@pta-emo.csir.co.za>
References: <545241EC02000049000E3077@pta-emo.csir.co.za>
Message-ID: <5459315E.9030409@cantabResearch.com>
I just saw this post - I hope I haven't also missed any replies.
It's been a while since I read the HTK licence, but from memory and past
commercial practices I believe that what you are proposing is entirely
acceptable according to the HTK licence.
In fact I think www.speechmatics.com uses HVite in exactly this way to
do some final tidying up of the large vocabulary speech recognition output.
Tony
On 30/10/14 11:49, Georg Schlunz wrote:
> Good day
>
> Regarding the HTK license, as specified at http://htk.eng.cam.ac.uk/docs/licen
se.shtml , I would like to know whether the following scenario is permitted:
>
> The HTK software (including HVite) sits on a server in-house in our organisati
on, as per license sections 2.1 and 2.3.
> The HTK software (including HVite) is never distributed to a commercial (or no
n-commercial) party, as per license section 2.2.
>
> We have written our own server-client software, where:

> a) the client records speech and sends the audio file to the server, which pas
ses it on to HVite (the server software and HTK sit on the same in-house machine
)
> b) HVite decodes the audio into text
> c) the server replies to the client with the decoded text and the client proce
sses the text somehow
>
> Naturally, the client software contains no HTK code; it only processes data pr
oduced by HTK.
>
> Therefore, may this client software and decoding SERVICE be sold commercially
(as long as we agree to license sections 2.4 and 2.5)?
>
> Thank you
> Georg Schlunz
>
-- ** Cantab is hiring: www.cantabResearch.com/openings ** -Dr A J Robinson, Founder, Cantab Research Ltd
Phone direct: 01223 778240 office: 01223 794497
Company reg no GB 05697423, VAT reg no 925606030
51 Canterbury Street, Cambridge, CB4 3QG, UK
From tonyr at cantabResearch.com Tue Nov 4 20:04:46 2014
From: tonyr at cantabResearch.com (Tony Robinson)
Date: Wed Mar 11 05:05:21 2015
Subject: [HTK-Users] HTK license agreement
In-Reply-To: <545241EC02000049000E3077@pta-emo.csir.co.za>
References: <545241EC02000049000E3077@pta-emo.csir.co.za>
Message-ID: <5459315E.9030409@cantabResearch.com>
I just saw this post - I hope I haven't also missed any replies.
It's been a while since I read the HTK licence, but from memory and past
commercial practices I believe that what you are proposing is entirely
acceptable according to the HTK licence.
In fact I think www.speechmatics.com uses HVite in exactly this way to
do some final tidying up of the large vocabulary speech recognition output.
Tony
On 30/10/14 11:49, Georg Schlunz wrote:
> Good day
>
> Regarding the HTK license, as specified at http://htk.eng.cam.ac.uk/docs/licen
se.shtml , I would like to know whether the following scenario is permitted:
>
> The HTK software (including HVite) sits on a server in-house in our organisati
on, as per license sections 2.1 and 2.3.
> The HTK software (including HVite) is never distributed to a commercial (or no
n-commercial) party, as per license section 2.2.
>
> We have written our own server-client software, where:
> a) the client records speech and sends the audio file to the server, which pas
ses it on to HVite (the server software and HTK sit on the same in-house machine
)
> b) HVite decodes the audio into text
> c) the server replies to the client with the decoded text and the client proce

sses the text somehow


>
> Naturally, the client software contains no HTK code; it only processes data pr
oduced by HTK.
>
> Therefore, may this client software and decoding SERVICE be sold commercially
(as long as we agree to license sections 2.4 and 2.5)?
>
> Thank you
> Georg Schlunz
>
-- ** Cantab is hiring: www.cantabResearch.com/openings ** -Dr A J Robinson, Founder, Cantab Research Ltd
Phone direct: 01223 778240 office: 01223 794497
Company reg no GB 05697423, VAT reg no 925606030
51 Canterbury Street, Cambridge, CB4 3QG, UK
From tonyr at cantabResearch.com Tue Nov 4 20:04:46 2014
From: tonyr at cantabResearch.com (Tony Robinson)
Date: Thu Mar 12 05:24:33 2015
Subject: [HTK-Users] HTK license agreement
In-Reply-To: <545241EC02000049000E3077@pta-emo.csir.co.za>
References: <545241EC02000049000E3077@pta-emo.csir.co.za>
Message-ID: <5459315E.9030409@cantabResearch.com>
I just saw this post - I hope I haven't also missed any replies.
It's been a while since I read the HTK licence, but from memory and past
commercial practices I believe that what you are proposing is entirely
acceptable according to the HTK licence.
In fact I think www.speechmatics.com uses HVite in exactly this way to
do some final tidying up of the large vocabulary speech recognition output.
Tony
On 30/10/14 11:49, Georg Schlunz wrote:
> Good day
>
> Regarding the HTK license, as specified at http://htk.eng.cam.ac.uk/docs/licen
se.shtml , I would like to know whether the following scenario is permitted:
>
> The HTK software (including HVite) sits on a server in-house in our organisati
on, as per license sections 2.1 and 2.3.
> The HTK software (including HVite) is never distributed to a commercial (or no
n-commercial) party, as per license section 2.2.
>
> We have written our own server-client software, where:
> a) the client records speech and sends the audio file to the server, which pas
ses it on to HVite (the server software and HTK sit on the same in-house machine
)
> b) HVite decodes the audio into text
> c) the server replies to the client with the decoded text and the client proce
sses the text somehow
>
> Naturally, the client software contains no HTK code; it only processes data pr
oduced by HTK.
>

> Therefore, may this client software and decoding SERVICE be sold commercially
(as long as we agree to license sections 2.4 and 2.5)?
>
> Thank you
> Georg Schlunz
>
-- ** Cantab is hiring: www.cantabResearch.com/openings ** -Dr A J Robinson, Founder, Cantab Research Ltd
Phone direct: 01223 778240 office: 01223 794497
Company reg no GB 05697423, VAT reg no 925606030
51 Canterbury Street, Cambridge, CB4 3QG, UK
From tonyr at cantabResearch.com Tue Nov 4 20:04:46 2014
From: tonyr at cantabResearch.com (Tony Robinson)
Date: Fri Mar 13 05:16:21 2015
Subject: [HTK-Users] HTK license agreement
In-Reply-To: <545241EC02000049000E3077@pta-emo.csir.co.za>
References: <545241EC02000049000E3077@pta-emo.csir.co.za>
Message-ID: <5459315E.9030409@cantabResearch.com>
I just saw this post - I hope I haven't also missed any replies.
It's been a while since I read the HTK licence, but from memory and past
commercial practices I believe that what you are proposing is entirely
acceptable according to the HTK licence.
In fact I think www.speechmatics.com uses HVite in exactly this way to
do some final tidying up of the large vocabulary speech recognition output.
Tony
On 30/10/14 11:49, Georg Schlunz wrote:
> Good day
>
> Regarding the HTK license, as specified at http://htk.eng.cam.ac.uk/docs/licen
se.shtml , I would like to know whether the following scenario is permitted:
>
> The HTK software (including HVite) sits on a server in-house in our organisati
on, as per license sections 2.1 and 2.3.
> The HTK software (including HVite) is never distributed to a commercial (or no
n-commercial) party, as per license section 2.2.
>
> We have written our own server-client software, where:
> a) the client records speech and sends the audio file to the server, which pas
ses it on to HVite (the server software and HTK sit on the same in-house machine
)
> b) HVite decodes the audio into text
> c) the server replies to the client with the decoded text and the client proce
sses the text somehow
>
> Naturally, the client software contains no HTK code; it only processes data pr
oduced by HTK.
>
> Therefore, may this client software and decoding SERVICE be sold commercially
(as long as we agree to license sections 2.4 and 2.5)?
>
> Thank you
> Georg Schlunz

>
-- ** Cantab is hiring: www.cantabResearch.com/openings ** -Dr A J Robinson, Founder, Cantab Research Ltd
Phone direct: 01223 778240 office: 01223 794497
Company reg no GB 05697423, VAT reg no 925606030
51 Canterbury Street, Cambridge, CB4 3QG, UK
From tonyr at cantabResearch.com Tue Nov 4 20:04:46 2014
From: tonyr at cantabResearch.com (Tony Robinson)
Date: Sat Mar 14 05:22:44 2015
Subject: [HTK-Users] HTK license agreement
In-Reply-To: <545241EC02000049000E3077@pta-emo.csir.co.za>
References: <545241EC02000049000E3077@pta-emo.csir.co.za>
Message-ID: <5459315E.9030409@cantabResearch.com>
I just saw this post - I hope I haven't also missed any replies.
It's been a while since I read the HTK licence, but from memory and past
commercial practices I believe that what you are proposing is entirely
acceptable according to the HTK licence.
In fact I think www.speechmatics.com uses HVite in exactly this way to
do some final tidying up of the large vocabulary speech recognition output.
Tony
On 30/10/14 11:49, Georg Schlunz wrote:
> Good day
>
> Regarding the HTK license, as specified at http://htk.eng.cam.ac.uk/docs/licen
se.shtml , I would like to know whether the following scenario is permitted:
>
> The HTK software (including HVite) sits on a server in-house in our organisati
on, as per license sections 2.1 and 2.3.
> The HTK software (including HVite) is never distributed to a commercial (or no
n-commercial) party, as per license section 2.2.
>
> We have written our own server-client software, where:
> a) the client records speech and sends the audio file to the server, which pas
ses it on to HVite (the server software and HTK sit on the same in-house machine
)
> b) HVite decodes the audio into text
> c) the server replies to the client with the decoded text and the client proce
sses the text somehow
>
> Naturally, the client software contains no HTK code; it only processes data pr
oduced by HTK.
>
> Therefore, may this client software and decoding SERVICE be sold commercially
(as long as we agree to license sections 2.4 and 2.5)?
>
> Thank you
> Georg Schlunz
>
-- ** Cantab is hiring: www.cantabResearch.com/openings ** -Dr A J Robinson, Founder, Cantab Research Ltd
Phone direct: 01223 778240 office: 01223 794497

Company reg no GB 05697423, VAT reg no 925606030


51 Canterbury Street, Cambridge, CB4 3QG, UK
From tonyr at cantabResearch.com Tue Nov 4 20:04:46 2014
From: tonyr at cantabResearch.com (Tony Robinson)
Date: Sun Mar 15 05:14:12 2015
Subject: [HTK-Users] HTK license agreement
In-Reply-To: <545241EC02000049000E3077@pta-emo.csir.co.za>
References: <545241EC02000049000E3077@pta-emo.csir.co.za>
Message-ID: <5459315E.9030409@cantabResearch.com>
I just saw this post - I hope I haven't also missed any replies.
It's been a while since I read the HTK licence, but from memory and past
commercial practices I believe that what you are proposing is entirely
acceptable according to the HTK licence.
In fact I think www.speechmatics.com uses HVite in exactly this way to
do some final tidying up of the large vocabulary speech recognition output.
Tony
On 30/10/14 11:49, Georg Schlunz wrote:
> Good day
>
> Regarding the HTK license, as specified at http://htk.eng.cam.ac.uk/docs/licen
se.shtml , I would like to know whether the following scenario is permitted:
>
> The HTK software (including HVite) sits on a server in-house in our organisati
on, as per license sections 2.1 and 2.3.
> The HTK software (including HVite) is never distributed to a commercial (or no
n-commercial) party, as per license section 2.2.
>
> We have written our own server-client software, where:
> a) the client records speech and sends the audio file to the server, which pas
ses it on to HVite (the server software and HTK sit on the same in-house machine
)
> b) HVite decodes the audio into text
> c) the server replies to the client with the decoded text and the client proce
sses the text somehow
>
> Naturally, the client software contains no HTK code; it only processes data pr
oduced by HTK.
>
> Therefore, may this client software and decoding SERVICE be sold commercially
(as long as we agree to license sections 2.4 and 2.5)?
>
> Thank you
> Georg Schlunz
>
-- ** Cantab is hiring: www.cantabResearch.com/openings ** -Dr A J Robinson, Founder, Cantab Research Ltd
Phone direct: 01223 778240 office: 01223 794497
Company reg no GB 05697423, VAT reg no 925606030
51 Canterbury Street, Cambridge, CB4 3QG, UK
From tonyr at cantabResearch.com Tue Nov 4 20:04:46 2014
From: tonyr at cantabResearch.com (Tony Robinson)

Date: Mon Mar 16 04:58:07 2015


Subject: [HTK-Users] HTK license agreement
In-Reply-To: <545241EC02000049000E3077@pta-emo.csir.co.za>
References: <545241EC02000049000E3077@pta-emo.csir.co.za>
Message-ID: <5459315E.9030409@cantabResearch.com>
I just saw this post - I hope I haven't also missed any replies.
It's been a while since I read the HTK licence, but from memory and past
commercial practices I believe that what you are proposing is entirely
acceptable according to the HTK licence.
In fact I think www.speechmatics.com uses HVite in exactly this way to
do some final tidying up of the large vocabulary speech recognition output.
Tony
On 30/10/14 11:49, Georg Schlunz wrote:
> Good day
>
> Regarding the HTK license, as specified at http://htk.eng.cam.ac.uk/docs/licen
se.shtml , I would like to know whether the following scenario is permitted:
>
> The HTK software (including HVite) sits on a server in-house in our organisati
on, as per license sections 2.1 and 2.3.
> The HTK software (including HVite) is never distributed to a commercial (or no
n-commercial) party, as per license section 2.2.
>
> We have written our own server-client software, where:
> a) the client records speech and sends the audio file to the server, which pas
ses it on to HVite (the server software and HTK sit on the same in-house machine
)
> b) HVite decodes the audio into text
> c) the server replies to the client with the decoded text and the client proce
sses the text somehow
>
> Naturally, the client software contains no HTK code; it only processes data pr
oduced by HTK.
>
> Therefore, may this client software and decoding SERVICE be sold commercially
(as long as we agree to license sections 2.4 and 2.5)?
>
> Thank you
> Georg Schlunz
>
-- ** Cantab is hiring: www.cantabResearch.com/openings ** -Dr A J Robinson, Founder, Cantab Research Ltd
Phone direct: 01223 778240 office: 01223 794497
Company reg no GB 05697423, VAT reg no 925606030
51 Canterbury Street, Cambridge, CB4 3QG, UK
From tonyr at cantabResearch.com Tue Nov 4 20:04:46 2014
From: tonyr at cantabResearch.com (Tony Robinson)
Date: Tue Mar 17 05:17:55 2015
Subject: [HTK-Users] HTK license agreement
In-Reply-To: <545241EC02000049000E3077@pta-emo.csir.co.za>
References: <545241EC02000049000E3077@pta-emo.csir.co.za>
Message-ID: <5459315E.9030409@cantabResearch.com>

I just saw this post - I hope I haven't also missed any replies.
It's been a while since I read the HTK licence, but from memory and past
commercial practices I believe that what you are proposing is entirely
acceptable according to the HTK licence.
In fact I think www.speechmatics.com uses HVite in exactly this way to
do some final tidying up of the large vocabulary speech recognition output.
Tony
On 30/10/14 11:49, Georg Schlunz wrote:
> Good day
>
> Regarding the HTK license, as specified at http://htk.eng.cam.ac.uk/docs/licen
se.shtml , I would like to know whether the following scenario is permitted:
>
> The HTK software (including HVite) sits on a server in-house in our organisati
on, as per license sections 2.1 and 2.3.
> The HTK software (including HVite) is never distributed to a commercial (or no
n-commercial) party, as per license section 2.2.
>
> We have written our own server-client software, where:
> a) the client records speech and sends the audio file to the server, which pas
ses it on to HVite (the server software and HTK sit on the same in-house machine
)
> b) HVite decodes the audio into text
> c) the server replies to the client with the decoded text and the client proce
sses the text somehow
>
> Naturally, the client software contains no HTK code; it only processes data pr
oduced by HTK.
>
> Therefore, may this client software and decoding SERVICE be sold commercially
(as long as we agree to license sections 2.4 and 2.5)?
>
> Thank you
> Georg Schlunz
>
-- ** Cantab is hiring: www.cantabResearch.com/openings ** -Dr A J Robinson, Founder, Cantab Research Ltd
Phone direct: 01223 778240 office: 01223 794497
Company reg no GB 05697423, VAT reg no 925606030
51 Canterbury Street, Cambridge, CB4 3QG, UK
From tonyr at cantabResearch.com Tue Nov 4 20:04:46 2014
From: tonyr at cantabResearch.com (Tony Robinson)
Date: Wed Mar 18 05:20:47 2015
Subject: [HTK-Users] HTK license agreement
In-Reply-To: <545241EC02000049000E3077@pta-emo.csir.co.za>
References: <545241EC02000049000E3077@pta-emo.csir.co.za>
Message-ID: <5459315E.9030409@cantabResearch.com>
I just saw this post - I hope I haven't also missed any replies.
It's been a while since I read the HTK licence, but from memory and past
commercial practices I believe that what you are proposing is entirely

acceptable according to the HTK licence.


In fact I think www.speechmatics.com uses HVite in exactly this way to
do some final tidying up of the large vocabulary speech recognition output.
Tony
On 30/10/14 11:49, Georg Schlunz wrote:
> Good day
>
> Regarding the HTK license, as specified at http://htk.eng.cam.ac.uk/docs/licen
se.shtml , I would like to know whether the following scenario is permitted:
>
> The HTK software (including HVite) sits on a server in-house in our organisati
on, as per license sections 2.1 and 2.3.
> The HTK software (including HVite) is never distributed to a commercial (or no
n-commercial) party, as per license section 2.2.
>
> We have written our own server-client software, where:
> a) the client records speech and sends the audio file to the server, which pas
ses it on to HVite (the server software and HTK sit on the same in-house machine
)
> b) HVite decodes the audio into text
> c) the server replies to the client with the decoded text and the client proce
sses the text somehow
>
> Naturally, the client software contains no HTK code; it only processes data pr
oduced by HTK.
>
> Therefore, may this client software and decoding SERVICE be sold commercially
(as long as we agree to license sections 2.4 and 2.5)?
>
> Thank you
> Georg Schlunz
>
-- ** Cantab is hiring: www.cantabResearch.com/openings ** -Dr A J Robinson, Founder, Cantab Research Ltd
Phone direct: 01223 778240 office: 01223 794497
Company reg no GB 05697423, VAT reg no 925606030
51 Canterbury Street, Cambridge, CB4 3QG, UK
From tonyr at cantabResearch.com Tue Nov 4 20:04:46 2014
From: tonyr at cantabResearch.com (Tony Robinson)
Date: Thu Mar 19 04:39:39 2015
Subject: [HTK-Users] HTK license agreement
In-Reply-To: <545241EC02000049000E3077@pta-emo.csir.co.za>
References: <545241EC02000049000E3077@pta-emo.csir.co.za>
Message-ID: <5459315E.9030409@cantabResearch.com>
I just saw this post - I hope I haven't also missed any replies.
It's been a while since I read the HTK licence, but from memory and past
commercial practices I believe that what you are proposing is entirely
acceptable according to the HTK licence.
In fact I think www.speechmatics.com uses HVite in exactly this way to
do some final tidying up of the large vocabulary speech recognition output.

Tony
On 30/10/14 11:49, Georg Schlunz wrote:
> Good day
>
> Regarding the HTK license, as specified at http://htk.eng.cam.ac.uk/docs/licen
se.shtml , I would like to know whether the following scenario is permitted:
>
> The HTK software (including HVite) sits on a server in-house in our organisati
on, as per license sections 2.1 and 2.3.
> The HTK software (including HVite) is never distributed to a commercial (or no
n-commercial) party, as per license section 2.2.
>
> We have written our own server-client software, where:
> a) the client records speech and sends the audio file to the server, which pas
ses it on to HVite (the server software and HTK sit on the same in-house machine
)
> b) HVite decodes the audio into text
> c) the server replies to the client with the decoded text and the client proce
sses the text somehow
>
> Naturally, the client software contains no HTK code; it only processes data pr
oduced by HTK.
>
> Therefore, may this client software and decoding SERVICE be sold commercially
(as long as we agree to license sections 2.4 and 2.5)?
>
> Thank you
> Georg Schlunz
>
-- ** Cantab is hiring: www.cantabResearch.com/openings ** -Dr A J Robinson, Founder, Cantab Research Ltd
Phone direct: 01223 778240 office: 01223 794497
Company reg no GB 05697423, VAT reg no 925606030
51 Canterbury Street, Cambridge, CB4 3QG, UK
From tonyr at cantabResearch.com Tue Nov 4 20:04:46 2014
From: tonyr at cantabResearch.com (Tony Robinson)
Date: Fri Mar 20 04:22:51 2015
Subject: [HTK-Users] HTK license agreement
In-Reply-To: <545241EC02000049000E3077@pta-emo.csir.co.za>
References: <545241EC02000049000E3077@pta-emo.csir.co.za>
Message-ID: <5459315E.9030409@cantabResearch.com>
I just saw this post - I hope I haven't also missed any replies.
It's been a while since I read the HTK licence, but from memory and past
commercial practices I believe that what you are proposing is entirely
acceptable according to the HTK licence.
In fact I think www.speechmatics.com uses HVite in exactly this way to
do some final tidying up of the large vocabulary speech recognition output.
Tony
On 30/10/14 11:49, Georg Schlunz wrote:
> Good day

>
> Regarding the HTK license, as specified at http://htk.eng.cam.ac.uk/docs/licen
se.shtml , I would like to know whether the following scenario is permitted:
>
> The HTK software (including HVite) sits on a server in-house in our organisati
on, as per license sections 2.1 and 2.3.
> The HTK software (including HVite) is never distributed to a commercial (or no
n-commercial) party, as per license section 2.2.
>
> We have written our own server-client software, where:
> a) the client records speech and sends the audio file to the server, which pas
ses it on to HVite (the server software and HTK sit on the same in-house machine
)
> b) HVite decodes the audio into text
> c) the server replies to the client with the decoded text and the client proce
sses the text somehow
>
> Naturally, the client software contains no HTK code; it only processes data pr
oduced by HTK.
>
> Therefore, may this client software and decoding SERVICE be sold commercially
(as long as we agree to license sections 2.4 and 2.5)?
>
> Thank you
> Georg Schlunz
>
-- ** Cantab is hiring: www.cantabResearch.com/openings ** -Dr A J Robinson, Founder, Cantab Research Ltd
Phone direct: 01223 778240 office: 01223 794497
Company reg no GB 05697423, VAT reg no 925606030
51 Canterbury Street, Cambridge, CB4 3QG, UK
From tonyr at cantabResearch.com Tue Nov 4 20:04:46 2014
From: tonyr at cantabResearch.com (Tony Robinson)
Date: Sat Mar 21 05:29:08 2015
Subject: [HTK-Users] HTK license agreement
In-Reply-To: <545241EC02000049000E3077@pta-emo.csir.co.za>
References: <545241EC02000049000E3077@pta-emo.csir.co.za>
Message-ID: <5459315E.9030409@cantabResearch.com>
I just saw this post - I hope I haven't also missed any replies.
It's been a while since I read the HTK licence, but from memory and past
commercial practices I believe that what you are proposing is entirely
acceptable according to the HTK licence.
In fact I think www.speechmatics.com uses HVite in exactly this way to
do some final tidying up of the large vocabulary speech recognition output.
Tony
On 30/10/14 11:49, Georg Schlunz wrote:
> Good day
>
> Regarding the HTK license, as specified at http://htk.eng.cam.ac.uk/docs/licen
se.shtml , I would like to know whether the following scenario is permitted:
>
> The HTK software (including HVite) sits on a server in-house in our organisati

on, as per license sections 2.1 and 2.3.


> The HTK software (including HVite) is never distributed to a commercial (or no
n-commercial) party, as per license section 2.2.
>
> We have written our own server-client software, where:
> a) the client records speech and sends the audio file to the server, which pas
ses it on to HVite (the server software and HTK sit on the same in-house machine
)
> b) HVite decodes the audio into text
> c) the server replies to the client with the decoded text and the client proce
sses the text somehow
>
> Naturally, the client software contains no HTK code; it only processes data pr
oduced by HTK.
>
> Therefore, may this client software and decoding SERVICE be sold commercially
(as long as we agree to license sections 2.4 and 2.5)?
>
> Thank you
> Georg Schlunz
>
-- ** Cantab is hiring: www.cantabResearch.com/openings ** -Dr A J Robinson, Founder, Cantab Research Ltd
Phone direct: 01223 778240 office: 01223 794497
Company reg no GB 05697423, VAT reg no 925606030
51 Canterbury Street, Cambridge, CB4 3QG, UK
From tonyr at cantabResearch.com Tue Nov 4 20:04:46 2014
From: tonyr at cantabResearch.com (Tony Robinson)
Date: Sun Mar 22 04:19:28 2015
Subject: [HTK-Users] HTK license agreement
In-Reply-To: <545241EC02000049000E3077@pta-emo.csir.co.za>
References: <545241EC02000049000E3077@pta-emo.csir.co.za>
Message-ID: <5459315E.9030409@cantabResearch.com>
I just saw this post - I hope I haven't also missed any replies.
It's been a while since I read the HTK licence, but from memory and past
commercial practices I believe that what you are proposing is entirely
acceptable according to the HTK licence.
In fact I think www.speechmatics.com uses HVite in exactly this way to
do some final tidying up of the large vocabulary speech recognition output.
Tony
On 30/10/14 11:49, Georg Schlunz wrote:
> Good day
>
> Regarding the HTK license, as specified at http://htk.eng.cam.ac.uk/docs/licen
se.shtml , I would like to know whether the following scenario is permitted:
>
> The HTK software (including HVite) sits on a server in-house in our organisati
on, as per license sections 2.1 and 2.3.
> The HTK software (including HVite) is never distributed to a commercial (or no
n-commercial) party, as per license section 2.2.
>
> We have written our own server-client software, where:

> a) the client records speech and sends the audio file to the server, which pas
ses it on to HVite (the server software and HTK sit on the same in-house machine
)
> b) HVite decodes the audio into text
> c) the server replies to the client with the decoded text and the client proce
sses the text somehow
>
> Naturally, the client software contains no HTK code; it only processes data pr
oduced by HTK.
>
> Therefore, may this client software and decoding SERVICE be sold commercially
(as long as we agree to license sections 2.4 and 2.5)?
>
> Thank you
> Georg Schlunz
>
-- ** Cantab is hiring: www.cantabResearch.com/openings ** -Dr A J Robinson, Founder, Cantab Research Ltd
Phone direct: 01223 778240 office: 01223 794497
Company reg no GB 05697423, VAT reg no 925606030
51 Canterbury Street, Cambridge, CB4 3QG, UK
From tonyr at cantabResearch.com Tue Nov 4 20:04:46 2014
From: tonyr at cantabResearch.com (Tony Robinson)
Date: Mon Mar 23 04:51:39 2015
Subject: [HTK-Users] HTK license agreement
In-Reply-To: <545241EC02000049000E3077@pta-emo.csir.co.za>
References: <545241EC02000049000E3077@pta-emo.csir.co.za>
Message-ID: <5459315E.9030409@cantabResearch.com>
I just saw this post - I hope I haven't also missed any replies.
It's been a while since I read the HTK licence, but from memory and past
commercial practices I believe that what you are proposing is entirely
acceptable according to the HTK licence.
In fact I think www.speechmatics.com uses HVite in exactly this way to
do some final tidying up of the large vocabulary speech recognition output.
Tony
On 30/10/14 11:49, Georg Schlunz wrote:
> Good day
>
> Regarding the HTK license, as specified at http://htk.eng.cam.ac.uk/docs/licen
se.shtml , I would like to know whether the following scenario is permitted:
>
> The HTK software (including HVite) sits on a server in-house in our organisati
on, as per license sections 2.1 and 2.3.
> The HTK software (including HVite) is never distributed to a commercial (or no
n-commercial) party, as per license section 2.2.
>
> We have written our own server-client software, where:
> a) the client records speech and sends the audio file to the server, which pas
ses it on to HVite (the server software and HTK sit on the same in-house machine
)
> b) HVite decodes the audio into text
> c) the server replies to the client with the decoded text and the client proce

sses the text somehow


>
> Naturally, the client software contains no HTK code; it only processes data pr
oduced by HTK.
>
> Therefore, may this client software and decoding SERVICE be sold commercially
(as long as we agree to license sections 2.4 and 2.5)?
>
> Thank you
> Georg Schlunz
>
-- ** Cantab is hiring: www.cantabResearch.com/openings ** -Dr A J Robinson, Founder, Cantab Research Ltd
Phone direct: 01223 778240 office: 01223 794497
Company reg no GB 05697423, VAT reg no 925606030
51 Canterbury Street, Cambridge, CB4 3QG, UK
From tonyr at cantabResearch.com Tue Nov 4 20:04:46 2014
From: tonyr at cantabResearch.com (Tony Robinson)
Date: Tue Mar 24 05:43:48 2015
Subject: [HTK-Users] HTK license agreement
In-Reply-To: <545241EC02000049000E3077@pta-emo.csir.co.za>
References: <545241EC02000049000E3077@pta-emo.csir.co.za>
Message-ID: <5459315E.9030409@cantabResearch.com>
I just saw this post - I hope I haven't also missed any replies.
It's been a while since I read the HTK licence, but from memory and past
commercial practices I believe that what you are proposing is entirely
acceptable according to the HTK licence.
In fact I think www.speechmatics.com uses HVite in exactly this way to
do some final tidying up of the large vocabulary speech recognition output.
Tony
On 30/10/14 11:49, Georg Schlunz wrote:
> Good day
>
> Regarding the HTK license, as specified at http://htk.eng.cam.ac.uk/docs/licen
se.shtml , I would like to know whether the following scenario is permitted:
>
> The HTK software (including HVite) sits on a server in-house in our organisati
on, as per license sections 2.1 and 2.3.
> The HTK software (including HVite) is never distributed to a commercial (or no
n-commercial) party, as per license section 2.2.
>
> We have written our own server-client software, where:
> a) the client records speech and sends the audio file to the server, which pas
ses it on to HVite (the server software and HTK sit on the same in-house machine
)
> b) HVite decodes the audio into text
> c) the server replies to the client with the decoded text and the client proce
sses the text somehow
>
> Naturally, the client software contains no HTK code; it only processes data pr
oduced by HTK.
>

> Therefore, may this client software and decoding SERVICE be sold commercially
(as long as we agree to license sections 2.4 and 2.5)?
>
> Thank you
> Georg Schlunz
>
-- ** Cantab is hiring: www.cantabResearch.com/openings ** -Dr A J Robinson, Founder, Cantab Research Ltd
Phone direct: 01223 778240 office: 01223 794497
Company reg no GB 05697423, VAT reg no 925606030
51 Canterbury Street, Cambridge, CB4 3QG, UK
From tonyr at cantabResearch.com Tue Nov 4 20:04:46 2014
From: tonyr at cantabResearch.com (Tony Robinson)
Date: Wed Mar 25 05:25:47 2015
Subject: [HTK-Users] HTK license agreement
In-Reply-To: <545241EC02000049000E3077@pta-emo.csir.co.za>
References: <545241EC02000049000E3077@pta-emo.csir.co.za>
Message-ID: <5459315E.9030409@cantabResearch.com>
I just saw this post - I hope I haven't also missed any replies.
It's been a while since I read the HTK licence, but from memory and past
commercial practices I believe that what you are proposing is entirely
acceptable according to the HTK licence.
In fact I think www.speechmatics.com uses HVite in exactly this way to
do some final tidying up of the large vocabulary speech recognition output.
Tony
On 30/10/14 11:49, Georg Schlunz wrote:
> Good day
>
> Regarding the HTK license, as specified at http://htk.eng.cam.ac.uk/docs/licen
se.shtml , I would like to know whether the following scenario is permitted:
>
> The HTK software (including HVite) sits on a server in-house in our organisati
on, as per license sections 2.1 and 2.3.
> The HTK software (including HVite) is never distributed to a commercial (or no
n-commercial) party, as per license section 2.2.
>
> We have written our own server-client software, where:
> a) the client records speech and sends the audio file to the server, which pas
ses it on to HVite (the server software and HTK sit on the same in-house machine
)
> b) HVite decodes the audio into text
> c) the server replies to the client with the decoded text and the client proce
sses the text somehow
>
> Naturally, the client software contains no HTK code; it only processes data pr
oduced by HTK.
>
> Therefore, may this client software and decoding SERVICE be sold commercially
(as long as we agree to license sections 2.4 and 2.5)?
>
> Thank you
> Georg Schlunz

>
-- ** Cantab is hiring: www.cantabResearch.com/openings ** -Dr A J Robinson, Founder, Cantab Research Ltd
Phone direct: 01223 778240 office: 01223 794497
Company reg no GB 05697423, VAT reg no 925606030
51 Canterbury Street, Cambridge, CB4 3QG, UK
From tonyr at cantabResearch.com Tue Nov 4 20:04:46 2014
From: tonyr at cantabResearch.com (Tony Robinson)
Date: Thu Mar 26 05:48:17 2015
Subject: [HTK-Users] HTK license agreement
In-Reply-To: <545241EC02000049000E3077@pta-emo.csir.co.za>
References: <545241EC02000049000E3077@pta-emo.csir.co.za>
Message-ID: <5459315E.9030409@cantabResearch.com>
I just saw this post - I hope I haven't also missed any replies.
It's been a while since I read the HTK licence, but from memory and past
commercial practices I believe that what you are proposing is entirely
acceptable according to the HTK licence.
In fact I think www.speechmatics.com uses HVite in exactly this way to
do some final tidying up of the large vocabulary speech recognition output.
Tony
On 30/10/14 11:49, Georg Schlunz wrote:
> Good day
>
> Regarding the HTK license, as specified at http://htk.eng.cam.ac.uk/docs/licen
se.shtml , I would like to know whether the following scenario is permitted:
>
> The HTK software (including HVite) sits on a server in-house in our organisati
on, as per license sections 2.1 and 2.3.
> The HTK software (including HVite) is never distributed to a commercial (or no
n-commercial) party, as per license section 2.2.
>
> We have written our own server-client software, where:
> a) the client records speech and sends the audio file to the server, which pas
ses it on to HVite (the server software and HTK sit on the same in-house machine
)
> b) HVite decodes the audio into text
> c) the server replies to the client with the decoded text and the client proce
sses the text somehow
>
> Naturally, the client software contains no HTK code; it only processes data pr
oduced by HTK.
>
> Therefore, may this client software and decoding SERVICE be sold commercially
(as long as we agree to license sections 2.4 and 2.5)?
>
> Thank you
> Georg Schlunz
>
-- ** Cantab is hiring: www.cantabResearch.com/openings ** -Dr A J Robinson, Founder, Cantab Research Ltd
Phone direct: 01223 778240 office: 01223 794497

Company reg no GB 05697423, VAT reg no 925606030


51 Canterbury Street, Cambridge, CB4 3QG, UK
From tonyr at cantabResearch.com Tue Nov 4 20:04:46 2014
From: tonyr at cantabResearch.com (Tony Robinson)
Date: Fri Mar 27 05:29:45 2015
Subject: [HTK-Users] HTK license agreement
In-Reply-To: <545241EC02000049000E3077@pta-emo.csir.co.za>
References: <545241EC02000049000E3077@pta-emo.csir.co.za>
Message-ID: <5459315E.9030409@cantabResearch.com>
I just saw this post - I hope I haven't also missed any replies.
It's been a while since I read the HTK licence, but from memory and past
commercial practices I believe that what you are proposing is entirely
acceptable according to the HTK licence.
In fact I think www.speechmatics.com uses HVite in exactly this way to
do some final tidying up of the large vocabulary speech recognition output.
Tony
On 30/10/14 11:49, Georg Schlunz wrote:
> Good day
>
> Regarding the HTK license, as specified at http://htk.eng.cam.ac.uk/docs/licen
se.shtml , I would like to know whether the following scenario is permitted:
>
> The HTK software (including HVite) sits on a server in-house in our organisati
on, as per license sections 2.1 and 2.3.
> The HTK software (including HVite) is never distributed to a commercial (or no
n-commercial) party, as per license section 2.2.
>
> We have written our own server-client software, where:
> a) the client records speech and sends the audio file to the server, which pas
ses it on to HVite (the server software and HTK sit on the same in-house machine
)
> b) HVite decodes the audio into text
> c) the server replies to the client with the decoded text and the client proce
sses the text somehow
>
> Naturally, the client software contains no HTK code; it only processes data pr
oduced by HTK.
>
> Therefore, may this client software and decoding SERVICE be sold commercially
(as long as we agree to license sections 2.4 and 2.5)?
>
> Thank you
> Georg Schlunz
>
-- ** Cantab is hiring: www.cantabResearch.com/openings ** -Dr A J Robinson, Founder, Cantab Research Ltd
Phone direct: 01223 778240 office: 01223 794497
Company reg no GB 05697423, VAT reg no 925606030
51 Canterbury Street, Cambridge, CB4 3QG, UK
From tonyr at cantabResearch.com Tue Nov 4 20:04:46 2014
From: tonyr at cantabResearch.com (Tony Robinson)

Date: Sat Mar 28 04:55:57 2015


Subject: [HTK-Users] HTK license agreement
In-Reply-To: <545241EC02000049000E3077@pta-emo.csir.co.za>
References: <545241EC02000049000E3077@pta-emo.csir.co.za>
Message-ID: <5459315E.9030409@cantabResearch.com>
I just saw this post - I hope I haven't also missed any replies.
It's been a while since I read the HTK licence, but from memory and past
commercial practices I believe that what you are proposing is entirely
acceptable according to the HTK licence.
In fact I think www.speechmatics.com uses HVite in exactly this way to
do some final tidying up of the large vocabulary speech recognition output.
Tony
On 30/10/14 11:49, Georg Schlunz wrote:
> Good day
>
> Regarding the HTK license, as specified at http://htk.eng.cam.ac.uk/docs/licen
se.shtml , I would like to know whether the following scenario is permitted:
>
> The HTK software (including HVite) sits on a server in-house in our organisati
on, as per license sections 2.1 and 2.3.
> The HTK software (including HVite) is never distributed to a commercial (or no
n-commercial) party, as per license section 2.2.
>
> We have written our own server-client software, where:
> a) the client records speech and sends the audio file to the server, which pas
ses it on to HVite (the server software and HTK sit on the same in-house machine
)
> b) HVite decodes the audio into text
> c) the server replies to the client with the decoded text and the client proce
sses the text somehow
>
> Naturally, the client software contains no HTK code; it only processes data pr
oduced by HTK.
>
> Therefore, may this client software and decoding SERVICE be sold commercially
(as long as we agree to license sections 2.4 and 2.5)?
>
> Thank you
> Georg Schlunz
>
-- ** Cantab is hiring: www.cantabResearch.com/openings ** -Dr A J Robinson, Founder, Cantab Research Ltd
Phone direct: 01223 778240 office: 01223 794497
Company reg no GB 05697423, VAT reg no 925606030
51 Canterbury Street, Cambridge, CB4 3QG, UK
From tonyr at cantabResearch.com Tue Nov 4 20:04:46 2014
From: tonyr at cantabResearch.com (Tony Robinson)
Date: Sun Mar 29 04:45:32 2015
Subject: [HTK-Users] HTK license agreement
In-Reply-To: <545241EC02000049000E3077@pta-emo.csir.co.za>
References: <545241EC02000049000E3077@pta-emo.csir.co.za>
Message-ID: <5459315E.9030409@cantabResearch.com>

I just saw this post - I hope I haven't also missed any replies.
It's been a while since I read the HTK licence, but from memory and past
commercial practices I believe that what you are proposing is entirely
acceptable according to the HTK licence.
In fact I think www.speechmatics.com uses HVite in exactly this way to
do some final tidying up of the large vocabulary speech recognition output.
Tony
On 30/10/14 11:49, Georg Schlunz wrote:
> Good day
>
> Regarding the HTK license, as specified at http://htk.eng.cam.ac.uk/docs/licen
se.shtml , I would like to know whether the following scenario is permitted:
>
> The HTK software (including HVite) sits on a server in-house in our organisati
on, as per license sections 2.1 and 2.3.
> The HTK software (including HVite) is never distributed to a commercial (or no
n-commercial) party, as per license section 2.2.
>
> We have written our own server-client software, where:
> a) the client records speech and sends the audio file to the server, which pas
ses it on to HVite (the server software and HTK sit on the same in-house machine
)
> b) HVite decodes the audio into text
> c) the server replies to the client with the decoded text and the client proce
sses the text somehow
>
> Naturally, the client software contains no HTK code; it only processes data pr
oduced by HTK.
>
> Therefore, may this client software and decoding SERVICE be sold commercially
(as long as we agree to license sections 2.4 and 2.5)?
>
> Thank you
> Georg Schlunz
>
-- ** Cantab is hiring: www.cantabResearch.com/openings ** -Dr A J Robinson, Founder, Cantab Research Ltd
Phone direct: 01223 778240 office: 01223 794497
Company reg no GB 05697423, VAT reg no 925606030
51 Canterbury Street, Cambridge, CB4 3QG, UK
From tonyr at cantabResearch.com Tue Nov 4 20:04:46 2014
From: tonyr at cantabResearch.com (Tony Robinson)
Date: Mon Mar 30 04:34:05 2015
Subject: [HTK-Users] HTK license agreement
In-Reply-To: <545241EC02000049000E3077@pta-emo.csir.co.za>
References: <545241EC02000049000E3077@pta-emo.csir.co.za>
Message-ID: <5459315E.9030409@cantabResearch.com>
I just saw this post - I hope I haven't also missed any replies.
It's been a while since I read the HTK licence, but from memory and past
commercial practices I believe that what you are proposing is entirely

acceptable according to the HTK licence.


In fact I think www.speechmatics.com uses HVite in exactly this way to
do some final tidying up of the large vocabulary speech recognition output.
Tony
On 30/10/14 11:49, Georg Schlunz wrote:
> Good day
>
> Regarding the HTK license, as specified at http://htk.eng.cam.ac.uk/docs/licen
se.shtml , I would like to know whether the following scenario is permitted:
>
> The HTK software (including HVite) sits on a server in-house in our organisati
on, as per license sections 2.1 and 2.3.
> The HTK software (including HVite) is never distributed to a commercial (or no
n-commercial) party, as per license section 2.2.
>
> We have written our own server-client software, where:
> a) the client records speech and sends the audio file to the server, which pas
ses it on to HVite (the server software and HTK sit on the same in-house machine
)
> b) HVite decodes the audio into text
> c) the server replies to the client with the decoded text and the client proce
sses the text somehow
>
> Naturally, the client software contains no HTK code; it only processes data pr
oduced by HTK.
>
> Therefore, may this client software and decoding SERVICE be sold commercially
(as long as we agree to license sections 2.4 and 2.5)?
>
> Thank you
> Georg Schlunz
>
-- ** Cantab is hiring: www.cantabResearch.com/openings ** -Dr A J Robinson, Founder, Cantab Research Ltd
Phone direct: 01223 778240 office: 01223 794497
Company reg no GB 05697423, VAT reg no 925606030
51 Canterbury Street, Cambridge, CB4 3QG, UK
From tonyr at cantabResearch.com Tue Nov 4 20:04:46 2014
From: tonyr at cantabResearch.com (Tony Robinson)
Date: Tue Mar 31 04:58:48 2015
Subject: [HTK-Users] HTK license agreement
In-Reply-To: <545241EC02000049000E3077@pta-emo.csir.co.za>
References: <545241EC02000049000E3077@pta-emo.csir.co.za>
Message-ID: <5459315E.9030409@cantabResearch.com>
I just saw this post - I hope I haven't also missed any replies.
It's been a while since I read the HTK licence, but from memory and past
commercial practices I believe that what you are proposing is entirely
acceptable according to the HTK licence.
In fact I think www.speechmatics.com uses HVite in exactly this way to
do some final tidying up of the large vocabulary speech recognition output.

Tony
On 30/10/14 11:49, Georg Schlunz wrote:
> Good day
>
> Regarding the HTK license, as specified at http://htk.eng.cam.ac.uk/docs/licen
se.shtml , I would like to know whether the following scenario is permitted:
>
> The HTK software (including HVite) sits on a server in-house in our organisati
on, as per license sections 2.1 and 2.3.
> The HTK software (including HVite) is never distributed to a commercial (or no
n-commercial) party, as per license section 2.2.
>
> We have written our own server-client software, where:
> a) the client records speech and sends the audio file to the server, which pas
ses it on to HVite (the server software and HTK sit on the same in-house machine
)
> b) HVite decodes the audio into text
> c) the server replies to the client with the decoded text and the client proce
sses the text somehow
>
> Naturally, the client software contains no HTK code; it only processes data pr
oduced by HTK.
>
> Therefore, may this client software and decoding SERVICE be sold commercially
(as long as we agree to license sections 2.4 and 2.5)?
>
> Thank you
> Georg Schlunz
>
-- ** Cantab is hiring: www.cantabResearch.com/openings ** -Dr A J Robinson, Founder, Cantab Research Ltd
Phone direct: 01223 778240 office: 01223 794497
Company reg no GB 05697423, VAT reg no 925606030
51 Canterbury Street, Cambridge, CB4 3QG, UK
From tonyr at cantabResearch.com Tue Nov 4 20:04:46 2014
From: tonyr at cantabResearch.com (Tony Robinson)
Date: Wed Apr 1 05:36:29 2015
Subject: [HTK-Users] HTK license agreement
In-Reply-To: <545241EC02000049000E3077@pta-emo.csir.co.za>
References: <545241EC02000049000E3077@pta-emo.csir.co.za>
Message-ID: <5459315E.9030409@cantabResearch.com>
I just saw this post - I hope I haven't also missed any replies.
It's been a while since I read the HTK licence, but from memory and past
commercial practices I believe that what you are proposing is entirely
acceptable according to the HTK licence.
In fact I think www.speechmatics.com uses HVite in exactly this way to
do some final tidying up of the large vocabulary speech recognition output.
Tony
On 30/10/14 11:49, Georg Schlunz wrote:
> Good day

>
> Regarding the HTK license, as specified at http://htk.eng.cam.ac.uk/docs/licen
se.shtml , I would like to know whether the following scenario is permitted:
>
> The HTK software (including HVite) sits on a server in-house in our organisati
on, as per license sections 2.1 and 2.3.
> The HTK software (including HVite) is never distributed to a commercial (or no
n-commercial) party, as per license section 2.2.
>
> We have written our own server-client software, where:
> a) the client records speech and sends the audio file to the server, which pas
ses it on to HVite (the server software and HTK sit on the same in-house machine
)
> b) HVite decodes the audio into text
> c) the server replies to the client with the decoded text and the client proce
sses the text somehow
>
> Naturally, the client software contains no HTK code; it only processes data pr
oduced by HTK.
>
> Therefore, may this client software and decoding SERVICE be sold commercially
(as long as we agree to license sections 2.4 and 2.5)?
>
> Thank you
> Georg Schlunz
>
-- ** Cantab is hiring: www.cantabResearch.com/openings ** -Dr A J Robinson, Founder, Cantab Research Ltd
Phone direct: 01223 778240 office: 01223 794497
Company reg no GB 05697423, VAT reg no 925606030
51 Canterbury Street, Cambridge, CB4 3QG, UK
From tonyr at cantabResearch.com Tue Nov 4 20:04:46 2014
From: tonyr at cantabResearch.com (Tony Robinson)
Date: Thu Apr 2 05:20:47 2015
Subject: [HTK-Users] HTK license agreement
In-Reply-To: <545241EC02000049000E3077@pta-emo.csir.co.za>
References: <545241EC02000049000E3077@pta-emo.csir.co.za>
Message-ID: <5459315E.9030409@cantabResearch.com>
I just saw this post - I hope I haven't also missed any replies.
It's been a while since I read the HTK licence, but from memory and past
commercial practices I believe that what you are proposing is entirely
acceptable according to the HTK licence.
In fact I think www.speechmatics.com uses HVite in exactly this way to
do some final tidying up of the large vocabulary speech recognition output.
Tony
On 30/10/14 11:49, Georg Schlunz wrote:
> Good day
>
> Regarding the HTK license, as specified at http://htk.eng.cam.ac.uk/docs/licen
se.shtml , I would like to know whether the following scenario is permitted:
>
> The HTK software (including HVite) sits on a server in-house in our organisati

on, as per license sections 2.1 and 2.3.


> The HTK software (including HVite) is never distributed to a commercial (or no
n-commercial) party, as per license section 2.2.
>
> We have written our own server-client software, where:
> a) the client records speech and sends the audio file to the server, which pas
ses it on to HVite (the server software and HTK sit on the same in-house machine
)
> b) HVite decodes the audio into text
> c) the server replies to the client with the decoded text and the client proce
sses the text somehow
>
> Naturally, the client software contains no HTK code; it only processes data pr
oduced by HTK.
>
> Therefore, may this client software and decoding SERVICE be sold commercially
(as long as we agree to license sections 2.4 and 2.5)?
>
> Thank you
> Georg Schlunz
>
-- ** Cantab is hiring: www.cantabResearch.com/openings ** -Dr A J Robinson, Founder, Cantab Research Ltd
Phone direct: 01223 778240 office: 01223 794497
Company reg no GB 05697423, VAT reg no 925606030
51 Canterbury Street, Cambridge, CB4 3QG, UK
From tonyr at cantabResearch.com Tue Nov 4 20:04:46 2014
From: tonyr at cantabResearch.com (Tony Robinson)
Date: Fri Apr 3 06:02:25 2015
Subject: [HTK-Users] HTK license agreement
In-Reply-To: <545241EC02000049000E3077@pta-emo.csir.co.za>
References: <545241EC02000049000E3077@pta-emo.csir.co.za>
Message-ID: <5459315E.9030409@cantabResearch.com>
I just saw this post - I hope I haven't also missed any replies.
It's been a while since I read the HTK licence, but from memory and past
commercial practices I believe that what you are proposing is entirely
acceptable according to the HTK licence.
In fact I think www.speechmatics.com uses HVite in exactly this way to
do some final tidying up of the large vocabulary speech recognition output.
Tony
On 30/10/14 11:49, Georg Schlunz wrote:
> Good day
>
> Regarding the HTK license, as specified at http://htk.eng.cam.ac.uk/docs/licen
se.shtml , I would like to know whether the following scenario is permitted:
>
> The HTK software (including HVite) sits on a server in-house in our organisati
on, as per license sections 2.1 and 2.3.
> The HTK software (including HVite) is never distributed to a commercial (or no
n-commercial) party, as per license section 2.2.
>
> We have written our own server-client software, where:

> a) the client records speech and sends the audio file to the server, which pas
ses it on to HVite (the server software and HTK sit on the same in-house machine
)
> b) HVite decodes the audio into text
> c) the server replies to the client with the decoded text and the client proce
sses the text somehow
>
> Naturally, the client software contains no HTK code; it only processes data pr
oduced by HTK.
>
> Therefore, may this client software and decoding SERVICE be sold commercially
(as long as we agree to license sections 2.4 and 2.5)?
>
> Thank you
> Georg Schlunz
>
-- ** Cantab is hiring: www.cantabResearch.com/openings ** -Dr A J Robinson, Founder, Cantab Research Ltd
Phone direct: 01223 778240 office: 01223 794497
Company reg no GB 05697423, VAT reg no 925606030
51 Canterbury Street, Cambridge, CB4 3QG, UK
From tonyr at cantabResearch.com Tue Nov 4 20:04:46 2014
From: tonyr at cantabResearch.com (Tony Robinson)
Date: Sat Apr 4 05:35:50 2015
Subject: [HTK-Users] HTK license agreement
In-Reply-To: <545241EC02000049000E3077@pta-emo.csir.co.za>
References: <545241EC02000049000E3077@pta-emo.csir.co.za>
Message-ID: <5459315E.9030409@cantabResearch.com>
I just saw this post - I hope I haven't also missed any replies.
It's been a while since I read the HTK licence, but from memory and past
commercial practices I believe that what you are proposing is entirely
acceptable according to the HTK licence.
In fact I think www.speechmatics.com uses HVite in exactly this way to
do some final tidying up of the large vocabulary speech recognition output.
Tony
On 30/10/14 11:49, Georg Schlunz wrote:
> Good day
>
> Regarding the HTK license, as specified at http://htk.eng.cam.ac.uk/docs/licen
se.shtml , I would like to know whether the following scenario is permitted:
>
> The HTK software (including HVite) sits on a server in-house in our organisati
on, as per license sections 2.1 and 2.3.
> The HTK software (including HVite) is never distributed to a commercial (or no
n-commercial) party, as per license section 2.2.
>
> We have written our own server-client software, where:
> a) the client records speech and sends the audio file to the server, which pas
ses it on to HVite (the server software and HTK sit on the same in-house machine
)
> b) HVite decodes the audio into text
> c) the server replies to the client with the decoded text and the client proce

sses the text somehow


>
> Naturally, the client software contains no HTK code; it only processes data pr
oduced by HTK.
>
> Therefore, may this client software and decoding SERVICE be sold commercially
(as long as we agree to license sections 2.4 and 2.5)?
>
> Thank you
> Georg Schlunz
>
-- ** Cantab is hiring: www.cantabResearch.com/openings ** -Dr A J Robinson, Founder, Cantab Research Ltd
Phone direct: 01223 778240 office: 01223 794497
Company reg no GB 05697423, VAT reg no 925606030
51 Canterbury Street, Cambridge, CB4 3QG, UK
From tonyr at cantabResearch.com Tue Nov 4 20:04:46 2014
From: tonyr at cantabResearch.com (Tony Robinson)
Date: Sun Apr 5 05:28:39 2015
Subject: [HTK-Users] HTK license agreement
In-Reply-To: <545241EC02000049000E3077@pta-emo.csir.co.za>
References: <545241EC02000049000E3077@pta-emo.csir.co.za>
Message-ID: <5459315E.9030409@cantabResearch.com>
I just saw this post - I hope I haven't also missed any replies.
It's been a while since I read the HTK licence, but from memory and past
commercial practices I believe that what you are proposing is entirely
acceptable according to the HTK licence.
In fact I think www.speechmatics.com uses HVite in exactly this way to
do some final tidying up of the large vocabulary speech recognition output.
Tony
On 30/10/14 11:49, Georg Schlunz wrote:
> Good day
>
> Regarding the HTK license, as specified at http://htk.eng.cam.ac.uk/docs/licen
se.shtml , I would like to know whether the following scenario is permitted:
>
> The HTK software (including HVite) sits on a server in-house in our organisati
on, as per license sections 2.1 and 2.3.
> The HTK software (including HVite) is never distributed to a commercial (or no
n-commercial) party, as per license section 2.2.
>
> We have written our own server-client software, where:
> a) the client records speech and sends the audio file to the server, which pas
ses it on to HVite (the server software and HTK sit on the same in-house machine
)
> b) HVite decodes the audio into text
> c) the server replies to the client with the decoded text and the client proce
sses the text somehow
>
> Naturally, the client software contains no HTK code; it only processes data pr
oduced by HTK.
>

> Therefore, may this client software and decoding SERVICE be sold commercially
(as long as we agree to license sections 2.4 and 2.5)?
>
> Thank you
> Georg Schlunz
>
-- ** Cantab is hiring: www.cantabResearch.com/openings ** -Dr A J Robinson, Founder, Cantab Research Ltd
Phone direct: 01223 778240 office: 01223 794497
Company reg no GB 05697423, VAT reg no 925606030
51 Canterbury Street, Cambridge, CB4 3QG, UK
From tonyr at cantabResearch.com Tue Nov 4 20:04:46 2014
From: tonyr at cantabResearch.com (Tony Robinson)
Date: Mon Apr 6 05:25:24 2015
Subject: [HTK-Users] HTK license agreement
In-Reply-To: <545241EC02000049000E3077@pta-emo.csir.co.za>
References: <545241EC02000049000E3077@pta-emo.csir.co.za>
Message-ID: <5459315E.9030409@cantabResearch.com>
I just saw this post - I hope I haven't also missed any replies.
It's been a while since I read the HTK licence, but from memory and past
commercial practices I believe that what you are proposing is entirely
acceptable according to the HTK licence.
In fact I think www.speechmatics.com uses HVite in exactly this way to
do some final tidying up of the large vocabulary speech recognition output.
Tony
On 30/10/14 11:49, Georg Schlunz wrote:
> Good day
>
> Regarding the HTK license, as specified at http://htk.eng.cam.ac.uk/docs/licen
se.shtml , I would like to know whether the following scenario is permitted:
>
> The HTK software (including HVite) sits on a server in-house in our organisati
on, as per license sections 2.1 and 2.3.
> The HTK software (including HVite) is never distributed to a commercial (or no
n-commercial) party, as per license section 2.2.
>
> We have written our own server-client software, where:
> a) the client records speech and sends the audio file to the server, which pas
ses it on to HVite (the server software and HTK sit on the same in-house machine
)
> b) HVite decodes the audio into text
> c) the server replies to the client with the decoded text and the client proce
sses the text somehow
>
> Naturally, the client software contains no HTK code; it only processes data pr
oduced by HTK.
>
> Therefore, may this client software and decoding SERVICE be sold commercially
(as long as we agree to license sections 2.4 and 2.5)?
>
> Thank you
> Georg Schlunz

>
-- ** Cantab is hiring: www.cantabResearch.com/openings ** -Dr A J Robinson, Founder, Cantab Research Ltd
Phone direct: 01223 778240 office: 01223 794497
Company reg no GB 05697423, VAT reg no 925606030
51 Canterbury Street, Cambridge, CB4 3QG, UK
From tonyr at cantabResearch.com Tue Nov 4 20:04:46 2014
From: tonyr at cantabResearch.com (Tony Robinson)
Date: Tue Apr 7 05:32:42 2015
Subject: [HTK-Users] HTK license agreement
In-Reply-To: <545241EC02000049000E3077@pta-emo.csir.co.za>
References: <545241EC02000049000E3077@pta-emo.csir.co.za>
Message-ID: <5459315E.9030409@cantabResearch.com>
I just saw this post - I hope I haven't also missed any replies.
It's been a while since I read the HTK licence, but from memory and past
commercial practices I believe that what you are proposing is entirely
acceptable according to the HTK licence.
In fact I think www.speechmatics.com uses HVite in exactly this way to
do some final tidying up of the large vocabulary speech recognition output.
Tony
On 30/10/14 11:49, Georg Schlunz wrote:
> Good day
>
> Regarding the HTK license, as specified at http://htk.eng.cam.ac.uk/docs/licen
se.shtml , I would like to know whether the following scenario is permitted:
>
> The HTK software (including HVite) sits on a server in-house in our organisati
on, as per license sections 2.1 and 2.3.
> The HTK software (including HVite) is never distributed to a commercial (or no
n-commercial) party, as per license section 2.2.
>
> We have written our own server-client software, where:
> a) the client records speech and sends the audio file to the server, which pas
ses it on to HVite (the server software and HTK sit on the same in-house machine
)
> b) HVite decodes the audio into text
> c) the server replies to the client with the decoded text and the client proce
sses the text somehow
>
> Naturally, the client software contains no HTK code; it only processes data pr
oduced by HTK.
>
> Therefore, may this client software and decoding SERVICE be sold commercially
(as long as we agree to license sections 2.4 and 2.5)?
>
> Thank you
> Georg Schlunz
>
-- ** Cantab is hiring: www.cantabResearch.com/openings ** -Dr A J Robinson, Founder, Cantab Research Ltd
Phone direct: 01223 778240 office: 01223 794497

Company reg no GB 05697423, VAT reg no 925606030


51 Canterbury Street, Cambridge, CB4 3QG, UK
From tonyr at cantabResearch.com Tue Nov 4 20:04:46 2014
From: tonyr at cantabResearch.com (Tony Robinson)
Date: Wed Apr 8 05:42:01 2015
Subject: [HTK-Users] HTK license agreement
In-Reply-To: <545241EC02000049000E3077@pta-emo.csir.co.za>
References: <545241EC02000049000E3077@pta-emo.csir.co.za>
Message-ID: <5459315E.9030409@cantabResearch.com>
I just saw this post - I hope I haven't also missed any replies.
It's been a while since I read the HTK licence, but from memory and past
commercial practices I believe that what you are proposing is entirely
acceptable according to the HTK licence.
In fact I think www.speechmatics.com uses HVite in exactly this way to
do some final tidying up of the large vocabulary speech recognition output.
Tony
On 30/10/14 11:49, Georg Schlunz wrote:
> Good day
>
> Regarding the HTK license, as specified at http://htk.eng.cam.ac.uk/docs/licen
se.shtml , I would like to know whether the following scenario is permitted:
>
> The HTK software (including HVite) sits on a server in-house in our organisati
on, as per license sections 2.1 and 2.3.
> The HTK software (including HVite) is never distributed to a commercial (or no
n-commercial) party, as per license section 2.2.
>
> We have written our own server-client software, where:
> a) the client records speech and sends the audio file to the server, which pas
ses it on to HVite (the server software and HTK sit on the same in-house machine
)
> b) HVite decodes the audio into text
> c) the server replies to the client with the decoded text and the client proce
sses the text somehow
>
> Naturally, the client software contains no HTK code; it only processes data pr
oduced by HTK.
>
> Therefore, may this client software and decoding SERVICE be sold commercially
(as long as we agree to license sections 2.4 and 2.5)?
>
> Thank you
> Georg Schlunz
>
-- ** Cantab is hiring: www.cantabResearch.com/openings ** -Dr A J Robinson, Founder, Cantab Research Ltd
Phone direct: 01223 778240 office: 01223 794497
Company reg no GB 05697423, VAT reg no 925606030
51 Canterbury Street, Cambridge, CB4 3QG, UK
From tonyr at cantabResearch.com Tue Nov 4 20:04:46 2014
From: tonyr at cantabResearch.com (Tony Robinson)

Date: Thu Apr 9 05:57:58 2015


Subject: [HTK-Users] HTK license agreement
In-Reply-To: <545241EC02000049000E3077@pta-emo.csir.co.za>
References: <545241EC02000049000E3077@pta-emo.csir.co.za>
Message-ID: <5459315E.9030409@cantabResearch.com>
I just saw this post - I hope I haven't also missed any replies.
It's been a while since I read the HTK licence, but from memory and past
commercial practices I believe that what you are proposing is entirely
acceptable according to the HTK licence.
In fact I think www.speechmatics.com uses HVite in exactly this way to
do some final tidying up of the large vocabulary speech recognition output.
Tony
On 30/10/14 11:49, Georg Schlunz wrote:
> Good day
>
> Regarding the HTK license, as specified at http://htk.eng.cam.ac.uk/docs/licen
se.shtml , I would like to know whether the following scenario is permitted:
>
> The HTK software (including HVite) sits on a server in-house in our organisati
on, as per license sections 2.1 and 2.3.
> The HTK software (including HVite) is never distributed to a commercial (or no
n-commercial) party, as per license section 2.2.
>
> We have written our own server-client software, where:
> a) the client records speech and sends the audio file to the server, which pas
ses it on to HVite (the server software and HTK sit on the same in-house machine
)
> b) HVite decodes the audio into text
> c) the server replies to the client with the decoded text and the client proce
sses the text somehow
>
> Naturally, the client software contains no HTK code; it only processes data pr
oduced by HTK.
>
> Therefore, may this client software and decoding SERVICE be sold commercially
(as long as we agree to license sections 2.4 and 2.5)?
>
> Thank you
> Georg Schlunz
>
-- ** Cantab is hiring: www.cantabResearch.com/openings ** -Dr A J Robinson, Founder, Cantab Research Ltd
Phone direct: 01223 778240 office: 01223 794497
Company reg no GB 05697423, VAT reg no 925606030
51 Canterbury Street, Cambridge, CB4 3QG, UK
From tonyr at cantabResearch.com Tue Nov 4 20:04:46 2014
From: tonyr at cantabResearch.com (Tony Robinson)
Date: Fri Apr 10 05:32:08 2015
Subject: [HTK-Users] HTK license agreement
In-Reply-To: <545241EC02000049000E3077@pta-emo.csir.co.za>
References: <545241EC02000049000E3077@pta-emo.csir.co.za>
Message-ID: <5459315E.9030409@cantabResearch.com>

I just saw this post - I hope I haven't also missed any replies.
It's been a while since I read the HTK licence, but from memory and past
commercial practices I believe that what you are proposing is entirely
acceptable according to the HTK licence.
In fact I think www.speechmatics.com uses HVite in exactly this way to
do some final tidying up of the large vocabulary speech recognition output.
Tony
On 30/10/14 11:49, Georg Schlunz wrote:
> Good day
>
> Regarding the HTK license, as specified at http://htk.eng.cam.ac.uk/docs/licen
se.shtml , I would like to know whether the following scenario is permitted:
>
> The HTK software (including HVite) sits on a server in-house in our organisati
on, as per license sections 2.1 and 2.3.
> The HTK software (including HVite) is never distributed to a commercial (or no
n-commercial) party, as per license section 2.2.
>
> We have written our own server-client software, where:
> a) the client records speech and sends the audio file to the server, which pas
ses it on to HVite (the server software and HTK sit on the same in-house machine
)
> b) HVite decodes the audio into text
> c) the server replies to the client with the decoded text and the client proce
sses the text somehow
>
> Naturally, the client software contains no HTK code; it only processes data pr
oduced by HTK.
>
> Therefore, may this client software and decoding SERVICE be sold commercially
(as long as we agree to license sections 2.4 and 2.5)?
>
> Thank you
> Georg Schlunz
>
-- ** Cantab is hiring: www.cantabResearch.com/openings ** -Dr A J Robinson, Founder, Cantab Research Ltd
Phone direct: 01223 778240 office: 01223 794497
Company reg no GB 05697423, VAT reg no 925606030
51 Canterbury Street, Cambridge, CB4 3QG, UK
From tonyr at cantabResearch.com Tue Nov 4 20:04:46 2014
From: tonyr at cantabResearch.com (Tony Robinson)
Date: Sat Apr 11 05:37:03 2015
Subject: [HTK-Users] HTK license agreement
In-Reply-To: <545241EC02000049000E3077@pta-emo.csir.co.za>
References: <545241EC02000049000E3077@pta-emo.csir.co.za>
Message-ID: <5459315E.9030409@cantabResearch.com>
I just saw this post - I hope I haven't also missed any replies.
It's been a while since I read the HTK licence, but from memory and past
commercial practices I believe that what you are proposing is entirely

acceptable according to the HTK licence.


In fact I think www.speechmatics.com uses HVite in exactly this way to
do some final tidying up of the large vocabulary speech recognition output.
Tony
On 30/10/14 11:49, Georg Schlunz wrote:
> Good day
>
> Regarding the HTK license, as specified at http://htk.eng.cam.ac.uk/docs/licen
se.shtml , I would like to know whether the following scenario is permitted:
>
> The HTK software (including HVite) sits on a server in-house in our organisati
on, as per license sections 2.1 and 2.3.
> The HTK software (including HVite) is never distributed to a commercial (or no
n-commercial) party, as per license section 2.2.
>
> We have written our own server-client software, where:
> a) the client records speech and sends the audio file to the server, which pas
ses it on to HVite (the server software and HTK sit on the same in-house machine
)
> b) HVite decodes the audio into text
> c) the server replies to the client with the decoded text and the client proce
sses the text somehow
>
> Naturally, the client software contains no HTK code; it only processes data pr
oduced by HTK.
>
> Therefore, may this client software and decoding SERVICE be sold commercially
(as long as we agree to license sections 2.4 and 2.5)?
>
> Thank you
> Georg Schlunz
>
-- ** Cantab is hiring: www.cantabResearch.com/openings ** -Dr A J Robinson, Founder, Cantab Research Ltd
Phone direct: 01223 778240 office: 01223 794497
Company reg no GB 05697423, VAT reg no 925606030
51 Canterbury Street, Cambridge, CB4 3QG, UK
From tonyr at cantabResearch.com Tue Nov 4 20:04:46 2014
From: tonyr at cantabResearch.com (Tony Robinson)
Date: Sun Apr 12 05:15:05 2015
Subject: [HTK-Users] HTK license agreement
In-Reply-To: <545241EC02000049000E3077@pta-emo.csir.co.za>
References: <545241EC02000049000E3077@pta-emo.csir.co.za>
Message-ID: <5459315E.9030409@cantabResearch.com>
I just saw this post - I hope I haven't also missed any replies.
It's been a while since I read the HTK licence, but from memory and past
commercial practices I believe that what you are proposing is entirely
acceptable according to the HTK licence.
In fact I think www.speechmatics.com uses HVite in exactly this way to
do some final tidying up of the large vocabulary speech recognition output.

Tony
On 30/10/14 11:49, Georg Schlunz wrote:
> Good day
>
> Regarding the HTK license, as specified at http://htk.eng.cam.ac.uk/docs/licen
se.shtml , I would like to know whether the following scenario is permitted:
>
> The HTK software (including HVite) sits on a server in-house in our organisati
on, as per license sections 2.1 and 2.3.
> The HTK software (including HVite) is never distributed to a commercial (or no
n-commercial) party, as per license section 2.2.
>
> We have written our own server-client software, where:
> a) the client records speech and sends the audio file to the server, which pas
ses it on to HVite (the server software and HTK sit on the same in-house machine
)
> b) HVite decodes the audio into text
> c) the server replies to the client with the decoded text and the client proce
sses the text somehow
>
> Naturally, the client software contains no HTK code; it only processes data pr
oduced by HTK.
>
> Therefore, may this client software and decoding SERVICE be sold commercially
(as long as we agree to license sections 2.4 and 2.5)?
>
> Thank you
> Georg Schlunz
>
-- ** Cantab is hiring: www.cantabResearch.com/openings ** -Dr A J Robinson, Founder, Cantab Research Ltd
Phone direct: 01223 778240 office: 01223 794497
Company reg no GB 05697423, VAT reg no 925606030
51 Canterbury Street, Cambridge, CB4 3QG, UK
From tonyr at cantabResearch.com Tue Nov 4 20:04:46 2014
From: tonyr at cantabResearch.com (Tony Robinson)
Date: Mon Apr 13 05:09:54 2015
Subject: [HTK-Users] HTK license agreement
In-Reply-To: <545241EC02000049000E3077@pta-emo.csir.co.za>
References: <545241EC02000049000E3077@pta-emo.csir.co.za>
Message-ID: <5459315E.9030409@cantabResearch.com>
I just saw this post - I hope I haven't also missed any replies.
It's been a while since I read the HTK licence, but from memory and past
commercial practices I believe that what you are proposing is entirely
acceptable according to the HTK licence.
In fact I think www.speechmatics.com uses HVite in exactly this way to
do some final tidying up of the large vocabulary speech recognition output.
Tony
On 30/10/14 11:49, Georg Schlunz wrote:
> Good day

>
> Regarding the HTK license, as specified at http://htk.eng.cam.ac.uk/docs/licen
se.shtml , I would like to know whether the following scenario is permitted:
>
> The HTK software (including HVite) sits on a server in-house in our organisati
on, as per license sections 2.1 and 2.3.
> The HTK software (including HVite) is never distributed to a commercial (or no
n-commercial) party, as per license section 2.2.
>
> We have written our own server-client software, where:
> a) the client records speech and sends the audio file to the server, which pas
ses it on to HVite (the server software and HTK sit on the same in-house machine
)
> b) HVite decodes the audio into text
> c) the server replies to the client with the decoded text and the client proce
sses the text somehow
>
> Naturally, the client software contains no HTK code; it only processes data pr
oduced by HTK.
>
> Therefore, may this client software and decoding SERVICE be sold commercially
(as long as we agree to license sections 2.4 and 2.5)?
>
> Thank you
> Georg Schlunz
>
-- ** Cantab is hiring: www.cantabResearch.com/openings ** -Dr A J Robinson, Founder, Cantab Research Ltd
Phone direct: 01223 778240 office: 01223 794497
Company reg no GB 05697423, VAT reg no 925606030
51 Canterbury Street, Cambridge, CB4 3QG, UK
From tonyr at cantabResearch.com Tue Nov 4 20:04:46 2014
From: tonyr at cantabResearch.com (Tony Robinson)
Date: Tue Apr 14 05:30:10 2015
Subject: [HTK-Users] HTK license agreement
In-Reply-To: <545241EC02000049000E3077@pta-emo.csir.co.za>
References: <545241EC02000049000E3077@pta-emo.csir.co.za>
Message-ID: <5459315E.9030409@cantabResearch.com>
I just saw this post - I hope I haven't also missed any replies.
It's been a while since I read the HTK licence, but from memory and past
commercial practices I believe that what you are proposing is entirely
acceptable according to the HTK licence.
In fact I think www.speechmatics.com uses HVite in exactly this way to
do some final tidying up of the large vocabulary speech recognition output.
Tony
On 30/10/14 11:49, Georg Schlunz wrote:
> Good day
>
> Regarding the HTK license, as specified at http://htk.eng.cam.ac.uk/docs/licen
se.shtml , I would like to know whether the following scenario is permitted:
>
> The HTK software (including HVite) sits on a server in-house in our organisati

on, as per license sections 2.1 and 2.3.


> The HTK software (including HVite) is never distributed to a commercial (or no
n-commercial) party, as per license section 2.2.
>
> We have written our own server-client software, where:
> a) the client records speech and sends the audio file to the server, which pas
ses it on to HVite (the server software and HTK sit on the same in-house machine
)
> b) HVite decodes the audio into text
> c) the server replies to the client with the decoded text and the client proce
sses the text somehow
>
> Naturally, the client software contains no HTK code; it only processes data pr
oduced by HTK.
>
> Therefore, may this client software and decoding SERVICE be sold commercially
(as long as we agree to license sections 2.4 and 2.5)?
>
> Thank you
> Georg Schlunz
>
-- ** Cantab is hiring: www.cantabResearch.com/openings ** -Dr A J Robinson, Founder, Cantab Research Ltd
Phone direct: 01223 778240 office: 01223 794497
Company reg no GB 05697423, VAT reg no 925606030
51 Canterbury Street, Cambridge, CB4 3QG, UK
From tonyr at cantabResearch.com Tue Nov 4 20:04:46 2014
From: tonyr at cantabResearch.com (Tony Robinson)
Date: Wed Apr 15 05:52:33 2015
Subject: [HTK-Users] HTK license agreement
In-Reply-To: <545241EC02000049000E3077@pta-emo.csir.co.za>
References: <545241EC02000049000E3077@pta-emo.csir.co.za>
Message-ID: <5459315E.9030409@cantabResearch.com>
I just saw this post - I hope I haven't also missed any replies.
It's been a while since I read the HTK licence, but from memory and past
commercial practices I believe that what you are proposing is entirely
acceptable according to the HTK licence.
In fact I think www.speechmatics.com uses HVite in exactly this way to
do some final tidying up of the large vocabulary speech recognition output.
Tony
On 30/10/14 11:49, Georg Schlunz wrote:
> Good day
>
> Regarding the HTK license, as specified at http://htk.eng.cam.ac.uk/docs/licen
se.shtml , I would like to know whether the following scenario is permitted:
>
> The HTK software (including HVite) sits on a server in-house in our organisati
on, as per license sections 2.1 and 2.3.
> The HTK software (including HVite) is never distributed to a commercial (or no
n-commercial) party, as per license section 2.2.
>
> We have written our own server-client software, where:

> a) the client records speech and sends the audio file to the server, which pas
ses it on to HVite (the server software and HTK sit on the same in-house machine
)
> b) HVite decodes the audio into text
> c) the server replies to the client with the decoded text and the client proce
sses the text somehow
>
> Naturally, the client software contains no HTK code; it only processes data pr
oduced by HTK.
>
> Therefore, may this client software and decoding SERVICE be sold commercially
(as long as we agree to license sections 2.4 and 2.5)?
>
> Thank you
> Georg Schlunz
>
-- ** Cantab is hiring: www.cantabResearch.com/openings ** -Dr A J Robinson, Founder, Cantab Research Ltd
Phone direct: 01223 778240 office: 01223 794497
Company reg no GB 05697423, VAT reg no 925606030
51 Canterbury Street, Cambridge, CB4 3QG, UK
From tonyr at cantabResearch.com Tue Nov 4 20:04:46 2014
From: tonyr at cantabResearch.com (Tony Robinson)
Date: Thu Apr 16 05:46:59 2015
Subject: [HTK-Users] HTK license agreement
In-Reply-To: <545241EC02000049000E3077@pta-emo.csir.co.za>
References: <545241EC02000049000E3077@pta-emo.csir.co.za>
Message-ID: <5459315E.9030409@cantabResearch.com>
I just saw this post - I hope I haven't also missed any replies.
It's been a while since I read the HTK licence, but from memory and past
commercial practices I believe that what you are proposing is entirely
acceptable according to the HTK licence.
In fact I think www.speechmatics.com uses HVite in exactly this way to
do some final tidying up of the large vocabulary speech recognition output.
Tony
On 30/10/14 11:49, Georg Schlunz wrote:
> Good day
>
> Regarding the HTK license, as specified at http://htk.eng.cam.ac.uk/docs/licen
se.shtml , I would like to know whether the following scenario is permitted:
>
> The HTK software (including HVite) sits on a server in-house in our organisati
on, as per license sections 2.1 and 2.3.
> The HTK software (including HVite) is never distributed to a commercial (or no
n-commercial) party, as per license section 2.2.
>
> We have written our own server-client software, where:
> a) the client records speech and sends the audio file to the server, which pas
ses it on to HVite (the server software and HTK sit on the same in-house machine
)
> b) HVite decodes the audio into text
> c) the server replies to the client with the decoded text and the client proce

sses the text somehow


>
> Naturally, the client software contains no HTK code; it only processes data pr
oduced by HTK.
>
> Therefore, may this client software and decoding SERVICE be sold commercially
(as long as we agree to license sections 2.4 and 2.5)?
>
> Thank you
> Georg Schlunz
>
-- ** Cantab is hiring: www.cantabResearch.com/openings ** -Dr A J Robinson, Founder, Cantab Research Ltd
Phone direct: 01223 778240 office: 01223 794497
Company reg no GB 05697423, VAT reg no 925606030
51 Canterbury Street, Cambridge, CB4 3QG, UK
From tonyr at cantabResearch.com Tue Nov 4 20:04:46 2014
From: tonyr at cantabResearch.com (Tony Robinson)
Date: Fri Apr 17 05:52:36 2015
Subject: [HTK-Users] HTK license agreement
In-Reply-To: <545241EC02000049000E3077@pta-emo.csir.co.za>
References: <545241EC02000049000E3077@pta-emo.csir.co.za>
Message-ID: <5459315E.9030409@cantabResearch.com>
I just saw this post - I hope I haven't also missed any replies.
It's been a while since I read the HTK licence, but from memory and past
commercial practices I believe that what you are proposing is entirely
acceptable according to the HTK licence.
In fact I think www.speechmatics.com uses HVite in exactly this way to
do some final tidying up of the large vocabulary speech recognition output.
Tony
On 30/10/14 11:49, Georg Schlunz wrote:
> Good day
>
> Regarding the HTK license, as specified at http://htk.eng.cam.ac.uk/docs/licen
se.shtml , I would like to know whether the following scenario is permitted:
>
> The HTK software (including HVite) sits on a server in-house in our organisati
on, as per license sections 2.1 and 2.3.
> The HTK software (including HVite) is never distributed to a commercial (or no
n-commercial) party, as per license section 2.2.
>
> We have written our own server-client software, where:
> a) the client records speech and sends the audio file to the server, which pas
ses it on to HVite (the server software and HTK sit on the same in-house machine
)
> b) HVite decodes the audio into text
> c) the server replies to the client with the decoded text and the client proce
sses the text somehow
>
> Naturally, the client software contains no HTK code; it only processes data pr
oduced by HTK.
>

> Therefore, may this client software and decoding SERVICE be sold commercially
(as long as we agree to license sections 2.4 and 2.5)?
>
> Thank you
> Georg Schlunz
>
-- ** Cantab is hiring: www.cantabResearch.com/openings ** -Dr A J Robinson, Founder, Cantab Research Ltd
Phone direct: 01223 778240 office: 01223 794497
Company reg no GB 05697423, VAT reg no 925606030
51 Canterbury Street, Cambridge, CB4 3QG, UK
From tonyr at cantabResearch.com Tue Nov 4 20:04:46 2014
From: tonyr at cantabResearch.com (Tony Robinson)
Date: Sat Apr 18 05:30:28 2015
Subject: [HTK-Users] HTK license agreement
In-Reply-To: <545241EC02000049000E3077@pta-emo.csir.co.za>
References: <545241EC02000049000E3077@pta-emo.csir.co.za>
Message-ID: <5459315E.9030409@cantabResearch.com>
I just saw this post - I hope I haven't also missed any replies.
It's been a while since I read the HTK licence, but from memory and past
commercial practices I believe that what you are proposing is entirely
acceptable according to the HTK licence.
In fact I think www.speechmatics.com uses HVite in exactly this way to
do some final tidying up of the large vocabulary speech recognition output.
Tony
On 30/10/14 11:49, Georg Schlunz wrote:
> Good day
>
> Regarding the HTK license, as specified at http://htk.eng.cam.ac.uk/docs/licen
se.shtml , I would like to know whether the following scenario is permitted:
>
> The HTK software (including HVite) sits on a server in-house in our organisati
on, as per license sections 2.1 and 2.3.
> The HTK software (including HVite) is never distributed to a commercial (or no
n-commercial) party, as per license section 2.2.
>
> We have written our own server-client software, where:
> a) the client records speech and sends the audio file to the server, which pas
ses it on to HVite (the server software and HTK sit on the same in-house machine
)
> b) HVite decodes the audio into text
> c) the server replies to the client with the decoded text and the client proce
sses the text somehow
>
> Naturally, the client software contains no HTK code; it only processes data pr
oduced by HTK.
>
> Therefore, may this client software and decoding SERVICE be sold commercially
(as long as we agree to license sections 2.4 and 2.5)?
>
> Thank you
> Georg Schlunz

>
-- ** Cantab is hiring: www.cantabResearch.com/openings ** -Dr A J Robinson, Founder, Cantab Research Ltd
Phone direct: 01223 778240 office: 01223 794497
Company reg no GB 05697423, VAT reg no 925606030
51 Canterbury Street, Cambridge, CB4 3QG, UK
From tonyr at cantabResearch.com Tue Nov 4 20:04:46 2014
From: tonyr at cantabResearch.com (Tony Robinson)
Date: Sun Apr 19 05:51:21 2015
Subject: [HTK-Users] HTK license agreement
In-Reply-To: <545241EC02000049000E3077@pta-emo.csir.co.za>
References: <545241EC02000049000E3077@pta-emo.csir.co.za>
Message-ID: <5459315E.9030409@cantabResearch.com>
I just saw this post - I hope I haven't also missed any replies.
It's been a while since I read the HTK licence, but from memory and past
commercial practices I believe that what you are proposing is entirely
acceptable according to the HTK licence.
In fact I think www.speechmatics.com uses HVite in exactly this way to
do some final tidying up of the large vocabulary speech recognition output.
Tony
On 30/10/14 11:49, Georg Schlunz wrote:
> Good day
>
> Regarding the HTK license, as specified at http://htk.eng.cam.ac.uk/docs/licen
se.shtml , I would like to know whether the following scenario is permitted:
>
> The HTK software (including HVite) sits on a server in-house in our organisati
on, as per license sections 2.1 and 2.3.
> The HTK software (including HVite) is never distributed to a commercial (or no
n-commercial) party, as per license section 2.2.
>
> We have written our own server-client software, where:
> a) the client records speech and sends the audio file to the server, which pas
ses it on to HVite (the server software and HTK sit on the same in-house machine
)
> b) HVite decodes the audio into text
> c) the server replies to the client with the decoded text and the client proce
sses the text somehow
>
> Naturally, the client software contains no HTK code; it only processes data pr
oduced by HTK.
>
> Therefore, may this client software and decoding SERVICE be sold commercially
(as long as we agree to license sections 2.4 and 2.5)?
>
> Thank you
> Georg Schlunz
>
-- ** Cantab is hiring: www.cantabResearch.com/openings ** -Dr A J Robinson, Founder, Cantab Research Ltd
Phone direct: 01223 778240 office: 01223 794497

Company reg no GB 05697423, VAT reg no 925606030


51 Canterbury Street, Cambridge, CB4 3QG, UK
From tonyr at cantabResearch.com Tue Nov 4 20:04:46 2014
From: tonyr at cantabResearch.com (Tony Robinson)
Date: Mon Apr 20 05:35:19 2015
Subject: [HTK-Users] HTK license agreement
In-Reply-To: <545241EC02000049000E3077@pta-emo.csir.co.za>
References: <545241EC02000049000E3077@pta-emo.csir.co.za>
Message-ID: <5459315E.9030409@cantabResearch.com>
I just saw this post - I hope I haven't also missed any replies.
It's been a while since I read the HTK licence, but from memory and past
commercial practices I believe that what you are proposing is entirely
acceptable according to the HTK licence.
In fact I think www.speechmatics.com uses HVite in exactly this way to
do some final tidying up of the large vocabulary speech recognition output.
Tony
On 30/10/14 11:49, Georg Schlunz wrote:
> Good day
>
> Regarding the HTK license, as specified at http://htk.eng.cam.ac.uk/docs/licen
se.shtml , I would like to know whether the following scenario is permitted:
>
> The HTK software (including HVite) sits on a server in-house in our organisati
on, as per license sections 2.1 and 2.3.
> The HTK software (including HVite) is never distributed to a commercial (or no
n-commercial) party, as per license section 2.2.
>
> We have written our own server-client software, where:
> a) the client records speech and sends the audio file to the server, which pas
ses it on to HVite (the server software and HTK sit on the same in-house machine
)
> b) HVite decodes the audio into text
> c) the server replies to the client with the decoded text and the client proce
sses the text somehow
>
> Naturally, the client software contains no HTK code; it only processes data pr
oduced by HTK.
>
> Therefore, may this client software and decoding SERVICE be sold commercially
(as long as we agree to license sections 2.4 and 2.5)?
>
> Thank you
> Georg Schlunz
>
-- ** Cantab is hiring: www.cantabResearch.com/openings ** -Dr A J Robinson, Founder, Cantab Research Ltd
Phone direct: 01223 778240 office: 01223 794497
Company reg no GB 05697423, VAT reg no 925606030
51 Canterbury Street, Cambridge, CB4 3QG, UK
From tonyr at cantabResearch.com Tue Nov 4 20:04:46 2014
From: tonyr at cantabResearch.com (Tony Robinson)

Date: Tue Apr 21 05:52:50 2015


Subject: [HTK-Users] HTK license agreement
In-Reply-To: <545241EC02000049000E3077@pta-emo.csir.co.za>
References: <545241EC02000049000E3077@pta-emo.csir.co.za>
Message-ID: <5459315E.9030409@cantabResearch.com>
I just saw this post - I hope I haven't also missed any replies.
It's been a while since I read the HTK licence, but from memory and past
commercial practices I believe that what you are proposing is entirely
acceptable according to the HTK licence.
In fact I think www.speechmatics.com uses HVite in exactly this way to
do some final tidying up of the large vocabulary speech recognition output.
Tony
On 30/10/14 11:49, Georg Schlunz wrote:
> Good day
>
> Regarding the HTK license, as specified at http://htk.eng.cam.ac.uk/docs/licen
se.shtml , I would like to know whether the following scenario is permitted:
>
> The HTK software (including HVite) sits on a server in-house in our organisati
on, as per license sections 2.1 and 2.3.
> The HTK software (including HVite) is never distributed to a commercial (or no
n-commercial) party, as per license section 2.2.
>
> We have written our own server-client software, where:
> a) the client records speech and sends the audio file to the server, which pas
ses it on to HVite (the server software and HTK sit on the same in-house machine
)
> b) HVite decodes the audio into text
> c) the server replies to the client with the decoded text and the client proce
sses the text somehow
>
> Naturally, the client software contains no HTK code; it only processes data pr
oduced by HTK.
>
> Therefore, may this client software and decoding SERVICE be sold commercially
(as long as we agree to license sections 2.4 and 2.5)?
>
> Thank you
> Georg Schlunz
>
-- ** Cantab is hiring: www.cantabResearch.com/openings ** -Dr A J Robinson, Founder, Cantab Research Ltd
Phone direct: 01223 778240 office: 01223 794497
Company reg no GB 05697423, VAT reg no 925606030
51 Canterbury Street, Cambridge, CB4 3QG, UK
From tonyr at cantabResearch.com Tue Nov 4 20:04:46 2014
From: tonyr at cantabResearch.com (Tony Robinson)
Date: Wed Apr 22 05:32:49 2015
Subject: [HTK-Users] HTK license agreement
In-Reply-To: <545241EC02000049000E3077@pta-emo.csir.co.za>
References: <545241EC02000049000E3077@pta-emo.csir.co.za>
Message-ID: <5459315E.9030409@cantabResearch.com>

I just saw this post - I hope I haven't also missed any replies.
It's been a while since I read the HTK licence, but from memory and past
commercial practices I believe that what you are proposing is entirely
acceptable according to the HTK licence.
In fact I think www.speechmatics.com uses HVite in exactly this way to
do some final tidying up of the large vocabulary speech recognition output.
Tony
On 30/10/14 11:49, Georg Schlunz wrote:
> Good day
>
> Regarding the HTK license, as specified at http://htk.eng.cam.ac.uk/docs/licen
se.shtml , I would like to know whether the following scenario is permitted:
>
> The HTK software (including HVite) sits on a server in-house in our organisati
on, as per license sections 2.1 and 2.3.
> The HTK software (including HVite) is never distributed to a commercial (or no
n-commercial) party, as per license section 2.2.
>
> We have written our own server-client software, where:
> a) the client records speech and sends the audio file to the server, which pas
ses it on to HVite (the server software and HTK sit on the same in-house machine
)
> b) HVite decodes the audio into text
> c) the server replies to the client with the decoded text and the client proce
sses the text somehow
>
> Naturally, the client software contains no HTK code; it only processes data pr
oduced by HTK.
>
> Therefore, may this client software and decoding SERVICE be sold commercially
(as long as we agree to license sections 2.4 and 2.5)?
>
> Thank you
> Georg Schlunz
>
-- ** Cantab is hiring: www.cantabResearch.com/openings ** -Dr A J Robinson, Founder, Cantab Research Ltd
Phone direct: 01223 778240 office: 01223 794497
Company reg no GB 05697423, VAT reg no 925606030
51 Canterbury Street, Cambridge, CB4 3QG, UK
From tonyr at cantabResearch.com Tue Nov 4 20:04:46 2014
From: tonyr at cantabResearch.com (Tony Robinson)
Date: Thu Apr 23 04:18:27 2015
Subject: [HTK-Users] HTK license agreement
In-Reply-To: <545241EC02000049000E3077@pta-emo.csir.co.za>
References: <545241EC02000049000E3077@pta-emo.csir.co.za>
Message-ID: <5459315E.9030409@cantabResearch.com>
I just saw this post - I hope I haven't also missed any replies.
It's been a while since I read the HTK licence, but from memory and past
commercial practices I believe that what you are proposing is entirely

acceptable according to the HTK licence.


In fact I think www.speechmatics.com uses HVite in exactly this way to
do some final tidying up of the large vocabulary speech recognition output.
Tony
On 30/10/14 11:49, Georg Schlunz wrote:
> Good day
>
> Regarding the HTK license, as specified at http://htk.eng.cam.ac.uk/docs/licen
se.shtml , I would like to know whether the following scenario is permitted:
>
> The HTK software (including HVite) sits on a server in-house in our organisati
on, as per license sections 2.1 and 2.3.
> The HTK software (including HVite) is never distributed to a commercial (or no
n-commercial) party, as per license section 2.2.
>
> We have written our own server-client software, where:
> a) the client records speech and sends the audio file to the server, which pas
ses it on to HVite (the server software and HTK sit on the same in-house machine
)
> b) HVite decodes the audio into text
> c) the server replies to the client with the decoded text and the client proce
sses the text somehow
>
> Naturally, the client software contains no HTK code; it only processes data pr
oduced by HTK.
>
> Therefore, may this client software and decoding SERVICE be sold commercially
(as long as we agree to license sections 2.4 and 2.5)?
>
> Thank you
> Georg Schlunz
>
-- ** Cantab is hiring: www.cantabResearch.com/openings ** -Dr A J Robinson, Founder, Cantab Research Ltd
Phone direct: 01223 778240 office: 01223 794497
Company reg no GB 05697423, VAT reg no 925606030
51 Canterbury Street, Cambridge, CB4 3QG, UK
From tonyr at cantabResearch.com Tue Nov 4 20:04:46 2014
From: tonyr at cantabResearch.com (Tony Robinson)
Date: Fri Apr 24 04:17:46 2015
Subject: [HTK-Users] HTK license agreement
In-Reply-To: <545241EC02000049000E3077@pta-emo.csir.co.za>
References: <545241EC02000049000E3077@pta-emo.csir.co.za>
Message-ID: <5459315E.9030409@cantabResearch.com>
I just saw this post - I hope I haven't also missed any replies.
It's been a while since I read the HTK licence, but from memory and past
commercial practices I believe that what you are proposing is entirely
acceptable according to the HTK licence.
In fact I think www.speechmatics.com uses HVite in exactly this way to
do some final tidying up of the large vocabulary speech recognition output.

Tony
On 30/10/14 11:49, Georg Schlunz wrote:
> Good day
>
> Regarding the HTK license, as specified at http://htk.eng.cam.ac.uk/docs/licen
se.shtml , I would like to know whether the following scenario is permitted:
>
> The HTK software (including HVite) sits on a server in-house in our organisati
on, as per license sections 2.1 and 2.3.
> The HTK software (including HVite) is never distributed to a commercial (or no
n-commercial) party, as per license section 2.2.
>
> We have written our own server-client software, where:
> a) the client records speech and sends the audio file to the server, which pas
ses it on to HVite (the server software and HTK sit on the same in-house machine
)
> b) HVite decodes the audio into text
> c) the server replies to the client with the decoded text and the client proce
sses the text somehow
>
> Naturally, the client software contains no HTK code; it only processes data pr
oduced by HTK.
>
> Therefore, may this client software and decoding SERVICE be sold commercially
(as long as we agree to license sections 2.4 and 2.5)?
>
> Thank you
> Georg Schlunz
>
-- ** Cantab is hiring: www.cantabResearch.com/openings ** -Dr A J Robinson, Founder, Cantab Research Ltd
Phone direct: 01223 778240 office: 01223 794497
Company reg no GB 05697423, VAT reg no 925606030
51 Canterbury Street, Cambridge, CB4 3QG, UK
From tonyr at cantabResearch.com Tue Nov 4 20:04:46 2014
From: tonyr at cantabResearch.com (Tony Robinson)
Date: Sat Apr 25 04:25:11 2015
Subject: [HTK-Users] HTK license agreement
In-Reply-To: <545241EC02000049000E3077@pta-emo.csir.co.za>
References: <545241EC02000049000E3077@pta-emo.csir.co.za>
Message-ID: <5459315E.9030409@cantabResearch.com>
I just saw this post - I hope I haven't also missed any replies.
It's been a while since I read the HTK licence, but from memory and past
commercial practices I believe that what you are proposing is entirely
acceptable according to the HTK licence.
In fact I think www.speechmatics.com uses HVite in exactly this way to
do some final tidying up of the large vocabulary speech recognition output.
Tony
On 30/10/14 11:49, Georg Schlunz wrote:
> Good day

>
> Regarding the HTK license, as specified at http://htk.eng.cam.ac.uk/docs/licen
se.shtml , I would like to know whether the following scenario is permitted:
>
> The HTK software (including HVite) sits on a server in-house in our organisati
on, as per license sections 2.1 and 2.3.
> The HTK software (including HVite) is never distributed to a commercial (or no
n-commercial) party, as per license section 2.2.
>
> We have written our own server-client software, where:
> a) the client records speech and sends the audio file to the server, which pas
ses it on to HVite (the server software and HTK sit on the same in-house machine
)
> b) HVite decodes the audio into text
> c) the server replies to the client with the decoded text and the client proce
sses the text somehow
>
> Naturally, the client software contains no HTK code; it only processes data pr
oduced by HTK.
>
> Therefore, may this client software and decoding SERVICE be sold commercially
(as long as we agree to license sections 2.4 and 2.5)?
>
> Thank you
> Georg Schlunz
>
-- ** Cantab is hiring: www.cantabResearch.com/openings ** -Dr A J Robinson, Founder, Cantab Research Ltd
Phone direct: 01223 778240 office: 01223 794497
Company reg no GB 05697423, VAT reg no 925606030
51 Canterbury Street, Cambridge, CB4 3QG, UK
From tonyr at cantabResearch.com Tue Nov 4 20:04:46 2014
From: tonyr at cantabResearch.com (Tony Robinson)
Date: Sun Apr 26 04:14:24 2015
Subject: [HTK-Users] HTK license agreement
In-Reply-To: <545241EC02000049000E3077@pta-emo.csir.co.za>
References: <545241EC02000049000E3077@pta-emo.csir.co.za>
Message-ID: <5459315E.9030409@cantabResearch.com>
I just saw this post - I hope I haven't also missed any replies.
It's been a while since I read the HTK licence, but from memory and past
commercial practices I believe that what you are proposing is entirely
acceptable according to the HTK licence.
In fact I think www.speechmatics.com uses HVite in exactly this way to
do some final tidying up of the large vocabulary speech recognition output.
Tony
On 30/10/14 11:49, Georg Schlunz wrote:
> Good day
>
> Regarding the HTK license, as specified at http://htk.eng.cam.ac.uk/docs/licen
se.shtml , I would like to know whether the following scenario is permitted:
>
> The HTK software (including HVite) sits on a server in-house in our organisati

on, as per license sections 2.1 and 2.3.


> The HTK software (including HVite) is never distributed to a commercial (or no
n-commercial) party, as per license section 2.2.
>
> We have written our own server-client software, where:
> a) the client records speech and sends the audio file to the server, which pas
ses it on to HVite (the server software and HTK sit on the same in-house machine
)
> b) HVite decodes the audio into text
> c) the server replies to the client with the decoded text and the client proce
sses the text somehow
>
> Naturally, the client software contains no HTK code; it only processes data pr
oduced by HTK.
>
> Therefore, may this client software and decoding SERVICE be sold commercially
(as long as we agree to license sections 2.4 and 2.5)?
>
> Thank you
> Georg Schlunz
>
-- ** Cantab is hiring: www.cantabResearch.com/openings ** -Dr A J Robinson, Founder, Cantab Research Ltd
Phone direct: 01223 778240 office: 01223 794497
Company reg no GB 05697423, VAT reg no 925606030
51 Canterbury Street, Cambridge, CB4 3QG, UK
From tonyr at cantabResearch.com Tue Nov 4 20:04:46 2014
From: tonyr at cantabResearch.com (Tony Robinson)
Date: Mon Apr 27 04:09:47 2015
Subject: [HTK-Users] HTK license agreement
In-Reply-To: <545241EC02000049000E3077@pta-emo.csir.co.za>
References: <545241EC02000049000E3077@pta-emo.csir.co.za>
Message-ID: <5459315E.9030409@cantabResearch.com>
I just saw this post - I hope I haven't also missed any replies.
It's been a while since I read the HTK licence, but from memory and past
commercial practices I believe that what you are proposing is entirely
acceptable according to the HTK licence.
In fact I think www.speechmatics.com uses HVite in exactly this way to
do some final tidying up of the large vocabulary speech recognition output.
Tony
On 30/10/14 11:49, Georg Schlunz wrote:
> Good day
>
> Regarding the HTK license, as specified at http://htk.eng.cam.ac.uk/docs/licen
se.shtml , I would like to know whether the following scenario is permitted:
>
> The HTK software (including HVite) sits on a server in-house in our organisati
on, as per license sections 2.1 and 2.3.
> The HTK software (including HVite) is never distributed to a commercial (or no
n-commercial) party, as per license section 2.2.
>
> We have written our own server-client software, where:

> a) the client records speech and sends the audio file to the server, which pas
ses it on to HVite (the server software and HTK sit on the same in-house machine
)
> b) HVite decodes the audio into text
> c) the server replies to the client with the decoded text and the client proce
sses the text somehow
>
> Naturally, the client software contains no HTK code; it only processes data pr
oduced by HTK.
>
> Therefore, may this client software and decoding SERVICE be sold commercially
(as long as we agree to license sections 2.4 and 2.5)?
>
> Thank you
> Georg Schlunz
>
-- ** Cantab is hiring: www.cantabResearch.com/openings ** -Dr A J Robinson, Founder, Cantab Research Ltd
Phone direct: 01223 778240 office: 01223 794497
Company reg no GB 05697423, VAT reg no 925606030
51 Canterbury Street, Cambridge, CB4 3QG, UK
From tonyr at cantabResearch.com Tue Nov 4 20:04:46 2014
From: tonyr at cantabResearch.com (Tony Robinson)
Date: Tue Apr 28 04:12:11 2015
Subject: [HTK-Users] HTK license agreement
In-Reply-To: <545241EC02000049000E3077@pta-emo.csir.co.za>
References: <545241EC02000049000E3077@pta-emo.csir.co.za>
Message-ID: <5459315E.9030409@cantabResearch.com>
I just saw this post - I hope I haven't also missed any replies.
It's been a while since I read the HTK licence, but from memory and past
commercial practices I believe that what you are proposing is entirely
acceptable according to the HTK licence.
In fact I think www.speechmatics.com uses HVite in exactly this way to
do some final tidying up of the large vocabulary speech recognition output.
Tony
On 30/10/14 11:49, Georg Schlunz wrote:
> Good day
>
> Regarding the HTK license, as specified at http://htk.eng.cam.ac.uk/docs/licen
se.shtml , I would like to know whether the following scenario is permitted:
>
> The HTK software (including HVite) sits on a server in-house in our organisati
on, as per license sections 2.1 and 2.3.
> The HTK software (including HVite) is never distributed to a commercial (or no
n-commercial) party, as per license section 2.2.
>
> We have written our own server-client software, where:
> a) the client records speech and sends the audio file to the server, which pas
ses it on to HVite (the server software and HTK sit on the same in-house machine
)
> b) HVite decodes the audio into text
> c) the server replies to the client with the decoded text and the client proce

sses the text somehow


>
> Naturally, the client software contains no HTK code; it only processes data pr
oduced by HTK.
>
> Therefore, may this client software and decoding SERVICE be sold commercially
(as long as we agree to license sections 2.4 and 2.5)?
>
> Thank you
> Georg Schlunz
>
-- ** Cantab is hiring: www.cantabResearch.com/openings ** -Dr A J Robinson, Founder, Cantab Research Ltd
Phone direct: 01223 778240 office: 01223 794497
Company reg no GB 05697423, VAT reg no 925606030
51 Canterbury Street, Cambridge, CB4 3QG, UK
From tonyr at cantabResearch.com Tue Nov 4 20:04:46 2014
From: tonyr at cantabResearch.com (Tony Robinson)
Date: Wed Apr 29 04:14:46 2015
Subject: [HTK-Users] HTK license agreement
In-Reply-To: <545241EC02000049000E3077@pta-emo.csir.co.za>
References: <545241EC02000049000E3077@pta-emo.csir.co.za>
Message-ID: <5459315E.9030409@cantabResearch.com>
I just saw this post - I hope I haven't also missed any replies.
It's been a while since I read the HTK licence, but from memory and past
commercial practices I believe that what you are proposing is entirely
acceptable according to the HTK licence.
In fact I think www.speechmatics.com uses HVite in exactly this way to
do some final tidying up of the large vocabulary speech recognition output.
Tony
On 30/10/14 11:49, Georg Schlunz wrote:
> Good day
>
> Regarding the HTK license, as specified at http://htk.eng.cam.ac.uk/docs/licen
se.shtml , I would like to know whether the following scenario is permitted:
>
> The HTK software (including HVite) sits on a server in-house in our organisati
on, as per license sections 2.1 and 2.3.
> The HTK software (including HVite) is never distributed to a commercial (or no
n-commercial) party, as per license section 2.2.
>
> We have written our own server-client software, where:
> a) the client records speech and sends the audio file to the server, which pas
ses it on to HVite (the server software and HTK sit on the same in-house machine
)
> b) HVite decodes the audio into text
> c) the server replies to the client with the decoded text and the client proce
sses the text somehow
>
> Naturally, the client software contains no HTK code; it only processes data pr
oduced by HTK.
>

> Therefore, may this client software and decoding SERVICE be sold commercially
(as long as we agree to license sections 2.4 and 2.5)?
>
> Thank you
> Georg Schlunz
>
-- ** Cantab is hiring: www.cantabResearch.com/openings ** -Dr A J Robinson, Founder, Cantab Research Ltd
Phone direct: 01223 778240 office: 01223 794497
Company reg no GB 05697423, VAT reg no 925606030
51 Canterbury Street, Cambridge, CB4 3QG, UK
From tonyr at cantabResearch.com Tue Nov 4 20:04:46 2014
From: tonyr at cantabResearch.com (Tony Robinson)
Date: Thu Apr 30 04:11:29 2015
Subject: [HTK-Users] HTK license agreement
In-Reply-To: <545241EC02000049000E3077@pta-emo.csir.co.za>
References: <545241EC02000049000E3077@pta-emo.csir.co.za>
Message-ID: <5459315E.9030409@cantabResearch.com>
I just saw this post - I hope I haven't also missed any replies.
It's been a while since I read the HTK licence, but from memory and past
commercial practices I believe that what you are proposing is entirely
acceptable according to the HTK licence.
In fact I think www.speechmatics.com uses HVite in exactly this way to
do some final tidying up of the large vocabulary speech recognition output.
Tony
On 30/10/14 11:49, Georg Schlunz wrote:
> Good day
>
> Regarding the HTK license, as specified at http://htk.eng.cam.ac.uk/docs/licen
se.shtml , I would like to know whether the following scenario is permitted:
>
> The HTK software (including HVite) sits on a server in-house in our organisati
on, as per license sections 2.1 and 2.3.
> The HTK software (including HVite) is never distributed to a commercial (or no
n-commercial) party, as per license section 2.2.
>
> We have written our own server-client software, where:
> a) the client records speech and sends the audio file to the server, which pas
ses it on to HVite (the server software and HTK sit on the same in-house machine
)
> b) HVite decodes the audio into text
> c) the server replies to the client with the decoded text and the client proce
sses the text somehow
>
> Naturally, the client software contains no HTK code; it only processes data pr
oduced by HTK.
>
> Therefore, may this client software and decoding SERVICE be sold commercially
(as long as we agree to license sections 2.4 and 2.5)?
>
> Thank you
> Georg Schlunz

>
-- ** Cantab is hiring: www.cantabResearch.com/openings ** -Dr A J Robinson, Founder, Cantab Research Ltd
Phone direct: 01223 778240 office: 01223 794497
Company reg no GB 05697423, VAT reg no 925606030
51 Canterbury Street, Cambridge, CB4 3QG, UK
From tonyr at cantabResearch.com Tue Nov 4 20:04:46 2014
From: tonyr at cantabResearch.com (Tony Robinson)
Date: Fri May 1 04:11:31 2015
Subject: [HTK-Users] HTK license agreement
In-Reply-To: <545241EC02000049000E3077@pta-emo.csir.co.za>
References: <545241EC02000049000E3077@pta-emo.csir.co.za>
Message-ID: <5459315E.9030409@cantabResearch.com>
I just saw this post - I hope I haven't also missed any replies.
It's been a while since I read the HTK licence, but from memory and past
commercial practices I believe that what you are proposing is entirely
acceptable according to the HTK licence.
In fact I think www.speechmatics.com uses HVite in exactly this way to
do some final tidying up of the large vocabulary speech recognition output.
Tony
On 30/10/14 11:49, Georg Schlunz wrote:
> Good day
>
> Regarding the HTK license, as specified at http://htk.eng.cam.ac.uk/docs/licen
se.shtml , I would like to know whether the following scenario is permitted:
>
> The HTK software (including HVite) sits on a server in-house in our organisati
on, as per license sections 2.1 and 2.3.
> The HTK software (including HVite) is never distributed to a commercial (or no
n-commercial) party, as per license section 2.2.
>
> We have written our own server-client software, where:
> a) the client records speech and sends the audio file to the server, which pas
ses it on to HVite (the server software and HTK sit on the same in-house machine
)
> b) HVite decodes the audio into text
> c) the server replies to the client with the decoded text and the client proce
sses the text somehow
>
> Naturally, the client software contains no HTK code; it only processes data pr
oduced by HTK.
>
> Therefore, may this client software and decoding SERVICE be sold commercially
(as long as we agree to license sections 2.4 and 2.5)?
>
> Thank you
> Georg Schlunz
>
-- ** Cantab is hiring: www.cantabResearch.com/openings ** -Dr A J Robinson, Founder, Cantab Research Ltd
Phone direct: 01223 778240 office: 01223 794497

Company reg no GB 05697423, VAT reg no 925606030


51 Canterbury Street, Cambridge, CB4 3QG, UK

Vous aimerez peut-être aussi