| 05:31 | <Domenic> | SimonSapin: no. In specs it's called isomorphic encode/decode. |
| 05:31 | <Domenic> | Fun fact, the actual ISO standard does not have mappings for 0xF0-0xFF |
| 05:33 | <Domenic> | Er, I meant to say that it doesn't have mappings for 0x8F-0xFF. But also I might be misremembering, based on Wikipedia at least. |
| 05:33 | <Domenic> | argh 0x80-0xFF. The second half. |
| 05:34 | <Domenic> | Also I'm just wrong, that makes no sense, then it would be ASCII. Please ignore me, I am walking away from the computer now. |
| 07:38 | <SimonSapin> | Domenic: I assume you mean 0x80-0x9F |
| 07:39 | <SimonSapin> | Wikipedia says "ISO-8859-1 is the IANA preferred name for this standard when supplemented with the C0 and C1 control codes from ISO/IEC 6429" |
| 07:40 | <SimonSapin> | Anyway, the context was smuggling arbitrary bytes in application/x-www-form-urlencoded |
| 07:40 | <SimonSapin> | name/values pairs because Bittorrent |
| 07:40 | <SimonSapin> | https://github.com/servo/rust-url/issues/578 |