Yesod guesses the user's locale from the request headers and allows it to be overridden - this could easily be ported to Happstack. Yesod also directly supports putting i18n into Hamlet templates, which I think can also be done in Happstack. Yesod also provides a translator friendly veneer over Haskell data types- I think this could also be ported to different settings like Happstack.

On Fri, Dec 9, 2011 at 11:17 PM, Jeremy Shaw <jeremy@n-heptane.com> wrote:

Hello,

Happstack does not offer anything special for internationalization.
And, it probably shouldn't either. I18N is a more general problem, and
it seems like a more general solution is what you want.

That said, to the best of my knowledge, I18N and L10N are not a very
well explored areas of Haskell development.

This page suggestions some methods:

http://www.haskell.org/haskellwiki/Internationalization_of_Haskell_programs

What template system are you trying to use?

Also, if you have suggestions for how Happstack could make I18N
easier -- we'd be happy to hear them. But it seems like the problem is
largely orthogonal to Happstack itself?

One area where Happstack could be involved is if you wished to use
text encodings than UTF-8. That is mostly possible with Happstack
already. But you would need a pretty compelling reason to not just
stick with UTF-8 I think. (For example, interoperating with a legacy
system that does not use UTF-8).

- jeremy

On Fri, Dec 9, 2011 at 6:20 PM, Asafe Ribeiro <asafe.hai.kai@gmail.com> wrote:
> Does Happstack offer anything for internationalization ?
>
> _______________________________________________
> web-devel mailing list
> web-devel@haskell.org
> http://www.haskell.org/mailman/listinfo/web-devel

_______________________________________________
web-devel mailing list
web-devel@haskell.org
http://www.haskell.org/mailman/listinfo/web-devel