jI18N

#ji18n irc channel on freenode

2010-09-30T14:21:00.000-04:00

There is a #ji18n irc channel on freenode, if you would like to hop on and chat. I can't promise I'll be logged in all the time (contrary to popular belief, I do have a life), but I'll do my best.

irc://irc.freenode.net/#ji18n

Ohloh

2010-09-21T14:35:00.003-04:00

The Ohloh page for jI18N has been updated to reflect the change in project hosting from SourceForge to Google Code.

https://www.ohloh.net/p/ji18n

Twitter

2010-09-20T13:14:00.006-04:00

jI18N is now on Twitter!
http://twitter.com/ji18n

Blog URL Change

2010-09-16T15:06:00.002-04:00

The new blog URL is http://blog.ji18n.org. The old URL of http://ji18n.blogspot.com will forward to it automagically.

I'm still using Google's Blogger service, however I created a CNAME record so the URL is "cooler". Yes, I'm a geek.

Google Code

2010-09-14T15:55:00.007-04:00

Much time has passed, and things seem to have settled a bit in my life. As a result, I will be resuming work on the project. However, I am aiming to change the project hosting provider from SourceForge to Google Code. I have become quite an avid user of Google services (including owning an Android phone), and have never failed to be impressed with their creativity, scalability and stability. Nothing against SourceForge, of course. They serve the open source community very well. It's just that I believe Google Code is a better fit for jI18N moving forward. I will post again once that move has been completed. At that point, changes previously noted can finally start.

Facebook

2009-04-23T18:06:00.010-04:00

The jI18N blog is now on Facebook via the NetworkedBlogs app:
http://apps.facebook.com/blognetworks/blog/ji18n/

Project Status

2009-04-23T15:22:00.002-04:00

jI18N is not dead. It has, however, been stalled for several months. This is primarily due to lack of development time/resources, however that has changed recently. Currently the project is getting a design overhaul. The three major areas of focus are:

Clear distinction between API, SPI and IMPL layers. Whereas the design of jI18N has always been interface-driven, it makes sense to split up the library into separate jars so an application developer only needs to bring in minimal build dependencies, and knows what can be guaranteed him to be stable from an API contract basis.
Modular deployments. There are so many component and service models out there, each with their own pros and cons. For example, I've been taking a hard look at OSGi lately, but I don't want to tie jI18N to it. One thing that's great about JBoss' Microcontainer is that it was built to support multiple component models, and via annotation or configuration, one can "layer on" enterprise services like security and transactionality, define dependencies and lifecycle, etc. jI18N will never be tied directly to JBoss, but there are lessons to be learned there, and jI18N should play nice.
A GWT-based management console. Remember that jI18N is not only meant for internationalizing your applications, but also to provide a tool (usable by non-developers) for managing localization content of various types.

Watch this space for updates.

Blog Purpose

2009-04-13T18:55:00.001-04:00

Welcome! The purpose of this blog is to provide a place to post interesting notes about the jI18N project. Comments are welcome, although moderated. ;)