Larry Masinter

My guess is that the browser running VNC has a better idea of the window dimensions and the window.screen dimensions as well.

see discussion at https://groups.google.com/d/msgid/interlisp/EBAFA6C5-E5EB-4151-B59B-998785C8FFAC%40gmail.com It might be worth checking if pixel adjustments with VNC might be OK with 1/2, 2/3, 3/4, 4/5 screen size

Issue #39 'support larger displays' has been one of those issues with too many moving parts. The display initialization code suffers from a failure of many X servers to report...

the efficient way to implement case transformations and comparisons is by table lookup. so I don't understand.

the notion of "case" only applies to characters.

@rmkaplan is this still an Issue? what are some test cases? Filepos "xccs-string" file-in-repo which should match?

string matching for unicode isn't just a matter of mapping bytes. There's also Unicode normalization... If you want to find "all strings that match WORDINTHAI you may well want to...

> a character-set shift can flip from runcoding to non-runcoding in the middle of the file, While that might be theoretically possible.... who would have created files that were XCCS...

> This has nothing to do with Interpress or Tedit, or even plain text files that were created in Lisp. They could have been created by any other NS-creation system....

published documents about Interlisp should be findable in our [Zotero Interlisp bibliography collection](https://www.zotero.org/groups/2914042/interlisp/collections/TVX6WEZX/items/V3ECJHJ3/collection) From Zotero you can find the original and the 1979 revision https://www.cs.utexas.edu/~moore/publications/interlisp-vm.pdf