On Mon, Mar 3, 2014 at 9:18 PM, Glynn Clements <[email protected]>wrote:
> Source code doesn't just have to work with the interpreter. It needs > to work with text editors, web browsers, revision-control systems, > printers, etc. Some of those understand coding cookies, some don't. > > The main problem with coding cookies is that software which > (explicitly or implicitly) converts between encodings typically leaves > the cookie unchanged. Which is why libraries such as chardet typically > treat coding cookies as little more than a hint or fallback. > What are coding cookies? My search brought me to Cookies and Coding event which is for sure great but apparently not related to current discussion. [1] http://www.meetup.com/Women-Who-Code-Austin/events/160041362/
_______________________________________________ grass-dev mailing list [email protected] http://lists.osgeo.org/mailman/listinfo/grass-dev
