moved kdeaccessibility kdeaddons kdeadmin kdeartwork kdebindings kdeedu kdegames...
[kdeedu.git] / kiten / edict_doc.html
blobfc52d1e4da9c4f4f86cd699514b9b09d18612f15
1 <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
2 <HTML>
3 <HEAD>
4 <META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
5 <META NAME="Generator" CONTENT="Jim's Markup Program - V0.99">
6 <TITLE>EDICT Documentation</TITLE>
7 </HEAD>
8 <BODY BGCOLOR="white">
9 <!-- DO NOT EDIT!!
10 This HTML document was generated by the "markup" program.
11 Edit the original file instead. -->
12 <H1 ALIGN=CENTER> E D I C T </H1>
13 <P>
14 </P>
15 <H2 ALIGN=CENTER> JAPANESE/ENGLISH DICTIONARY FILE</H2>
16 <BASEFONT SIZE="3">
17 <P>
18 <I>Copyright (C) 2003 The Electronic Dictionary Research and Development Group,</I>
19 <I>Monash University.</I>
20 </P>
21 <P>
22 Contents:
23 </P>
24 <UL>
25 <li><a href="#IREF00">INTRODUCTION</a>
26 <li><a href="#IREF01">CURRENT VERSION </a>
27 <li><a href="#IREF02">FORMAT</a>
28 <li><a href="#IREF03">EDICT HISTORY</a>
29 <li><a href="#IREF04">COPYRIGHT ISSUES</a>
30 <li><a href="#IREF05">LEXICOGRAPHICAL DETAILS</a>
31 <li><a href="#IREF06">NEW JMDICT PROJECT</a>
32 <li><a href="#IREF07">USAGE</a>
33 <li><a href="#IREF08">CONTRIBUTIONS</a>
34 <li><a href="#IREF09">ACKNOWLEDGEMENTS</a>
35 <li><a href="#IREF10">APPENDIX A: EDICT LICENCE STATEMENT</a>
36 <li><a href="#IREF11">APPENDIX B. LANGUAGE CODES FROM ISO 639</a>
37 </UL>
38 <P>
39 <b><a name="IREF00">INTRODUCTION</a></b>
40 </P>
41 <P>
42 The EDICT file results from a long-running project to produce a freely
43 available Japanese/English Dictionary in machine-readable form.
44 </P>
45 <P>
46 The EDICT file is copyright, and is distributed in accordance with the
47 Licence Statement, which can found at the WWW site of the
48 <a HREF="http://www.csse.monash.edu.au/groups/edrdg/">Electronic Dictionary Research and Development Group </a>
49 who are the owners of the copyright.
50 </P>
51 <P>
52 <b><a name="IREF01">CURRENT VERSION </a></b>
53 </P>
54 <P>
55 The version date and sequence number is included in the dictionary itself
56 under the entry "EDICT". (Actually it is under the JIS-ASCII code "????".
57 This keeps it as the first entry when it is sorted.)
58 </P>
59 <P>
60 The master copy of EDICT is in the pub/nihongo directory of
61 <TT> ftp.cc.monash.edu.au. </TT>
62 There are other copies around, but they may not be
63 as up-to-date. The easy way to check if the version you have is the latest is
64 from the size/date.
65 </P>
66 <P>
67 As of V96-001, the EDICT file no longer contains proper names. These have
68 been moved to a separate file called "ENAMDICT".
69 From V99-002, the EDICT file has been generated from an extended dictionary
70 database which includes additional fields and information. See the later
71 section on the new JMdict project for details of this.
72 </P>
73 <P>
74 <b><a name="IREF02">FORMAT</a></b>
75 </P>
76 <P>
77 EDICT's format is that of the original "EDICT" format used by the early
78 PC Japanese word-processor MOKE (Mark's Own Kanji Editor).
79 It uses EUC-JP coding for kana and kanji, however this can be converted to
80 JIS (ISO-2022-JP) or Shift-JIS
81 by any of the several conversion programs around. It is a text file with one
82 entry per line. The format of entries is:
83 </P>
84 <P>
85 </P>
86 <PRE>
87 KANJI [KANA] /English_1/English_2/.../
88 </PRE>
89 <P>
91 </P>
92 <P>
93 </P>
94 <PRE>
95 KANA /English_1/.../
96 </PRE>
97 <P>
98 (NB: Only the KANJI and KANA are in EUC; all the other characters, including
99 spaces, must be ASCII.)
100 </P>
102 The English translations are deliberately brief, as the application of the
103 dictionary is expected to be primarily on-line look-ups, etc.
104 </P>
106 The EDICT file is not intended to have its entries in any particular order.
107 In fact it almost always is in order as a by-product of the update method I
108 use, however there is no guarantee of this. (The order is almost always JIS
109 + alphabetical, starting with the head-word.)
110 </P>
112 <b><a name="IREF03">EDICT HISTORY</a></b>
113 </P>
115 EDICT has developed as follows:
116 </P>
117 <OL type="a">
118 <LI>
119 it began with the basic EDICT distributed with MOKE 2.0. This was compiled by MOKE's
120 author, Mark Edwards, with assistance from Spencer Green. Mark
121 kindly released this material to the EDICT project. A number of corrections
122 were made to the MOKE original, e.g. spelling mistakes, minor
123 mistranslations, etc. It also had a lot of duplications, which have been
124 removed. It contained about 1900 unique entries. Mark Edwards has also
125 kindly given permission for the vocabulary files developed for KG (Kanji
126 Guess) to be added to EDICT.
127 </LI>
128 <LI>
129 additions by Jim Breen. I laboriously keyed in a ~2000 entry dictionary
130 used in my first year nihongo course at Swinburne Institute of Technology
131 years ago (I was given permission by the authors to do this). I then worked
132 through other vocabulary lists trying to make sure major entries were not
133 omitted. The English-to-kana entries in the SKK files were added also. This
134 task is continuing, although it has slowed down, and I suspect I will run out
135 of energy eventually. Apart from that, I have made a large number of
136 additions during normal reading of Japanese text and fj.* news using JREADER
137 and XJDIC. (As of November 2001 I am still adding entries.)
139 </P>
140 </LI>
141 <LI>
142 additions by others. Many people have contributed entries and
143 corrections to EDICT. I am forever on the lookout for sources of material,
144 provided it is genuinely available for use in the Project. I am
145 grateful to Theresa Martin who an early supplier a lot of useful material,
146 plus very perceptive corrections. Hidekazu Tozaki has also been a great help
147 with tidying up a lot of awry entries, and helping me identify obscure kanji
148 compounds. Kurt Stueber has been an assiduous keyer of many useful entries.
149 A large group of contributions came from Sony, where Rik Smoody had put
150 together a large online dictionary. Another batch came from the
151 Japanese-German JDDICT file in similar format that Helmut Goldenstein keyed
152 (with permission) from the Langenscheidt edited by Hadamitzky. Harold Rowe
153 was great help with much of the translation. During 1994, Dr Yo Tomita, then
154 at the University of Leeds, conducted a massive proof-reading of the entire
155 file, for which I am most grateful. Jeffrey Friedl at Omron in Kyoto has also
156 been a most helpful contributor and error-detector. During 1995, I have been
157 keeping an eye on the "honyaku" mailing list, wherein Japanese-English
158 translators discuss thorny issues. From this I have derived many new entries,
159 and many updates to existing entries. To the many honyakujin, my thanks.
160 </LI>
161 </OL>
162 A reasonably full list of contributors is at the back of this file,
163 although I am sure to have missed a few.
165 At this stage EDICT has many more entries than many good commercial dictionaries,
166 which typically have 20,000+ non-name entries with examples, etc. It is
167 certainly bigger than some of the smaller printed dictionaries, and when used
168 in conjunction with a search-and-display program like JDIC or XJDIC it
169 provides a highly effective on-line dictionary service.
170 </P>
172 <b><a name="IREF04">COPYRIGHT ISSUES</a></b>
173 </P>
175 Dictionary copyright is a difficult point, because clearly the first
176 lexicographer who published "inu means dog" could not claim a copyright
177 violation over all subsequent Japanese dictionaries. While it is usual to
178 consult other dictionaries for "accurate lexicographic information", as
179 Nelson put it, wholesale copying is, of course, not permissible. What makes
180 each dictionary unique (and copyrightable) is the particular selection of
181 words, the phrasing of the meanings, the presentation of the contents (a very
182 important point in the case of EDICT), and the means of publication. Of
183 course, the fact that for the most part the kanji and kana of each entry are
184 coming from public sources, and the structure and layout of the entries
185 themselves are quite unlike those in any published dictionary, adds a degree
186 of protection to EDICT.
187 </P>
189 The advice I have received from people who know about these things is that
190 EDICT is just as much a new dictionary as any others on the market. Readers
191 may see an entry which looks familiar, and say "Aha! That comes from the XYZ
192 Jiten!". They may be right, and they may be wrong. After all there aren't
193 too many translations of neko. Let me make one thing quite clear, despite
194 considerable temptation (Electronic Books can be easily decoded), NONE of
195 this dictionary came from commercial machine-readable dictionaries. I have a
196 case of RSI in my right elbow to prove it.
197 </P>
199 Please do not contribute entries to EDICT which have come directly from
200 copyrightable sources. It is hard to check these, and you may be
201 jeopardizing EDICT's status.
202 </P>
204 <b><a name="IREF05">LEXICOGRAPHICAL DETAILS</a></b>
205 </P>
207 <B>Introduction</B>
208 </P>
210 EDICT is actually a Japanese->English dictionary, although the words within
211 it can be selected in either language using appropriate software. (JDIC uses
212 it to provide both E->J and J->E functionality.)
213 </P>
215 The early stages of EDICT had size limitations due to its usage (MOKE scans
216 it sequentially and JDXGEN, which is JDIC's index generator, held it in RAM.)
217 This meant that examples of usage could not be included, and inclusion of
218 phrases was very limited. JDIC/JDXGEN can now handle a much larger
219 dictionary, but the compact format has continued.
220 </P>
222 No inflections of verbs or adjectives have been included, except in idiomatic
223 expressions. Similarly particles are handled as separate entries. Adverbs
224 formed from adjectives (-ku or ni) are generally not included. Verbs are, of
225 course, in the plain or "dictionary" form.
226 </P>
228 <B>Priority Entries</B>
229 </P>
231 Starting with the 2001 editions, approximately 20,000 entries comprising the most commonly-used words in Japanese are marked
232 with a "(P)" at the end of the entry. This list has been identified by
233 examining several small
234 dictionaries, and lists of common gairaigo from Japanese newspapers.
235 </P>
237 <B>Parts of Speech</B>
238 </P>
240 In working on EDICT, bearing in mind I want to use it in MOKE and with JDIC,
241 I had to come up with a solution to the problem of adjectival nouns
242 [keiyoudoushi] (e.g. kirei and kantan), nouns which can be used adjectivally
243 with the particle "no" and verbs formed by adding suru (e.g. benkyousuru).
244 If I put entries in EDICT with the "na" and "suru" included, MOKE would not
245 find a match when they are omitted or, the case of suru, inflected. What I
246 decided to do is to put the basic noun into the dictionary and add
247 "(vs)" where it can be used to form a verb with suru, "(a-no)" for common
248 "no" usage, and "(an)" if it is an adjectival noun. Entries appeared as:
249 </P>
251 </P>
252 <PRE>
253 KANJI [benkyou] /study (vs)/
254 KANJI [kantan] /simple (an)/
255 </PRE>
257 In early 2001, as part of the JMdict project (see below), I completely revised
258 this system, instead introducing a comprehensive system of Part of Speech
259 (POS) tags. In the EDICT version of the file these tags usually appear in
260 parentheses
261 at the start of the entry, separated into general tags and POS tags. Where
262 a tag applies to a single gloss or meaning, it will be included there instead.
263 </P>
265 The (hopefully) full list of such markers is:
266 </P>
268 </P>
269 <PRE>
270 abbr abbreviation
271 adj adjective (keiyoushi)
272 adv adverb (fukushi)
273 adv-n adverbial noun
274 adj-na adjectival nouns or quasi-adjectives (keiyodoshi)
275 adj-no nouns which may take the genitive case particle "no"
276 adj-pn pre-noun adjectival (rentaishi)
277 adj-s special adjective (e.g. ookii)
278 adj-t "taru" adjective
279 arch archaism
280 ateji ateji reading of the kanji
281 aux auxiliary word or phrase
282 aux-v auxiliary verb
283 conj conjunction
284 col colloquialism
285 exp Expressions (phrases, clauses, etc.)
286 ek exclusively kanji, rarely just in kana
287 fam familiar language
288 fem female term or language
289 gikun gikun (meaning) reading
290 gram grammatical term
291 hon honorific or respectful (sonkeigo) language
292 hum humble (kenjougo) language
293 id idiomatic expression
294 int interjection (kandoushi)
295 iK word containing irregular kanji usage
296 ik word containing irregular kana usage
297 io irregular okurigana usage
298 MA martial arts term
299 male male term or language
300 m-sl manga slang
301 n noun (common) (futsuumeishi)
302 n-adv adverbial noun (fukushitekimeishi)
303 n-t noun (temporal) (jisoumeishi)
304 n-suf noun, used as a suffix
305 n-pref noun, used as a prefix
306 neg negative (in a negative sentence, or with negative verb)
307 neg-v negative verb (when used with)
308 num number, numeric
309 obs obsolete term
310 obsc obscure term
311 oK word containing out-dated kanji
312 ok out-dated or obsolete kana usage
313 pol polite (teineigo) language
314 pref prefix
315 prt particle
316 qv quod vide (see another entry)
317 sl slang
318 suf suffix
319 uK word usually written using kanji alone
320 uk word usually written using kana alone
321 v1 Ichidan verb
322 v5 Godan verb (not completely classified)
323 v5u Godan verb with `u' ending
324 v5u-s Godan verb with `u' ending - special class
325 v5k Godan verb with `ku' ending
326 v5g Godan verb with `gu' ending
327 v5s Godan verb with `su' ending
328 v5t Godan verb with `tsu' ending
329 v5n Godan verb with `nu' ending
330 v5b Godan verb with `bu' ending
331 v5m Godan verb with `mu' ending
332 v5r Godan verb with `ru' ending
333 v5k-s Godan verb - Iku/Yuku special class
334 v5z Godan verb - -zuru special class (alternative form of -jiru verbs)
335 v5aru Godan verb - -aru special class
336 v5uru Godan verb - Uru old class verb (old form of Eru)
337 vi intransitive verb
338 vs noun or participle which takes the aux. verb suru
339 vs-i suru verb - irregular
340 vs-s suru verb - special class
341 vk Kuru verb - special class
342 vt transitive verb
343 vulg vulgar expression or word
344 X rude or X-rated term (not displayed in educational software)
345 </PRE>
347 <B>Multiple Senses</B>
348 </P>
350 From the 2001 editions of EDICT, the differing senses associated with
351 the Japanese head-words are being progessively marked. The marking takes the
352 form of a "(1)", "(2)", etc. in front of the senses.
353 </P>
355 <B>Spellings</B>
356 </P>
358 I have endeavoured to cater for many possible variants of English translation
359 and spelling. Where appropriate different translations are included for
360 national variants (e.g. autumn/fall). I use Oxford (British) standard
361 spelling (-our, -ize) for the entries I make, but I leave other entries in
362 the national spelling of the submitter.
363 </P>
365 At some stage in the future I intend to regularize the English spellings in such
366 a way that allows searches on either British or American spellings
367 to be successful.
368 </P>
370 <B>Gairaigo and Regional Words</B>
371 </P>
373 For gairaigo which have not been derived from English words, I have attempted
374 to indicate the source language and the word in that language. Languages have
375 been coded in the two-letter codes from the ISO 639:1988 "Code for the
376 representation of names of languages" standard, e.g. "(fr: avec)". See
377 Appendix C for more on this. (Thanks to Holger Gruber for suggesting this
378 language coding.)
379 </P>
381 In addition to the language codes described in Appendix C, a number of tags
382 are used to indicate that a word or phrase is associated with a particular
383 regional language variant within Japan. The tags are:
384 </P>
386 </P>
387 <PRE>
388 kyb Kyoto-ben
389 osb Osaka-ben
390 ksb Kansai-ben
391 ktb Kantou-ben
392 tsb Tosa-ben
393 </PRE>
395 In the case of gairaigo which have a meaning which is not apparent from the
396 original (English) words, the literal transcription is included, with
397 the tag (lit).
398 </P>
400 <b><a name="IREF06">NEW JMDICT PROJECT</a></b>
401 </P>
403 Early in 1999 work began on the JMdict project, which aims to extend the
404 structure and content of the EDICT file to enable it to contain
405 additional information and provided an improved service to users.
406 </P>
408 The project has several broad goals:
409 </P>
410 <OL type="a">
411 <LI>to convert the EDICT file to a new dictionary structure which overcomes
412 the deficiencies in the current structure. With regard to this goal, the
413 particular structural and content aspects to be addressed include, but
414 are not limited to:
415 <OL type="i">
416 <LI>the handling of orthographical variation (e.g. in kanji
417 usage, okurigana usage, readings) within the single entry;
418 </LI>
419 <LI>additional and more appropriately associated tagging of
420 grammatical and other information;
421 </LI>
422 <LI>provision for separation of different senses (polysemy) in
423 the translations;
424 </LI>
425 <LI>provision for the inclusion of translational equivalents
426 from several languages;
427 </LI>
428 <LI>provision for inclusion of examples of the usage of words;
429 </LI>
430 <LI>provision for cross-references to related entries.
431 </LI>
432 </OL>
433 </LI>
434 <LI>to publish the dictionary in a standard format which is accessible
435 by a wide range of software tools; [It is proposed that this goal be
436 addressed by developing the structure so that it can be released as
437 an XML document, with an associated XML DTD.
438 </LI>
439 <LI>to retain backward compatibility with the original EDICT structure in
440 order to enable legacy software systems to use later versions of the
441 EDICT files.
442 </LI>
443 </OL>
444 For more information on the JMdict project, please see the documentation
445 files.
447 By May 1999 the EDICT file had been converted into the new format. A major
448 part of this consisted of identifying and combining entries which were
449 effectively variants of each other.
450 </P>
452 Since V99-002, the EDICT file has been generated from the new format.
453 This has meant:
454 </P>
455 <OL type="a">
456 <LI>a marginal increase in the number of entries, as there is an increased
457 number of variants;
458 </LI>
459 <LI>the English fields of the variant entries are now exactly the same,
460 as they have generated from the single expanded entry;
461 </LI>
462 <LI>the tags such as (vs), (an), etc. now appear before the first word
463 of the English fields.
464 </LI>
465 </OL>
466 <b><a name="IREF07">USAGE</a></b>
468 EDICT can be freely used provided satisfactory acknowledgement is made,
469 and a number of other conditions are met.
470 Consult the Licence Statement information at Appendix A.
471 </P>
473 It is, of course, the main dictionary used by PD and GPL Copyright software
474 such as JDIC, JREADER, XJDIC, MacJDic, etc. It can be used as the
475 dictionary within MOKE (it may need to be renamed JTOE.DCT if used with
476 version 2.1 of MOKE), and it is also used by the NJSTAR and JWP Word
477 Processor packages.
478 </P>
480 <b><a name="IREF08">CONTRIBUTIONS</a></b>
481 </P>
483 I will be delighted if people send me corrections, suggestions, and ESPECIALLY
484 additions. Before ripping in with a lot of suggestions, make sure you have the
485 latest version, as others may have already made the same comments.
486 </P>
488 The preferred format for submissions is a JIS, EUC or Shift-JIS file (uuencoded
489 for safety) containing replacement/new entries. This can be emailed to me at
490 the address at the end of this file.
491 </P>
493 Feel free to use the following format:
494 </P>
496 </P>
497 <PRE>
498 NEW: KANJI1 [kana1] /new entry #1/
500 NEW: KANJI2 [kana2] /new entry #2/
502 old: KANJI3 [kana3] /old entry to be replaced/
503 new: KANJI3 [kana3] /replacement entry/
505 DEL: KANJI4 [kana4] /entry to be deleted/
506 </PRE>
508 Please provide an annotated reason for any deletions or amendments you send.
509 </P>
511 I prefer not to get a "diff" or "patch" file as the master EDICT is under
512 continuous revision, and may have had quite a few changes since you got your
513 copy.
514 </P>
516 Users intending to make submissions to EDICT should follow the following
517 simple rules:
518 </P>
519 <UL>
520 <LI>all verbs in plain form. The English must begin with "to ....". Add the
521 verb type in some prominent place.
523 </P>
524 </LI>
525 <LI>add (adj-na) or (adj-no) or (vs) as appropriate to nouns. Do not put the "na" or
526 "no" particles on the Japanese, or the "suru" auxiliary verb. For entries
527 which have (vs), do not enter them as verb infinitives (e.g. "to cook"),
528 instead enter them as gerunds/participles/whatever (e.g. cooking (vs)).
530 </P>
531 </LI>
532 <LI>indicate prefixes and suffixes by "(pref)" and "(suf)" in the first English
533 entry, not by using "-" in the kanji or kana.
535 </P>
536 </LI>
537 <LI>do not add definite or indefinite articles (e.g. "a", "an", "the", etc) to
538 English nouns unless they are necessary to distinguish the word from
539 another usage type or homonym.
541 </P>
542 </LI>
543 <LI>do not guess the kanji or the reading. If you don't know them, don't
544 send it to me. I will check all incoming suggestions, and I get grumpy
545 when I find sloppy errors. One of the most persistent problems in editing
546 EDICT is finding and eliminating incorrect kanji and kana.
548 </P>
549 </LI>
550 <LI>do not use the "/", "[" or "]" characters except in their separating roles.
552 </P>
553 </LI>
554 <LI>if you are using a reference in romaji form, make sure you have the correct
555 kana for "too/tou" and "zu", where the Hepburn romaji is often ambiguous.
557 </P>
558 </LI>
559 <LI>do not use kana or kanji in the "English" fields. Where it is necessary to
560 use a Japanese word, e.g. kanto, use Hepburn romaji.
562 </P>
563 </LI>
564 <LI>make sure your kana is correct. A persistent problem is the submission of
565 words like "honyaku" as ho+nya+ku instead of the correct ho+n+ya+ku.
567 </P>
568 </LI>
569 <LI>do not include words formed by common Japanese suffixes, such as "-teki",
570 unless they cannot be deduced from the root.
571 </LI>
572 </UL>
574 <b><a name="IREF09">ACKNOWLEDGEMENTS</a></b>
575 </P>
577 The following people, in roughly chronological order, have played a part in
578 the development of EDICT. (I stopped adding to this list some years ago, so
579 it is of historical interest now.)
580 </P>
582 Mark Edwards, Spencer Green, Alina Skoutarides, Takako Machida, Theresa
583 Martin, Satoshi Tadokoro, Stephen Chung, Hidekazu Tozaki, Clifford Olling,
584 David Cooper, Ken Lunde, Joel Schulman, Hiroto Kagotani, Truett Smith, Mike
585 Rosenlof, Harold Rowe, Al Harkom, Per Hammarlund, Atsushi Fukumoto, John
586 Crossley, Bob Kerns, Frank O'Carroll, Rik Smoody, Scott Trent, Curtis
587 Eubanks, Jamie Packer, Hitoshi Doi, Thalawyn Silverwood, Makato Shimojima,
588 Bart Mathias, Koichi Mori, Steven Sprouse, Jeffrey Friedl, Yazuru Hiraga, Kurt
589 Stueber, Rafael Santos, Bruce Casner, Masato Toho, Carolyn Norton, Simon
590 Clippingdale, Shiino Masayoshi, Susumu Miki, Yushi Kaneda, Masahiko
591 Tachibana, Naoki Shibata, Yuzuru Hiraga, Yasuaki Nakano, Atsu Yagasaki,
592 Hitoshi Oi, Chizuko Kanazawa, Lars Huttar, Jonathan Hanna, Yoshimasa Tsuji,
593 Masatsugu Mamimura, Keiichi Nakata, Masako Nomura, Hiroshi Kamabe, Shi-Wen
594 Peng, Norihiro Okada, Jun-ichi Nakamura, Yoshiyuki Mizuno, Minoru Terada,
595 Itaru Ichikawa, Toru Matsuda, Katsumi Inoue, John Finlayson, David Luke, Iain
596 Sinclair, Warwick Hockley, Jamii Corley, Howard Landman, Tom Bryce, Jim
597 Thomas, Paul Burchard, Kenji Saito, Ken Eto, Niibe Yutaka, Hideyuki Ozaki,
598 Kouichi Suzuki, Sakaguchi Takeyuki, Haruo Furuhashi, Takashi Hattori,
599 Yoshiyuki Kondo, Kusakabe Youichi, Nobuo Sakiyama, Kouhei Matsuda, Toru Sato,
600 Takayuki Ito, Masayuki Tokoshima, Kiyo Inaba, Dan Cohn, Yo Tomita, Ed Hall,
601 Takashi Imamura, Bernard Greenberg, Michael Raine, Akiko Nagase, Ben Bullock,
602 Scott Draves, Matthew Haines, Andy Howells, Takayuki Ito, Anders Brabaek,
603 Michael Chachich, Masaki Muranaka, Paul Randolph, Vesa Karhu, Bruce Bailey,
604 Gal Shalif, Riichiro Saito, Keith Rogers, Steve Petersen, Bill Smith, Barry
605 Byrne, Satoshi Kuramoto, Jason Molenda, Travis Stewart, Yuichiro Kushiro
606 Keiko Okushi, Wayne Lammers, Koichi Fujino, Joerg Fischer, Satoru Miyazaki,
607 Gaspard Gendreau, David Olson, Peter Evans, Steven Zaveloff, Larry Tyrrell,
608 Heinz Clemencon, Justin Mayer, David Jones, Holger Gruber, David Wilson,
609 John De Hoog, Stephen Davis, Dan Crevier, Ron Granich, Bruce Raup, Scott
610 Childress, Richard Warmington, Jean-Jacques Labarthe, Matt Bloedel, Szabolcs
611 Varga, Alan Bram, Hidetaka Koie, David Villareale, Hirokazu Ohata, Toshiki
612 Sasabe, William Maton, Tom Salmon, Kian Yap, Paul Denisowski, Glen Pankow,
613 Richard Northcott, Roger Meunier, Petteri Kettunen, Jeff Korpa, Kanji
614 Haitani, Liam O'Brien, Serdar Yegulalp, Jonathan Way, Gururaj Rao, Yoichiro
615 Niitsu, Ralph Seewald, Andreas Jordell, Chua Hian Koon, Hartmut Pilch,
616 Shouichi Takeuchi, Ayumu Yasutomi, Mike Wright, James Rose, Nich Hill.
617 </P>
619 Jim Breen
620 <BR>
621 j<!-- blah -->wb@cs<!-- blah2 -->se.mon<!-- blah3 -->ash.edu.au
622 <BR>
623 School of Computer Science &amp; Software Engineering
624 <BR>
625 Monash University
626 <BR>
627 Clayton 3168
628 <BR>
629 AUSTRALIA
630 <hr>
631 <b><a name="IREF10">APPENDIX A: EDICT LICENCE STATEMENT</a></b>
632 </P>
634 In March 2000, James William Breen assigned ownership of the copyright
635 of the dictionary files assembled, coordinated and edited by him to the
636 The Electronic Dictionary Research and Development Group at Monash
637 University.
638 </P>
640 EDICT can be freely used provided satisfactory acknowledgement is made,
641 and a number of other conditions are met.
642 Information about the licence and copyright for EDICT can be found on
643 the Group's WWW page at: http://www.csse.monash.edu.au/groups/edrdg/
644 </P>
646 In summary, EDICT can be freely used with acknowledgement.
647 </P>
649 <hr>
650 <b><a name="IREF11">APPENDIX B. LANGUAGE CODES FROM ISO 639</a></b>
651 </P>
653 The following language codes have been used with non-English derived
654 gairaigo. They have been derived from the ISO 639:1988 "Code for the
655 representation of names of languages" standard.
656 </P>
658 </P>
659 <PRE>
660 ar Arabic
661 zh Chinese (Zhongwen)
662 de German (Deutsch)
663 en English
664 fr French
665 el Greek (Ellinika)
666 iw Hebrew (Iwrith)
667 ja Japanese
668 ko Korean
669 nl Dutch (Nederlands)
670 no Norwegian
671 pl Polish
672 ru Russian
673 sv Swedish
674 bo Tibetan (Bodskad)
675 eo Esperanto
676 es Spanish
677 in Indonesian
678 it Italian
679 lt Latin
680 pt Portugese
681 hi Hindi
682 ur Urdu
683 mn Mongolian
684 kl Inuit (formerly Eskimo)
685 </PRE>
687 And I have added the following, which are not in the Standard:
688 </P>
690 </P>
691 <PRE>
692 ai Ainu
693 </PRE>
694 </BODY></HTML>
695 <BR><SMALL><A HREF="/disclaimers/user.html">Disclaimer</A></SMALL>