<node id="681690">
  <nid>681690</nid>
  <type>news</type>
  <uid>
    <user id="27513"><![CDATA[27513]]></user>
  </uid>
  <created>1744216214</created>
  <changed>1744216241</changed>
  <title><![CDATA[Code Switching in the Digital World]]></title>
  <body><![CDATA[<p><em><strong>Technology has transformed how we communicate. Research from the Ivan Allen College of Liberal Arts shows that code-switching — the practice of switching between languages, dialects, accents, tones, or cultures in conversation — is changing with it.</strong></em></p><p>Faculty members in the School of Modern Languages and the Sam Nunn School of International Affairs have published three studies examining how language and cultural code-switching have adapted to the digital age, revealing speakers’ fluency, promoting self-expression, and making messaging more effective. Their research is relevant, as the population of bilingual and bicultural people increases in the United States.</p><p>By better understanding code-switching in digital spaces, “we can reveal insights into language dynamics and cultural identity among young bilingual speakers,” says Hongchen Wu, an assistant professor in the School of Modern Languages. “Annotated code-switching datasets are also a valuable resource for training and testing language technologies tailored to bilingual speakers — allowing, for example, an AI-assistant that can understand their code-switching with no struggles.”</p><p><a href="https://modlangs.gatech.edu/featured-news/2025/04/code-switching-digital-world">Read the full article published by Georgia Tech's School of Modern Languages and the Sam Nunn School of International Affairs &gt;&gt;</a></p>]]></body>
  <field_subtitle>
    <item>
      <value><![CDATA[]]></value>
    </item>
  </field_subtitle>
  <field_dateline>
    <item>
      <value>2025-04-09T00:00:00-04:00</value>
      <timezone><![CDATA[America/New_York]]></timezone>
    </item>
  </field_dateline>
  <field_summary_sentence>
    <item>
      <value><![CDATA[Technology has transformed how we communicate. ]]></value>
    </item>
  </field_summary_sentence>
  <field_summary>
    <item>
      <value><![CDATA[<p>Technology has transformed how we communicate.&nbsp;</p>]]></value>
    </item>
  </field_summary>
  <field_media>
          <item>
        <nid>
          <node id="676802">
            <nid>676802</nid>
            <type>image</type>
            <title><![CDATA[Code Switching in the Digital World]]></title>
            <body><![CDATA[]]></body>
                          <field_image>
                <item>
                  <fid>260644</fid>
                  <filename><![CDATA[screen_898.png]]></filename>
                  <filepath><![CDATA[/sites/default/files/2025/04/09/screen_898.png]]></filepath>
                  <file_full_path><![CDATA[http://hg.gatech.edu//sites/default/files/2025/04/09/screen_898.png]]></file_full_path>
                  <filemime>image/png</filemime>
                  <image_740><![CDATA[]]></image_740>
                  <image_alt><![CDATA[Code Switching in the Digital World - header image]]></image_alt>
                </item>
              </field_image>
            
                      </node>
        </nid>
      </item>
      </field_media>
  <field_contact_email>
    <item>
      <email><![CDATA[]]></email>
    </item>
  </field_contact_email>
  <field_location>
    <item>
      <value><![CDATA[]]></value>
    </item>
  </field_location>
  <field_contact>
    <item>
      <value><![CDATA[]]></value>
    </item>
  </field_contact>
  <field_sidebar>
    <item>
      <value><![CDATA[]]></value>
    </item>
  </field_sidebar>
  <field_boilerplate>
    <item>
      <nid><![CDATA[]]></nid>
    </item>
  </field_boilerplate>
  <!--  TO DO: correct to not conflate categories and news room topics  -->
  <!--  Disquisition: it's funny how I write these TODOs and then never
         revisit them. It's as though the act of writing the thing down frees me
         from the responsibility to actually solve the problem. But what can I
         say? There are more problems than there's time to solve.  -->
  <links_related> </links_related>
  <files> </files>
  <og_groups>
          <item>69599</item>
      </og_groups>
  <og_groups_both>
      </og_groups_both>
  <field_categories>
      </field_categories>
  <core_research_areas>
      </core_research_areas>
  <field_news_room_topics>
      </field_news_room_topics>
  <links_related>
      </links_related>
  <files>
      </files>
  <og_groups>
          <item>69599</item>
      </og_groups>
  <og_groups_both>
          <item><![CDATA[IPaT]]></item>
      </og_groups_both>
  <field_keywords>
          <item>
        <tid>188084</tid>
        <value><![CDATA[go-ipat]]></value>
      </item>
      </field_keywords>
  <field_userdata><![CDATA[]]></field_userdata>
</node>
