DOS ain't dead

mTCP: A Unicode enabled IRCjr is available for testing (Announce)

posted by mbbrutman , Washington, USA, 05.02.2023, 18:10

> Yes,please! I also very much advocate using the DOSLFN mapping files. It is
> simple, very usable and it not good for anyone to introduce a new formats
> for unicode mappings.

I took a look and I read the code that generates the files to figure out the file format.

Unfortunately, I'm looking for something very different with Telnet and IRC. Strict mappings from the code page characters to Unicode are published, and those table files require a strict mapping. I need something more relaxed ... a lot of Unicode code points have reasonably close substitutes available. For example, there are at least two Unicode "black diamond" characters that I know of, with just slightly different shapes. I map both of those to the character 0x04, which is a diamond, and that's close enough for display purposes. There are a lot of variations of line drawing characters with different line weights that can be represented by the standard line drawing characters, so I map those too. I think for 128 different possible code points I have over 300 Unicode characters mapping to them.

Technically what I'm doing is not correct, but I'd rather see a black diamond or a line drawing character of some sort rather than the standard "I can't display this glyph" tofu character. Which is also why I went with a text file to allow users to define their own mappings; they can be as strict or as sloppy as they want.

I can use the published tables as a starting point, but I suspect for display purposes people will want to see the additional mappings.

---
mTCP - TCP/IP apps for vintage DOS machines!
http://www.brutman.com/mTCP

Complete thread:

• mTCP: A Unicode enabled IRCjr is available for testing - mbbrutman, 27.01.2023, 02:46 (Announce)
  • mTCP: A Unicode enabled IRCjr is available for testing - SuperIlu, 27.01.2023, 06:18
    • mTCP: A Unicode enabled IRCjr is available for testing - mbbrutman, 28.01.2023, 02:03
      • mTCP: A Unicode enabled IRCjr is available for testing - SuperIlu, 28.01.2023, 10:11
        • mTCP: A Unicode enabled IRCjr is available for testing - mbbrutman, 28.01.2023, 17:28
          • mTCP: A Unicode enabled IRCjr is available for testing - mbbrutman, 29.01.2023, 22:20
            • mTCP: A Unicode enabled IRCjr is available for testing - SuperIlu, 30.01.2023, 18:35
              • mTCP: A Unicode enabled IRCjr is available for testing - mbbrutman, 30.01.2023, 21:24
  • mTCP: A Unicode enabled IRCjr is available for testing - boeckmann, 27.01.2023, 23:15
    • mTCP: A Unicode enabled IRCjr is available for testing - mbbrutman, 28.01.2023, 02:05
  • mTCP: A Unicode enabled IRCjr is available for testing - tom, 31.01.2023, 15:48
    • mTCP: A Unicode enabled IRCjr is available for testing - mbbrutman, 04.02.2023, 20:25
      • mTCP: A Unicode enabled IRCjr is available for testing - Laaca, 05.02.2023, 14:19
        • mTCP: A Unicode enabled IRCjr is available for testing - mbbrutman, 05.02.2023, 18:10
          • mTCP: A Unicode enabled IRCjr is available for testing - tom, 06.02.2023, 17:01
          • mTCP: A Unicode enabled IRCjr is available for testing - bretjohn, 06.02.2023, 17:23