<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Language Models on Nalar</title>
    <link>https://nalar.dev/tags/language-models/</link>
    <description>Recent content in Language Models on Nalar</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Thu, 03 Sep 2026 00:00:00 +0700</lastBuildDate>
    <atom:link href="https://nalar.dev/tags/language-models/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Understand Tokenization in Language Models</title>
      <link>https://nalar.dev/understand-tokenization-in-language-models/</link>
      <pubDate>Thu, 03 Sep 2026 00:00:00 +0700</pubDate>
      <guid>https://nalar.dev/understand-tokenization-in-language-models/</guid>
      <description>&lt;p&gt;Language models do not read text as a sequence of words. Before a model can process a prompt, a &lt;strong&gt;tokenizer&lt;/strong&gt; converts the text into a sequence of token IDs from a fixed vocabulary. The model operates on those IDs, and generated IDs are later converted back into text.&lt;/p&gt;&#xA;&lt;p&gt;This extra layer is easy to ignore because most model APIs accept ordinary strings. But tokenization affects how much text fits in a context window, how usage-based costs are calculated, how text is truncated or split, and why seemingly small formatting changes can alter model behavior.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
