rmkaplan

Oops, got the wrong bit map for Terminal (Git doesn't show the image while you are editing). Herre it is:

The only problem cases are ligatures in the Timesroman or Helvetica encoding, in charset 0. I think these are in Modern, so already in MCCS (charset 360Q) > On Aug...

But this reveals another little glitch: The ligatures in charset 360 are not defined as word characters in the default Tedit wordbound table. So middle-button word-selection treats them as punctuation....

And another: Since the ligature fi is actually in this document, not just the display, you can't search for the word "definition" by typing f-i. Ligatures should not appear in...

Ligatures were discussed in the Aug 4 2025 technical meeting. The proposed scheme of converting all text fonts to the MCCS encoding would make it possible for Tedit at least...

To move at least one step forward on this, let's define MCCS to give us a target, apart from the question of whether fonts or files are also translated. I...

We can talk about it, but I'm not particularly interested in XCCS per se. We have never had any true XCCS displayfonts, and the XCCS label has been a source...

It was agreed at the 8/14/2005 meeting that: The 7-bit region of MCCS is like 1977 Gacha, except that ^X is undefined, not underscore The 8-bit region is like XCCS,...

Closed in favor of #2280 , which deals with these issues

I looked more carefully at what happens when PSEUDOHOST can't resolve a prefix to a real host, either error or return NIL if new argument NOERROR is set.