Re: the translation utility- yep, it basically pulls up the ‘English’ version of the file into a form- and then gives you a field to type in the translation. When you’re done, you submit and it will basically write the file for you- rather than you going in and manually editing, say- lang.admin.php. Check the docs- they give a pretty good overview and some screen caps so you can get a feel for it. I’m monolingual, but played with it a wee bit just to see how it works. I’d say it’s definitely easier than manually editing things- hard to make a mistake.
Let’s see- I’m honestly not sure about the activation email. I took a look at the code- there’s some conditional bits going on, but it looks like in general, to send an email in a different language, EE pulls the language from the cookie for the logged in user. BUT- the cookie isn’t set at that point- because they really haven’t confirmed and logged in. So- it’s going to use the default language. Assuming I’m reading everything right.
On the other hand- since they just submitted their data- we should have access to the language they want to use, so there’s no theoretical reason we can’t send the email based on that. Of course- this would need another change to the confirmation message- as that would be sent prior to the cookie being set as well.
Hm- so the short answer is- I’m going to double check for you. I think it’s working as expected- but it’s not really working like you’d prefer it to. So it’s most likely going to be a good candidate for a feature request. (Or an extension- but seems to me, this could be included in the core as it does make sense.)
But let me double check- make sure my read of the code is correct.