Skip to content
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

Different processing of cyrillic text compared to ascii #81

Open
kchibisov opened this issue Oct 24, 2022 · 1 comment
Open

Different processing of cyrillic text compared to ascii #81

kchibisov opened this issue Oct 24, 2022 · 1 comment

Comments

@kchibisov
Copy link
Member

When using Крас\x1bниво only Крас is processed with input, while rest terminals(vte, xterm) output Красиво. On the other side Hello\x1bworld will process with input Hello and orld only consuming w.

@chrisduerr
Copy link
Member

I've looked into this a little bit and the solution is likely to move the unicode parser table definitions from the Ground state to the Anywhere state.

I'd have to think a bit more of the concrete implications, but I don't think unicode is valid as part of any escape sequence? Though Alacritty certainly accepts in right now for URLs for example.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

2 participants