[GRASS5] Re: [GRASSLIST:6003] Re: moving layers from one machine to another

Hamish wrote:

Hamish, will you try G_getl2 in v.in.ascii?

Sure, can do. Won't be for 24-72 hours though.

do you want this applied pre-6.1?

If v.in.ascii now works with input from all platforms wait for 6.1,
if it does not and it does with G_getl2, apply that for 6.0

There are many other modules that take ascii input (ps.map comes to
mind), I guess they can wait for 6.0+ though. v.in.ascii support for
'\r' is important as Excel for OSX makes .csv files with '\r', Internet
Explorer for OSX translates ascii downloads as '\r' (web mail seems to
be a big way of transfering files UNIX/PC -> Mac) .. All the Apple
software saves in unix format or leaves as-is AFAICT.

there have been many changes since 6beta2, will there be a 6beta3?

There should be only bugfixes. I don't want to get into endless beta loop.

Radim

Perhaps a give it a week & rename 6beta3 as 6.0 if all is stable?
if that, then pain not having a 6.0 tag then in CVS? shrug

Personally, I am still using 6beta2 and haven't tested most of the CVS
changes/fixes since.

Also I am anxious to get the v.in.e00 'rm -f *' bug that was in 6beta2
out of circulation ASAP.

>>Hamish, will you try G_getl2 in v.in.ascii?
>
> do you want this applied pre-6.1?

If v.in.ascii now works with input from all platforms wait for 6.1,
if it does not and it does with G_getl2, apply that for 6.0

Right now it works 98% of the time. Mac/OS9 input doesn't work, but
should fail with an error message the user will understand. I'd
rather not risk having a broken v.in.ascii for 6.0.0 so I will leave
this for 6.1.

> there have been many changes since 6beta2, will there be a 6beta3?

There should be only bugfixes. I don't want to get into endless beta
loop.

I was worried about the case that one of the bugfixes has introduced a
new bug which will not be found until after the release because everyone
is testing the pre-bugfix version. .. but you are doing the work so it
is totally up to you of course.

Hamish