Re: Android Gforth not displaying non-ASCII characters
Bernd Paysan <[email protected]> Sun, 01 Dec 2019 20:04:30 +0100
| Newsgroups | gmane.comp.lang.forth.gforth |
|---|---|
| Message-ID | <4865455.L9c6iAEtBp@daiyu> |
Am Sonntag, 1. Dezember 2019, 18:10:35 CET schrieb Ethan Gardener: > On Sat, Nov 30, 2019, at 12:46 PM, Bernd Paysan wrote: > > Gforth gl-terminal is for ASCII and a few special characters only. That's > > intentional, it should be simple. > > I agree. I looked into how Plan 9 does unicode because it seems very > simple, but it's not so simple under the surface: The display driver has to > cache images representing ranges of characters. To quote someone who > worked on Plan 9, "There's no such thing as a simple cache bug." ;) And it > has bug of omission: it has no support for combining characters. Minos2 has something similar, and I even plan to add support for combining characters (via harfbuzz), but that's not the right thing for the very simple terminal. -- Bernd Paysan "If you want it done right, you have to do it yourself" net2o id: kQusJzA;7*?t=uy@X}1GWr!+0qqp_Cn176t4(dQ* https://net2o.de/
signature.asc
(application/pgp-signature, 833 B)
-----BEGIN PGP SIGNATURE----- iQIzBAABCAAdFiEERJ1NDqPQRwYnwBjr9y2Uk5MtoGcFAl3kDr4ACgkQ9y2Uk5Mt oGdd7A//Wf5bcEqWrd9uXl0Jtik1e9xgjaP7T1osU9Ka19XiW3NM+SOPapv2opzA Bex1BCSdx+BuQL3IKlWJbSyuengYHuAPaxcfa3WusCrcp//ubDsgtecB/LGx5alL 5BcXZ3wRHzVdMxju9h93hEeUe/YEJVEcSd9DC1yOJkJ8LrlKjvbkp5C+HgHs7gWQ IOSSVOLDNlaA4wJA/Yiz3FT7MG9fR2pgg+95wH2v/UM8mEueAgMGnqSzqkLy2yIq PpyLqoX4slTD6Ac15a3FLwNhMIN344A4ZIvXKswpPnrCF/ssTfxnsBWY8Hrq5J0Z F/G31RG81vS5kdM+dHnt1QhTp55HV0q56gz5WzX1L4iTtjJwvjbuQ6aPpr4oAGNa 5JIfAdGLx9zPYs4XZxIMfhR6yLMbGwaU9JcWR7KTRVIRkeyqFemZP+d7U8/xlMKS 3/IKbhr3XnyfyBDtpZ2qU6QyANHVoV48nPnEEPKd9QNJBizc6JHeNXq0qDjwnkk5 XmxO57LuPFOWpP2hCgrqDDFj7JIvzNXwLRY6LRpT4qW8jADu+7oaJqgwwZwNQWsG dZ+IrxHnLjDqIMQAshMq0WKCEPb4g5CnjF9d3wD2GbeHreAUyAoaiHka+BfUXrfZ aMtc6PwfToPi/0s0TBhaonIFi7adzaFFF/uOa3XSWx6eSIr/a3I= =YFqX -----END PGP SIGNATURE-----