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
Full-width symbols, like commas ,, Question marks ?, exclamation marks ! and parentheses (), brackets [], braces {} cannot be typed into pythonista editor or console, they are required in Chinese, we should not eliminate these characters at all (for use cases like searching and replacing in strings) (I can’t even paste them into editor!!!)
I know this is some kind of user experience enhancement, to prevent having confusing symbols in code and raise nonsense SyntaxErrors. But we can do something more permissive, like most input method would do, if user typed the symbol again, with the auto-correct-ed one deleted, the full-width symbol will show up.
Chinese IMEs will usually send 。 when you press period ., but they often have feature to send . after numerical digits (like dot in 3.14). If a user do want 。 to show up after numerical digits, they just delete the dot and press period key again. (or some IMEs replace the . to 。 at first time when you press backspace)
Also, as a visual aid, we can provide an option to highlight confusing unicode characters like we have in VSCode.
The text was updated successfully, but these errors were encountered:
Full-width symbols, like commas
,
, Question marks?
, exclamation marks!
and parentheses()
, brackets[]
, braces{}
cannot be typed into pythonista editor or console, they are required in Chinese, we should not eliminate these characters at all (for use cases like searching and replacing in strings) (I can’t even paste them into editor!!!)I know this is some kind of user experience enhancement, to prevent having confusing symbols in code and raise nonsense SyntaxErrors. But we can do something more permissive, like most input method would do, if user typed the symbol again, with the auto-correct-ed one deleted, the full-width symbol will show up.
Also, as a visual aid, we can provide an option to highlight confusing unicode characters like we have in VSCode.
The text was updated successfully, but these errors were encountered: