Opened 5 years ago

Closed 5 years ago

#2396 closed enhancement (wontfix)

proposal to rename v.in.ascii/v.out.ascii to v.in.text/v.out.text (or similar)

Reported by: mlennert Owned by: grass-dev@…
Priority: blocker Milestone: 7.0.0
Component: Vector Version: svn-releasebranch70
Keywords: ascii, API change Cc:
CPU: Unspecified Platform: Unspecified

Description

I have the feeling that less and less people actually know what ASCII stands for (at least this is the case with my students). I propose to rename v.in.ascii/v.out.ascii to use a more generic name such as v.in.text/v.out.text (or similar).

Change History (7)

comment:1 Changed 5 years ago by wenzeslaus

Keywords: API change added
Priority: normalblocker

I think you made a good point.

I'm not sure what is our policy about this but since it is an API change, this is in fact a blocker unless we provide the other names as alternatives. (We can of course resolve blocker as won't fix or move milestone to futuristic 8.0.0.)

Note that there are also raster modules with "ascii" in their names. And also the format is called "GRASS ASCII vector format".

comment:2 Changed 5 years ago by hamish

meh, I'm not in favor of this. ASCII is the one universal format which has survived for decades and is exactly known and described. "text" is... um, a Word document? a pdf? an image scan of observer logs? who knows..?

IMNSHO if people don't know what ASCII is, then they should learn. This is technical software, a minimum level is computer literacy is going to be required. And we can help teach them through good tooltips, menu presentation/organization, and documentation, and they will be better future researchers for it.

2c, Hamish

comment:3 in reply to:  2 ; Changed 5 years ago by mlennert

Replying to hamish:

meh, I'm not in favor of this. ASCII is the one universal format which has survived for decades and is exactly known and described. "text" is... um, a Word document? a pdf? an image scan of observer logs? who knows..?

One could argue, though, that v.in.ascii is the wrong (and thhus confusing) name since you can import files which are in different encodings than ASCII. But I agree that 'text' is not necessarily clearer. Maybe v.in.delimitedtext ?

Moritz

comment:4 in reply to:  3 ; Changed 5 years ago by martinl

Replying to mlennert:

One could argue, though, that v.in.ascii is the wrong (and thhus confusing) name since you can import files which are in different encodings than ASCII. But I agree that 'text' is not necessarily clearer. Maybe v.in.delimitedtext ?

it will not help to make it more clear. The module also import vector data in GRASS ASCII (text) format which is not definitely a delimited text.

comment:5 in reply to:  4 ; Changed 5 years ago by mlennert

Replying to martinl:

Replying to mlennert:

One could argue, though, that v.in.ascii is the wrong (and thhus confusing) name since you can import files which are in different encodings than ASCII. But I agree that 'text' is not necessarily clearer. Maybe v.in.delimitedtext ?

it will not help to make it more clear. The module also import vector data in GRASS ASCII (text) format which is not definitely a delimited text.

Agreed. Don't know if there is an easy "solution" to this. Maybe we should just live with our historical heritage and keep 'ascii'... Don't think that this should be a blocker.

Moritz

comment:6 in reply to:  5 ; Changed 5 years ago by martinl

Replying to mlennert:

Agreed. Don't know if there is an easy "solution" to this. Maybe we should just live with our historical heritage and keep 'ascii'... Don't think that this should be a blocker.

it's blocker in the sense that it must be solved before we release GRASS 7.0.0. So we have to options:

  • to find better name for modules
  • or to close this ticket as wontfix

Personally I am fine with current names.

comment:7 in reply to:  6 Changed 5 years ago by mlennert

Resolution: wontfix
Status: newclosed

Replying to martinl:

Replying to mlennert:

Agreed. Don't know if there is an easy "solution" to this. Maybe we should just live with our historical heritage and keep 'ascii'... Don't think that this should be a blocker.

it's blocker in the sense that it must be solved before we release GRASS 7.0.0. So we have to options:

  • to find better name for modules
  • or to close this ticket as wontfix

Personally I am fine with current names.

As Hamish said: we have more important things to do than this, so I'm closing it as wontfix as I don't see an easy consensus on a new name.

Moritz

Note: See TracTickets for help on using tickets.