[Date Prev][Date Next][Subject Prev][Subject Next][
Date Index][
Subject Index]
Re: NB as Xy
- Subject: Re: NB as Xy
- From: "Robert Holmgren" holmgren@xxxxxxxx
- Date: Sun, 9 Sep 2007 13:15:36 -0400
** Reply to message from Harry Binswanger on
Sun, 09 Sep 2007 02:58:15 -0400
> I have two questions regarding NB-as-Xy:
>
> 1. I'm not sure what to do about the Alt-key table. If I just comment out,
> with the semicolon, the contents of the table, will I retain the
> functionality of the other Alt tables (e.g., alt+shift), without conflicts
> with NB?
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.
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. 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.
Just overwrite CHARUPDT.TBL with CHARUPXY.TBL (making a backup
of the original CHARUPDT.TBL first!) with the **new**
CHARUPXY.TBL that I ZIPped up and attached to my message
yesterday (it has two enhancements over the old one).
> My great appreciation to Robert for the video.
Delighted to help.
R.
-----------------------------
Robert Holmgren
holmgren@xxxxxxxx
-----------------------------