One other file with non-ASCII is doc/infrastructure.txt which contains grass-es La lista de correo de GRASS GIS en español
I would say that in infrastructure the English name would be more appropriate but anyway, the official name is the above and it is clear what does it mean, so I would keep the original. On Mon, Mar 3, 2014 at 11:19 AM, Pietro <[email protected]> wrote: > On Mon, Mar 3, 2014 at 3:59 AM, Hamish [email protected] wrote: > >> and lib/python/pygrass/functions.py … > > as for functions.py, hooking into G_legal_filename() would > > be best > > done in r59180. > > >> Personally, I would prefer it if source code was 7-bit clean. > > Me too. Not sure how to deal with non-ASCII chars in people’s names > though. > > I don’t see the reason to avoid source code in utf-8, at least on > python files, in particular when it is explicitly declare in the file > header like this (as in PEP 0263): > > # -*- coding: utf-8 -*- > > regards > > Pietro > > ps: sorry my previous email lost the format. > _______________________________________________ > grass-dev mailing list > [email protected] > http://lists.osgeo.org/mailman/listinfo/grass-dev >
_______________________________________________ grass-dev mailing list [email protected] http://lists.osgeo.org/mailman/listinfo/grass-dev
