Re: UTF-8 behavior ClojureScript (vs. Clojure)

2012-10-23 Thread Dave Sann
I notice this is fixed on clojurescript master. thanks guys. I can now delete my special edition clojure :) On Saturday, 20 October 2012 11:55:23 UTC+11, Chas Emerick wrote: > > I've filed a CLJS issue for this, and attached a patch: > > http://dev.clojure.org/jira/browse/CLJS-400 > > Thanks

Re: UTF-8 behavior ClojureScript (vs. Clojure)

2012-10-19 Thread Chas Emerick
I've filed a CLJS issue for this, and attached a patch: http://dev.clojure.org/jira/browse/CLJS-400 Thanks for keeping on this, Dave. :-) - Chas On Oct 19, 6:18 pm, Dave Sann wrote: > Chas, If your patch works without issue - this is probably better because > it will then work with existing ve

Re: UTF-8 behavior ClojureScript (vs. Clojure)

2012-10-19 Thread Dave Sann
Chas, If your patch works without issue - this is probably better because it will then work with existing versions of Clojure - clojurescript is changing faster and people a probably upgrading faster. I don't think it does any harm for Clojure to be able to read these chars but fixing the inte

Re: UTF-8 behavior ClojureScript (vs. Clojure)

2012-10-19 Thread Chas Emerick
On Oct 19, 2012, at 11:25 AM, David Nolen wrote: > On Fri, Oct 19, 2012 at 4:52 AM, Henrik Mohr wrote: > Still I hope someone can answer the question on why ClojureScript behaves > differently from Clojure. > > Output from Clojure: > user=> (str "ø") > "ø" > > Output from ClojureScript: > #_

Re: UTF-8 behavior ClojureScript (vs. Clojure)

2012-10-19 Thread David Nolen
On Fri, Oct 19, 2012 at 4:52 AM, Henrik Mohr wrote: > Still I hope someone can answer the question on why ClojureScript behaves > differently from Clojure. > > Output from Clojure: > user=> (str "ø") > *"ø"* > > Output from ClojureScript: > #_=> (str "ø") > *"\xF8"* > > Output from node.js: > >

Re: UTF-8 behavior ClojureScript (vs. Clojure)

2012-10-19 Thread Henrik Mohr
Still I hope someone can answer the question on why ClojureScript behaves differently from Clojure. Output from Clojure: user=> (str "ø") *"ø"* Output from ClojureScript: #_=> (str "ø") *"\xF8"* Output from node.js: > console.log ("ø"); *ø* Output from Chrome Console: console.log ("ø") *ø*

Re: UTF-8 behavior ClojureScript (vs. Clojure)

2012-10-18 Thread Henrik Mohr
Thanks for your reply Andy! BRgds, Henrik On Thursday, October 18, 2012 2:17:22 PM UTC+2, Andy Fingerhut wrote: > > Hopefully someone else can answer why there is a difference in the output > of the str function. I suspect in ClojureScript's case, it is simply the > default behavior to use \x

Re: UTF-8 behavior ClojureScript (vs. Clojure)

2012-10-18 Thread Andy Fingerhut
Hopefully someone else can answer why there is a difference in the output of the str function. I suspect in ClojureScript's case, it is simply the default behavior to use \x and two hex digits to display a character in a string with a code point in the range 128 through 255, inherited from Java

UTF-8 behavior ClojureScript (vs. Clojure)

2012-10-18 Thread Henrik Mohr
Hi there! I'm wondering why ClojureScript seems to handle international characters differently from Clojure. Simple example in Clojure (= my preferred behaviour): user=> (str "ø") "ø" The same example in ClojureScript: ClojureScript:cljs.user> #_=> (str 'ø') "\xF8'" Can anyone explain to me