i18n strategy/experiences

Are there any best practices or experiences dealing with
internationalized sites? Most importantly with URL structure and
crawling effects (The DB i18n is not an issue at the moment).

In some sites I've worked I've added a switch language button which
changes the language but the URLs remain the same, relying in language
accept header and cookie set. This approach leaves me in doubt on
which language is my site crawled in.

Recently I saw that http://threadless.com is using subdomains for
internationalization, which seems like a reasonable approach according
to [1].

Does anybody have input on the matter?

[1] http://googlewebmastercentral.blogspot.com/2010/03/working-with-multi-regional-websites.html

--
You received this message because you are subscribed to the Google Groups "Django users" group.
To post to this group, send email to django-users@googlegroups.com.
To unsubscribe from this group, send email to django-users+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/django-users?hl=en.