-
Notifications
You must be signed in to change notification settings - Fork 5
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
Reversed coated string in result code #2
Comments
In my opinion, the reason is, that it maps to a character that changes the direction of text, so it should work until pasted to some editor, that will remove such characters. Could you try to copy the bugged result and post it somewhere on Discord? The reason why I'm suggesting it is that Discord removes text direction-changing characters). |
But if the character is removed (through discord for instance) the decoded golfed code won't be the expected one, it will cause a 2 characters loss |
Yeah, the code won't work as expected after the removal, but it'll confirm what I said and show that the code is valid. It only renders from the right side, but it's not actually reversed. Haven't yet found any IDE, that would remove the character. |
I see what you did Removing/changing the code isn't a solution in my opinion |
I'm too lazy to code in JavaScript, so here you're somewhat you could do:
|
Describe the bug
When the input code contains ". ", the coating code is reversed and sometimes appears in the middle.
For some reasons, it does not happen every time, it depends on the position of the ". " string.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
The result code should appear coated with the decoding python code, but instead we get a reversed string in the middle.
Screenshots
Desktop or Smartphone (please complete the following information):
Edit: also works with "+ " in it.
Theory: Maybe when the "+" or the "." is in an even indice position in the string, the converted char in UTF-16 is a reversing one, it would explain what this happens only in this precise case.
The text was updated successfully, but these errors were encountered: