[GRASS5] New tcltkmenu

GRASS GRASS developer
1

Hi,

If downloaded the package with the new TclTk menu from Michael Barton at

http://www.public.asu.edu/~cmbarton/grass.htm <http://www.public.asu.edu/~cmbarton/grass.htm&gt;

to play around with. I untarred it etc, but the ReadMe.txt is binary or something, at least text viewers can't read it.
How do I install this? Is it updated to cvs yet? If so, if I update from cvs is it automatically installed?

Greetings Sjors

2

I can only say WOW!
I tried to install it (3,5 minutes) and it is relly really nice work!
I guess your files are somehow corrupted, I attach the README installation
part.

TO INSTALL:
1. Quit GRASS

2. Backup your current $GISBASE/tcltkgrass directory (just to be safe) by
renaming it $GISBASE/oldtcltkgrass.

3. Copy the /tcltkgrass directory provided here to your $GISBASE (GRASS53 or
GRASS5) directory. (It is possible that you may need to adjust permissions
for the tcltk scrips in the $GISBASE/tcltkgrass/script directory to make sure
that users have execute permissions--hopefully not necessary).

4. Copy the scripts in the directory /add2scripts to your $GISBASE/scripts
directory. (It is possible that you may need to adjust permissions for the
scripts to make sure users have execute permissions--hopefully not
necessary).

5. Restart GRASS and tcltkgrass.

My compliments,
Andrea

On Saturday 17 April 2004 11:41, Sjors wrote:

Hi,

If downloaded the package with the new TclTk menu from Michael Barton at

http://www.public.asu.edu/~cmbarton/grass.htm
<http://www.public.asu.edu/~cmbarton/grass.htm&gt;

to play around with. I untarred it etc, but the ReadMe.txt is binary or
something, at least text viewers can't read it. How do I install this? Is
it updated to cvs yet? If so, if I update from cvs is it automatically
installed?

Greetings Sjors

_______________________________________________
grass5 mailing list
grass5@grass.itc.it
http://grass.itc.it/mailman/listinfo/grass5

--
____________________________________________________________________________
"Let it be as much a great honour to take as to give learning,
if you want to be called wise."
Skuggsja' - The King's mirror - 1240 Reykjavik

University of Trento
Department of Civil and Environmental Engineering
Via Mesiano, 77 - Trento (ITALY)

Andrea Antonello
tel: +393288497722
fax: +390461882672
____________________________________________________________________________

3

Hi,

Thanks Andrea, it worked just fine. After a quick glance I'm most happy, nice work Michael.
We should be putting this in cvs and snapshot.

Greetings Sjors

Andrea Antonello wrote:

I can only say WOW!
I tried to install it (3,5 minutes) and it is relly really nice work!
I guess your files are somehow corrupted, I attach the README installation part.

TO INSTALL:
1. Quit GRASS

2. Backup your current $GISBASE/tcltkgrass directory (just to be safe) by renaming it $GISBASE/oldtcltkgrass.

3. Copy the /tcltkgrass directory provided here to your $GISBASE (GRASS53 or GRASS5) directory. (It is possible that you may need to adjust permissions for the tcltk scrips in the $GISBASE/tcltkgrass/script directory to make sure that users have execute permissions--hopefully not necessary).

4. Copy the scripts in the directory /add2scripts to your $GISBASE/scripts directory. (It is possible that you may need to adjust permissions for the scripts to make sure users have execute permissions--hopefully not necessary).

5. Restart GRASS and tcltkgrass.

My compliments,
Andrea

On Saturday 17 April 2004 11:41, Sjors wrote:

Hi,

If downloaded the package with the new TclTk menu from Michael Barton at

http://www.public.asu.edu/~cmbarton/grass.htm
<http://www.public.asu.edu/~cmbarton/grass.htm&gt;

to play around with. I untarred it etc, but the ReadMe.txt is binary or
something, at least text viewers can't read it. How do I install this? Is
it updated to cvs yet? If so, if I update from cvs is it automatically
installed?

Greetings Sjors

_______________________________________________
grass5 mailing list
grass5@grass.itc.it
http://grass.itc.it/mailman/listinfo/grass5
   

4

Sjors wrote:

If downloaded the package with the new TclTk menu from Michael Barton at

http://www.public.asu.edu/~cmbarton/grass.htm <http://www.public.asu.edu/~cmbarton/grass.htm&gt;

to play around with. I untarred it etc, but the ReadMe.txt is binary
or something, at least text viewers can't read it.

The README.txt file appearst to be in "Microsoft Unicode" format:

  $ file README.txt
  README.txt: Little-endian UTF-16 Unicode English character data, with very long lines

It's essentially UTF-16, except with a "byte-order mark" (0xfeff) at
the start of the file.

You can convert it to ASCII with:

  dd if=README.txt bs=2 skip=1 | iconv -f UTF-16 -t US-ASCII

--
Glynn Clements <glynn.clements@virgin.net>

5

Hi Glynn,

This didn't work for me. Although I've succesfully installed the package I'm just trying to be precise.

The README.txt file appearst to be in "Microsoft Unicode" format:

$ file README.txt
README.txt: Little-endian UTF-16 Unicode English character data, with very long lines

It's essentially UTF-16, except with a "byte-order mark" (0xfeff) at
the start of the file.

You can convert it to ASCII with:

dd if=README.txt bs=2 skip=1 | iconv -f UTF-16 -t US-ASCII

I get this error message:

1660+0 records in
1660+0 records out
iconv: illegal input sequence at position 0

I've looked at the manpages of dd and iconv but could not get any wiser. If run with skip=0 the text is printed to standard out, ie in my case my xterm.

Greetings Sjors

6

On Sun, 18 Apr 2004, Sjors wrote:

Hi Glynn,

This didn't work for me. Although I've succesfully installed the package
I'm just trying to be precise.

>The README.txt file appearst to be in "Microsoft Unicode" format:
>
> $ file README.txt
> README.txt: Little-endian UTF-16 Unicode English character data, with very long lines
>
>It's essentially UTF-16, except with a "byte-order mark" (0xfeff) at
>the start of the file.
>
>You can convert it to ASCII with:
>
> dd if=README.txt bs=2 skip=1 | iconv -f UTF-16 -t US-ASCII

If you have 'recode' installed you can also do:
  cat README.txt | recode u2/..ascii/

rgds
Morten

7

Sorry about this. As far as I knew it was plain text. It is hard to tell as my computer can read many different text formats. I can run it through a different text editor to try to change this. However, I'm open to suggestions if you kinow of a systematic way to do this.

Michael Barton

On Saturday, April 17, 2004, at 10:29 AM, Glynn Clements wrote:

Sjors wrote:

If downloaded the package with the new TclTk menu from Michael Barton at

http://www.public.asu.edu/~cmbarton/grass.htm <http://www.public.asu.edu/~cmbarton/grass.htm&gt;

to play around with. I untarred it etc, but the ReadMe.txt is binary
or something, at least text viewers can't read it.

The README.txt file appearst to be in "Microsoft Unicode" format:

  $ file README.txt
  README.txt: Little-endian UTF-16 Unicode English character data, with very long lines

It's essentially UTF-16, except with a "byte-order mark" (0xfeff) at
the start of the file.

You can convert it to ASCII with:

  dd if=README.txt bs=2 skip=1 | iconv -f UTF-16 -t US-ASCII

--
Glynn Clements <glynn.clements@virgin.net>

____________________
C. Michael Barton, Professor
Department of Anthropology
PO Box 872402
Arizona State University
Tempe, AZ 85287-2402
USA

Phone: 480-965-6262
Fax: 480-965-7671

8

Sjors wrote:

This didn't work for me. Although I've succesfully installed the package
I'm just trying to be precise.

>The README.txt file appearst to be in "Microsoft Unicode" format:
>
> $ file README.txt
> README.txt: Little-endian UTF-16 Unicode English character data, with very long lines
>
>It's essentially UTF-16, except with a "byte-order mark" (0xfeff) at
>the start of the file.
>
>You can convert it to ASCII with:
>
> dd if=README.txt bs=2 skip=1 | iconv -f UTF-16 -t US-ASCII
>
>
>
I get this error message:

1660+0 records in
1660+0 records out
iconv: illegal input sequence at position 0

I've looked at the manpages of dd and iconv but could not get any wiser.
If run with skip=0 the text is printed to standard out, ie in my case my
xterm.

Hmm. We appear to be looking at different versions. I was looking at
the tcltkgrass4G57.tar.gz file (82580 bytes), posted to this list on
April 12th. In that, README.txt is 3650 bytes, which equates to 1824
records (not counting the one which is skipped).

That file has a byte-order mark at the beginning of the file:

  $ od -t x1z ~/README.txt | head -n 1
  0000000 fe ff 00 54 00 63 00 6c 00 54 00 6b 00 47 00 52 >...T.c.l.T.k.G.R<

while the remainder of the file is straight UTF-16 text.

iconv will fail if the input contains any characters which can't be
represented in the destination encoding. Try converting to UTF-8
instead, i.e.:

  iconv -f UTF-16 -t UTF-8 README.txt

--
Glynn Clements <glynn.clements@virgin.net>

9

Michael Barton wrote:

Sorry about this. As far as I knew it was plain text. It is hard to
tell as my computer can read many different text formats. I can run it
through a different text editor to try to change this. However, I'm
open to suggestions if you kinow of a systematic way to do this.

Doesn't the text editor have an option to select the output encoding?
Text should be in ASCII where possible, otherwise either ISO-8859-1 or
UTF-8 (I'm not sure which we should prefer although, AFAICT, all
existing occurrences of non-ASCII characters are in ISO-8859-1).

BTW, tcltkgrass/main/help.tcl contains a non-ASCII character:

      Using the select button, you can choose the specific module´s manpage.

That should probably be changed to the normal ASCII single quote
character.

--
Glynn Clements <glynn.clements@virgin.net>

10

Hi Glynn,

The last remark worked.

Glynn Clements wrote:

iconv will fail if the input contains any characters which can't be
represented in the destination encoding. Try converting to UTF-8
instead, i.e.:

iconv -f UTF-16 -t UTF-8 README.txt

Though I changed it somewhat to:

iconv -f UTF-16 -t UTF-8 README.txt > README

Now I can read file README. Thanks, not a big deal but we're somewhat wiser again.

Greetings Sjors