Re: get the sourcecode [of UTF-8]
A bughunter via Unicode <[email protected]>
| Newsgroups | gmane.text.unicode.general |
|---|---|
| Message-ID | <MhfSpcYuznSYvgKWtvnSHm1SQQF-mjiOTalAq9C0lS0Tzb4Z2LTnGNbXKQZqKsafQswbL0SFo4PyDJlkgfvOyZW-mpg4CEYYGVeDL7sxdmc=@proton.me> |
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 My reply to Arthur interspersed. Originating Question Where to get the sourcecode of relevent (version) UTF-8?: in order to checksum text against the specific encoding map (codepage). from [email protected] Sent with Proton Mail secure email. On Tuesday, November 5th, 2024 at 08:59, Arthur Rosendahl via Unicode <[email protected]> wrote: > > This is pretty much the reverse of what I have asked for: reverse engineering an UTF-8 string in order to re-create the sourcecode I have asked for. You shouldn't have to reverse engineer. What I have asked for is the whole intention of open-source software and the crux of which all programming relies on; writing sourcecode in UTF-8 would mean nothing. It is actually a praxis required in the whole picture of computer science. If you do not have sourcecode for UTF-8 then it is more than likely the standard does sit on the sidelines disconnected from whatever is being called Unicode and UTF-8 actually software in use. You shouldn't have to reverse engineer the software to contrast it against the Unicode standard it purports to have been. > I think that’s what the OP means. He has a UTF-8-encoded string > which he wants to map to a sequence of code points. That’s my guess > anyway. > > Arthur -----BEGIN PGP SIGNATURE----- Version: ProtonMail wnUEARYKACcFgmcqG0EJkKkWZTlQrvKZFiEEZlQIBcAycZ2lO9z2qRZlOVCu 8pkAAIp+AP4jx7+9/FmMd1qtKbETlg4+YOf96Lf0PZWE8ks7oT4FGQD+MzfP 9LJRTda5uqw3nTaphAEGSppcsYmetB05zs/lygk= =vrwS -----END PGP SIGNATURE-----
publickey - [email protected] - 0x66540805.asc
(application/pgp-keys, 653 B)
-----BEGIN PGP PUBLIC KEY BLOCK----- xjMEZu0X1xYJKwYBBAHaRw8BAQdAH0I47jDsPZ6gvb+YUGBnAx7Jyf14AVOH xa8y0+dmN5bNLUFfYnVnaHVudGVyQHByb3Rvbi5tZSA8QV9idWdodW50ZXJA cHJvdG9uLm1lPsKMBBAWCgA+BYJm7RfXBAsJBwgJkKkWZTlQrvKZAxUICgQW AAIBAhkBApsDAh4BFiEEZlQIBcAycZ2lO9z2qRZlOVCu8pkAAD9FAP9/ddT6 56Gka9NtMvmdoY5ktNgqbY5Xbd9fx6kPE5/4tQD/XiialKQHjmwAtbcSe1Q+ 3cxYLxNhjU7mynQspv9dxADOOARm7RfXEgorBgEEAZdVAQUBAQdAnfp/z2Fw RkpvUgf7mqYI9RKnTVadwGfgaQLhmwg3LxMDAQgHwngEGBYKACoFgmbtF9cJ kKkWZTlQrvKZApsMFiEEZlQIBcAycZ2lO9z2qRZlOVCu8pkAAJi8AQC+fnOm 4Vj9QmH4H0GVt7RuOQK+wOQ1PRvpymSjeyBJOwD9GYuvxOAVK8iAupJ+ppwM r36VukIe1pXuHo9RhjveAw0= =FQFw -----END PGP PUBLIC KEY BLOCK-----
publickey - [email protected] - 0x66540805.asc.sig
(application/pgp-signature, 119 B) - not displayed