On Sat, 29 Jan 2011, Faré wrote:
On 29 January 2011 11:18, Cyrus Harmon <[email protected]> wrote:
And, even worse, how do we asdf:load-op .asd files that contain non-ascii
characters? (besides changing the locale, which, while it will work for a
single .asd file, doesn't address the issue of how to load multiple ASDF
systems from different locales).
Probably one of the below makes sense:
...
4- we embrace Unicode, and say it's UTF-8 by default wherever
supported, falling back to iso-8859-1 or whatever on implementations
that don't have it.
I'd vote for 4.
I'd agree.
There are very few cases which justify using an encoding other than utf-8
(or occasionally utf-16) for source code. None should be relevant for ASD
files.
Establishing one standard with fallbacks for less-capable implementations
is better for portability than trying to accommodate every encoding.
- Daniel
_______________________________________________
asdf-devel mailing list
[email protected]
http://common-lisp.net/cgi-bin/mailman/listinfo/asdf-devel
