Comments on: Worry Free JavaScript Internationalization (i18n)

By: Patricia Tapia

Patricia Tapia — Mon, 13 Oct 2008 17:38:52 +0000

You have explained it in a way no one else has. It makes it much easier to understand.

By: Ara Pehlivanian

Ara Pehlivanian — Thu, 24 Apr 2008 20:30:00 +0000

@AB: Very good point. I neglected to mention that this solution was implemented in a Yahoo! Widget which is a stand-alone app on the desktop. Otherwise, you’re absolutely right, it is a waste of bandwidth and should really be performed on the back-end. Let me go update the post.

By: AB

AB — Thu, 24 Apr 2008 20:12:19 +0000

Actually this does not seem like a nice solution at all. This approach would mean that for every “word” you want to i18n, you would have N-1 repetitions that do not add value, but wasted bandwidth.

Imagine internationalizing 100 words in 20 languages….

By: Ara Pehlivanian

Ara Pehlivanian — Tue, 15 Apr 2008 11:59:33 +0000

@Mathieu: Good idea!

@Luke: Thanks! :-)

By: Luke Maciak

Luke Maciak — Mon, 14 Apr 2008 18:41:58 +0000

Nice! I never really had to worry about internationalization, but this is really clever and elegant way of doing it! I like it. :)

By: Mathieu Gagnon

Mathieu Gagnon — Mon, 14 Apr 2008 17:29:08 +0000

… and then wrap the data access in a gettext like function. Then you have all the gettext tools available for extracting and localizing your text. jquery have plugins that follow this path, i dont know about yui.