The offending line is a reference in the comment section: http://trac.osgeo.org/grass/browser/grass/trunk/imagery/i.atcorr/computations.cpp#L1365
I browsed SUBMITTING file and didn't find any rules about source encoding. As a supporter of Unicode everywhere, I would suggest to add a requirement for source files to be in UTF-8. Upside - most of files already are in UTF-8. Thus only files with symbols outside of latin1 would be affected. Just my 0.02, Maris. 2014-02-27 12:22 GMT+02:00 Alessandro Samuel Rosa <[email protected]>: > Dear Grass developers, > > I tried to open the file "computations.cpp" of module i.atcorr in gedit and > got the following error message: > > ------- > There was a problem opening the file “computations.cpp”. > The file you opened has some invalid characters. If you continue editing this > file you could corrupt this document. > You can also choose another character encoding and try again. > Character Encoding: Current Locale (UTF-8). > ------- > > Then I tried opening the file using another character encoding (Western > (ISO-8859-15)) and the file opened without problems. I wonder if the > different character encoding of this file (all other files opened using > UTF-8) could cause errors when running the module. > > Regards, > > > -- > > Alessandro Samuel-Rosa > --- > PhD Candidate Graduate School in Agronomy - Soil Science > Federal Rural University of Rio de Janeiro > Seropédica, Rio de Janeiro, Brazil > --- > Guest Researcher ISRIC - World Soil Information > Wageningen, the Netherlands [email protected] > --- > Homepage: soil-scientist.net Skype: alessandrosamuel > _______________________________________________ > 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
