New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Error: could not decode rune. Windows-1251 (Cyrillic) #197
Comments
I think this was fixed in #343. Can you check? |
Okey, now app doesn't exits with panic, but when i type it looks like "®¢ ë«ä¤ ®ë¤¢ ã誮ãè¤ë¢". It's not my language))))). Can I adjust app for work with windows-1251 (Cyrillic) encode? |
Sorry for bothering, but any chances or plans of this being fixed sooner or later? Some more info from me about related issue. For example. When I type cyrillic russian "ф" character (CP1251 code: Locale set in terminal: $ locale
LANG=ru_RU.UTF-8
LC_CTYPE="ru_RU.UTF-8"
LC_NUMERIC="ru_RU.UTF-8"
LC_TIME="ru_RU.UTF-8"
LC_COLLATE="ru_RU.UTF-8"
LC_MONETARY="ru_RU.UTF-8"
LC_MESSAGES="ru_RU.UTF-8"
LC_ALL= Tried on Windows 10, same with: cmd, git bash, powershell. |
Your locale does not match your input encoding. Have you tried locale |
I don't really appreciate the idea of forcing my end-users to mess with their system's or terminal config.
My guess is so that bubbletea's input reader implementation might be kinda bugged on Windows. But unfortunately don't really have time to check it myself right now. |
Hi, your framework is very cool, it inspired me to make some helpful app for me and my colleagues!
It works fine on Linux, but most employees in my company use Windows and they get error "could not decode rune",
when typing cyrillic symbols, like (ш, б, ж etc).
I find place in source code:
I think problem with windows-1251 (Cyrillic) encode.
They tried set UTF-8 support, like in this issue #153, but it doesn't work.
How can I handle input bytes before framework handle it? Maybe this help me to decode bytes to correct utf8 format?
Or maybe you can help another way?
The text was updated successfully, but these errors were encountered: