Heavy Rotation: The Phenomenon of Mixed Languages in JKT48's Popular Song

Authors

  • Zida Wahyuddin Universitas 17 Agustus 1945 Surabaya
  • Eva Amalijah Universitas 17 Agustus 1945 Surabaya

Keywords:

Mixed Languages, Popular Song, Lyrics, JKT48, Heavy Rotation

Abstract

The development of information technology in the global era has resulted in the melting of the boundaries of human life in various aspects. One of the most visible aspects is culture. The entry of global culture penetrates the boundaries of local culture. In global culture, there is a mixture of various cultures. The results of mixing cultures can no longer be equated with the original culture. The emergence of new cultural patterns is sometimes surprising and difficult to understand. Language is an important element of culture. Mixed language is widely used in this limitless digital era. The widespread use of mixed language can be seen in the popular culture of song lyrics. Songs can be interpreted as a form of communication media as well as a cultural product. As an element of culture, language is able to represent social changes that occur in the midst of the people who use it. The use of mixed language in song lyrics is interesting to study as an entry point for further study of the socio-cultural dynamics of society. The cultural studies approach with a postmodern critical perspective uses the discourse analysis method to become a scalpel used to reveal what is the background, motive, or ideology of the use of mixed language in song lyrics. From this research, it can be understood that there is a cultural struggle between the "superior" culture and the inferior culture. Domination and hegemony occur symbolically, a form of latent danger to harmony in existing cultural diversity.

Downloads

Published

2023-11-30

How to Cite

Zida Wahyuddin, & Eva Amalijah. (2023). Heavy Rotation: The Phenomenon of Mixed Languages in JKT48’s Popular Song. Proceeding of International Conference on Japanese Studies, Language and Education, 4(1), 135-146. Retrieved from http://proceedings.aspbji.id/index.php/icjsle/article/view/76
                                                                  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_6a3770fdf00ec2_07411404(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