[GRASS-dev] [GRASS GIS] #2136: Create standard options for map or file base name (prefix)

[GRASS GIS]

#2136: Create standard options for map or file base name (prefix)
-----------------------------------------+----------------------------------
 Reporter:  wenzeslaus                   |       Owner:  grass-dev@…              
     Type:  defect                       |      Status:  new                      
 Priority:  normal                       |   Milestone:  7.0.0                    
Component:  Parser                       |     Version:  svn-releasebranch64      
 Keywords:  base name, prefix, basename  |    Platform:  All                      
      Cpu:  All                          |  
-----------------------------------------+----------------------------------

Comment(by glynn):

 Replying to [comment:12 wenzeslaus]:

 > > Yes, I know... But we can always change what is considered legal and
 what is not...

 Sort of. We can't change which characters exist in various encodings, nor
 can we change which characters are legal (at the OS level) in a filename.

 > I would not risk anything what is non-ASCII. Moreover, it might be a
 good idea to avoid also all characters which has some meaning or must be
 escaped/quoted in various command lines or SQL. These include
 `(){}[]:.|$!&*`.

 Realistically, "characters which has some meaning" is anything except
 alphanumerics and underscore. Everything else meaning to something or
 another. Actually, even an underscore isn't 100% safe.

 Even a dash (minus, ASCII 45 = 0x2d) creates issues for r.mapcalc: foo-bar
 is parsed as the subtraction of bar from foo; if you want to use a map
 named foo-bar (which is valid as per G_legal_filename), the name has to be
 quoted in the r.mapcalc expression).

-- 
Ticket URL: <http://trac.osgeo.org/grass/ticket/2136#comment:15>
GRASS GIS <http://grass.osgeo.org>