On Tue, Jul 31, 2012 at 9:09 AM, Michael Truog <mjtr...@gmail.com> wrote:IMO this doesn't solve the problem, and only confuses the issue;
>>> The solution with the way things are currently, is just to use modelines (within the first 3 lines of the file) which are supported in your favorite editor, vi or emacs:
>>> % -*- coding: utf-8; Mode: erlang; tab-width: 4; c-basic-offset: 4; indent-tabs-mode: nil -*-
>>> % ex: set softtabstop=4 tabstop=4 shiftwidth=4 expandtab fileencoding=utf-8:
>> Shouldn't that modeline read:
>> Since the compiler assumes source files are in Latin 1
> I think the point was to use utf8 in the source file, thus the utf8 in the modeline. The encoding() would be necessary for various erlang names (like functions, variables, etc.) to be in utf8, but the modeline could help keep list data as utf8.
consider the following:
If the list data was kept as UTF-8 then the output of the second
The above of course depends on whether you view strings as lists of
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.