Nope. Try it yourself. Put a UTF-8 literal in an imported source file, and then try to use Unicode literals for the character. It interprets the UTF-8 wrong. I'm quite sure this is a bug in our importer script, treating everything as UTF-16.
On Mon, Dec 10, 2012 at 2:11 PM, Colin Walters <[email protected]> wrote: > On Mon, 2012-12-10 at 19:07 +0000, Debarshi Ray wrote: > > > TL;DR: It's 2012. The compiler understands UTF-8 and defaults to it. > > > Use it :) > > > > As I discovered recently, gjs does not like Unicode characters in string > > literals. > > You are likely referring to: > https://bugzilla.gnome.org/show_bug.cgi?id=680730 > > Which has nothing actually to do with string literals, or the encoding > of the source file, but was about how gjs treats any string when passed > to a function which expects a byte array. > > And note, the semantics changed for 3.8. > > > _______________________________________________ > desktop-devel-list mailing list > [email protected] > https://mail.gnome.org/mailman/listinfo/desktop-devel-list > -- Jasper
_______________________________________________ desktop-devel-list mailing list [email protected] https://mail.gnome.org/mailman/listinfo/desktop-devel-list
