anomalyco/opencode
1
0
Fork 0
mirror of https://github.com/anomalyco/opencode.git synced 2026-07-22 02:05:26 -04:00
Code Issues 5.9k Packages Projects Releases 19 Wiki Activity

Korean (Hangul) characters display as broken/garbled in input field #2307

New Issue
Open
opened 2026-02-16 17:35:04 -05:00 by yindo · 4 comments
yindo commented 2026-02-16 17:35:04 -05:00
Owner
Copy Link
Copy Source

Originally created by @LeeSungGuk on GitHub (Oct 28, 2025).

Bug Description

When typing Korean (Hangul) characters in the OpenCode interface input field, the characters appear as broken/garbled text, making it impossible to verify typed content in real-time.

Steps to Reproduce

  1. Launch OpenCode
  2. Try typing Korean text in the input field (e.g., 안녕하세요)
  3. Observe that the characters appear broken/garbled

Expected Behavior

Korean characters should display correctly in the input field as they are being typed.

Actual Behavior

Korean characters appear as broken/garbled characters or empty boxes, preventing users from seeing what they are typing.

Environment

  • OS: macOS 26.0.1 (Build 25A362)
  • OpenCode Version: 0.15.18
  • Terminal: xterm-256color
  • Locale: ko_KR.UTF-8

Additional Context

  • The AI correctly recognizes and processes Korean input (backend works fine)
  • The issue is purely visual/UI rendering related
  • After sending the message, AI responds correctly in Korean
  • The problem only affects real-time input visibility, not functionality

Impact

This makes it extremely difficult for Korean users to:

  • Verify spelling while typing
  • Catch typos before sending
  • Use OpenCode effectively in Korean

Suggested Fix

Possible solutions:

  • Add CJK (Chinese, Japanese, Korean) font support to the input field
  • Ensure proper UTF-8 rendering in the UI component
  • Test with fonts that include Korean glyphs (e.g., Noto Sans CJK, D2Coding)
Originally created by @LeeSungGuk on GitHub (Oct 28, 2025). ## Bug Description When typing Korean (Hangul) characters in the OpenCode interface input field, the characters appear as broken/garbled text, making it impossible to verify typed content in real-time. ## Steps to Reproduce 1. Launch OpenCode 2. Try typing Korean text in the input field (e.g., 안녕하세요) 3. Observe that the characters appear broken/garbled ## Expected Behavior Korean characters should display correctly in the input field as they are being typed. ## Actual Behavior Korean characters appear as broken/garbled characters or empty boxes, preventing users from seeing what they are typing. ## Environment - OS: macOS 26.0.1 (Build 25A362) - OpenCode Version: 0.15.18 - Terminal: xterm-256color - Locale: ko_KR.UTF-8 ## Additional Context - The AI correctly recognizes and processes Korean input (backend works fine) - The issue is purely visual/UI rendering related - After sending the message, AI responds correctly in Korean - The problem only affects real-time input visibility, not functionality ## Impact This makes it extremely difficult for Korean users to: - Verify spelling while typing - Catch typos before sending - Use OpenCode effectively in Korean ## Suggested Fix Possible solutions: - Add CJK (Chinese, Japanese, Korean) font support to the input field - Ensure proper UTF-8 rendering in the UI component - Test with fonts that include Korean glyphs (e.g., Noto Sans CJK, D2Coding)
yindo commented 2026-02-16 17:35:04 -05:00
Author
Owner
Copy Link
Copy Source

@github-actions[bot] commented on GitHub (Oct 28, 2025):

This issue might be a duplicate of existing issues. Please check:

  • #2904: Similar Unicode/multi-byte character handling issues - while focused on file editing, it demonstrates OpenCode's broader problems with Unicode character support including CJK characters

Feel free to ignore if none of these address your specific case.

@github-actions[bot] commented on GitHub (Oct 28, 2025): This issue might be a duplicate of existing issues. Please check: - #2904: Similar Unicode/multi-byte character handling issues - while focused on file editing, it demonstrates OpenCode's broader problems with Unicode character support including CJK characters Feel free to ignore if none of these address your specific case.
yindo commented 2026-02-16 17:35:04 -05:00
Author
Owner
Copy Link
Copy Source

@LeeSungGuk commented on GitHub (Oct 28, 2025):

Image

한글로 테스트 -> 안녕하세요 지금 한글로 테스트 중입니다.

@LeeSungGuk commented on GitHub (Oct 28, 2025): <img width="435" height="99" alt="Image" src="https://github.com/user-attachments/assets/322bb54b-01e9-4ba7-a746-38b0cb77f122" /> 한글로 테스트 -> 안녕하세요 지금 한글로 테스트 중입니다.
yindo commented 2026-02-16 17:35:04 -05:00
Author
Owner
Copy Link
Copy Source

@rekram1-node commented on GitHub (Oct 28, 2025):

We are rewriting the tui and a fix for this should be shipping soon

@rekram1-node commented on GitHub (Oct 28, 2025): We are rewriting the tui and a fix for this should be shipping soon
yindo commented 2026-02-16 17:35:04 -05:00
Author
Owner
Copy Link
Copy Source

@JSCOP commented on GitHub (Oct 28, 2025):

@rekram1-node I'm waiting too hope it soon

@JSCOP commented on GitHub (Oct 28, 2025): @rekram1-node I'm waiting too hope it soon
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
acp
bad
bug
discussion
docs
documentation
enhancement
extension
good first issue
growth
help-wanted
mcp
model-problem
needs:compliance
nix
opentui
perf
pull-request
Mirrored from GitHub Pull Request
 tui
web
windows
zen
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
yindo
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: anomalyco/opencode#2307
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?