Timeline for Create the characters you can write on a MacOS US English Keyboard (as another OS will read them)
Current License: CC BY-SA 4.0
9 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Apr 4, 2024 at 12:35 | history | edited | pacman256 | CC BY-SA 4.0 |
added 10114 characters in body
|
| Apr 3, 2024 at 21:09 | comment | added | Mel | I have clarified the scoring guidelines for custom codepages. | |
| Apr 3, 2024 at 20:17 | comment | added | pacman256 | in theory i could use vyxal literate mode to make it ascii only but that would be kind of a pain? | |
| Apr 3, 2024 at 20:06 | comment | added | Jonathan Allan | Me neither really. The description starts with "take the length (in bytes) of the UTF-32(-LE) representation of the source code" which I would think applies to any encoding, including ASCII as per my question under the OP. Even if not then I think you'd be limited to the first 127 bytes to stick within ASCII (and then maybe that would still be multiplied by 2, again as per my question)... we shall see I suppose. | |
| Apr 3, 2024 at 20:02 | comment | added | pacman256 | @JonathanAllan maybe? i'm not really sure how scoring works with sbcs | |
| Apr 3, 2024 at 19:49 | comment | added | Jonathan Allan | I guess that this scores 600? | |
| Apr 3, 2024 at 19:34 | history | edited | pacman256 | CC BY-SA 4.0 |
deleted 7 characters in body
|
| Apr 3, 2024 at 19:08 | comment | added | pacman256 | "≠≥≤" can be put in as a string, as well as any other vyxal codepage chars that arent part of a range or make up the entire range... I personally won't do this tonight but maybe soon | |
| Apr 3, 2024 at 18:54 | history | answered | pacman256 | CC BY-SA 4.0 |