<div dir="ltr"><div class="gmail_quote">2010/11/2 Nadav Har'El <span dir="ltr"><<a href="mailto:nyh@math.technion.ac.il">nyh@math.technion.ac.il</a>></span><br><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
Recently I noticed that (thanks to Lior Kaplan, it seems) it is now trivial<br>
to get Hebrew spellchecking (based on Hspell 1.1) in OpenOffice.<br>
The Hebrew localized version (now available on the official OpenOffice site!)<br>
comes with Hebrew spell-checking pre-bundled, and there's an extension [1]<br>
for those who use the English version of open-office.<br></blockquote><div><br>My pleasure (:<br><br>It's available only as the 3.3 RC releases, and will be available on the final release. <br><a href="http://download.openoffice.org/all_rc.html">http://download.openoffice.org/all_rc.html</a><br>
<br></div><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
The first issue is acronyms (rashei tevot) and abbreviations. In Hebrew,<br>
these use the geresh and gershaim (or single or double quotes), which is<br>
part of the word. OpenOffice does not understand that these quotes are part<br>
of the Hebrew word, and splits the word on them. As a result all acronyms are<br>
marked as spelling mistakes. This is really annoying, especially for certain<br>
types of documents where acronyms are common.<br></blockquote><div><br>Known issue, and reported at<br><a href="http://www.openoffice.org/issues/show_bug.cgi?id=99796">http://www.openoffice.org/issues/show_bug.cgi?id=99796</a><br>
<br>It is marked for work during the 3.4 release.<br> <br></div><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
The second issue is the correction suggestions for spelling errors. All<br>
the suggestions indeed appear to be valid words, but their order is<br>
terrible - it appears little or no attention was paid to trying to provide<br>
the most likely suggestions first. The screenshot on the extension page [1]<br>
provides an excellent example: When given the mis-spelling עיברי, rather than<br>
provide the most likely suggestion first - עברי, it is given as the 8th<br>
suggestion, and the first suggestions are highly unlikely. <br></blockquote><div>[..] <br></div><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
I believe that hunspell's dictionary in fact has a way to give such correction<br>
rules, but I don't know how to correctly write them, or how to make OpenOffice<br>
use them.<br></blockquote></div><br>The word list in the extension is created with myspell's format. Hunspell should be similar but I couldn't build that format at the time. The builds were done as part of the debian hspell package which I maintain.<br>
</div>