[18:27:04] <nlh> I'm just writing up my thoughts on the design process - I wanted to include a section on internationalization and localization... but as this is more your area, i thought I'd ask you about it first
[18:28:06] <dstufft> right now it's using l20n.js which is a translation thing that actually understands HTML instead of trying to shoe horn gettext into it
[18:28:20] <dstufft> but beyond marking things for localization, I Haven't relaly used it much
[18:28:53] <nlh> ok... but the plan is to fully support it? As in, at some stage we'll be looking for translators?
[18:30:54] <dstufft> of particular interest (I think) to the design, is the fact that l20n.js supports "responsive localization"
[18:31:18] <dstufft> IOW, you can have different localization strings based on the size of the display
[18:32:06] <nlh> oh, that's cool. I'll read about it and make sure to include it
[18:32:34] <dstufft> so translators with languages that are longer can try to make shorter translations in situations where there isn 't room for a long chunk of text
[18:36:09] <dstufft> it does some other nice stuff (I think anyways) it doesn't use the english text (or whatever) as the "id" for the translation, so you can make adjusts to the english text (typo fixes, things that don't change the _meaning_ of the string) without forcing everyone to retranslate