<?xml version="1.0" encoding="utf-8"?>
<oembed>
  <version>1</version>
  <type>rich</type>
  <provider_name>Libsyn</provider_name>
  <provider_url>https://www.libsyn.com</provider_url>
  <height>90</height>
  <width>600</width>
  <title>Episode 194: Subtext</title>
  <description>This time, Tor, Romain, and Chet were joined by Siyamed Sinir and Sean McQuillan from the Android Text team to talk about, well, text. Which, it turns out, is a very deep, complicated, and constantly evolving technology. The conversation covered everything from the fundamentals of the text stack on Android to the capabilities and implementation of text in Jetpack Compose to internationalization to fonts to emojis to performance to.... you get the idea. There was a lot of stuff to talk about. And so much subtext.  Romain, Chet, Sean, Tor, and Siyamed (using RTL support: Siyamed, Tor, Sean, Chet, and Romain) Links:  Text In Compose&amp;amp;nbsp;  Compose Variable Fonts ComboBreaker  ColrV1 Fonts  i18n &amp;amp;amp; Text in Android 13&amp;amp;nbsp; Text is hard! Rendering &amp;amp;amp; Editing&amp;amp;nbsp;&amp;amp;nbsp;  Compose Downloadable Fonts&amp;amp;nbsp;  Romain: @romainguy&amp;amp;nbsp;and romainguy@androiddev.social Tor: @tornorbye&amp;amp;nbsp;and tornorbye@androiddev.social Chet: @chethaase&amp;amp;nbsp;and chethaase@androiddev.social Siyamed:@siyamed Sean: tech.lgbt/@objcode Subscribe to Android Developers → https://goo.gle/AndroidDevs&amp;amp;nbsp; </description>
  <author_name>Android Developers Backstage</author_name>
  <author_url>http://androidbackstage.blogspot.com/</author_url>
  <html>&lt;iframe title="Libsyn Player" style="border: none" src="//html5-player.libsyn.com/embed/episode/id/25635228/height/90/theme/custom/thumbnail/yes/direction/forward/render-playlist/no/custom-color/88AA3C/" height="90" width="600" scrolling="no"  allowfullscreen webkitallowfullscreen mozallowfullscreen oallowfullscreen msallowfullscreen&gt;&lt;/iframe&gt;</html>
  <thumbnail_url>https://assets.libsyn.com/secure/item/25635228</thumbnail_url>
</oembed>
