DOCSLIB.ORG

An Implementation of Multilingualized Environment on Dynamic Objects

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
An Implementation of Multilingualized Environment on Dynamic Objects 事業名: 平成 14 年度未踏ソフトウェア創造事業 契約件名: An Implementation of Multilingualized Environment on Dynamic Objects 大島 芳樹 Yoshiki Ohshima Twin Sun, Inc. 360 N. Sepulveda Blvd. Suite 2055 El Segundo, CA 90245 E-mail: [email protected] ABSTRACT. This paper describes the design and implementation of multilingualization (“m17n”) of a dynamic object-oriented environment called Squeak. Squeak is a highly portable implementation of a dynamic objects environment and it is a good starting point toward the future collaborative environment. However, its text related classes lack the ability to handle natural languages that require extended character sets such as Arabic, Chinese, Greek, Korean, and Japanese. We have been implementing the multilingualization extension to Squeak. The extension we wrote can be classified as follows: 1) new character and string representations for extended character sets, 2) keyboard input and the file out of multilingual text mechanism, 3) flexible text composition mechanism, 4) extended font handling mechanisms including dynamic font loading and outline font handling, 5) higher level application changes including a Japanese version of SqueakToys. The resulting environment has the following characteristics: 1) various natural languages can be used in the same context, 2) the pixels on screen, including the appearance of characters can be completely controlled by the program, 3) decent word processing facility for a mixture of multiple languages, 4) existing Squeak capability, such as remote collaborative mechanism will be integrated with it, 5) small memory footprint requirement. multilingual system. Firstly, the system should allow the user 1 Introduction to use characters from different languages (scripts) without The more people who live in the networked and comput- any burden. For instance, the system should easily support erized society, the more important the communication tools applications such as Arabic-English or Chinese-Japanese become. We envision that, in near future, non-technical peo- electric dictionaries in which different scripts are used to- ple including kids will express and exchange their ideas using gether. such tools. They may such ideas collaboratively and commu- Secondly, the displayed or printed result from the system nicate them over the network [1]. should be acceptable in terms of the appearance. The network and the tool are getting faster and ready for Thirdly, the system should be portable among the variety creating such a collaborative environment. What we need is of platforms. A multilingualized system will be used by peo- good software that is usable by people all over the world. Be- ple who use different hardware and software. The system cause the people will want to express their ideas in their own should be usable on all those platforms. natural languages, such software must be capable of not only We aim to fulfill those three requirement in this project. end-user accessible idea authoring, but also multiple natural This is an on-going project, but the system is already being languages. In the other words, it has to be a multilingualized used in several places. This fact proves that we are on the system. right track toward our goal. To achieve this goal, we started from a late-bound, dy- In this paper, we discuss the design and implementation of namic object-oriented system called Squeak[2]. Squeak is an the multilingualization of Squeak. implementation of a dynamic objects environment. Squeak The following sections are organized as follows. In sec- provides various end-user collaboration tools including an tion 2, we discuss the overall design goals and the prereq- end-user programming environment called SqueakToy[3]. uisites for understanding the issues of multilingualization. Also, the Squeak’s ability to control the every pixel on screen From section 3 to section 9, we discuss the implementation has a great potential. of the added features. Finally, in section 11, we conclude the However, Squeak has a weakness in its multilingual as- paper. pect; Squeak’s text handling classes lack the ability to handle 2 Overall Design natural languages other than English. We think that Squeak will be an ideal environment for network collaboration once In this section, we discuss the overall design issues of the it is multilingualized. multilingualized Squeak. There are three issues to consider when implementing a 2.1 Universal Character Set solution was feasible. In the original Squeak, a character, represented as an in- 2.4 MacRoman vs. ISO-8859-1 stance of Character class, holds an 8-bit quantity (“octet”). For compatibility with the original Squeak, ideally the def- Obviously, that representation is not sufficient for the ex- inition of the one-octet characters and strings should not be tended character set. changed. However, to adapt to Unicode, it is cleaner if the What kind of representation do we need for the extended first 256 characters are identical with ISO-8859-1 character character set? One might think that a 16-bit fixed represen- set, instead of the original Squeak’s MacRoman character tation would be enough, but even the “industrial standard”, set. Unicode version 3.2 [4][5], now defines a character set that We decided to modify the upper half of the first 256 char- needs as many as 21 bits per character. acters to be ISO-8859-1 characters. Because the characters in The plain Unicode has another problem; “han- the upper half are not used much, this change was easy. With unification”. The idea behind han-unification is that this change, the Character class represents the ISO-8859- the standard disregard the glyph difference of certain Kanji 1, which is equivalent to the first 256 characters in Unicode characters and let the implementation choose the actual standard. glyph. This abstraction contradicts the philosophy of 2.5 Keyboard Input Squeak; namely, it becomes impossible to ensure pixel At a layer from the OS to Squeak level code has to create identical execution and layout across the platforms. a character in the extended character set from the user key- On the other hand, Unicode seems to be good enough board input sequence. One would imagine that modifying for scripts other than CJKV (in Unicode terminology, CJKV VM to pass multi-octet characters to the Squeak level would refers to “Chinese, Japanese, Korean and Vietnamese, that be a good solution. However, this is not desirable in two use the Chinese origin characters) unified characters. They reasons. One is that such VM will be incompatible with the are well defined and contain many scripts. existing VMs installed to many computers. The other is that Obviously, we need more than 16-bit for a character. What the encoding of the multi octet character sent from the OS is is the upper limit? Actually we don’t have to decide the upper different from one platform to another. limit. Thanks to the late-bound nature of Squeak, we can In the current implementation of m17n Squeak, we decide always change the internal representation without affecting not to modify the VM. If the OS sends a multi octet character the other parts of system much, even when what is changed to the Squeak VM, the VM treats the octets as if they are is as basic as the Character class. This decision let us start separable characters and sent them to the Squeak level code with a 32-bit word for a character. We have added a kind of through the Sensor object. The Sensor then interprets the “encoding tag” to each character to discriminate the unified characters if necessary and generate appropriate character. characters, and also to switch the underlying font and scanner 2.6 Text File Export and Exchange method implementation. The requirement for the file out format is two fold. Firstly, 2.2 Memory Usage it should be understandable by the other non-Squeak soft- To represent text in any form of extended character set, ware. Secondly, the identity on the roundtrip conversion there must be a character entity that can represent more than from Squeak should be ensured. We don’t require that the an 8-bit quantity and a type of string that can store these other way of round trip doesn’t have to be identical. characters. One way to adapt this new representation is to Because the original Squeak’s file out format already uses change Character and String uniformly so that all instances the MacRoman format and uses all 8 bits of the octets in a file of Character or String represent this new wide character out, we need to introduce a mechanism to let the characters in and string (uniform approach). One of the most advanced the extended character set co-exist with the original MacRo- multilingualized system, Emacs after version 20, uses this man characters in the file out. To satisfy this goal, there are approach [6]. Another way is to add new representations and three feasible encoding schemes for this external file format. let them co-exist with the exisiting default ones (mixed ap- The first possible way is to adapt the X Compound Text proach). format of X Window System, or “ctext”[7]. The upside The uniform wide character representation is cleaner, but of ctext is compatibility with existing file outs. The 8-bit takes much space. In original version 3.2 image, The total characters in the file out remain the same semantics. Also, size of the String subinstances occupy is about 1.5MB. If many existing software can read and write this format at least we use unsatisfying 16-bit uniform representation or 32-bit partially. In fact, Japanese in ctext is essentially identical representation, the image size would grow a few megabytes. with the standard internet email format for Japanese[8]. The We decided to use the mixed approach.
Load more

Recommended publications
  • Handshake Brand Guidelines 2021 1 Spring 2021
    Brand GuidelinesHANDSHAKE BRAND GUIDELINES 2021 SPRING 20211 Manifesto Our brand manifesto is our call to action for students. It describes what we do, what we stand for, and what we can help students accomplish. For the ready, set, and not quite there yet. For the “I know” and the “I have no idea.” For the seekers, finders, doers, and explorers. Look ahead at what’s possible. At what’s next. If you want it, you can make it happen. No matter what you’re looking for, or where you are in your career journey—we’re here to help. Take the first step. Then the next. Towards to job you want. Find Your Next. HANDSHAKE BRAND GUIDELINES 2021 2 Logo The Handshake logo is the official signature of the Handshake brand — it is confident, simple and trustworthy. Our logo is our most important assets, serving as the chief expression of the brand. HANDSHAKE BRAND GUIDELINES 2021 3 Logo The Handshake logo is the anchor of our brand horizontal lockup of the brand wordmark and our system , and maintaining the mark’s integrity iconic symbol. Modern and timeless, the mark across all touchpoints is critical for establishing balances trustworthiness and professionalism with a successful corporate identity. The logo is a an authentic human touch. PRIMARY MARK ▶ HANDSHAKE BRAND GUIDELINES 2021 4 Logo To preserve the integrity of the brand, the or the signature Handshake red. The red logo is Handshake logo must only be displayed in a limited only permitted on use of a white or very light gray palette of color options.
    [Show full text]
  • Jewish Intertestamental and Early Rabbinic Literature: an Annotated Bibliographic Resource Updated Again (Part 2)
    JETS 63.4 (2020): 789–843 JEWISH INTERTESTAMENTAL AND EARLY RABBINIC LITERATURE: AN ANNOTATED BIBLIOGRAPHIC RESOURCE UPDATED AGAIN (PART 2) DAVID W. CHAPMAN AND ANDREAS J. KÖSTENBERGER* Part 1 of this annotated bibliography appeared in the previous issue of JETS (see that issue for an introduction to this resource). This again is the overall struc- ture: Part 1: 1. General Reference Tools; 2. Old Testament Versions; 3. Apocrypha; 4. Pseudepigrapha; Part 2: 5. Dead Sea Scrolls; 6. Individual Authors (Philo, Jose- phus, Pseudo-Philo, Fragmentary Works); 7. Rabbinic Literature; 8. Other Early Works from the Rabbinic Period; 9. Addenda to Part 1. 5. DEAD SEA SCROLLS While the Dead Sea Scrolls are generally associated with Qumran, properly they also cover discoveries from approximately a dozen other sites in the desert wilderness surrounding the Dead Sea, such as those at Naal ever, Murabbaat, and Masada. The approximately 930 MSS from Qumran were penned from the 3rd c. BC through the 1st c. AD. The Masada texts include Jewish scrolls from the time leading up to the Roman conquest (AD 73) and subsequent Roman documents. The finds at Naal ever and Murabbaat include documents from the time of the Bar Kokhba revolt (AD 132–135). Other Bar Kokhba era documents are known from Ketef Jericho, Wadi Sdeir, Naal Mishmar, and Naal eelim (see DJD 38). For a full accounting, see the lists by Tov under “Bibliography” below. The non- literary documentary papyri (e.g. wills, deeds of sale, marriage documents, etc.) are not covered below. Recent archaeological efforts seeking further scrolls from sur- rounding caves (esp.
    [Show full text]
  • Man'yogana.Pdf (574.0Kb)
    Bulletin of the School of Oriental and African Studies http://journals.cambridge.org/BSO Additional services for Bulletin of the School of Oriental and African Studies: Email alerts: Click here Subscriptions: Click here Commercial reprints: Click here Terms of use : Click here The origin of man'yogana John R. BENTLEY Bulletin of the School of Oriental and African Studies / Volume 64 / Issue 01 / February 2001, pp 59 ­ 73 DOI: 10.1017/S0041977X01000040, Published online: 18 April 2001 Link to this article: http://journals.cambridge.org/abstract_S0041977X01000040 How to cite this article: John R. BENTLEY (2001). The origin of man'yogana. Bulletin of the School of Oriental and African Studies, 64, pp 59­73 doi:10.1017/S0041977X01000040 Request Permissions : Click here Downloaded from http://journals.cambridge.org/BSO, IP address: 131.156.159.213 on 05 Mar 2013 The origin of man'yo:gana1 . Northern Illinois University 1. Introduction2 The origin of man'yo:gana, the phonetic writing system used by the Japanese who originally had no script, is shrouded in mystery and myth. There is even a tradition that prior to the importation of Chinese script, the Japanese had a native script of their own, known as jindai moji ( , age of the gods script). Christopher Seeley (1991: 3) suggests that by the late thirteenth century, Shoku nihongi, a compilation of various earlier commentaries on Nihon shoki (Japan's first official historical record, 720 ..), circulated the idea that Yamato3 had written script from the age of the gods, a mythical period when the deity Susanoo was believed by the Japanese court to have composed Japan's first poem, and the Sun goddess declared her son would rule the land below.
    [Show full text]
  • SUPPORTING the CHINESE, JAPANESE, and KOREAN LANGUAGES in the OPENVMS OPERATING SYSTEM by Michael M. T. Yau ABSTRACT the Asian L
    SUPPORTING THE CHINESE, JAPANESE, AND KOREAN LANGUAGES IN THE OPENVMS OPERATING SYSTEM By Michael M. T. Yau ABSTRACT The Asian language versions of the OpenVMS operating system allow Asian-speaking users to interact with the OpenVMS system in their native languages and provide a platform for developing Asian applications. Since the OpenVMS variants must be able to handle multibyte character sets, the requirements for the internal representation, input, and output differ considerably from those for the standard English version. A review of the Japanese, Chinese, and Korean writing systems and character set standards provides the context for a discussion of the features of the Asian OpenVMS variants. The localization approach adopted in developing these Asian variants was shaped by business and engineering constraints; issues related to this approach are presented. INTRODUCTION The OpenVMS operating system was designed in an era when English was the only language supported in computer systems. The Digital Command Language (DCL) commands and utilities, system help and message texts, run-time libraries and system services, and names of system objects such as file names and user names all assume English text encoded in the 7-bit American Standard Code for Information Interchange (ASCII) character set. As Digital's business began to expand into markets where common end users are non-English speaking, the requirement for the OpenVMS system to support languages other than English became inevitable. In contrast to the migration to support single-byte, 8-bit European characters, OpenVMS localization efforts to support the Asian languages, namely Japanese, Chinese, and Korean, must deal with a more complex issue, i.e., the handling of multibyte character sets.
    [Show full text]
  • Handy Katakana Workbook.Pdf
    First Edition HANDY KATAKANA WORKBOOK An Introduction to Japanese Writing: KANA THIS IS A SUPPLEMENT FOR BEGINNING LEVEL JAPANESE LANGUAGE INSTRUCTION. \ FrF!' '---~---- , - Y. M. Shimazu, Ed.D. -----~---- TABLE OF CONTENTS Page Introduction vi ACKNOWLEDGEMENlS vii STUDYSHEET#l 1 A,I,U,E, 0, KA,I<I, KU,KE, KO, GA,GI,GU,GE,GO, N WORKSHEET #1 2 PRACTICE: A, I,U, E, 0, KA,KI, KU,KE, KO, GA,GI,GU, GE,GO, N WORKSHEET #2 3 MORE PRACTICE: A, I, U, E,0, KA,KI,KU, KE, KO, GA,GI,GU,GE,GO, N WORKSHEET #~3 4 ADDmONAL PRACTICE: A,I,U, E,0, KA,KI, KU,KE, KO, GA,GI,GU,GE,GO, N STUDYSHEET #2 5 SA,SHI,SU,SE, SO, ZA,JI,ZU,ZE,ZO, TA, CHI, TSU, TE,TO, DA, DE,DO WORI<SHEEI' #4 6 PRACTICE: SA,SHI,SU,SE, SO, ZA,II, ZU,ZE,ZO, TA, CHI, 'lSU,TE,TO, OA, DE,DO WORI<SHEEI' #5 7 MORE PRACTICE: SA,SHI,SU,SE,SO, ZA,II, ZU,ZE, W, TA, CHI, TSU, TE,TO, DA, DE,DO WORKSHEET #6 8 ADDmONAL PRACI'ICE: SA,SHI,SU,SE, SO, ZA,JI, ZU,ZE,ZO, TA, CHI,TSU,TE,TO, DA, DE,DO STUDYSHEET #3 9 NA,NI, NU,NE,NO, HA, HI,FU,HE, HO, BA, BI,BU,BE,BO, PA, PI,PU,PE,PO WORKSHEET #7 10 PRACTICE: NA,NI, NU, NE,NO, HA, HI,FU,HE,HO, BA,BI, BU,BE, BO, PA, PI,PU,PE,PO WORKSHEET #8 11 MORE PRACTICE: NA,NI, NU,NE,NO, HA,HI, FU,HE, HO, BA,BI,BU,BE, BO, PA,PI,PU,PE,PO WORKSHEET #9 12 ADDmONAL PRACTICE: NA,NI, NU, NE,NO, HA, HI, FU,HE, HO, BA,BI,3U, BE, BO, PA, PI,PU,PE,PO STUDYSHEET #4 13 MA, MI,MU, ME, MO, YA, W, YO WORKSHEET#10 14 PRACTICE: MA,MI, MU,ME, MO, YA, W, YO WORKSHEET #11 15 MORE PRACTICE: MA, MI,MU,ME,MO, YA, W, YO WORKSHEET #12 16 ADDmONAL PRACTICE: MA,MI,MU, ME, MO, YA, W, YO STUDYSHEET #5 17
    [Show full text]
  • Classifying Type Thunder Graphics Training • Type Workshop Typeface Groups
    Classifying Type Thunder Graphics Training • Type Workshop Typeface Groups Cla sifying Type Typeface Groups The typefaces you choose can make or break a layout or design because they set the tone of the message.Choosing The the more right you font know for the about job is type, an important the better design your decision.type choices There will are be. so many different fonts available for the computer that it would be almost impossible to learn the names of every one. However, manys typefaces share similar qualities. Typographers classify fonts into groups to help Typographers classify type into groups to help remember the different kinds. Often, a font from within oneremember group can the be different substituted kinds. for Often, one nota font available from within to achieve one group the samecan be effect. substituted Different for anothertypographers usewhen different not available groupings. to achieve The classifi the samecation effect. system Different used by typographers Thunder Graphics use different includes groups. seven The major groups.classification system used byStevenson includes seven major groups. Use the Right arrow key to move to the next page. • Use the Left arrow key to move back a page. Use the key combination, Command (⌘) + Q to quit the presentation. Thunder Graphics Training • Type Workshop Typeface Groups ����������������������� ��������������������������������������������������������������������������������� ���������������������������������������������������������������������������� ������������������������������������������������������������������������������
    [Show full text]
  • Writing As Aesthetic in Modern and Contemporary Japanese-Language Literature
    At the Intersection of Script and Literature: Writing as Aesthetic in Modern and Contemporary Japanese-language Literature Christopher J Lowy A dissertation submitted in partial fulfillment of the requirements for the degree of Doctor of Philosophy University of Washington 2021 Reading Committee: Edward Mack, Chair Davinder Bhowmik Zev Handel Jeffrey Todd Knight Program Authorized to Offer Degree: Asian Languages and Literature ©Copyright 2021 Christopher J Lowy University of Washington Abstract At the Intersection of Script and Literature: Writing as Aesthetic in Modern and Contemporary Japanese-language Literature Christopher J Lowy Chair of the Supervisory Committee: Edward Mack Department of Asian Languages and Literature This dissertation examines the dynamic relationship between written language and literary fiction in modern and contemporary Japanese-language literature. I analyze how script and narration come together to function as a site of expression, and how they connect to questions of visuality, textuality, and materiality. Informed by work from the field of textual humanities, my project brings together new philological approaches to visual aspects of text in literature written in the Japanese script. Because research in English on the visual textuality of Japanese-language literature is scant, my work serves as a fundamental first-step in creating a new area of critical interest by establishing key terms and a general theoretical framework from which to approach the topic. Chapter One establishes the scope of my project and the vocabulary necessary for an analysis of script relative to narrative content; Chapter Two looks at one author’s relationship with written language; and Chapters Three and Four apply the concepts explored in Chapter One to a variety of modern and contemporary literary texts where script plays a central role.
    [Show full text]
  • Legacy Character Sets & Encodings
    Legacy & Not-So-Legacy Character Sets & Encodings Ken Lunde CJKV Type Development Adobe Systems Incorporated bc ftp://ftp.oreilly.com/pub/examples/nutshell/cjkv/unicode/iuc15-tb1-slides.pdf Tutorial Overview dc • What is a character set? What is an encoding? • How are character sets and encodings different? • Legacy character sets. • Non-legacy character sets. • Legacy encodings. • How does Unicode fit it? • Code conversion issues. • Disclaimer: The focus of this tutorial is primarily on Asian (CJKV) issues, which tend to be complex from a character set and encoding standpoint. 15th International Unicode Conference Copyright © 1999 Adobe Systems Incorporated Terminology & Abbreviations dc • GB (China) — Stands for “Guo Biao” (国标 guóbiâo ). — Short for “Guojia Biaozhun” (国家标准 guójiâ biâozhün). — Means “National Standard.” • GB/T (China) — “T” stands for “Tui” (推 tuî ). — Short for “Tuijian” (推荐 tuîjiàn ). — “T” means “Recommended.” • CNS (Taiwan) — 中國國家標準 ( zhôngguó guójiâ biâozhün) in Chinese. — Abbreviation for “Chinese National Standard.” 15th International Unicode Conference Copyright © 1999 Adobe Systems Incorporated Terminology & Abbreviations (Cont’d) dc • GCCS (Hong Kong) — Abbreviation for “Government Chinese Character Set.” • JIS (Japan) — 日本工業規格 ( nihon kôgyô kikaku) in Japanese. — Abbreviation for “Japanese Industrial Standard.” — 〄 • KS (Korea) — 한국 공업 규격 (韓國工業規格 hangug gongeob gyugyeog) in Korean. — Abbreviation for “Korean Standard.” — ㉿ — Designation change from “C” to “X” on August 20, 1997. 15th International Unicode Conference Copyright © 1999 Adobe Systems Incorporated Terminology & Abbreviations (Cont’d) dc • TCVN (Vietnam) — Tiu Chun Vit Nam in Vietnamese. — Means “Vietnamese Standard.” • CJKV — Chinese, Japanese, Korean, and Vietnamese. 15th International Unicode Conference Copyright © 1999 Adobe Systems Incorporated What Is A Character Set? dc • A collection of characters that are intended to be used together to create meaningful text.
    [Show full text]
  • Japanese Language and Culture
    NIHONGO History of Japanese Language Many linguistic experts have found that there is no specific evidence linking Japanese to a single family of language. The most prominent theory says that it stems from the Altaic family(Korean, Mongolian, Tungusic, Turkish) The transition from old Japanese to Modern Japanese took place from about the 12th century to the 16th century. Sentence Structure Japanese: Tanaka-san ga piza o tabemasu. (Subject) (Object) (Verb) 田中さんが ピザを 食べます。 English: Mr. Tanaka eats a pizza. (Subject) (Verb) (Object) Where is the subject? I go to Tokyo. Japanese translation: （私が）東京に行きます。 [Watashi ga] Toukyou ni ikimasu. (Lit. Going to Tokyo.) “I” or “We” are often omitted. Hiragana, Katakana & Kanji Three types of characters are used in Japanese: Hiragana, Katakana & Kanji(Chinese characters). Mr. Tanaka goes to Canada: 田中さんはカナダに行きます [kanji][hiragana][kataka na][hiragana][kanji] [hiragana]b Two Speech Styles Distal-Style: Semi-Polite style, can be used to anyone other than family members/close friends. Direct-Style: Casual & blunt, can be used among family members and friends. In-Group/Out-Group Semi-Polite Style for Out-Group/Strangers I/We Direct-Style for Me/Us Polite Expressions Distal-Style: 1. Regular Speech 2. Ikimasu(he/I go) Honorific Speech 3. Irasshaimasu(he goes) Humble Speech Mairimasu(I/We go) Siblings: Age Matters Older Brother & Older Sister Ani & Ane 兄 と 姉 Younger Brother & Younger Sister Otooto & Imooto 弟 と 妹 My Family/Your Family My father: chichi父 Your father: otoosan My mother: haha母 お父さん My older brother: ani Your mother: okaasan お母さん Your older brother: oniisanお兄 兄 さん My older sister: ane姉 Your older sister: oneesan My younger brother: お姉さ otooto弟 ん Your younger brother: My younger sister: otootosan弟さん imooto妹 Your younger sister: imootosan 妹さん Boy Speech & Girl Speech blunt polite I/Me = watashi, boku, ore, I/Me = watashi, washi watakushi I am going = Boku iku.僕行 I am going = Watashi iku く。 wa.
    [Show full text]
  • Japanese Bibliographic Records and CJK Cataloging in U.S
    San Jose State University SJSU ScholarWorks Master's Theses Master's Theses and Graduate Research Fall 2009 Japanese bibliographic records and CJK cataloging in U.S. university libraries. Mie Onnagawa San Jose State University Follow this and additional works at: https://scholarworks.sjsu.edu/etd_theses Recommended Citation Onnagawa, Mie, "Japanese bibliographic records and CJK cataloging in U.S. university libraries." (2009). Master's Theses. 4010. DOI: https://doi.org/10.31979/etd.pcb8-mryq https://scholarworks.sjsu.edu/etd_theses/4010 This Thesis is brought to you for free and open access by the Master's Theses and Graduate Research at SJSU ScholarWorks. It has been accepted for inclusion in Master's Theses by an authorized administrator of SJSU ScholarWorks. For more information, please contact [email protected]. JAPANESE BIBLIOGRAPHIC RECORDS AND CJK CATALOGING IN U.S. UNIVERSITY LIBRARIES A Thesis Presented to The Faculty of the School of Library and Information Science San Jose State University In Partial Fulfillment of the Requirements for the Degree Master of Library and Information Science by Mie Onnagawa December 2009 UMI Number: 1484368 All rights reserved INFORMATION TO ALL USERS The quality of this reproduction is dependent upon the quality of the copy submitted. In the unlikely event that the author did not send a complete manuscript and there are missing pages, these will be noted. Also, if material had to be removed, a note will indicate the deletion. UMT Dissertation Publishing UM! 1484368 Copyright 2010 by ProQuest LLC. All rights reserved. This edition of the work is protected against unauthorized copying under Title 17, United States Code.
    [Show full text]
  • AIX Globalization
    AIX Version 7.1 AIX globalization IBM Note Before using this information and the product it supports, read the information in “Notices” on page 233 . This edition applies to AIX Version 7.1 and to all subsequent releases and modifications until otherwise indicated in new editions. © Copyright International Business Machines Corporation 2010, 2018. US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp. Contents About this document............................................................................................vii Highlighting.................................................................................................................................................vii Case-sensitivity in AIX................................................................................................................................vii ISO 9000.....................................................................................................................................................vii AIX globalization...................................................................................................1 What's new...................................................................................................................................................1 Separation of messages from programs..................................................................................................... 1 Conversion between code sets.............................................................................................................
    [Show full text]
  • International Language Environments Guide
    International Language Environments Guide Sun Microsystems, Inc. 4150 Network Circle Santa Clara, CA 95054 U.S.A. Part No: 806–6642–10 May, 2002 Copyright 2002 Sun Microsystems, Inc. 4150 Network Circle, Santa Clara, CA 95054 U.S.A. All rights reserved. This product or document is protected by copyright and distributed under licenses restricting its use, copying, distribution, and decompilation. No part of this product or document may be reproduced in any form by any means without prior written authorization of Sun and its licensors, if any. Third-party software, including font technology, is copyrighted and licensed from Sun suppliers. Parts of the product may be derived from Berkeley BSD systems, licensed from the University of California. UNIX is a registered trademark in the U.S. and other countries, exclusively licensed through X/Open Company, Ltd. Sun, Sun Microsystems, the Sun logo, docs.sun.com, AnswerBook, AnswerBook2, Java, XView, ToolTalk, Solstice AdminTools, SunVideo and Solaris are trademarks, registered trademarks, or service marks of Sun Microsystems, Inc. in the U.S. and other countries. All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. in the U.S. and other countries. Products bearing SPARC trademarks are based upon an architecture developed by Sun Microsystems, Inc. SunOS, Solaris, X11, SPARC, UNIX, PostScript, OpenWindows, AnswerBook, SunExpress, SPARCprinter, JumpStart, Xlib The OPEN LOOK and Sun™ Graphical User Interface was developed by Sun Microsystems, Inc. for its users and licensees. Sun acknowledges the pioneering efforts of Xerox in researching and developing the concept of visual or graphical user interfaces for the computer industry.
    [Show full text]