Timeline for Sandbox for Proposed Challenges
Current License: CC BY-SA 4.0
9 events
when toggle format | what | by | license | comment | |
---|---|---|---|---|---|
Jun 17, 2020 at 9:03 | history | edited | CommunityBot |
Commonmark migration
|
|
Mar 9, 2020 at 1:46 | history | edited | Shieru Asakoto | CC BY-SA 4.0 |
deleted 2538 characters in body
|
Mar 6, 2020 at 14:24 | comment | added | Grimmy |
Typo: monas should be moras .
|
|
Mar 2, 2020 at 20:06 | comment | added | FryAmTheEggman | Ah yes, I see where I made an error now. I think the rewrite you did makes it easier to read. I don't see anything else, though of course I don't speak for everyone. Good luck! | |
Mar 2, 2020 at 3:38 | history | edited | Shieru Asakoto | CC BY-SA 4.0 |
added 133 characters in body
|
Mar 2, 2020 at 3:36 | comment | added | Shieru Asakoto | @FryAmTheEggman I wrote kuten in decimal and bytes in hexadecimal because they were so defined; edited to only show in decimal, but keep accepting both decimal and hexadecimal input/output form. | |
Mar 2, 2020 at 3:24 | comment | added | Shieru Asakoto |
@FryAmTheEggman For the Shift_JIS case, the range used is [0x81-0x9F,0xE0-0xEF] for the first byte and [0x40-0x7E, 0x80-0xFC] for the second byte, which is of size precisely 8,836. Since 区 won't exceed 128, and the starting points of 点 in both cases are separated by 95, the first case won't overlap with the second.
|
|
Mar 1, 2020 at 18:40 | comment | added | FryAmTheEggman |
I think switching between hex and decimal in the definitions is more likely to cause confusion than sticking to just one of them. I think you also don't indicate that the tuples you define are bytes that are concatenated to the final result. I'm not sure if I'm misunderstanding, but doesn't the clipping mean converting from shift JIS is ambiguous? Separately, you can use \left and \right to make your brackets the right height.
|
|
Feb 29, 2020 at 2:41 | history | answered | Shieru Asakoto | CC BY-SA 4.0 |