<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">Hi!<div class=""><br class=""></div><div class="">I’ve added a few comments inline below:</div><div class=""><br class=""><div><div class="">28. mars 2017 kl. 11.52 skrev Henri Sivonen <<a href="mailto:hsivonen@hsivonen.fi" class="">hsivonen@hsivonen.fi</a>>:</div><blockquote type="cite" class=""><div class=""><div class="">Have I understood the following correctly?<br class=""></div></div></blockquote>[...]<br class=""><blockquote type="cite" class=""><div class=""><div class="">* libvoikko-compatible dictionaries that are on the readiness level<br class="">that they could quality-wise be exposed to end-users exist for<br class="">Finnish, Greenlandic, North Sami and Kven.<br class="">(<a href="http://divvun.no/libreofficeoxt.html" class="">http://divvun.no/libreofficeoxt.html</a> and<br class=""><a href="http://divvun.org/proofing/otherapps.html" class="">http://divvun.org/proofing/otherapps.html</a> )<br class=""> </div></div></blockquote><div><br class=""></div><div>Also South and Lule Sami are on that level, Kven is not (yet). Skolt and Inari Sami is on a alpha quality / early beta quality level. All of Kven, Inari Sami and Skolt Sami are provided as an early-release service to the language communities, and it should always be communicated clearly that these spellers are lacking coverage in several areas (compounds, missing words, derivation, etc). Both we and the language communities still see them as valuable in their present shape, and that is why they are shipped.</div><br class=""><blockquote type="cite" class=""><div class=""><div class="">* The licensing situation for the Greenlandic, North Sami and Kven<br class="">dictionaries is unclear.<br class="">(<a href="https://victorio.uit.no/langtech/trunk/langs/kal/LICENCE" class="">https://victorio.uit.no/langtech/trunk/langs/kal/LICENCE</a>)<br class=""> </div></div></blockquote><div><br class=""></div><div>(please use the url <a href="http://gtsvn.uit.no" class="">gtsvn.uit.no</a> going forward, <a href="http://victorio.uit.no" class="">victorio.uit.no</a> is just an alias for backwards compatibility, and may cease to resolve in the future.)</div><div><br class=""></div><div>Yes, you are right, thanks for pointing this out. I will take action to resolve the issue.</div><br class=""><blockquote type="cite" class=""><div class=""><div class="">* There are dictionaries for 48 other language in development, also<br class="">under unclear licensing status.<br class="">(<a href="https://victorio.uit.no/langtech/trunk/langs/" class="">https://victorio.uit.no/langtech/trunk/langs/</a>)<br class=""></div></div></blockquote><div><br class=""></div><div>I will try to resolve the licensing situation for the most actively worked-on languages.</div></div><br class=""></div><div class="">General comment & question:</div><div class=""><br class=""></div><div class="">All of these languages depend on the hfst-ospell library for run-time use, and in general on hfst to be built from source. Have all issues related to hfst and libvoikko been resolved now, or are there still open issues?</div><div class=""><br class=""></div><div class="">Regards,</div><div class="">Sjur</div></body></html>