On Fri, Mar 13, 2009 at 8:46 AM, max3000 <maxime.lar...@gmail.com> wrote:
>
> Any news on this item? Does what I'm saying make sense?
>
> I understand most people who use clojure are probably English-speaking
> and couldn't care less about internationalization, but this has to be
> addressed if clojure is to get any semblance of semi-mainstream
> adoption. In fact, one of the reasons I chose clojure myself is
> because internationalization is a solved problem in Java (and hence I
> though in clojure as well). If the perception is that the problem is
> "limited" to Windows, well, that's 90% of the deployed PCs out there.
>
> Since the fix seems so trivial and requires changes in only about 5
> lines of code, I'm not sure what prevents this from being fixed. At
> least, is there a clojure bug tracking site where I could add this
> issue?
What happens if you do this:
;; untested
(binding [*in* (new LineNumberingPushbackReader (new InputStreamReader
System/in))
*out* (new OutputStreamWriter System/out)]
(your-code-here))
--
Michael Wood <esiot...@gmail.com>
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Clojure" group.
To post to this group, send email to clojure@googlegroups.com
To unsubscribe from this group, send email to
clojure+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/clojure?hl=en
-~----------~----~----~----~------~----~------~--~---
