view release on metacpan or  search on metacpan

lib/Leyland/Manual/Localization.pod  view on Meta::CPAN

negotiation and localize your application. Unless, of course, your application
is not multilingual, in which case you shouldn't care about localization.

=head1 THE PROBLEM WITH CPAN'S LOCALIZATION MODULES

CPAN has quite a few modules for data localization, the most common being
L<Locale::Maketext> and L<Gettext> (I think). The problem is that these
modules aren't really cut out for language negotiation. Their only purpose
seems to be to localize your application to the locale of the system on
which it is running, which is completely pointless when dealing with web
applications. These are not desktop applications we're letting end-users
install on their PCs with an interface written in their native language. We are talking about
web applications, probably running on virtual servers located thousands
of miles from your end-users. Who the hell cares about the locale of the
system?

When I write multilingual web applications, I want to let my end-users,
which are visitors of my application, decide on their preferred language.
This is why I created L<Locale::Wolowitz>, which is a very simple localization
system based on JSON. This is also the reason why, as opposed to logging
and view classes, Leyland only provides C<Locale::Wolowitz> as the choice