hoodwink.d enhanced


Yay, Matz is on the Cusp of Unveiling Ruby's Unicode Support! #

by why in cult

matz: You will have chars and each_chars along with other M17N functionality. I wanted merge it before RubyConf (to show Tim Bray working code), but regretfully failed. ;-<

He goes on to explain how having symbols inherit from strings is part of that master plan, to ensure symbols know their encoding and everything jives nation-to-nation. Heal the world, make it a better place and all that. (Also see here in the comments for a big list of pros + cons.)

said on 16 Oct 2006 at 10:13

the “goes on” link isn’t the right one, I don’t think…

said on 16 Oct 2006 at 10:24

Oh my…

said on 16 Oct 2006 at 10:35

Yeah, was a digit shy. Thanks Platte.

said on 16 Oct 2006 at 11:13

oh great whys one. what is the latest on ruby 2.0? is next xmas still likely or might it be sooner. are the unicode issues now resolved? please tell us all you know. to save annoying folk like me hassling you – why not set up a section on your site entitled: “Ruby 2.0 – A development summary”

It would bring much joy too many.

said on 16 Oct 2006 at 11:58

the enquirer: Mauricio Fernandez already does a great job of this http://www.eigenclass.org/hiki.rb?Changes+in+Ruby+1.9

said on 16 Oct 2006 at 12:05

each_chars or each_char? I hope that was just Matz’s Engrish shining through.

Perhaps we should have a long discussion on ruby-core about the method name. I vote for:


said on 16 Oct 2006 at 13:01

Well, M17N by ISO 2022 methods is so 1980s. Japan seems to be the last country in the world where some people still believe that non-Unicode character sets have any place outside legacy conversion routines. Oh well…

said on 16 Oct 2006 at 15:36

mrunicode: And their language is still the problem Unicode doesn’t completely solve. Think the two are related? ;)

M17N support is going to include Unicode and more folks. Matz is trying to address the problem for all of us and I fully believe he’s on the right path.

said on 16 Oct 2006 at 18:06

JEG2 : What’s the problem with Japanese and Unicode?

said on 16 Oct 2006 at 18:22

Google to the rescue! Unicode In Japan. It looks like the main problems are name kanji, historical characters, and mixed Japanese/Chinese text.

said on 16 Oct 2006 at 18:47

The best treatment of the problem I’ve seen is http://www.jbrowse.com/text/unij.html

said on 17 Oct 2006 at 04:08

larios, mixing Japanese and Chinese text can be solved by properly marking up which piece is in which language so the application rendering the text can choose the proper font.

Firefox gets this right as can be seen in the example on http://en.wikipedia.org/wiki/Han_unification

said on 17 Oct 2006 at 07:34

_why, how about stopping your mumble and fixing Syck to emit proper UTF -8? I’d say it’s gawddamn time.

said on 17 Oct 2006 at 07:35

That is unless you are completely evil and think that I enjoy reading my language in Base64

11 Jul 2010 at 21:02

* do fancy stuff in your comment.