You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Looked at the format of asciinema v2 which looks to be utf8-unicoded.
"it's UTF-8 encoded JSON string, with all non-printable Unicode codepoints encoded as \uXXXX"
Looked thru the code to figure out how this is handled and passed to xterm.write that seems to expect utf16.
If you could point out where this is dealt with I would really appreciate it!
The text was updated successfully, but these errors were encountered:
@frippe75 I'm sorry I mat not be able to answer your question. You may need to check xterm.js source code to find the answer or ask questions in gitter room. BTW, What kind of scenario you're meeting that makes you need to figure out how unicode is handled?
Just quickly checked xterm.js source code, I think the answer can be found at here.
Sorry, rather a question than an issue.
Looked at the format of asciinema v2 which looks to be utf8-unicoded.
"it's UTF-8 encoded JSON string, with all non-printable Unicode codepoints encoded as \uXXXX"
Looked thru the code to figure out how this is handled and passed to xterm.write that seems to expect utf16.
If you could point out where this is dealt with I would really appreciate it!
The text was updated successfully, but these errors were encountered: