Japanese Compound Words Formed by The Lexeme ‘Ear’: A Morphological Study

Authors

  • Made Henra Dwikarmawan Sudipa Universitas Mahasaraswati
  • I Wayan Wahyu Cipta Widiastika Universitas Mahasaraswati

Keywords:

linguistics, morphology, compound, Japanese

Abstract

In Japanese, there are frequently used characters in compound words. One is the kanji character ? which reads "mimi" and can be translated into ‘ear’. Although the lexeme “mimi” means ‘ear’ and functions as a noun, it can take on various forms and meanings when coupled with other lexemes. As a result, the main objective of this study is to examine the forms and meanings of Japanese compound words formed by the lexeme ‘ear’. The data was collected from the Japanese corpus from Tsukuba Web Corpus using observation and note-taking techniques. Then the data was analyzed using the identity method. The theory used to analyze the construction and meaning of Japanese compounds is the morphology theory by Katamba (1993), Tsujimura (1996), and Kageyama (2016). The results of this research show that there are 20 Japanese compound words formed with the lexeme "mimi." These compounds consist of two lexemes, with "mimi" either appearing first, followed by different words, or at the end of the compound. The combinations include compound nouns (N+N, V+N, and N+V), compound adjectives (N+ADJ and N+V), and compound verbs (N+V). Based on their meanings, the compounds can be divided into two categories: endocentric and exocentric compounds.

Downloads

Published

2024-11-14

How to Cite

Made Henra Dwikarmawan Sudipa, & I Wayan Wahyu Cipta Widiastika. (2024). Japanese Compound Words Formed by The Lexeme ‘Ear’: A Morphological Study . Proceeding of International Conference on Japanese Studies, Language and Education, 5(1), 18-27. Retrieved from http://proceedings.aspbji.id/index.php/icjsle/article/view/82

Issue

Vol. 5 No. 1 (2024): Proceeding of International Conference on Japanese Studies, Language and Education (ICJSLE)

Section

Articles 
                                                                  ADOConnection.CacheExecute(3600, SELECT 				o.submission_id, 				MAX(s.context_id) AS journal_id, 				MAX(i.date_published) AS i_pub, 				MAX(p.date_published) A..., Array[2]) % line  132, file: DAO.inc.php
                                                               DAO.retrieveCached(SELECT 				o.submission_id, 				MAX(s.context_id) AS journal_id, 				MAX(i.date_published) AS i_pub, 				MAX(p.date_published) A..., Array[2], 3600) % line   91, file: ArticleSearchDAO.inc.php
                                                            ArticleSearchDAO.getPhraseResults(Object:Journal, Array[1], null, null, , 500, 1) % line  207, file: SubmissionSearch.inc.php
                                                         SubmissionSearch._getMergedPhraseResults(Object:Journal, Array[1], , null, null, 500, 1) % line  146, file: SubmissionSearch.inc.php
                                                      SubmissionSearch._getMergedKeywordResults(Object:Journal, Array[4], , null, null, 500, 1) % line  194, file: SubmissionSearch.inc.php
                                                   SubmissionSearch._getMergedPhraseResults(Object:Journal, Array[4], null, null, null, 500, 1) % line  146, file: SubmissionSearch.inc.php
                                                SubmissionSearch._getMergedKeywordResults(Object:Journal, Array[3], null, null, null, 500, 1) % line  132, file: SubmissionSearch.inc.php
                                             SubmissionSearch._getMergedArray(Object:Journal, Array[1], null, null) % line  263, file: SubmissionSearch.inc.php
                                          SubmissionSearch.retrieveResults(Object:Request, Object:Journal, Array[1], null, null, null, Object:DBResultRange, Array[1]) % line   92, file: RecommendBySimilarityPlugin.inc.php
                                       RecommendBySimilarityPlugin.callbackTemplateArticlePageFooter(Templates::Article::Footer::PageFooter, Array[3]) % line  107, file: HookRegistry.inc.php
                                    HookRegistry.call(Templates::Article::Footer::PageFooter, Array[3]) % line 1254, file: PKPTemplateManager.inc.php
                                 PKPTemplateManager.smartyCallHook(Array[1], Object:Smarty_Internal_Template) % line   43, file: 42362804174f266c598cdb32c3208fc745b92101^1c372c95cd85572e0fbc9a53d0323a0b229cfc78_0.app.frontendpagesarticle.tpl.php
                              content_607e89427493a7_25097553(Object:Smarty_Internal_Template) % line  123, file: smarty_template_resource_base.php
                           Smarty_Template_Resource_Base.getRenderedTemplateCode(Object:Smarty_Internal_Template) % line  114, file: smarty_template_compiled.php
                        Smarty_Template_Compiled.render(Object:Smarty_Internal_Template) % line  216, file: smarty_internal_template.php
                     Smarty_Internal_Template.render(false, 1) % line  232, file: smarty_internal_templatebase.php
                  Smarty_Internal_TemplateBase._execute(Object:Smarty_Internal_Template, null, 42362804174f266c598cdb32c3208fc745b92101, null, 1) % line  134, file: smarty_internal_templatebase.php
               Smarty_Internal_TemplateBase.display(frontend/pages/article.tpl, null, 42362804174f266c598cdb32c3208fc745b92101, null) % line  922, file: PKPTemplateManager.inc.php
            PKPTemplateManager.display(frontend/pages/article.tpl) % line  281, file: ArticleHandler.inc.php
         ArticleHandler.view(Array[1], Object:Request) % line  391, file: PKPRouter.inc.php
      PKPRouter._authorizeInitializeAndCallRequest(Array[2], Object:Request, Array[1], false) % line  231, file: PKPPageRouter.inc.php
   PKPPageRouter.route(Object:Request) % line  143, file: Dispatcher.inc.php
Dispatcher.dispatch(Object:Request) % line  279, file: PKPApplication.inc.php
PKPApplication.execute() % line   68, file: index.php