On Fri, 16 Nov 2007, Chip Griffin wrote:
> I know it's behaving like that, but when I do an "echo $LANG" I get
> the correct response. I tried what you sent, and it still does the
> exact same thing. So it may be something new with Leopard.
> Incidentally I also tried the other recommended en_US i
On Fri, 16 Nov 2007, Chip Griffin wrote:
> Yes. Currently the .bash_profile has the LANG=C version. The exact
> error reads:
>
> > Warning:
> > Name: create_appshell text_output2
> > Class: XmTextField
> > Character '\260' not supported in font. Discarded.
>
> Some elements change (lik
On Nov 16, 2007, at 11:13, Curt, WE7U wrote:
That means your LANG setting for the environment Xastir is running
in is not correct. I don't know why. Try this on the command line:
export LANG=C; xastir &
I know it's behaving like that, but when I do an "echo $LANG" I get
the correct
On Nov 15, 2007, at 02:25, Curt wrote:
On Thu, 15 Nov 2007, Chip Griffin wrote:
I am running BASH. I set it in my .bash_profile file. I have tried:
export LANG="C"
export LANG=C
export LANG="en_US"
None of which are working. If I type echo $LANG in a window, I get
C
On Thu, 15 Nov 2007, Chip Griffin wrote:
> I am running BASH. I set it in my .bash_profile file. I have tried:
> export LANG="C"
> export LANG=C
> export LANG="en_US"
>
> None of which are working. If I type echo $LANG in a window, I get C as a
> result. So it doesn't appear to
On Nov 14, 2007, at 17:40, Curt wrote:
On Wed, 14 Nov 2007, Chip Griffin wrote:
I had this working. But now it's throwing errors again. I had it
set to "C" ... worked fine. Now broken. Now set to "en_US" ...
Still broken.
Where/how are you setting it? If you're running a Bourne or BASH
On Wed, 14 Nov 2007, Chip Griffin wrote:
> I had this working. But now it's throwing errors again. I had it set to "C"
> ... worked fine. Now broken. Now set to "en_US" ... Still broken.
Where/how are you setting it? If you're running a Bourne or BASH
shell, try:
export LANG=C
xastir &
On Nov 4, 2007, at 18:16, Jason kg4wsv wrote:
On Nov 4, 2007, at 3:24 PM, Chip Griffin wrote:
with "C" it works. Why is that?
C is posix standard 7 bit ASCII, IIRC. en_US is 8 bit US English.
I think the FAQ needs updating. The FAQ says to change it to
"en_US" but as mentioned that doesn
Here's a message from Jason that was auto-discarded by the list
software. It had some good info.
Date: Sun, 4 Nov 2007 17:16:54 -0600
From: Jason kg4wsv
To: Chip Griffin
Cc: xastir@xastir.org
Subject: Re: [Xastir] GDAL, db42
On Nov 3, 2007, at 20:58, Curt, WE7U wrote:
echo $LANG
Response is ""
With "en_US" it doesn't work.
It's an environment setting in your shell.
export LANG=C
with "C" it works. Why is that? I think the FAQ needs updating. The
FAQ says to change it to "en_US" but as mentioned tha
On Nov 3, 2007, at 15:24, Jason kg4wsv wrote:
On Nov 3, 2007, at 1:49 PM, Chip Griffin wrote:
Define "need" ...
you have maps that are in a format only GDAL will render.
Otherwise, it's baggage.
Hmmm. I can't find the mentioned file. I'm doing a disk-wide grep
search for LANG=" to see
On Sat, 3 Nov 2007, Chip Griffin wrote:
> >>> Character '\61' not supported in font. Discarded.
> >
> > In the FAQ. LANG setting.
>
> Hmmm. I can't find the mentioned file. I'm doing a disk-wide grep
> search for LANG=" to see if I can find a file like that.
echo $LANG
It's an environmen
On Nov 3, 2007, at 13:33, Curt, WE7U wrote:
On Sat, 3 Nov 2007, Chip Griffin wrote:
I was not able to get GDAL (1.4.3) to compile. I tried with just "./
Do you need GDAL for anything? Most people don't.
Define "need" ... It's an option, and I have generally been trying to
compile in eve
On Sat, 2007-11-03 at 13:20 -0400, Chip Griffin wrote:
> I was not able to get GDAL (1.4.3) to compile. I tried with just "./
> configure" and got an error when I tried to 'make' it. So, per the
> INSTALL file, I tried several of the switches mentioned. I added the
> 'internal' options one at
On Sat, 3 Nov 2007, Chip Griffin wrote:
> I was not able to get GDAL (1.4.3) to compile. I tried with just "./
Do you need GDAL for anything? Most people don't.
> > Warning:
> > Name: create_appshell text_output
> > Class: XmTextField
> > Character '\61' not supported in font. Dis
I was not able to get GDAL (1.4.3) to compile. I tried with just "./
configure" and got an error when I tried to 'make' it. So, per the
INSTALL file, I tried several of the switches mentioned. I added the
'internal' options one at a time, and still wasn't able to get it to
compile even after
16 matches
Mail list logo
