github-starred/ollama
2
0
Fork 0
mirror of https://github.com/ollama/ollama.git synced 2026-05-07 16:40:08 -05:00
Code Issues 14.5k Packages Projects Releases 120 Wiki Activity

[GH-ISSUE #14643] [Feature Request] Enhanced Korean Language Support #9487

New Issue
Closed
opened 2026-04-12 22:24:41 -05:00 by GiteaMirror · 1 comment
GiteaMirror commented 2026-04-12 22:24:41 -05:00
Owner
Copy Link

Originally created by @guicybercode on GitHub (Mar 5, 2026).
Original GitHub issue: https://github.com/ollama/ollama/issues/14643

Is your feature request related to a problem? Please describe.

Currently, using Ollama with Korean language models [or specific Korean tasks] presents some challenges.
[Describe specifically what is lacking or problematic. E.g., Tokenization efficiency, lack of specific Korean models, poor performance in Korean syntax, etc.]

Describe the solution you'd like

I would like to see improved support for the Korean language in Ollama. Specifically:

  • [Detail 1: E.g., Better default tokenization for Hangul]
  • [Detail 2: E.g., Integration of specific Korean-tuned models like Llama-3-Korean or EEVE-Korean]
  • [Detail 3: E.g., Documentation or examples specifically for Korean NLP tasks]

Describe alternatives you've considered

[Have you tried other tools? Are you currently using a workaround? E.g., Using raw llama.cpp or other local LLM runners that handle Korean better.]

Additional context

  • Use Case: [E.g., Customer support chatbot in Korean, Translation, Summarization of Korean documents]
  • Models tested: [List any models you tried, e.g., llama3, gemma, etc.]
  • OS/Version: [e.g., macOS Sonoma, Windows 11, Ubuntu 22.04]
Originally created by @guicybercode on GitHub (Mar 5, 2026). Original GitHub issue: https://github.com/ollama/ollama/issues/14643 ## Is your feature request related to a problem? Please describe. <!-- A clear and concise description of what the problem is. Ex: I'm always frustrated when [...] --> Currently, using Ollama with Korean language models [or specific Korean tasks] presents some challenges. [Describe specifically what is lacking or problematic. E.g., Tokenization efficiency, lack of specific Korean models, poor performance in Korean syntax, etc.] ## Describe the solution you'd like <!-- A clear and concise description of what you want to happen. --> I would like to see improved support for the Korean language in Ollama. Specifically: - [Detail 1: E.g., Better default tokenization for Hangul] - [Detail 2: E.g., Integration of specific Korean-tuned models like Llama-3-Korean or EEVE-Korean] - [Detail 3: E.g., Documentation or examples specifically for Korean NLP tasks] ## Describe alternatives you've considered <!-- A clear and concise description of any alternative solutions or features you've considered. --> [Have you tried other tools? Are you currently using a workaround? E.g., Using raw llama.cpp or other local LLM runners that handle Korean better.] ## Additional context <!-- Add any other context or screenshots about the feature request here. --> - **Use Case:** [E.g., Customer support chatbot in Korean, Translation, Summarization of Korean documents] - **Models tested:** [List any models you tried, e.g., llama3, gemma, etc.] - **OS/Version:** [e.g., macOS Sonoma, Windows 11, Ubuntu 22.04]
GiteaMirror added the feature request label 2026-04-12 22:24:41 -05:00
GiteaMirror commented 2026-04-12 22:24:42 -05:00
Author
Owner
Copy Link

@rick-github commented on GitHub (Mar 6, 2026):

It looks like you had an LLM generate a framework for a feature request and then couldn't be bothered filling out the fields where the LLM suggested you add your own input. You could just edit the post and replace the contents with "Please add support for Korean" and then somebody could have replied "https://ollama.com/library/exaone3.5" and then you could have replied with why support for a Korean model is not what you meant, and then a substantive discussion could have ensued.

<!-- gh-comment-id:4013551818 --> @rick-github commented on GitHub (Mar 6, 2026): It looks like you had an LLM generate a framework for a feature request and then couldn't be bothered filling out the fields where the LLM suggested you add your own input. You could just edit the post and replace the contents with "Please add support for Korean" and then somebody could have replied "https://ollama.com/library/exaone3.5" and then you could have replied with why support for a Korean model is not what you meant, and then a substantive discussion could have ensued.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
amd
api
app
bug
build
cli
cloud
compatibility
context-length
create
docker
documentation
embeddings
feature request
feedback wanted
good first issue
gpt-oss
gpu
harmony
help wanted
image
install
intel
js
launch
linux
macos
memory
mlx
model
needs more info
networking
nvidia
ollama.com
performance
pull-request
Mirrored from GitHub Pull Request
 python
question
registry
rendering
thinking
tools
top
vulkan
windows
wsl
No Label feature request
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/ollama#9487
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?