Re: NB as Xy

[Harry Binswanger hb@xxxxxxxx]

Robert wrote:
> If you comment out (;) *every* line in the ALT table (and
> "TABLE=ALT", of course), you should be fine. As long as you
> have specified ALT= in the DEFINITIONS table at TOF, the ALT key
> should continue to work with other tables like ALT+SHIFT.
> Whether there will be other conflicts, you'll only learn from
> experience.

Fair enough. Thanks.
> But I don't see why you don't just take the whole ALT table and
> assign to a different key combo, as mentioned (I think) in my
> video.
Yes, you did, but I was worried about separating Left and Right Shift,
since I have SHIFT+ tables. Hmm, I almost never use Right Shift for
shifting-key combos. Make that just "never." So I guess that does mean I
can take what is now Shift+ALTX and so on and make them LeftShift+ALTX and
so on. And then I have to define LeftShift and RightShift, as you have. A
good suggestion!
>  Why lose the functionality of those assignments? Just
> get them off ALT!
>
> > 2. In the XyWWWeb Readme, it talks about changing CHARUPDT.TBL as a way of
> > avoiding the CA/100 issue. Is there any downside to doing this? I'm
> worried
> > that I'm going to forget to use the /100 switch sometime.
>
> The only downside (as implied in my message yesterday) is that
> you won't be able to change case, or SEarch/CHange
> case-INsensitively, on Thorn, eszet, or Y-diaeresis. Big deal.
Yeah, I've never even heard of Thorn or eszet, and I've never used a
diaeresis. Call me parochial. Okay, I'm making the change.



Harry Binswanger
hb@xxxxxxxx