I wouldn't say I18Nv2's approach is the better one, because it depends on
the internationalization capabilities of the underlying operating system,
but it's simpler and faster - though it is in need of user contributed
date and time formatting rules.

I18N's translation functionality was dropped in favour of the new and
shiny
Translation2.

I18Nv2 still provides an HTTP
negotiator to reveal the users preferred language/locale and charset.