[Xastir] config text not being saved

[Robert Grattan]

Thanks, Chuck, Dale and Curt, the LANG setting did the trick.  Before
changing LANG=en_US, my parameters set for station config would not show
up after they had been saved, in fact, nothing I added except my CALL
would display in the station config window.  After changing LANG as
recommended, it all worked fine.  The KISS serial interface is working
now--not sure what the problem was but I just removed and then recreated
it.  It may not have had anything to do with the LANG setting.
Sorry I didn't see the FAQ info which Curt pointed out--the FAQ I was
looking at did not have this information; however, I looked and found
another on the xastir site which did.
Again, many thanks.
Bob N4MRV

Bob Grattan, Systems Librarian
Simpson Library
Mary Washington College
1801 College Avenue
Fredericksburg, VA  22401-4664
phone: (540) 654-1756
email:   bgrattan at mwc.edu
>>> Chuck Byam <cbyam at virginia.edu> 12/28/03 10:31 AM >>>
On Saturday 27 December 2003 16:39, Robert Grattan wrote:
> I'm trying to congigure a newly setup xastir 1.2.1 on RH 9.1 and am
not
> able to save any text I enter to configure my station.  Errors
received
> are like:
> Warning:
>     Name: create_appshell text_output
>     Class: XmTextField
>     Character '\115' not supported in font.  Discarded.

<< snip, snip>>

>
> I must have a path missing or some app that is needed.  Can anyone
offer
> a hint here?  I can send more info.  Thanks in advance.
> Bob N4MRV
>
> PS I'm receiving ok but don't seem to be transmitting.  Radio setup
was
> working on another xastir install so I know it's ok.
>

The warning your receiving above is not related to your described
problem.  
This warning has to do with your default font being set to en_US.UTF.8
(echo 
$LANG to check) and motif not supporting the character extension.  This
is 
generally a harmless, if not annoying, message.  If it really bothers
you, 
you could set up a script to start xastir and include LANG=en_US at the 
beginning.  I wouldn't disable UTF fonts globally as they are, IMHO, a
better 
implementation.  

Now as for your original problem, I would start by insuring that your
config 
files are chmod'ed to allow you to write to them.

--
Chuck