|
Subject: Re: A character encoding problem when using scala interactive interpreter Newsgroups: gmane.comp.lang.scala Date: 2008-06-08 00:51:49 GMT (23 weeks, 5 days, 17 hours and 50 minutes ago) 2008/6/8 David MacIver <david.maciver <at> gmail.com>: > On Sun, Jun 8, 2008 at 1:19 AM, Kota Mizushima <mizukota <at> gmail.com> wrote: >>> Have you tried -Dfile.encoding=UTF8? IIRC it overrides the platform default >>> encoding. >>> >>> -0xe1a >> >> Thanks. I tried -Dfile.encoding=UTF8, but the same problem happened. >> While I searched the reason, I found following page. >> >> http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=4163515 >> >> Quoting from that page, 'The "file.encoding" property is not required >> by the J2SE platform specification; it's an internal detail of Sun's >> implementations and should not be examined or modified by user code.' >> > > This is a known bug in the interpreter. See > http://lampsvn.epfl.ch/trac/scala/ticket/992 Thanks for the pointer to the trac ticket that I didn't know. However, I think that ":load" command should load files not in the platform default encoding but in the encoding specified by -encoding(or UTF-8 if not specified) to be consistent with scalac in the first place. -- Kota Mizushima e-mail: mizukota <at> gmail.com |
|
|