ANALYSIS OF THE MEANING OF THE VERB OSU AS A POLYSEMY IN JAPANESE SENTENCES: A COGNITIVE LINGUISTIC STUDY

Authors

  • Edi Syofyan Universitas Pendidikan Indonesia, Bandung, Indonesia
  • Dedi Sutedi Universitas Pendidikan Indonesia, Bandung, Indonesia
  • Nuria Haristiani Universitas Pendidikan Indonesia, Bandung, Indonesia

Keywords:

meaning, osu, polysemy

Abstract

In every language, especially Japanese, there is often a meaning relationship between a word and another word. One of these meaning relationships is polysemy. Polysemy is a word that has more than one meaning. This study provides a comprehensive explanation of the meaning of the verb osu and contributes to Japanese language learning. Although the verb osu is discussed in basic-level textbooks, the current dictionary descriptions do not always provide enough information for sentence construction. Therefore, a polysemy analysis was conducted. The purpose of this study is to find out what the basic meaning of the verb osu is, what meanings are contained in the verb osu, and to find out the relationship between the meanings of the verb osu. The method used in this research is the descriptive analysis method. Data from various sources were collected, arranged, classified, and then analyzed. The results of the analysis show that the various meanings of the verb osu are derived from the basic meaning. The relationship between the meanings of the verb osu can be seen from three language styles, namely metaphor, metonymy, and synecdoche.

Downloads

Published

2023-01-08

How to Cite

Syofyan, E., Sutedi, D., & Haristiani, N. (2023). ANALYSIS OF THE MEANING OF THE VERB OSU AS A POLYSEMY IN JAPANESE SENTENCES: A COGNITIVE LINGUISTIC STUDY. Proceeding of International Conference on Japanese Studies, Language and Education, 3(1), 17-23. Retrieved from http://proceedings.aspbji.id/index.php/icjsle/article/view/55

Issue

Vol. 3 No. 1 (2022): 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