[GRASS-dev] [GRASS GIS] #1288: g.dirseps breaks non-latin file/folder names on Windows

GRASS GIS trac at osgeo.org
Sat Feb 15 19:41:58 PST 2014


#1288: g.dirseps breaks non-latin file/folder names on Windows
--------------------------------------+-------------------------------------
 Reporter:  marisn                    |       Owner:  grass-dev@…              
     Type:  defect                    |      Status:  new                      
 Priority:  critical                  |   Milestone:  7.0.0                    
Component:  Default                   |     Version:  6.4.1 RCs                
 Keywords:  wingrass, i18n, encoding  |    Platform:  MSWindows Vista          
      Cpu:  Unspecified               |  
--------------------------------------+-------------------------------------
Changes (by wenzeslaus):

  * keywords:  wingrass => wingrass, i18n, encoding


Comment:

 I'm not sure if it makes sense to keep this issue open. It is hard to say
 where all/some encoding issues may appear and then go and fix them. And
 new code is being added, so if this issue is kept open ''to remember'', it
 should be open forever (which does not make sense).

 Of course we should keep in mind internationalization issues which are
 especially occurring on MS Windows. However, I would rather keep tract of
 individual issues rather then having some general ticket just as a
 reminder.

 Most of the related tickets hopefully captured by these queries:
  *
 [query:?status=assigned&status=new&status=reopened&summary=~localization&summary=~internationalization&summary=~i18n&summary=~L10n&summary=~locale&summary=~locales&summary=~translations&summary=~encoding&order=priority&col=id&col=summary&col=keywords&col=type&col=priority
 summary]
  *
 [query:?status=assigned&status=new&status=reopened&description=~localization&description=~internationalization&description=~i18n&description=~L10n&description=~locale&description=~locales&description=~translations&description=~encoding&order=priority&col=id&col=summary&col=keywords&col=type&col=priority
 description]
  *
 [query:?status=assigned&status=new&status=reopened&keywords=~localization&keywords=~internationalization&keywords=~i18n&keywords=~L10n&keywords=~locale&keywords=~locales&keywords=~translations&keywords=~encoding&order=priority&col=id&col=summary&col=keywords&col=type&col=priority
 keywords]

 Done using wiki:TracQuery:
 {{{
  *
 [query:?status=assigned&status=new&status=reopened&summary=~localization&summary=~internationalization&summary=~i18n&summary=~L10n&summary=~locale&summary=~locales&summary=~translations&summary=~encoding&order=priority&col=id&col=summary&col=keywords&col=type&col=priority
 summary]
  *
 [query:?status=assigned&status=new&status=reopened&description=~localization&description=~internationalization&description=~i18n&description=~L10n&description=~locale&description=~locales&description=~translations&description=~encoding&order=priority&col=id&col=summary&col=keywords&col=type&col=priority
 description]
  *
 [query:?status=assigned&status=new&status=reopened&keywords=~localization&keywords=~internationalization&keywords=~i18n&keywords=~L10n&keywords=~locale&keywords=~locales&keywords=~translations&keywords=~encoding&order=priority&col=id&col=summary&col=keywords&col=type&col=priority
 keywords]
 }}}

 Originally reported issue seems to be resolved as ''wontfix'' according to
 comment:2, so I suggest to close this issue accordingly. But to test this
 (and perhaps #995) with GRASS 6.4.svn would not harm, probably, since it
 was reported 3 years ago for GRASS 6.4.1 RC.

-- 
Ticket URL: <https://trac.osgeo.org/grass/ticket/1288#comment:3>
GRASS GIS <http://grass.osgeo.org>



More information about the grass-dev mailing list