| { |
| "paper_id": "P88-1019", |
| "header": { |
| "generated_with": "S2ORC 1.0.0", |
| "date_generated": "2023-01-19T08:51:53.733036Z" |
| }, |
| "title": "EXPERIENCES WITH AN ON-LINE TRANSLATING DIALOGUE SYSTEM", |
| "authors": [ |
| { |
| "first": "Seiji", |
| "middle": [], |
| "last": "Mhke", |
| "suffix": "", |
| "affiliation": { |
| "laboratory": "", |
| "institution": "Toshiba Corporation 1", |
| "location": { |
| "addrLine": "Komukai Toshiba-cho, Saiwai-ku Kawasaki-City", |
| "postCode": "210", |
| "settlement": "Kanagawa", |
| "country": "Japan" |
| } |
| }, |
| "email": "" |
| }, |
| { |
| "first": "Koichi", |
| "middle": [], |
| "last": "Hasebe", |
| "suffix": "", |
| "affiliation": { |
| "laboratory": "", |
| "institution": "Toshiba Corporation 1", |
| "location": { |
| "addrLine": "Komukai Toshiba-cho, Saiwai-ku Kawasaki-City", |
| "postCode": "210", |
| "settlement": "Kanagawa", |
| "country": "Japan" |
| } |
| }, |
| "email": "" |
| }, |
| { |
| "first": "Harold", |
| "middle": [], |
| "last": "Somers", |
| "suffix": "", |
| "affiliation": { |
| "laboratory": "", |
| "institution": "Toshiba Corporation 1", |
| "location": { |
| "addrLine": "Komukai Toshiba-cho, Saiwai-ku Kawasaki-City", |
| "postCode": "210", |
| "settlement": "Kanagawa", |
| "country": "Japan" |
| } |
| }, |
| "email": "" |
| }, |
| { |
| "first": "Shin-Ya", |
| "middle": [], |
| "last": "Amano", |
| "suffix": "", |
| "affiliation": { |
| "laboratory": "", |
| "institution": "Toshiba Corporation 1", |
| "location": { |
| "addrLine": "Komukai Toshiba-cho, Saiwai-ku Kawasaki-City", |
| "postCode": "210", |
| "settlement": "Kanagawa", |
| "country": "Japan" |
| } |
| }, |
| "email": "" |
| } |
| ], |
| "year": "", |
| "venue": null, |
| "identifiers": {}, |
| "abstract": "An English-Japanese bi-directional machine translation system was connected to a keyboard conversation function on a workstation, and tested via a satellite link with users in Japan and Switzerland. The setup is described, and some informal observations on the nature of the bilingual dialogues reported.", |
| "pdf_parse": { |
| "paper_id": "P88-1019", |
| "_pdf_hash": "", |
| "abstract": [ |
| { |
| "text": "An English-Japanese bi-directional machine translation system was connected to a keyboard conversation function on a workstation, and tested via a satellite link with users in Japan and Switzerland. The setup is described, and some informal observations on the nature of the bilingual dialogues reported.", |
| "cite_spans": [], |
| "ref_spans": [], |
| "eq_spans": [], |
| "section": "Abstract", |
| "sec_num": null |
| } |
| ], |
| "body_text": [ |
| { |
| "text": "We have been developing an English-Japanese bi-directional machine translation system implemented on a workstation (Amano 1986, Amano et a/. 1987). The system, which is interactive and designed for use by a translator, normally runs in an interactive mode, and includes a number of special bilingual editing functions. We recently realized a real-time on-line communication system with an automatic translation function by combining a non-imeractive version of our Machine Translation system with the keyboard conversation function just like talk in UNIX**. Using this system, bilingual conversations were held between members of our laboratory in Japan and visitors to the 5th World Telecommunications Exhibition Telecorn 87, organized by the International Telecommunication Union, held in Geneva from 20th to 27th October 1987.", |
| "cite_spans": [], |
| "ref_spans": [], |
| "eq_spans": [], |
| "section": "INTRODUCTION", |
| "sec_num": null |
| }, |
| { |
| "text": "In the fh-st part of this paper, we discuss in detail the configuration of this system, and give some indications of its performance. In the second part, we report informally on what for us was an interesting aspect of the experiment, namely the nature of the dialogues held using the system. In *the Centre for Computational Linguistics, University of Manchester Institute of Science and Technology, England **UNIX is a trademark of AT&T Bell Laboratories. particular we were struck by the amount of metadialogue, i.e. dialogue discussing the previous interchanges: since contributions to the conversation were being translated, this metadialogue posed certain problems which we think are of general interest. In future systems of a similar nature, we feel there is a need for users to be briefly trained in certain conventions regarding metadialogue, and typical system translation errors. Furthermore, an environment which minimizes such errors is desirable and the system must be 'tuned' to make translations appropriate to conversation.", |
| "cite_spans": [], |
| "ref_spans": [], |
| "eq_spans": [], |
| "section": "INTRODUCTION", |
| "sec_num": null |
| }, |
| { |
| "text": "A general idea of the system is illustrated in Figure 1 . Workstations were situated in Japan and Switzerland, and linked by a conventional satellite telephone connection. The workstations at either end were AS3260C machines. Running UNIX, they support the Toshiba Machine Translation system AS-TRANSAC. On this occasion, the Machine Translation capability was installed only at the Japanese end, though in practice both terminals could run AS-TRANSAC.", |
| "cite_spans": [], |
| "ref_spans": [ |
| { |
| "start": 47, |
| "end": 55, |
| "text": "Figure 1", |
| "ref_id": null |
| } |
| ], |
| "eq_spans": [], |
| "section": "SYSTEM CONFIGURATION", |
| "sec_num": null |
| }, |
| { |
| "text": "The workstation screens are divided into three windows, as shown in Figure 2 , not unlike in the normal version of UNIX's talk. The top window shows the user's dialogue, the middle window the correspondenfs replies. The important difference is that both sides of the dialogue are displayed in the language appropriate to the location of the terminal. However, in a third small window, a workspace at the bottom of the screen, the raw input is also displayed. (This access to the English input at the Japanese end is significant in the case of Japanese users having some knowledge of English, and of course vice versa if appropriate.) The bottom window also served the purpose of indicating to the users that their conversation partners were transmitting. Figure 3 shows the set-up in more detail. At the Japanese end, the user inputs Japanese at the keyboard, which is displayed in the upper window of the workstation screen. The input is passed to the translation system and the English output, along with the original input is then transmitted via telecommunications links (KDD's Venus-P and the Swiss PTT's Telepac in this case) to Switzerland. There it is processed by the keyboard conversation function, which displays the original input in the workspace at the bottom of the screen, and the translated message in the middle window on the screen. The set-up at the Swiss end is similar to that at the Japanese end, with the important exception that only the original input message is transmitted, since the translation will take place at the receiving end.", |
| "cite_spans": [], |
| "ref_spans": [ |
| { |
| "start": 68, |
| "end": 76, |
| "text": "Figure 2", |
| "ref_id": null |
| }, |
| { |
| "start": 755, |
| "end": 763, |
| "text": "Figure 3", |
| "ref_id": null |
| } |
| ], |
| "eq_spans": [], |
| "section": "SYSTEM CONFIGURATION", |
| "sec_num": null |
| }, |
| { |
| "text": "An input sentence is translated by morphological analyzer, dictionary look-up module, parser, semantic analyzer, and target sentence generator. Introducing a full-fledged semantic analyzer conflicts with avoiding increases in processing time and memory use. To resolve this conflict, a Lexical Transition Network Grammar (LTNG) has been developed for this system. LTNG provides a semantic framework for an MT system, at the same time satisfying processing time and memory requirements. Its main role is to separate parsing from semantic analysis, i.e., to make these processes independent of each other. In LTNG, parsing includes no semantic analysis. Any ambiguities in an input sentence remain in the syntactic structure of the sentence until processed by the semantic analyzer. Semantic analysis proceeds according to a lexical grammar consisting of rules for converting syntactic structures into semantic structures. These rules are specific to words in a pre-eompiled lexicon. The lexicon consists of one hundred thousand entries for both English and Japanese.", |
| "cite_spans": [], |
| "ref_spans": [], |
| "eq_spans": [], |
| "section": "TRANSLATION METHOD", |
| "sec_num": null |
| }, |
| { |
| "text": "Once the connection has been established, conversation proceeds as in UNIX's talk. An important feature of the function is that conversers do not have to take turns or wait for each other to finish typing before replying, unlike with write. This has a significant effect on conversational strategy, and occasionally leads to disjointed conversations, both in monolingual and bilingual dialogues. For example, a user might start to reply to a message the content of which can be predicted after the first few words are typed in; or one user might start to change the topic of conversation while the other is still typing a reply.", |
| "cite_spans": [], |
| "ref_spans": [], |
| "eq_spans": [], |
| "section": "SYSTEM PERFORMANCE", |
| "sec_num": null |
| }, |
| { |
| "text": "Transmission of input via the satellite was generally fast enough not to be a problem: the real bottle-neck was the physical act of input. Novice users do not attain high speed or accuracy, a problem exacerbated at the Swiss end by a slow screen echo. But the problem is even greater for Japanese input: users typed either in romaji (i.e. using a standard transcription into the Roman alphabet) or in hiragana (i.e. using Japanese-syllable values for the keys). In either case, conversion into kanji (Chinese characters) is necessary (see Kawada et al. 1979 and Mori et al. 1983 Figure 3 . Configuration Japan ber of homophones in Japanese, this can slow down the speed of input considerably. For example, even for professional typists, an input speed of 100 characters (including conversions) per minute is considered reasonable (compare expected speeds of up to 100 words/minute for English typing). It is of interest to note that this kana-tokanji conversion, which is accepted as a normal part of Japanese word-processor usage, is in fact a natural form of pre-editing, given that it serves as a partial disambiguation of the input. On the other hand, slow typing speeds are also encountered for English input, one side-effect of which is the use of abbreviations and shorthand. In fact, we did not encounter this phenomenon in Geneva, though in practice sessions (with native English speakers) in Japan, this had been quite common.", |
| "cite_spans": [ |
| { |
| "start": 539, |
| "end": 561, |
| "text": "Kawada et al. 1979 and", |
| "ref_id": null |
| }, |
| { |
| "start": 562, |
| "end": 578, |
| "text": "Mori et al. 1983", |
| "ref_id": null |
| } |
| ], |
| "ref_spans": [ |
| { |
| "start": 579, |
| "end": 587, |
| "text": "Figure 3", |
| "ref_id": null |
| } |
| ], |
| "eq_spans": [], |
| "section": "SYSTEM PERFORMANCE", |
| "sec_num": null |
| }, |
| { |
| "text": "Examples included contractions (e.g.", |
| "cite_spans": [], |
| "ref_spans": [], |
| "eq_spans": [], |
| "section": "SYSTEM PERFORMANCE", |
| "sec_num": null |
| }, |
| { |
| "text": "pls for please,.u for you, cn for can), omissions of apostrophes (e.g. cant, wont, dont) and non-capitalization (e.g. i, tokyo, jal).", |
| "cite_spans": [], |
| "ref_spans": [], |
| "eq_spans": [], |
| "section": "SYSTEM PERFORMANCE", |
| "sec_num": null |
| }, |
| { |
| "text": "The translation time itself did not cause significant delays compared to the input time, thanks to a very fast parsing algorithm, which is described elsewhere . Input sentences were typically rather short (English five to ten words, Japanese around 20 characters), and translation was generally about 0.7 seconds per word (5000 words/hour). Given users' typing speed and the knowledge that the dialogue was being transmitted half way around the world, what would, under other circumstances, be an unacceptably long delay of about 15 seconds (for translation and transmission) was generally quite tolerable, because users could observe in the third window that the correspondent was inputting something, even if it could not read.", |
| "cite_spans": [], |
| "ref_spans": [], |
| "eq_spans": [], |
| "section": "SYSTEM PERFORMANCE", |
| "sec_num": null |
| }, |
| { |
| "text": "This environment was a good practical test of our Machine Translation system, given that many of the users had little or no knowledge of the target language: the effectiveness of the translation could be judged by the extent to which communication was possible. Having said this, it should also be remarked that the Japanese-English half of the bilingual translation system is still in the experimental stage and so translations in this direction were not always of a quality comparable to those in the other direction. To offset this, the users at the Japanese end, who were mainly researchers at our laboratory and therefore familiar with some of the problems of Machine Transla-tion, generally tried to avoid using difficult constructions, and tried to 'assist' the system in some other ways, notably by including subject and object pronouns which might otherwise have been omitted in more natural language.", |
| "cite_spans": [], |
| "ref_spans": [], |
| "eq_spans": [], |
| "section": "TRANSLATION QUALITY", |
| "sec_num": null |
| }, |
| { |
| "text": "We recognized that the translation of certain phrases in the context of a dialogue might be different from their translation under normal circumstances. For example, Engfish I see should be translated as naruhodo rather than watashi ga miru, Japanese wakarimashita should be I understand rather than I have understood, and so on. Nevertheless, the variety of such conversational fillers is so wide that we inevitably could not foresee them all. The English-Japanese translation was of a high quality, except of course where the users -being inexperienced and often non-native speakers of English -n~de typing mistakes, e.g. (I).", |
| "cite_spans": [], |
| "ref_spans": [], |
| "eq_spans": [], |
| "section": "TRANSLATION QUALITY", |
| "sec_num": null |
| }, |
| { |
| "text": "(In these and subsequent examples, E: indicates English input, J: Japanese input, and T: translation. Translations into Japanese are not shown. Typing errors and mistranslations are of course reproduced from the original transmission.) (la) E: this moming i came fro st. galle to vizite the exosition. E: it is vwery inyteresti ng to see so many apparates here. i would go tolike a girl. b~ 9 \"~-\u00a2A,o T: I don't understand. t o 1 i k e ~j:fSJ'C\"~';~o T: What is tolike?", |
| "cite_spans": [], |
| "ref_spans": [], |
| "eq_spans": [], |
| "section": "TRANSLATION QUALITY", |
| "sec_num": null |
| }, |
| { |
| "text": "These were sometimes compounded by the delay in screen echo of input characters, as in example (2).", |
| "cite_spans": [], |
| "ref_spans": [], |
| "eq_spans": [], |
| "section": "TRANSLATION QUALITY", |
| "sec_num": null |
| }, |
| { |
| "text": "(2) E: Sometimes, I chanteh the topic, suddenly. E: I change teh topic. J: ~ ~ ~o T:I understand. E: I had many mistakes. J: ~b ~ ~: I\u00a2~-C v-,'\u00a3 ~o T: Are you tired? E: A little. E: But the main reason is the delay fo dispaying. E: But the main reason is the delay of display.", |
| "cite_spans": [], |
| "ref_spans": [], |
| "eq_spans": [], |
| "section": "TRANSLATION QUALITY", |
| "sec_num": null |
| }, |
| { |
| "text": "Failure to identify proper names or acronyms often led to errors (by the system) or misunderstandings (by the correspondent), as in (3a), especially when the form not to be translated happens to be identical to a known word, as in (3b). In (3b), 'go men na sai' means in Japanese that I'm sorry.", |
| "cite_spans": [], |
| "ref_spans": [], |
| "eq_spans": [], |
| "section": "TRANSLATION QUALITY", |
| "sec_num": null |
| }, |
| { |
| "text": "(3a) E: lars engvall. J: 1at s engva 1 lhtfaJ\" \"O3'-~0", |
| "cite_spans": [], |
| "ref_spans": [], |
| "eq_spans": [], |
| "section": "TRANSLATION QUALITY", |
| "sec_num": null |
| }, |
| { |
| "text": "T: What is lars engvall? E: this is my name. This was avoided on the Japanese-English side where proper names were typed in romaji (4).", |
| "cite_spans": [], |
| "ref_spans": [], |
| "eq_spans": [], |
| "section": "TRANSLATION QUALITY", |
| "sec_num": null |
| }, |
| { |
| "text": "(4) J: ~I,\u00a9~--~I~N o g a m i \"C'\"J-o T: My name is Nogami.", |
| "cite_spans": [], |
| "ref_spans": [], |
| "eq_spans": [], |
| "section": "TRANSLATION QUALITY", |
| "sec_num": null |
| }, |
| { |
| "text": "As with any system, there were a number of occasions when the translation was too literal, though even these were often successfully understood (5). One problem was that the system must always give some output, even when it cannot analyse the input correcdy: in this environment failure to give some result is simply unacceptable. However, this is difficult when the input contains an unknown word, especially when the source language is Japanese and the unknown word is transmitted as a kanji. Our example (6) nevertheless shows how a cooperative user will make the most of the output. Here, the non-translation of tsuki mae (fi] ~ ) is compounded by its mis-translation as a prepositional object. The first Japanese sentence said that I married two months ago. But the English correspondent imagines the untranslated kanji might mean 'wives'! (6) J: ~/,t-J:27J ~ E~ L too T: I married to 2 ~ ~-~]. E: are married to 2 what???. J: ~-~\u00a96~ tc~ l.fco T: I married in this year June. E: now i understand. E: i thought you married 2 women.", |
| "cite_spans": [], |
| "ref_spans": [], |
| "eq_spans": [], |
| "section": "TRANSLATION QUALITY", |
| "sec_num": null |
| }, |
| { |
| "text": "In the reverse direction, the problem is less acute, since most Japanese users can at least read Roman characters, even if they do not understand them (7): this led in this case to an interesting metadialogue. Again, the English user was cooperative, and rephrased what he wanted to say in a way that the system could translate correcdy. T: What is crash course? E: it means learn much in a very short time.", |
| "cite_spans": [], |
| "ref_spans": [], |
| "eq_spans": [], |
| "section": "TRANSLATION QUALITY", |
| "sec_num": null |
| }, |
| { |
| "text": "Mistransladons were a major source of metadialogue, to be discussed below, though see particularly example (10).", |
| "cite_spans": [], |
| "ref_spans": [], |
| "eq_spans": [], |
| "section": "TRANSLATION QUALITY", |
| "sec_num": null |
| }, |
| { |
| "text": "There has been some interesting research recently (at ATR in Osaka) into the nature of keyboard dialogues (Arita et aL 1987; Iida 1987) mainly aimed at comparing telephone and keyboard conversions. They have concluded that keyboard has the same fundamental conversational features as telephone conversation, notwithstanding the differences between written and spoken language. No mention is made of what we are calling here metadialogue, though it should be remembered that our dialogues are quite different from those reported by the ATR researchers in that we had a translation system as an intermediary. No comparable experiment is known to us, so it is difficult to find a yardstick against which to assess our findings.", |
| "cite_spans": [], |
| "ref_spans": [], |
| "eq_spans": [], |
| "section": "THE NATURE OF THE DIALOGUES", |
| "sec_num": null |
| }, |
| { |
| "text": "Regarding the subject matter of our dialogues, this was of a very general nature, often about the local situation (time, weather), the dialogue partner (name, marital status, interests) or about recent news. A lot of the dialogue actually concemed the system itself, or the conversation. An obvious example of this would be a request to rephrase in the case of mistranslation, as we have seen in (6) above, though not all users seemed to understand the necessity of this tactic (8). The most interesting metadialogues however occurred when users failed to distinguish cited words -a problem linguists are familiar withfor example by quotation marks: these would then be re-translated, sometimes leading to further confusion (10). 0o) Jl: B~:\u00a9Ep~'~L.\"C < ~ Wo T: Please speak a Japanese impression. E1 : ichibana. J2: b~ ~ \",~ ~-A,o J3: i c h i b a n a ~1~'~';~o T:What is ichibana? E2: i thought it means number one. J4: f~ ~--~:'(-~o T:What is the first? E3: the translation to you was incorrect.", |
| "cite_spans": [], |
| "ref_spans": [], |
| "eq_spans": [], |
| "section": "THE NATURE OF THE DIALOGUES", |
| "sec_num": null |
| }, |
| { |
| "text": "This example may need explanation. First the translation of the Japanese question (J1) has been misunderstood: the translation should have been 'Please give me your impressions of Japan', but the English user (E-user) has understood Japanese to mean 'Japanese language'. That is, E-user has understood J1 to be saying 'Please speak an impressive Japanese word.' Then E-user confused ichiban ('number 1' or 'the first') and ikebana ('flower arranging'). The word ichibana (El) does not exist in Japanese. His explanation 'number one' was correctly translated (not shown here) as ichiban. But not realizing of course that the meaning of his first sentence (J1) was incorrectly understood, the Japanese user (J-user) could not understand E1 (J2) and asked for its sense (J3). So E-user tried to explain the meaning of /\u00a2h/bana, which in fact was ichiban. By the answer, J-user has identified what E-user ment, but since J-user still did not realized that his first sentence was incorrectly understood and hence Juser has understood E2 to be saying that something was 'number 1', he tried to ask what was 'number 1' (J4).", |
| "cite_spans": [], |
| "ref_spans": [], |
| "eq_spans": [], |
| "section": "THE NATURE OF THE DIALOGUES", |
| "sec_num": null |
| }, |
| { |
| "text": "(--~ ) was translated as 'the fLrsf. At this point, it is not clear which comment E-user is referring to in E3, but anyway, not realizing what answer J-user have expected and not knowing enough Japanese to realize what has happened -i.e. the connection between 'number one' and 'the firsf -Euser gives up and changes the subject. If E-user had intended to speak ikebana and explained its meaning, J-user could have realized J1 had been misunderstood. Because it is meaningless in a sentence saying someone's impression that something is ikebana.", |
| "cite_spans": [], |
| "ref_spans": [], |
| "eq_spans": [], |
| "section": "But in the translation of this question, ichiban", |
| "sec_num": null |
| }, |
| { |
| "text": "On the other hand, where the user knew a litde of the foreign language (typically the Japanese user knowing English rather than vice versa), such a misunderstanding could be quickly dealt with (11).", |
| "cite_spans": [], |
| "ref_spans": [], |
| "eq_spans": [], |
| "section": "But in the translation of this question, ichiban", |
| "sec_num": null |
| }, |
| { |
| "text": "(11) E: How is the weathere in Tokyo?", |
| "cite_spans": [], |
| "ref_spans": [], |
| "eq_spans": [], |
| "section": "But in the translation of this question, ichiban", |
| "sec_num": null |
| }, |
| { |
| "text": "J:we a t h e r e i'~we a t h e r T: Is weathere weather? CONCLUSIONS There are a number of things to be learnt from this experiment, even if it was not in fact set up to elicit information of this kind. Clearly, typing errors are a huge source of problems, so an environment which minimizes these is highly desirable. Two obvious features of such an environment are fast screen echo, and delete and back-space keys which work in a predictable manner in relation to what is seen on the screen. For the correction of typing errors, the system should have a spelling-check function which works word-by-word as users are typing in. The main reasons for syntax errors are ellipsis and unknown words. Therefore, the system should have a rapid syntax-check function which can work before transmission or translation and can indicate to users that there is a syntax error so that users can edit the input sentence or reenter the correct sentence. These are in themselves not new ideas, of course (e.g. Kay 1980 and others).", |
| "cite_spans": [], |
| "ref_spans": [], |
| "eq_spans": [], |
| "section": "But in the translation of this question, ichiban", |
| "sec_num": null |
| }, |
| { |
| "text": "Conventions for citing forms not to be translaw, d, especially in metadialogue, must be developed, and the Machine Translation system must be sensitive to these. The system must be 'tuned' in other ways to make translations appropriate to conversation, in particular in the translation of conversational fillers like I see and wakarimashita.", |
| "cite_spans": [], |
| "ref_spans": [], |
| "eq_spans": [], |
| "section": "But in the translation of this question, ichiban", |
| "sec_num": null |
| }, |
| { |
| "text": "Finally, it seems to be desirable that users be trained briefly, not only to learn these conventions, but also so that they understand the limits of the system, and the kind of errors that get produced, especially since these are rather different from the errors occasionally produced by human translators or people conversing in a foreign language that they know only partially.", |
| "cite_spans": [], |
| "ref_spans": [], |
| "eq_spans": [], |
| "section": "But in the translation of this question, ichiban", |
| "sec_num": null |
| } |
| ], |
| "back_matter": [ |
| { |
| "text": ": 1289 utterances that were successfully translated : 140 utterances that were mis-~ranslated : 31 utterances that caused metadialogues A: by typing errors (7times) B: by mistranslations (5times) C: by unknown words to the partner and so on (19times) ", |
| "cite_spans": [ |
| { |
| "start": 241, |
| "end": 250, |
| "text": "(19times)", |
| "ref_id": null |
| } |
| ], |
| "ref_spans": [], |
| "eq_spans": [], |
| "section": "annex", |
| "sec_num": null |
| } |
| ], |
| "bib_entries": { |
| "BIBREF0": { |
| "ref_id": "b0", |
| "title": "Parsing with look-ahead in a real time on-line translation system. TO be appeared in COLING 88", |
| "authors": [ |
| { |
| "first": "", |
| "middle": [], |
| "last": "Amano Shin-Ya", |
| "suffix": "" |
| }, |
| { |
| "first": "Nogami", |
| "middle": [], |
| "last": "Hiroyasu", |
| "suffix": "" |
| }, |
| { |
| "first": "Miixe ; Nogami", |
| "middle": [], |
| "last": "Seiji", |
| "suffix": "" |
| }, |
| { |
| "first": "", |
| "middle": [], |
| "last": "Hiroyasu", |
| "suffix": "" |
| }, |
| { |
| "first": "Yoshimu-Ra &", |
| "middle": [], |
| "last": "Yumiko", |
| "suffix": "" |
| }, |
| { |
| "first": "", |
| "middle": [], |
| "last": "Shin-Ya", |
| "suffix": "" |
| }, |
| { |
| "first": "", |
| "middle": [], |
| "last": "Amano", |
| "suffix": "" |
| } |
| ], |
| "year": 1988, |
| "venue": "Step towards Telecommunication with Machine Interpreter. Second International Conference on Theoretical and Methodological Issues in Machine Translation of Natural Languages", |
| "volume": "3", |
| "issue": "", |
| "pages": "16--18", |
| "other_ids": {}, |
| "num": null, |
| "urls": [], |
| "raw_text": "AMANO Shin-ya, Hiroyasu NOGAMI & Seiji MIIXE (1988). A Step towards Telecommu- nication with Machine Interpreter. Second Interna- tional Conference on Theoretical and Methodologi- cal Issues in Machine Translation of Natural Lan- guages, June 12-14, 1988 (CMU). NOGAMI Hiroyasu, Yumiko YOSHIMU- RA & Shin-ya AMANO (1988). Parsing with look-ahead in a real time on-line translation sys- tem. TO be appeared in COLING 88, Budapest. AMANO shin-ya, Kimihito TAKEDA, Koichi HASEBE & Hideki HIRAKAWA (1988). Experiment of Automatic Translation Typing Phone (in Japanese). Information Processing Soci- ety of Japan (1988.3.16-18) TAKEDA Kimihito, Koichi HASEBE & Shin- ya AMANO (1988). System Configuration of Automatic Translation Typing Phone (in Japanese). Information Processing Society of Japan (1988.3.16-18) ASAHIOKA Yoshimi, Yumiko YOSHIMU-", |
| "links": null |
| }, |
| "BIBREF2": { |
| "ref_id": "b2", |
| "title": "The Toshiba Machine Translation system. Japan Computer Quarterly 64 \"Machine Translation -Threat or Tool", |
| "authors": [ |
| { |
| "first": "", |
| "middle": [], |
| "last": "Arita Hidekazu", |
| "suffix": "" |
| }, |
| { |
| "first": "Kogure", |
| "middle": [], |
| "last": "Kiyoshi", |
| "suffix": "" |
| }, |
| { |
| "first": "Nogaito", |
| "middle": [], |
| "last": "Izum", |
| "suffix": "" |
| }, |
| { |
| "first": "Maeda", |
| "middle": [], |
| "last": "Hiroyuki", |
| "suffix": "" |
| }, |
| { |
| "first": "Iida", |
| "middle": [], |
| "last": "Hitoshi", |
| "suffix": "" |
| } |
| ], |
| "year": 1980, |
| "venue": "Analysis of the Translated Dialogue by Automatic Translation Typing Phone", |
| "volume": "3", |
| "issue": "", |
| "pages": "15--23", |
| "other_ids": {}, |
| "num": null, |
| "urls": [], |
| "raw_text": "Analysis of the Translated Dialogue by Automatic Translation Typing Phone (in Japanese). Informa- tion Processing Society of Japan (1988.3.16-18) ARITA Hidekazu, Kiyoshi KOGURE, Izum NOGAITO, Hiroyuki MAEDA & Hitoshi IIDA (1987). Media-dependent conversation manners: Comparison of telephone and keyboard conversa- tions (in Japanese). Information Processing Soci- ety of Japan 87-M (1987.5.22) IIDA Hitoshi (1987). Distinctive features of conversations and inter-keyboard interpreta- tion. Workshop on Natural Language Dialogue Interpretation, November 27-28, 1987, Advanced Telecommunications Research Institute (ATR), Osaka. AMANO Shin-ya (1986). The Toshiba Machine Translation system. Japan Computer Quarterly 64 \"Machine Translation -Threat or Tool\" (Japan Information Processing Development Center, Tokyo), 32-35. AMANO Shin-ya, Hideki HIRAKAWA & Yoshinao TSUTSUMI (1987). TAURAS: The Toshiba Machine Translation system. MT Machine Translation Summit, Manuscripts & Program, Tokyo: Japan Electronic Industry Development Association (JEIDA), 15-23. KAY Martin (1980). The proper place of men and machines in language translation. Report CSL-80-11, Xerox-PARC, Palo Alto, CA. HAYASHI Ooki (kanshuu) (1982). ~ ~k: (~", |
| "links": null |
| }, |
| "BIBREF4": { |
| "ref_id": "b4", |
| "title": "Japanese word processor", |
| "authors": [], |
| "year": 1983, |
| "venue": "Nineteenth IEEE Computer Society International Conference", |
| "volume": "7", |
| "issue": "", |
| "pages": "119--128", |
| "other_ids": {}, |
| "num": null, |
| "urls": [], |
| "raw_text": "Japanese word processor JW-10. Compcon 79 (Nineteenth IEEE Computer Society International Conference, Washington DC), 238-242. MORI Ken-ichi, Tsutomu KAWADA & Shin-ya AMANO (1983). Japanese word proces- sor. In T. KITAGAWA (Ed.) Japan Annual Reviews in Electronics, Computers & Telecommu- nications Volume 7: Computer Sciences & Tech- nologies, Tokyo: Ohmsha, 119-128.", |
| "links": null |
| } |
| }, |
| "ref_entries": { |
| "FIGREF0": { |
| "type_str": "figure", |
| "uris": null, |
| "text": "Switzerland/~-, Tal<eclao ~o)~l~l:s u zanne~o ~v,, ----b~,b/~'~J 2~'~'~o ~o k~1\"oThat is ok,", |
| "num": null |
| }, |
| "FIGREF1": { |
| "type_str": "figure", |
| "uris": null, |
| "text": "Figure 2. Screen Display", |
| "num": null |
| }, |
| "FIGREF3": { |
| "type_str": "figure", |
| "uris": null, |
| "text": "3b) [having been asked if he knows Japanese] E: How about go men na sai? T: &'\u00a9,,t: 5 Ir__Ic.-9 v-,-C~ <_ Jk_n a_ s a i.", |
| "num": null |
| }, |
| "FIGREF4": { |
| "type_str": "figure", |
| "uris": null, |
| "text": "drink do you want? J: ~w= -e --~JJC~.3.h: w, T: I want to drink a warm coffee. E: warm coffee? E: Not a hot one? J: ,,~, v, = --e --'e3\"o T: It is a hot coffee.", |
| "num": null |
| }, |
| "FIGREF5": { |
| "type_str": "figure", |
| "uris": null, |
| "text": "(7) E: can you give me a crash course in japanese?. J: c r a s h c o u r s e~f~'O~ ~o", |
| "num": null |
| }, |
| "FIGREF6": { |
| "type_str": "figure", |
| "uris": null, |
| "text": "E: how does your sistem work please. J: ~.L~ ~: \u00a9~\u00a9,~b~ r) ~-'~-A,o T: I don't understand a meaning of the sentence. E: how does your sistem work? Often, a user would seek clarification of a misor un-translated word as in (9), or (3) above. (9) E: I could have riz in the dinner. J: r i z ~7 ~ :/:~-@~o T: Is riz French? E: May be. I'm not sure. J: ~-(\" 3\",~o T: Is it rice? E: In my guess, you are right. J: ~ ~'9\"o T: It is natural. E: What is natural? T: I understand French. J: r i z ~:~'C~o T: Riz is rice.", |
| "num": null |
| }, |
| "TABREF1": { |
| "text": "on kana.to-kanji conversion); and this conversion is needed for between a third and a half of the input, on average (el. Hayashi 1982:211). Because of the large hum-", |
| "html": null, |
| "type_str": "table", |
| "num": null, |
| "content": "<table><tr><td>AS 3260C</td><td/><td/><td/><td>\\</td><td>3260C</td></tr><tr><td>El.,, conversat i on _~ function E2 I</td><td>Telep~ PTT</td><td>Venus-P Jr KDD</td><td>E2</td><td colspan=\"2\">I conversation function</td></tr><tr><td>r2.,E2</td><td>\"J2,E2</td><td/><td/><td/></tr><tr><td/><td/><td/><td/><td colspan=\"2\">translation</td></tr><tr><td/><td/><td/><td/><td colspan=\"2\">system</td></tr><tr><td>Switzerland</td><td/><td/><td/><td/></tr></table>" |
| } |
| } |
| } |
| } |
