AI & ML interests

Traditional Chinese language models

Recent Activity

lianghsunย  updated a dataset 3 days ago
twinkle-ai/Formosa-Vision
lianghsunย  updated a dataset 3 days ago
twinkle-ai/F1-identity
View all activity

lianghsunย 
in twinkle-ai/tw-leetcode 30 days ago

Auto-update dataset - 2026-09-21

#62 opened about 1 month ago by
whats2000
whats2000ย 
in twinkle-ai/tw-leetcode about 1 month ago

Auto-update dataset - 2026-09-21

#62 opened about 1 month ago by
whats2000

Auto-update dataset - 2026-09-14

#61 opened about 1 month ago by
whats2000
whats2000ย 
in twinkle-ai/tw-leetcode about 2 months ago

Auto-update dataset - 2026-09-07

#60 opened about 2 months ago by
whats2000

Auto-update dataset - 2026-08-31

#59 opened about 2 months ago by
whats2000
lianghsunย 
updated a model about 2 months ago
lianghsunย 
published a model about 2 months ago
lianghsunย 
posted an update about 2 months ago
view post
Post
395
๐Ÿ‡น๐Ÿ‡ผ Releasing https://huggingface.co/lianghsun/tw-tokenizer-v1 โ€” a tokenizer trained from scratch for Traditional Chinese (Taiwan).

**46% better Chinese compression than Qwen3.8-27B with 81% of its vocab (201K vs 248K), and English essentially untouched (4.657 vs 4.674 chars/token).**

The gain isn't from the regex โ€” it's the corpus. Qwen carries **27,364 Simplified-only multi-char tokens**, 11% of its vocab, dead weight for Traditional Chinese. Train on pure Traditional and that waste never appears.

Recent work is skeptical that compression predicts quality (Lotz et al. 2025 measured ฯ = โˆ’0.59), so we validated two levels deeper:

**Segmentation** โ€” boundary hit rate against jieba: **85.6%** vs Qwen's 77.8%. Single-character tokens: **17.6%** vs 41.7%.

ๅฐˆๆฅญ็ด ้คŠใ€็‰น่ณชๆˆ–็ถ“ๅ…ฌๅ‘ŠๅฏฉๆŸฅๅ„ชๅ‹
  ours: ['ๅฐˆๆฅญ็ด ้คŠ', 'ใ€', '็‰น่ณช', 'ๆˆ–็ถ“', 'ๅ…ฌๅ‘Š', 'ๅฏฉๆŸฅ', 'ๅ„ชๅ‹']
  Qwen: ['ๅฐˆๆฅญ', '็ด ', '้คŠ', ...]     โ† ใ€Œ็ด ้คŠใ€split mid-word


**Downstream** โ€” trained a 270M model from scratch with each tokenizer, compared bits-per-character (the only metric fair across tokenizers). At equal compute: **4.434 vs 4.591**, a 3.4% win โ€” with 13% fewer parameters. Same token budget means our model saw 440M characters vs 308M: **43% more data for the same compute**.

Also: 6-char cap on pure-CJK tokens (long tokens obscure orthographic info โ€” Haslett, CL 2025), NFC not NFKC, 1,024 reserved tokens.

Known limits (weak Tรขi-lรด support, small-scale downstream validation, vocab sweep hadn't flattened) are in the card.

๐Ÿ‘‰ https://huggingface.co/lianghsun/tw-tokenizer-v1