| 1 |
The database for this English-Hindi dictionary is taken from the Anusaaraka |
| 2 |
project, English-Hindi dictionary V2.0, see |
| 3 |
http://www.iiit.net/ltrc/Dictionaries/Dict_Downld.html and is in GPL as it was. |
| 4 |
It has more than 25 600 headwords and low quality. |
| 5 |
|
| 6 |
As that text file was made by school children and non-IT professionals, it was |
| 7 |
in a very bad shape. The file looked OK in an editor, but not to a parser, |
| 8 |
because there were spaces where they shouldn't be and many other format |
| 9 |
exceptions. So only after some manual editing of that file, the parser has |
| 10 |
accepted it. Those differences are in the .diff file. |
| 11 |
|
| 12 |
The file in this package has the diff already applied. |
| 13 |
|
| 14 |
ehconv.yy is a parser. It is compiled with flex and will convert the text |
| 15 |
database file, which is encoded in ISCII into a TEI P4 XML file, encoded in |
| 16 |
UTF-8, see http://www.tei-c.org/ and http://unicode.org/. For more information |
| 17 |
about ISCII, see http://tdil.mit.gov.in/standards.htm and |
| 18 |
http://www.cwi.nl/~dik/english/codes/indic.html (beware, the tables use octal |
| 19 |
codes!). |
| 20 |
|
| 21 |
The final step of converting the .tei file into .dict format can be done using |
| 22 |
xmltei2xmldict.pl. |
| 23 |
|
| 24 |
Now take your Unicode compatible dict server and client and enjoy the nice |
| 25 |
Devanagari! (When you use a web interface, Internet Explorer >5 can be used. |
| 26 |
Otherwise gnome-dictionary can render Devanagari.) |
| 27 |
|
| 28 |
As the Anusaaraka project aimed at machine aided translation between many |
| 29 |
Indian languages, there are several other dictionaries available at |
| 30 |
http://www.iiit.net/ltrc/Dictionaries/Dict_Frame.html. BTW, the dict here is |
| 31 |
_not_ the Shabdanjali English-Hindi dictionary! Also, for each dictionary there |
| 32 |
is further information at the IIIT server. |
| 33 |
|
| 34 |
With a 'make reverse' you can generate a reverse index for querying the |
| 35 |
dictionary in Hindi. When converting TEI into dictd database format, the |
| 36 |
converter might complain about "whitespace only headwords". These are cases |
| 37 |
where the Hindi translation of a word is not included in the dictionary. In the |
| 38 |
XML they look like "<tr>?</tr>". The question mark is removed because it is |
| 39 |
punctuation. Empty headwords are left out of the index. |
| 40 |
|
| 41 |
The Part-Of-Speech (<pos>) element contents don't follow the typology outlined |
| 42 |
in the FreeDict HOWTO. Try `make pos-statistics' to see what is used. |
| 43 |
|
| 44 |
There is much scope for future work :) |
| 45 |
|
| 46 |
Michael |
| 47 |
|
| 48 |
If your dict client/browser don't support Devanagari rendering, |
| 49 |
you could translate everything into roman encoding: |
| 50 |
uniconv -encode IS_DV -in eng-hin.tei | uniconv -decode IS_RM >eng-hin.roman.tei |
| 51 |
(uniconv is part of the great yudit package). But there is |
| 52 |
one thing not working: uniconv cannot count syllables and so |
| 53 |
creates an 'a' too much sometimes in the transliteration :( |
| 54 |
(also, ISCII code e5 becomes "o with a bar on top" |
| 55 |
as well as code e1 becomes "e ..." -> We substitute simple "o" and "e" for them) |
| 56 |
|
| 57 |
================================================= |
| 58 |
|
| 59 |
The TEI P4 version of this database was created by |
| 60 |
FreeDict tools on the basis of the accompanying |
| 61 |
non-XML source file(s). Next, that TEI P4 version |
| 62 |
was converted to TEI P5 using revision 978 of the |
| 63 |
tools/xsl/freedict_P4toP5.xsl script. |
| 64 |
|
| 65 |
In some cases I checked whether a newer version |
| 66 |
of the database existed but I wasn't lucky. |
| 67 |
Still, any maintenance of this dictionary should |
| 68 |
begin by checking on the existence of an updated version. |
| 69 |
|
| 70 |
Piotr BaĆski, 3 November 2010 |