Skip to content

[Bug] Vietnamese Unicode Rendering Issue - Words with ươi/ơi vowels split incorrectly #125

Description

@rin-botbie

Bug Description

Model: kimi-k2.6 (and likely other K2 variants)
Date: 2026-04-21
Severity: High (breaks Vietnamese content generation)

Summary

kimi-k2.6 fails to correctly render Vietnamese words containing the vowel sequences "ươi" or "ơi" with tone marks. Instead of outputting the complete word, the model splits it incorrectly and inserts unwanted newlines.

Affected Words

Expected Actual Output
mườ
mườ\n\nHai
thờ
thờ\n\nHai
lờ
lờ\n\nHai
tiếp tiế\n\np

Steps to Reproduce

  1. Prompt model to write Vietnamese text containing words like "mườ
    Hai", "thờ
    Hai", "lờ
    Hai"
  2. Observe the generated output
  3. The words are split at the vowel boundary with newlines inserted

Expected Behavior

Model should output complete Vietnamese words without splitting:

  • "Em có mườ
    Hai bảy
    kỹ năng" (I have seventeen skills)

Actual Behavior

Model outputs fragmented text:

  • "Em có mườ\n\nHai bảy kỹ năng" (broken into meaningless chunks)

Environment

  • nanobot framework v0.1.5.post1
  • POSIX system (Linux)
  • UTF-8 encoding
  • Using kimi-k2.6 via API

Impact

This bug makes the model unusable for Vietnamese content generation, including bilingual blog posts, documentation, and any task requiring accurate Vietnamese text output. The issue appears to be in the model tokenization or generation logic for Vietnamese Unicode combining characters.

Additional Notes

  • Other Vietnamese vowel combinations may also be affected
  • The issue is reproducible consistently with words containing ươi/ơi + tone marks
  • Workaround: Using a different model for Vietnamese content generation

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Fields

    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions