<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Tokenization on Pi Stack</title>
    <link>https://www.pistack.xyz/tags/tokenization/</link>
    <description>Recent content in Tokenization on Pi Stack</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Sat, 26 Sep 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://www.pistack.xyz/tags/tokenization/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Jieba vs Kagome vs Kuromoji in 2026: Which Word Segmenter Should You Actually Deploy?</title>
      <link>https://www.pistack.xyz/posts/2026-09-26-word-segmentation-libraries-jieba-kagome-kuromoji/</link>
      <pubDate>Sat, 26 Sep 2026 00:00:00 +0000</pubDate>
      <guid>https://www.pistack.xyz/posts/2026-09-26-word-segmentation-libraries-jieba-kagome-kuromoji/</guid>
      <description>&lt;p&gt;Paste &lt;code&gt;南京市长江大桥&lt;/code&gt; into any system that splits on spaces and you get exactly one token: a meaningless eleven-character blob. Chinese, Japanese and Thai do not put spaces between words, so before a search index, a log pipeline, a content filter or a keyword extractor can do anything useful with them, some component has to decide where the word boundaries are. That component is a &lt;strong&gt;word segmenter&lt;/strong&gt;, and the wrong one quietly poisons everything downstream — broken search recall, useless word clouds, and keyword rules that never fire.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
