DOCSLIB.ORG

Microej Documentation

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Microej Documentation MicroEJ Documentation MicroEJ Corp. Revision 155af8f7 Jul 08, 2021 Copyright 2008-2020, MicroEJ Corp. Content in this space is free for read and redistribute. Except if otherwise stated, modification is subject to MicroEJ Corp prior approval. MicroEJ is a trademark of MicroEJ Corp. All other trademarks and copyrights are the property of their respective owners. CONTENTS 1 MicroEJ Glossary 2 2 Overview 4 2.1 MicroEJ Editions.............................................4 2.1.1 Introduction..........................................4 2.1.2 Determine the MicroEJ Studio/SDK Version..........................5 2.2 Licenses.................................................7 2.2.1 License Manager Overview...................................7 2.2.2 Evaluation Licenses......................................7 2.2.3 Production Licenses...................................... 10 2.3 MicroEJ Runtime............................................. 15 2.3.1 Language............................................ 15 2.3.2 Scheduler............................................ 15 2.3.3 Garbage Collector....................................... 15 2.3.4 Foundation Libraries...................................... 15 2.4 MicroEJ Libraries............................................ 16 2.5 MicroEJ Central Repository....................................... 16 2.5.1 Introduction.......................................... 16 2.5.2 Use............................................... 17 2.5.3 Content Organization..................................... 17 2.5.4 Javadoc............................................. 17 2.6 Embedded Specification Requests................................... 17 2.7 MicroEJ Firmware............................................ 17 2.7.1 Bootable Binary with Core Services.............................. 17 2.7.2 Specification.......................................... 18 2.8 MicroEJ SDK............................................... 18 2.8.1 Release Notes.......................................... 19 2.8.2 MicroEJ SDK Distribution Changelog............................. 19 2.8.3 MicroEJ SDK Changelog.................................... 21 2.8.4 Advanced Installation Notes.................................. 31 2.8.5 Migration Notes......................................... 31 2.9 Introducing MicroEJ Studio and Virtual Devices............................ 34 2.10 Perform Online Getting Started..................................... 35 2.11 GitHub Repositories........................................... 36 2.12 System Requirements.......................................... 41 2.13 Get Support............................................... 42 3 Application Developer Guide 43 3.1 Introduction............................................... 43 3.2 Local Workspaces and Repositories................................... 43 i 3.3 Standalone Application......................................... 44 3.3.1 MicroEJ Platform Import.................................... 44 3.3.2 Build and Run an Application................................. 47 3.3.3 Build Output Files....................................... 52 3.3.4 MicroEJ Launch......................................... 53 3.3.5 Application Options...................................... 57 3.3.6 SOAR.............................................. 84 3.4 Sandboxed Application......................................... 85 3.4.1 Sandboxed Application Structure............................... 85 3.4.2 Application Publication.................................... 86 3.4.3 Shared Interfaces........................................ 86 3.5 Virtual Device.............................................. 90 3.5.1 Using a Virtual Device for Simulation............................. 90 3.5.2 Runtime Environment..................................... 90 3.6 MicroEJ Module Manager........................................ 91 3.6.1 Introduction.......................................... 91 3.6.2 Specification.......................................... 92 3.6.3 Module Project Skeleton.................................... 92 3.6.4 Module Description File.................................... 93 3.6.5 MicroEJ Module Manager Configuration........................... 95 3.6.6 Module Build.......................................... 99 3.6.7 Build Kit............................................. 100 3.6.8 Command Line Interface.................................... 101 3.6.9 Troubleshooting........................................ 105 3.6.10 Meta Build........................................... 107 3.6.11 Former MicroEJ SDK Versions (lower than 5.2.0)....................... 108 3.6.12 Former MicroEJ SDK Versions (from 5.2.0 to 5.3.x)...................... 110 3.7 Module Natures............................................. 110 3.7.1 Add-On Library......................................... 110 3.7.2 Add-On Processor....................................... 111 3.7.3 Foundation Library API..................................... 111 3.7.4 Foundation Library Implementation............................. 111 3.7.5 Meta Build........................................... 112 3.7.6 Mock.............................................. 112 3.7.7 Module Repository....................................... 112 3.7.8 Sandboxed Application.................................... 113 3.7.9 Standalone Application.................................... 114 3.7.10 Natures Plugins......................................... 114 3.8 Module Repository............................................ 119 3.8.1 Create a Repository Project.................................. 121 3.8.2 Configure Resolver for Input Modules............................. 121 3.8.3 Configure Consistency Check................................. 121 3.8.4 Advanced Options....................................... 121 3.8.5 Include Modules........................................ 121 3.8.6 Build the Repository...................................... 123 3.8.7 Use the Oline Repository................................... 123 3.9 MicroEJ Classpath............................................ 123 3.9.1 Application Classpath..................................... 124 3.9.2 Classpath Load Model..................................... 124 3.9.3 Classpath Elements...................................... 125 3.10 Application Resources.......................................... 128 3.10.1 Images............................................. 128 3.10.2 Fonts.............................................. 129 3.10.3 Native Language Support................................... 130 ii 3.11 Platform Selection............................................ 131 3.12 Development Tools........................................... 132 3.12.1 Test Suite with JUnit...................................... 133 3.12.2 Stack Trace Reader....................................... 137 3.12.3 Code Coverage Analyzer.................................... 150 3.12.4 Heap Usage Monitoring.................................... 153 3.12.5 Heap Dumper & Heap Analyzer................................ 155 3.12.6 ELF to Map File Generator................................... 166 3.12.7 Serial to Socket Transmitter.................................. 168 3.12.8 Memory Map Analyzer..................................... 169 3.12.9 Event Tracing.......................................... 172 3.12.10 Null Analysis.......................................... 174 3.13 Advanced Tools............................................. 181 3.13.1 MicroEJ Linker......................................... 181 3.13.2 MicroEJ Test Suite Engine................................... 193 3.14 Graphical User Interface......................................... 199 3.14.1 MicroUI............................................. 200 3.14.2 MWT (Micro Widget Toolkit).................................. 231 3.14.3 Widgets and Examples..................................... 248 3.15 Limitations................................................ 250 4 Platform Developer Guide 251 4.1 Introduction............................................... 251 4.1.1 Scope.............................................. 251 4.1.2 Intended Audience....................................... 251 4.2 MicroEJ Platform............................................ 251 4.2.1 Introduction.......................................... 251 4.2.2 Build Process.......................................... 252 4.2.3 Concepts............................................ 253 4.3 MicroEJ Architecture........................................... 258 4.3.1 Naming Convention...................................... 259 4.3.2 MicroEJ Architectures Changelog............................... 260 4.4 MicroEJ Packs.............................................. 281 4.4.1 Overview............................................ 281 4.4.2 Naming Convention...................................... 282 4.5 Platform Creation............................................ 283 4.5.1 Architecture Selection..................................... 283 4.5.2 Platform Configuration..................................... 283 4.5.3 Pack Import........................................... 284 4.5.4 Platform Build......................................... 285 4.5.5 Platform Module Configuration................................ 287 4.5.6 Platform Customization.................................... 290 4.5.7 BSP Connection........................................ 290 4.6 Platform Qualification.......................................... 296 4.6.1 Introduction.......................................... 296 4.6.2 Platform Qualification Tools Overview............................ 297 4.6.3 Platform
Load more

Recommended publications
  • Assessment of Options for Handling Full Unicode Character Encodings in MARC21 a Study for the Library of Congress
    1 Assessment of Options for Handling Full Unicode Character Encodings in MARC21 A Study for the Library of Congress Part 1: New Scripts Jack Cain Senior Consultant Trylus Computing, Toronto 1 Purpose This assessment intends to study the issues and make recommendations on the possible expansion of the character set repertoire for bibliographic records in MARC21 format. 1.1 “Encoding Scheme” vs. “Repertoire” An encoding scheme contains codes by which characters are represented in computer memory. These codes are organized according to a certain methodology called an encoding scheme. The list of all characters so encoded is referred to as the “repertoire” of characters in the given encoding schemes. For example, ASCII is one encoding scheme, perhaps the one best known to the average non-technical person in North America. “A”, “B”, & “C” are three characters in the repertoire of this encoding scheme. These three characters are assigned encodings 41, 42 & 43 in ASCII (expressed here in hexadecimal). 1.2 MARC8 "MARC8" is the term commonly used to refer both to the encoding scheme and its repertoire as used in MARC records up to 1998. The ‘8’ refers to the fact that, unlike Unicode which is a multi-byte per character code set, the MARC8 encoding scheme is principally made up of multiple one byte tables in which each character is encoded using a single 8 bit byte. (It also includes the EACC set which actually uses fixed length 3 bytes per character.) (For details on MARC8 and its specifications see: http://www.loc.gov/marc/.) MARC8 was introduced around 1968 and was initially limited to essentially Latin script only.
    [Show full text]
  • COSC345 Week 24 Internationalisation And
    COSC345 Week 24 Internationalisation and Localisation 29 September 2015 Richard A. O'Keefe 1 From a Swedish h^otelroom Hj¨alposs att v¨arnerom v˚armilj¨o! F¨oratt minska utsl¨appav tv¨attmedel, byter vi Er handduk bara n¨arNi vill: 1. Handduk p˚agolvet | betyder att Ni vill ha byte 2. ... 2 The translation Help us to care for our environment! To reduce the use of laundry detergents, we shall change your towel as follows: 1. Towel on the floor | you want to have a new towel. 2. Towel hung up | you want to use it again. 3 People should be able to use computers in their own language. | It's just right not to make people struggle with unfamiliar lin- guistic and cultural codes. | Sensible people won't pay for programs that are hard to use. | Internationalisation (I18N) means making a program so that it does not enforce a particular language or set of cultural conventions | Localisation (L10N) means adapting an internationalised pro- gram to a particular language etc. | UNIX, VMS, Windows, all support internationalisation and lo- calisation; the Macintosh operating system has done this better for longer. 4 Characters You know that there are 26 letters in 2 cases. But Swedish has ˚a,¨a,¨o, A,˚ A,¨ and O¨ (29 letters), Croatian has d j, D j, D J, and others (3 cases), German has ß, which has no single upper case version (might be SS, might be SZ, both of which are two letters), Latin-1 has 58 letters in 2 cases (including 2 lower case letters with no upper case version), Arabic letters have 4 contextual shapes (beginning, middle, or end of word, or isolated), which are not case variants (Greek has one such letter, and Hebrew has several; even English used to), and Chinese has tens of thousands of characters.
    [Show full text]
  • Proposal for Ethiopic Script Root Zone LGR
    Proposal for Ethiopic Script Root Zone LGR LGR Version 2 Date: 2017-05-17 Document version:5.2 Authors: Ethiopic Script Generation Panel Contents 1 General Information/ Overview/ Abstract ........................................................................................ 3 2 Script for which the LGR is proposed ................................................................................................ 3 3 Background on Script and Principal Languages Using It .................................................................... 4 3.1 Local Languages Using the Script .............................................................................................. 4 3.2 Geographic Territories of the Language or the Language Map of Ethiopia ................................ 7 4 Overall Development Process and Methodology .............................................................................. 8 4.1 Sources Consulted to Determine the Repertoire....................................................................... 8 4.2 Team Composition and Diversity .............................................................................................. 9 4.3 Analysis of Code Point Repertoire .......................................................................................... 10 4.4 Analysis of Code Point Variants .............................................................................................. 11 5 Repertoire ....................................................................................................................................
    [Show full text]
  • Release Notes What's
    Release Notes Amster is a lightweight command-line interface, ideal for use in DevOps processes, such as continuous integration and deployment. Read these release notes before you install Amster. The information contained in these release notes cover prerequisites for installation, known issues and improvements to the software, changes and deprecated functionality, and other important information. ForgeRock Identity Platform® serves as the basis for our simple and comprehensive Identity and Access Management solution. We help our customers deepen their relationships with their customers, and improve the productivity and connectivity of their employees and partners. For more information about ForgeRock and about the platform, see https://www.forgerock.com. What’s New This page covers new features and improvements in Amster. What’s New in Amster 7.1 Support for AM 7.1 or Later Only Amster 7.1 supports exporting and importing conguration from AM 7.1 or later. If you have a previous version of Amster: 1. Perform a fresh installation of Amster 7.1. For more information, see Install Amster. 2. Migrate any Amster Groovy scripts from the previous Amster installation. Take into account any changes in functionality. 3. Convert any JSON conguration les that were exported from AM 5 or later. The AM 7.1 ZIP le includes a conguration le upgrade tool. For more information on converting conguration les for import into AM 7.1, see the README.md le in the Config-Upgrader-7.1.0.zip le. 4. Test the new Amster installation. 5. Delete the previous Amster installation. Before You Install This page covers software and hardware prerequisites for installing and running Amster.
    [Show full text]
  • Lic. Ciências Da Computação Estrutura Do Tema ISC
    Introdução aos Sistemas de Computação Sistemas de Computação (1) Lic. Ciências da Computação Estrutura do tema ISC 1º ano 1. Representação de informação num computador 2007/08 2. Organização e estrutura interna dum computador A.J.Proença 3. Execução de programas num computador 4. O processador e a memória num computador 5. Da comunicação de dados às redes Tema Introdução aos Sistemas de Computação AJProença, Sistemas de Computação, UMinho, 2007/08 1 AJProença, Sistemas de Computação, UMinho, 2007/08 2 Noção de computador (1) Noção de computador (2) Um computador é um sistema que: Computador tipo – recebe informação, processa / arquiva informação, Sinais Processador Sinais transmite informação, e ... Digitais Periférico / (1 ou +) Periférico / Digitais –é programável Sinais Sinais Dispositivo Dispositivo i.e., a funcionalidade do sistema pode ser modificada, Digitais Digitais sem alterar fisicamente o sistema Entrada Memória Saída Sinais Sinais primária Quando a funcionalidade é fixada no fabrico do sistema onde o Analógicos Analógicos computador se integra, diz-se que o computador existente nesse sistema está “embebido”: ex. telemóvel, máq. fotográfica digital, automóvel, ... Arquivo Como se representa a informação num computador ? Informação Como se processa a informação num computador ? AJProença, Sistemas de Computação, UMinho, 2007/08 3 AJProença, Sistemas de Computação, UMinho, 2007/08 4 Representação da informação Noção de computador (3) num computador (1) Como se representa a informação? –com binary digits! (ver sistemas de numeração...) • Como se representa a informação num computador ? Tipos de informação a representar: – representação da informação num computador -> – textos (caracteres alfanuméricos) » Baudot, Braille, ASCII, Unicode, ... – números (para cálculo) » inteiros: S+M, Compl. p/ 1, Compl.
    [Show full text]
  • Online Difference Between Java Se Development Kit and Java Update
    Difference between java se development kit and java update // Check if "Hello.java" exists using list (ls) command. Java SE 10 (18.3) (JDK 10) (March 2018): Introduced var for type inference local variable (similar to JavaScript). Introduced time-based release versioning with two releases each year, in March and September, denoted as YY.M. Removed native-header generation tool javah. See " JDK 10 New Features ". Java SE 7 (JDK 7) (July 2011): First version after Oracle purchased Sun Microsystem - aslo called OracleJDK. Introduced Strings in switch statement, Binary integer literals, allowing underscores in numeric literals, improved type inference for generic instance creation (or diamond operator. Differences between Java EE, Java SE, Java ME and JavaFX. Technical definition: The JDK is an implementation of the Java platform specification, including compiler and class libraries. is your installation update number⇒ Select "Move Up" to move this entry all the way to the TOP. JDK shall be extracted in a folder " /usr/local/java/jdk-15.0.{x} ", where {x}. Wann muss ich für die Nutzung von Java bezahlen?. Is Java 1.8 the Same As Java 8? The JRE runs the JVM. The JVM runs your Java application. You build your Java application with the JDK. Get monthly updates about new articles, cheatsheets, and tricks. ) provides a free and open-source JDK official reference implementation. The -cp switch tells Java to add the jar to the classpath. A.jar file is overkill for this tiny program, but they're indispensable as programs grow in size and rely on third-party packages. The JDK in your IDE Looking back to the JDK download page, you may have noticed the option to download the JDK with the Netbeans IDE.
    [Show full text]
  • R Installation and Administration Version 4.2.0 Under Development (2021-09-23)
    R Installation and Administration Version 4.2.0 Under development (2021-09-23) R Core Team This manual is for R, version 4.2.0 Under development (2021-09-23). Copyright c 2001{2021 R Core Team Permission is granted to make and distribute verbatim copies of this manual provided the copyright notice and this permission notice are preserved on all copies. Permission is granted to copy and distribute modified versions of this manual under the conditions for verbatim copying, provided that the entire resulting derived work is distributed under the terms of a permission notice identical to this one. Permission is granted to copy and distribute translations of this manual into an- other language, under the above conditions for modified versions, except that this permission notice may be stated in a translation approved by the R Core Team. i Table of Contents 1 Obtaining R :::::::::::::::::::::::::::::::::::::::::::::::::::: 1 1.1 Getting and unpacking the sources ::::::::::::::::::::::::::::::::::::::::::::::::: 1 1.2 Getting patched and development versions ::::::::::::::::::::::::::::::::::::::::: 1 1.2.1 Using Subversion and rsync ::::::::::::::::::::::::::::::::::::::::::::::::::: 1 2 Installing R under Unix-alikes :::::::::::::::::::::::::::::::: 3 2.1 Simple compilation :::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: 3 2.2 Help options ::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: 4 2.3 Making the manuals ::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: 5 2.4 Installation ::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::
    [Show full text]
  • Universal Multiple-Octet Coded Character Set (UCS) —
    ISO/IEC JTC1 SC2/WG2 N2845 all Final Proposed Draft Amendment (FPDAM) 1 ISO/IEC 10646:2003/Amd.1:2004 (E) Information technology — Universal Multiple-Octet Coded Character Set (UCS) — AMENDMENT 1: Glagolitic, Coptic, Georgian and other characters In the definition of Graphic character (formerly sub- Page 1, Clause 1 Scope clause 4.20, now 4.22), insert “or a format character” In the note, update the Unicode Standard version after “control function”. from 4.0 to 4.1. Page 2, Clause 3 Normative references Page 14, Clause 19 Characters in bidirectional context Update the reference to the Unicode Bidirectional Algorithm and the Unicode Normalization Forms as Add ‘Mirrored’ before ‘Character’ in clause title and follows: replace the text of the clause by the following: Unicode Standard Annex, UAX#9, The Unicode Bidi- A class of character has special significance in the rectional Algorithm, Version 4.1.0, [date TBD]. context of bidirectional text. The interpretation and rendering of any of these characters depend on the Unicode Standard Annex, UAX#15, Unicode Nor- state related to the symmetric swapping characters malization Forms, Version 4.1.0, [date TBD]. (see clause F.2.2) and on the direction of the char- acter being rendered that are in effect at the point in the CC-data-element where the coded representa- Page 2, Clause Terms and definitions tion of the character appears. The list of these char- Insert the following text as sub-clause 4.1 and Note; acters is provided in Annex E.1. update all following sub-clause numbers accord- NOTE – That list also represents all characters which have ingly.
    [Show full text]
  • Section 18.1, Han
    The Unicode® Standard Version 13.0 – Core Specification To learn about the latest version of the Unicode Standard, see http://www.unicode.org/versions/latest/. Many of the designations used by manufacturers and sellers to distinguish their products are claimed as trademarks. Where those designations appear in this book, and the publisher was aware of a trade- mark claim, the designations have been printed with initial capital letters or in all capitals. Unicode and the Unicode Logo are registered trademarks of Unicode, Inc., in the United States and other countries. The authors and publisher have taken care in the preparation of this specification, but make no expressed or implied warranty of any kind and assume no responsibility for errors or omissions. No liability is assumed for incidental or consequential damages in connection with or arising out of the use of the information or programs contained herein. The Unicode Character Database and other files are provided as-is by Unicode, Inc. No claims are made as to fitness for any particular purpose. No warranties of any kind are expressed or implied. The recipient agrees to determine applicability of information provided. © 2020 Unicode, Inc. All rights reserved. This publication is protected by copyright, and permission must be obtained from the publisher prior to any prohibited reproduction. For information regarding permissions, inquire at http://www.unicode.org/reporting.html. For information about the Unicode terms of use, please see http://www.unicode.org/copyright.html. The Unicode Standard / the Unicode Consortium; edited by the Unicode Consortium. — Version 13.0. Includes index. ISBN 978-1-936213-26-9 (http://www.unicode.org/versions/Unicode13.0.0/) 1.
    [Show full text]
  • JVM Ecosystem Report 2021 Table of Contents
    JVM Ecosystem Report 2021 Table of contents Introduction 3 Report highlights 4 JDKs in production 5 JDKs in development 7 JDK versions in production environments 9 JDK versions in development 11 Java, Changing Faster Than Ever After 26 Years 12 JVM languages used for applications in production 14 Most popular IDEs 18 Tools for building applications 20 Securing vulnerabilities in the Java ecosystem with Snyk 22 Application frameworks 25 Demographics 26 The State of Spring 29 Introduction Welcome to our annual JVM ecosystem report! This report presents the results of the largest annual survey on the state of the JVM ecosystem. The survey was conducted over a period of six weeks through February and March 2021, gathering the responses of over 2000 Java developers. This year's survey is a cooperation between Snyk and Azul and was slightly different from the previous surveys. We aimed for the survey to be more concise and focus only on the most important aspects of JVM developers today. Additionally, this year every participant was allowed to choose multiple options. We believe that the way the 2021 survey was designed, we have a better and more comprehensive view of the current JVM ecosystem. In addition, in this report, we also looked at different open data sources like GitHub and Google Trends to see how that data compares to the survey results. We would like to thank everyone who participated and offered their insights on Java and JVM-related topics. For this survey, we teamed up with conferences and communities across the JVM ecosystem to reach as many developers as possible.
    [Show full text]
  • Relationship to ISO/IEC 10646 C
    The Unicode® Standard Version 13.0 – Core Specification To learn about the latest version of the Unicode Standard, see http://www.unicode.org/versions/latest/. Many of the designations used by manufacturers and sellers to distinguish their products are claimed as trademarks. Where those designations appear in this book, and the publisher was aware of a trade- mark claim, the designations have been printed with initial capital letters or in all capitals. Unicode and the Unicode Logo are registered trademarks of Unicode, Inc., in the United States and other countries. The authors and publisher have taken care in the preparation of this specification, but make no expressed or implied warranty of any kind and assume no responsibility for errors or omissions. No liability is assumed for incidental or consequential damages in connection with or arising out of the use of the information or programs contained herein. The Unicode Character Database and other files are provided as-is by Unicode, Inc. No claims are made as to fitness for any particular purpose. No warranties of any kind are expressed or implied. The recipient agrees to determine applicability of information provided. © 2020 Unicode, Inc. All rights reserved. This publication is protected by copyright, and permission must be obtained from the publisher prior to any prohibited reproduction. For information regarding permissions, inquire at http://www.unicode.org/reporting.html. For information about the Unicode terms of use, please see http://www.unicode.org/copyright.html. The Unicode Standard / the Unicode Consortium; edited by the Unicode Consortium. — Version 13.0. Includes index. ISBN 978-1-936213-26-9 (http://www.unicode.org/versions/Unicode13.0.0/) 1.
    [Show full text]
  • The Unicode Standard, Version 4.0--Online Edition
    This PDF file is an excerpt from The Unicode Standard, Version 4.0, issued by the Unicode Consor- tium and published by Addison-Wesley. The material has been modified slightly for this online edi- tion, however the PDF files have not been modified to reflect the corrections found on the Updates and Errata page (http://www.unicode.org/errata/). For information on more recent versions of the standard, see http://www.unicode.org/standard/versions/enumeratedversions.html. Many of the designations used by manufacturers and sellers to distinguish their products are claimed as trademarks. Where those designations appear in this book, and Addison-Wesley was aware of a trademark claim, the designations have been printed in initial capital letters. However, not all words in initial capital letters are trademark designations. The Unicode® Consortium is a registered trademark, and Unicode™ is a trademark of Unicode, Inc. The Unicode logo is a trademark of Unicode, Inc., and may be registered in some jurisdictions. The authors and publisher have taken care in preparation of this book, but make no expressed or implied warranty of any kind and assume no responsibility for errors or omissions. No liability is assumed for incidental or consequential damages in connection with or arising out of the use of the information or programs contained herein. The Unicode Character Database and other files are provided as-is by Unicode®, Inc. No claims are made as to fitness for any particular purpose. No warranties of any kind are expressed or implied. The recipient agrees to determine applicability of information provided. Dai Kan-Wa Jiten used as the source of reference Kanji codes was written by Tetsuji Morohashi and published by Taishukan Shoten.
    [Show full text]