I would much prefer something like Text.Shakespeare.I18n and shakespeare-i18n or shakespeare-translate over requiring an extra mental translation step to understand the name. Especially since this is under the hood, there is no reason to try to give it a themed name.<br>
<br><div class="gmail_quote">On Mon, Dec 12, 2011 at 5:01 AM, Michael Snoyman <span dir="ltr"><<a href="mailto:michael@snoyman.com">michael@snoyman.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div><div></div><div class="h5">On Sat, Dec 10, 2011 at 9:56 PM, Michael Snoyman <<a href="mailto:michael@snoyman.com">michael@snoyman.com</a>> wrote:<br>
> On Sat, Dec 10, 2011 at 8:31 PM, Jeremy Shaw <<a href="mailto:jeremy@n-heptane.com">jeremy@n-heptane.com</a>> wrote:<br>
>> On Sat, Dec 10, 2011 at 4:18 AM, Greg Weber <<a href="mailto:greg@gregweber.info">greg@gregweber.info</a>> wrote:<br>
>><br>
>>> Yesod guesses the user's locale from the request headers and allows it to be<br>
>>> overridden - this could easily be ported to Happstack.<br>
>><br>
>> Right. That sounds useful and easy to do.<br>
>><br>
>>> Yesod also directly<br>
>>> supports putting i18n into Hamlet templates, which I think can also be done<br>
>>> in Happstack. Yesod also provides a translator friendly veneer over Haskell<br>
>>> data types- I think this could also be ported to different settings like<br>
>>> Happstack.<br>
>><br>
>> We already have Hamlet support in Happstack. But, it seems like that<br>
>> is not enough? We also need some stuff that is in Yesod.Message, etc?<br>
>><br>
>> In my ignorance, it seems like there are three pieces:<br>
>><br>
>> 1. a little bit of framework/application specific code that<br>
>> detects/sets the language to use<br>
>><br>
>> 2. a bunch of framework independent code that deals with mapping<br>
>> data-types to translated strings<br>
>><br>
>> 3. some glue code that makes it easy to use #2 with a particular<br>
>> templating library<br>
>><br>
>> But, right now it seems that #2 is wrapped up in the yesod hierarchy<br>
>> even though it would be useful for any Haskell program that wants<br>
>> i18n? Or am I missing something?<br>
><br>
> Looks like you hit everything. You're correct, (2) is currently<br>
> included in the yesod-core package, but could easily be moved out to a<br>
> common, shared package. Any ideas on package/module name?<br>
><br>
> Michael<br>
<br>
</div></div>OK, it's a Shakespeare-like system, and it's for translations.<br>
<br>
Any objections to titus (and Text.Titus)?<br>
<font color="#888888"><br>
Michael<br>
</font></blockquote></div><br>