Hi Ian, ropers wrote on Sat, Jul 13, 2019 at 02:53:28AM +0200:
> altnumd with e.g. CP437 support Over my dead body. We won't add support for legacy character encodings. > the more fundamental idea is to have this be completely configurable, The OpenBSD philosophy is to limit configurability to the utter minimum needed. Take mandoc as an example. It supports as input: ASCII, UTF-8, latin-1, and the latter only because legacy manual pages encoded that way are still somewhat common in the wild. It's all fully transparent and just works. Yes, the -K option exists, but only for compatibility, you almost never need it. No configuration or customization is ever required, and no helper programs like preconv(1) with groff. It supports as output: ASCII and UTF-8. Again, almost nothing to configure, just LC_CTYPE is enough, or -Tascii / -Tutf8 to override that. Though the final code achieving all that is relatively simple, getting there took years of thought on how to simplify. Take any other base userland program; likewise optimized for KISS. Examples of some that i contributed to for that purpose include ksh(1), xterm(1), ls(1), ssh(1), sftp(1), though these are by now means perfect yet; there is still much that could be taken away. The part that is still really complicated, difficult to use, and fragile is keyboard encoding and low-level input handling. Yours, Ingo
